# Is it safe to delete the font caches on a Mac?

Is it safe to delete? · macOS files · Updated 21 November 2026. By Mohit Nippanikar, who makes SiftMac.

## The short answer

- **Yes**, with Apple’s tools. Font caches are databases macOS builds from the fonts you have installed, so resetting them deletes no fonts. It’s a repair for fonts that misbehave, not a way to free space.
- **What it costs you:** a restart or a log out, and some Font Book choices to redo: fonts you turned off can be back on, and fonts you activated from other folders may need activating again.
- **Does it come back?** Yes. macOS builds new databases from the fonts in the standard font folders after you log out or restart.
- SiftMac’s verdict: Rebuilds

## 1. What it is

Every app that draws text asks macOS which fonts exist, where their files are and which ones are turned on. Rather than read every font file each time, macOS’s font service, `fontd`, keeps a registry: databases and cache files built from the fonts in the standard font folders, plus your choices in Font Book.

When fonts misbehave, for example text showing up in the wrong font or fonts missing from an app’s menus, a registry that no longer matches the fonts on disk is one of the usual suspects. Removing the caches makes macOS build them again from the font files themselves, which is why it’s a standard step in fixing font trouble.

## 2. Where it is

Your own font registry is in your per-user cache folder inside `/private/var/folders`. To see it:

```
ls "$(getconf DARWIN_USER_CACHE_DIR)com.apple.FontRegistry"
```

macOS keeps a separate set for the whole system, which you don’t need to find. Neither is where your fonts are: fonts you installed live in `~/Library/Fonts` (just for you) or `/Library/Fonts` (for everyone), and Font Book shows them all. Leave those folders alone when you’re fixing a cache problem; they are the fonts.

## 3. How big it gets

Small. The registry is an index of your fonts, not a copy of them, so resetting it gives back very little space. To check:

```
du -sh "$(getconf DARWIN_USER_CACHE_DIR)com.apple.FontRegistry"
```

If fonts really are taking space, measure the fonts themselves with `du -sh ~/Library/Fonts /Library/Fonts`, and remove the ones you don’t use in Font Book rather than in Finder.

## 4. How to reset it safely

Start with the gentlest step that fixes the problem:

1. **Check the fonts first.** In Font Book, select fonts and choose File › Validate Selection. Fonts that fail show in red, and you can remove them with Remove Checked. File › Resolve Duplicates deals with two copies of the same font.
2. **Start up in safe mode.** Apple says safe mode clears some system caches, including font caches, which macOS creates again as needed. Start up in safe mode, then restart normally and look at the fonts again.
3. **Reset your own font caches from Terminal.** Quit your apps, run `atsutil databases -removeUser`, then log out and back in, or restart.

```
atsutil databases -removeUser
```

Its manual says `-removeUser` removes the font databases for the active user only, which is enough for a problem in your own account; `-remove` clears the system’s databases as well. Older guides also tell you to run `atsutil server -shutdown` and `atsutil server -ping`. The `atsutil` in recent macOS has no `server` command (`atsutil help` lists what yours has); logging out or restarting does that job.

## 5. What happens afterwards

- The first log in, or the first launch of an app with many fonts, can take a little longer while macOS rebuilds the registry.
- Fonts in the standard folders come back by themselves. Fonts you activated from somewhere else, such as a project folder or a font manager, may need activating again.
- Fonts you had turned off in Font Book can be on again, and font libraries you made in Font Book may need making again.
- No font files are deleted.

## Questions

### Will clearing font caches free up space?

Hardly any. They’re indexes of your fonts, not the fonts. If you need space, the usual places are app caches, Downloads, the Trash and System Data.

### Does safe mode delete my fonts?

No. Apple says safe mode stops fonts that weren’t installed by macOS from loading while it’s running, and clears font caches. Your fonts are all there again after a normal restart.

### Do I need a font manager or a cleaner app to reset font caches?

No. Safe mode and `atsutil` come with macOS, and Font Book checks the fonts themselves.

### The fonts still look wrong after resetting. What now?

The cache may not be the problem. Validate the fonts in Font Book and resolve duplicates: a single damaged font, or two versions of the same one, can cause trouble on its own.

## How SiftMac handles it

SiftMac doesn’t touch font caches or fonts. They’re Apple’s caches in macOS’s per-user folder, which its App caches category deliberately leaves alone, and resetting them is a repair best done with safe mode or `atsutil`.

Download: https://siftmac.com/SiftMac.dmg (scanning is free, and so is the first 2 GB of cleaning).

## Sources

- [Apple: Start up your Mac in safe mode](https://support.apple.com/en-us/116946)
- [atsutil(8) man page: font registration system utility](https://keith.github.io/xcode-man-pages/atsutil.8.html)
- [Apple: Install and validate fonts in Font Book on Mac](https://support.apple.com/guide/font-book/fntbk1000/mac)

## Related

- [Is it safe to delete the Quick Look thumbnail cache?](https://siftmac.com/safe-to-delete/quicklook-thumbnail-cache)
- [Is it safe to delete /private/var/folders on a Mac?](https://siftmac.com/safe-to-delete/var-folders)
- [Is it safe to delete ~/Library/Caches on a Mac?](https://siftmac.com/safe-to-delete/library-caches)
- [What fills a designer’s Mac, and what’s safe to clear](https://siftmac.com/for/designers)
- [How to clear System Data on a Mac, safely](https://siftmac.com/guides/system-data-on-mac)

Canonical: https://siftmac.com/safe-to-delete/font-caches
