What is fontworker, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
fontworker is the macOS helper that registers and validates fonts, checking font files for problems before they are used. It is busy when you install fonts, when Font Book validates them, and when many fonts change at once, and it is idle the rest of the time. Removing damaged and duplicate fonts keeps it from repeating work.
fontworker at a glance
| fontworker | |
|---|---|
| Made by | Apple (part of macOS, fonts) |
| Type | Launch agent |
| Location | /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Support/fontworker |
| Runs as | your user |
| Started by | launchd job com.apple.FontWorker |
| Can you quit it? | Yes. launchd starts it again when fonts need checking. |
What is fontworker?
Its man page describes fontworker as the system font registration and validation daemon, with no configuration options. Font Book checks fonts for errors when you install them and lists any problems it finds, and you can validate installed fonts on demand; fontworker is the background process that does this kind of checking for the system.
launchd starts it for your user through the com.apple.FontWorker job when needed. It works alongside fontd, which keeps the record of installed fonts.
Is fontworker safe?
Yes. fontworker is part of macOS, signed by Apple, and lives inside the ATS framework on the read-only system volume. It runs as your user.
Why does fontworker use so much CPU and disk?
- Installing fonts. Each new font is checked, so installing a large family or a whole collection keeps fontworker busy for a while.
- Validating fonts in Font Book. Validating many fonts at once reads and checks every file.
- Damaged fonts. Font files with errors take longer to check and can be checked again when apps try to use them.
- Reading font files. Validation reads each font file, which shows as disk reads with large collections.
How much CPU is normal for fontworker?
Absent or near 0% CPU most of the time. A burst while fonts are installed or validated is expected.
How do you stop fontworker from using so much CPU?
- Install fonts in smaller batches. Installing a few families at a time spreads the checking out instead of one long burst.
- Remove fonts that fail validation. In Font Book, validate your fonts and remove ones marked with a red icon. Yellow icons are warnings worth reviewing.
- Resolve duplicates. In Font Book choose File > Resolve Duplicates so the same font is not checked and registered twice.
When should you worry about fontworker?
Look closer if fontworker keeps running at high CPU with no fonts being installed. A damaged font that apps keep loading is the usual cause; validate fonts in Font Book.
It should run only from the ATS framework path above.
How do you check fontworker in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type fontworker in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every fontworker process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). fs_usage prints each file it reads or writes until you press Control-C; it needs an administrator password.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'fontworker' | grep -v grep
sudo fs_usage -w -f filesys fontworker
How can Thrum help with fontworker?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when fontworker is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click fontworker in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions about fontworker
What is the difference between fontd and fontworker?
fontd makes installed fonts available to apps. fontworker registers and validates font files.
Is fontworker the same as Font Book?
No. Font Book is the app you use to manage fonts; fontworker is a background helper of the system.
Sources
- fontworker(8) man page: run man fontworker in Terminal
- Apple Support: Install and validate fonts in Font Book on Mac