I experience reoccurring incidents of fontd eating up all the process power. What could be the cause of this and how do I make it behave again?


sudo atsutil databases -remove; atsutil server -shutdown

From 50% cpu usage to 1%

Source: http://icicity.com/2014/02/13/high-cpu-usage-caused-by-fontd-on-os-x

  • 1
    This should be followed by a restart. – benwiggy Sep 15 '20 at 11:36

You might want to check for defective fonts. I believe there are apps that can help with that. "Doctoring" is the term used often


Do the following and place your removed fonts back to the "font" folder of your library folder.

Restore fonts that came with your Mac using Font Book You can restore the fonts that were originally included with your Mac. This may be useful if you’re having issues with Font Book. Restoring the standard fonts moves any fonts you’ve installed into a separate folder, which makes them unavailable to use in apps.

In the Font Book app on your Mac, choose File > Restore Standard Fonts.

Any fonts you’ve installed are placed in /Library/Fonts (Removed) or in ~/Library/Fonts (Removed). To install those fonts again, just reinstall them.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .