How to Clear the Font Cache on a Mac in 2026 (Fix Garbled or Missing Fonts)

If you've ever opened an app only to see scrambled text, boxes where letters should be, or fonts that look completely wrong, a corrupted font cache is almost certainly to blame. Knowing how to clear the font cache on a Mac is one of those quiet power-user skills that saves hours of frustration — and on macOS Sequoia and Tahoe running on Apple Silicon or Intel Macs, the process is straightforward once you know where to look. This guide walks you through every method, from the safest one-liner to the manual approach for edge cases.

What Is the Font Cache and Why Does It Get Corrupted?

macOS maintains a database of pre-rendered glyph data so that apps don't have to re-parse font files every time they draw text. This cache lives in a few different locations depending on which component owns it — the system font server, individual apps, or the current user session.

Corruption happens more often than you'd expect: interrupted updates, migrating from one Mac to another via Migration Assistant, installing a third-party font manager, or simply accumulating hundreds of fonts over years of use can all produce stale or conflicting cache entries. The symptoms are distinctive:

• Garbled or "tofu" boxes in menus, browsers, or design apps
• Correct font names in Font Book but wrong glyphs rendered on screen
• Ligatures or special characters showing as question marks
• Crash-on-launch in apps like Figma, Affinity, or the Adobe suite
• Slow app launch because the font server is rebuilding its index from scratch on every open

Where macOS Stores Font Cache Files

Before you delete anything, it helps to understand the landscape. Font cache data is spread across user-space and system-space locations.

The paths you care about most are the com.apple.ATS directories. The system-level one requires elevated privileges; the user-level one does not.

How to Clear the Font Cache on a Mac: Step-by-Step

There are two main approaches: using the built-in atsutil command (recommended) or deleting cache folders manually in Safe Mode. Start with the command-line method — it's faster and doesn't require a restart.

Method 1: Use atsutil (Fastest, No Restart Required)

1. Open Terminal (Applications > Utilities > Terminal, or search with Spotlight).
2. Quit every app that renders text — browsers, design tools, Office, everything.
3. Run the following command to flush the font server's database and restart the font service:
   sudo atsutil databases -remove && atsutil server -shutdown && atsutil server -ping
4. Enter your administrator password when prompted. The command removes the ATS database files, shuts down the font server, then immediately pings it — which forces macOS to rebuild a fresh cache from your installed fonts.
5. Relaunch your apps. In most cases the garbled-text issue is gone immediately.

If you'd rather target only the current user's cache without sudo:

Then log out and log back in. macOS recreates the directory on next login.

Method 2: Safe Mode (Thorough, Requires Restart)

Safe Mode disables third-party kernel extensions, clears several system caches automatically, and loads only essential system fonts — making it the gold standard for persistent font problems.

1. Apple Silicon Mac: Shut down. Press and hold the power button until "Loading startup options" appears. Select your startup disk, hold Shift, and click "Continue in Safe Mode."
2. Intel Mac: Restart and immediately hold the Shift key until the login screen appears with "Safe Boot" in the menu bar.
3. Log in. macOS automatically purges font caches as part of the Safe Mode boot sequence.
4. Restart normally. Your fonts should now render correctly.

Clearing Font Caches Left by Specific Apps

Some professional apps maintain their own font databases on top of macOS's system cache. If problems persist after flushing the system cache, check these locations:

• Adobe apps (Illustrator, InDesign, Photoshop): Delete ~/Library/Application Support/Adobe/Adobe Fonts/ and let the Creative Cloud desktop app resync.
• Figma: Remove ~/Library/Caches/com.figma.agent/ and relaunch.
• Microsoft Office: Trash ~/Library/Caches/com.microsoft.Word/ (and equivalent folders for Excel, PowerPoint).
• Font management apps (FontExplorer X, Suitcase Fusion): Use the app's own "Rebuild Database" or "Clean Cache" command — consult the vendor docs for your version.

Understanding the broader landscape of what cache files on a Mac actually are can help you decide which ones are worth clearing and which are better left alone.

Will Clearing the Font Cache Delete My Fonts?

No. Font cache files are derived data — macOS rebuilds them automatically from the actual font files stored in your Font folders. Deleting the cache does not touch:

• ~/Library/Fonts/ — your personal fonts
• /Library/Fonts/ — fonts shared across all users
• /System/Library/Fonts/ — system fonts (read-only, managed by macOS)

Your installed typefaces remain completely intact. Only the rendering database is rebuilt.

How Much Disk Space Can You Recover?

Font caches are generally small — typically 15–120 MB combined across all locations — so freeing space isn't the main motivation here. The real win is performance and rendering correctness. That said, if you have hundreds of fonts activated through a font manager, the ATS database can balloon beyond 200 MB on a heavily used creative workstation.

If disk space is your broader concern, font caches are just one small piece of the puzzle. A tool like Crumb can audit all your caches at once — font, system, app, and developer — and show exactly what's safe to remove before anything gets deleted. You can learn more about the system data category where caches appear in our guide to clearing the system cache on Mac.

Preventing Font Cache Corruption in the Future

A few habits significantly reduce how often you'll need to clear the font cache:

• Don't over-install fonts. macOS performs best with a reasonable font library. Activate only the fonts a project needs; deactivate the rest.
• Use Font Book's validation tool. Open Font Book, select all fonts (Cmd-A), then go to File > Validate Fonts. Remove any font that shows a yellow or red warning — corrupted source fonts are the leading cause of cache corruption.
• Restart after installing many new fonts at once. Bulk installs can confuse the font server. A clean restart after a large batch install lets macOS build the cache from a stable state.
• Keep macOS updated. Apple regularly improves the font rendering pipeline and ATS stability. Running macOS Sequoia 15.x or Tahoe 16.x gives you the latest fixes.
• Back up before installing third-party font managers. These tools hook into the system font service at a low level; a Time Machine snapshot before installation gives you a rollback point if things go sideways.

When to Suspect Something Other Than the Font Cache

If clearing the font cache doesn't fix the rendering problem, consider these alternatives:

• GPU or display driver issue: Garbled text that appears only in one app but renders correctly in screenshots often points to a GPU rendering bug, not a font problem. Try toggling "Reduce transparency" in System Settings > Accessibility > Display.
• Corrupt font file: Use Font Book's validate function to identify the offending font, then reinstall it from the original source.
• App-level rendering bug: Some apps ship with bundled fonts that conflict with system fonts of the same family name. Updating the app or removing the conflicting system font often resolves this.
• Disk permissions: On rare occasions, permission errors on ~/Library/Caches/ prevent macOS from writing a new cache. Run diskutil resetUserPermissions / $(id -u) in Terminal and then retry.