What is fontd, and why is it using so much CPU?
Last reviewed: 19 November 2026. Path, account, launchd job, man page and font cache folder checked on macOS 26.3.1.
fontd is the macOS daemon that makes fonts available to the system and apps, keeping track of every installed font. It uses CPU when fonts are installed, removed, activated or deactivated, and when it rebuilds its records of them, then goes idle. Large font collections and font managers that switch fonts often are the usual reasons it stays busy.
fontd at a glance
| fontd | |
|---|---|
| Made by | Apple (part of macOS, fonts) |
| Type | Launch agent |
| Location | /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/fontd |
| Runs as | your user |
| Started by | launchd job com.apple.xtyped |
| Can you quit it? | Yes. launchd starts it again when an app needs fonts. |
What is fontd?
Its man page describes fontd as the system font registration manager, a daemon that makes fonts available to the system, with no configuration options. When an app lists fonts or draws text in a font, it relies on fontd's record of which fonts exist and where they are.
launchd starts it for your user from /System/Library/LaunchAgents/com.apple.fontd.useragent.plist, whose job label is com.apple.xtyped. Your user's font records are kept in a com.apple.FontRegistry folder inside the folder that getconf DARWIN_USER_CACHE_DIR prints. Checking new font files is the job of its helper, fontworker.
Is fontd safe?
Yes. fontd is part of macOS, signed by Apple, and lives inside the ATS framework in /System/Library/Frameworks/ApplicationServices.framework on the read-only system volume. It runs as your user.
Why does fontd use so much CPU and memory?
- Installing or removing fonts. Adding or removing fonts, especially hundreds at once, makes fontd register each one and update its records.
- Font managers. Font management apps that activate and deactivate fonts automatically, for example as documents open, make fontd re-register them each time.
- Very large font collections. Thousands of installed fonts mean larger records to keep, and more work whenever an app asks for the full list.
- Damaged or duplicate fonts. A damaged font file, or many duplicate copies of the same font, can make registration slow or repeat.
How much CPU is normal for fontd?
Near 0% CPU most of the time. Bursts after installing fonts, when a font manager changes the active fonts, or when an app with a font menu starts are typical.
Memory use is typically in the tens of megabytes and grows with the number of installed fonts.
How do you stop fontd from using so much CPU?
- Let it finish after installing fonts. After adding a large set of fonts, give fontd a few minutes before judging its CPU use.
- Resolve duplicates. Open Font Book and choose File > Resolve Duplicates to deal with fonts installed more than once.
- Validate your fonts. In Font Book, select your fonts and validate them. Remove fonts marked with a red icon, which failed validation.
- Remove or deactivate fonts you do not use. In Font Book, remove or deactivate fonts you never use. Fewer active fonts means less for fontd to track.
- Check your font manager's settings. If you use a font manager, turn off automatic activation you do not need, or update the app.
When should you worry about fontd?
Look closer if fontd stays above about 20% CPU for many minutes with no fonts being installed and no font manager running. A damaged font is the likely cause; validating fonts in Font Book finds it.
It should run only from the ATS framework path above.
How do you check fontd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type fontd in the search field. The CPU tab shows its % CPU. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every fontd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'fontd' | grep -v grep
How can Thrum help with fontd?
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 fontd 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 fontd 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 fontd
Why does fontd use CPU when I open certain apps?
Apps with large font menus ask for the full list of fonts when they start, which fontd provides.
Can I delete fontd's cache?
It is better not to delete system cache folders by hand. Resolving duplicates and removing damaged fonts in Font Book usually fixes font problems.
Sources
- fontd(8) man page: run man fontd in Terminal
- Apple Support: Install and validate fonts in Font Book on Mac
- Apple Support: Remove, deactivate, or activate fonts in Font Book