Clear Font Cache on Mac Without Resetting Every Font
Missing letters or a font that never appears in an app do not, by themselves, prove that the Mac's font cache is damaged. Start with the affected font and document, then change one thing at a time. Keep the original font installer and a copy of the document before removing fonts or changing activation.
Identify the smallest failing case
Write down the font family, the affected characters and the app. Try those characters in another document and another app before changing system files. Use the results to decide what to investigate, not as a diagnosis by themselves.
| Observation | Next check |
|---|---|
| One document looks wrong | Check its intended font with its author |
| One app cannot find a font | Check that app's font instructions |
| The same family fails in several apps | Check its installation and validation |
Keep a screenshot or a short sample of the affected text. Retest that same sample after each change rather than judging a different document.
Validate the font and review duplicates
Apple's Font Book guidance documents font validation and resolving duplicates. Start with the affected family, review its validation results, and inspect duplicate copies before choosing which one to keep. Do not remove every font with a similar name.
Keep a usable original before removing a copy. If a font manager supplies the font, record its activation state and consult that manager's instructions before changing the same family in Font Book. Avoid making changes in both tools during the same test, so you can tell which change affected the result.
Try Safe Mode, then test after a normal restart
Apple says Safe Mode clears some system caches, including font caches, and recreates them as needed. It also prevents fonts not installed by macOS from loading. A missing custom font in Safe Mode is therefore not a useful test of whether that font has been repaired.
Save work, follow Apple's instructions for your Mac, then restart normally. The startup procedure differs between Apple silicon and Intel Macs; the Safe Mode guide covers that distinction. Test the original document again after normal startup and restore the font manager's intended activation state before comparing the result.
If the fault returns only after normal startup, investigate the software and activation that return with it. A change in Safe Mode is a clue, not proof that a cache alone caused the problem.
Leave manual database removal out of the first pass
Do not start by copying an old atsutil command or deleting system cache
directories. This guide does not prescribe either operation. Apple's linked
workflow gives you validation, duplicate review and Safe Mode without choosing
undocumented files to delete.
If those checks do not help, send the font vendor or app developer the same text sample, validation result and normal-startup result. Keep the installed font and your originals until there is a specific next step. For a wider maintenance question, see maintenance without broad resets.
Where Mole Fits
Mole Mac's Optimize tasks do not clear font registration databases. That step was removed so a maintenance run would not disturb font-manager registration state. Optimize is not a replacement for Font Book validation or duplicate review; use the font-specific workflow above for this problem.
FAQ
Does missing text prove the font cache is corrupt?
No. Record the exact family and characters, compare the same sample in another document or app, and validate the affected font before choosing a remedy.
Why is my custom font missing in Safe Mode?
Apple documents that Safe Mode prevents fonts not installed by macOS from loading. Judge the original problem again after a normal restart.
Should I clear font databases on every maintenance run?
No routine reset is needed for this workflow. Keep font originals, make one controlled change, and stop when the original sample works normally.