What the font cache is and how it breaks
To avoid re-parsing font files every time an app starts, Windows keeps a service-side cache of font data. The files live in %WINDIR%\ServiceProfiles\LocalService\AppData\Local\FontCache and normally take up a few megabytes. Browsers, Office, editors and the shell itself all read through this cache, which is exactly why one damaged file inside distorts text everywhere at once.
Corruption usually follows a power cut, a crashed update or a third-party font manager that was uninstalled mid-work. The cache is disposable by design — Windows rebuilds it from the installed fonts — so deleting it is one of the rare fixes that is both safe and effective. No font gets removed, no document is touched; only the temporary data goes.
- Characters render as empty boxes or question marks
- Word and Excel show a different font than the one selected
- Browser menus and pages show garbled or overlapping glyphs
- Installed fonts are missing from app font lists until reboot
- The Settings → Personalization → Fonts preview pane renders blank
Clearing the cache step by step
Close browsers, Office apps and anything else that displays custom fonts. Press Win+R, type services.msc and find Windows Font Cache Service; open it, click Stop and leave the startup type on Automatic — the service restarts on the next boot by itself. Now open %WINDIR%\ServiceProfiles\LocalService\AppData\Local\FontCache in File Explorer and delete everything inside. Some files refuse to go while the service runs, which is why stopping it comes first.
The command-line version of the same fix takes ten seconds in an elevated prompt: net stop FontCache and net stop FontCache3.0.0.0 (the second command covers the older .NET font cache, if it is present), then delete the folder contents and reboot. After the reboot the service quietly regenerates the cache. Fonts come back correct within a few minutes, and the whole cycle rarely takes longer.
If the fonts are still broken afterwards
When a cache rebuild changes nothing, the cache was not the culprit. Check the obvious first: reinstall the affected font — right-click the .ttf or .otf file and choose Install for all users — because a font installed only for one Windows account is invisible to apps running under another. A font file that came from an untrusted source can also be rejected by Windows silently.
Beyond that, look at font registration: open regedit and make sure the font is listed under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts. Third-party font managers and old typography suites are the usual suspects when entries are missing. To keep the whole cache family healthy on a schedule — fonts, icons, thumbnails — a cleaner like Kleaner PRO handles these caches in one pass, so a glitch never gets a chance to accumulate.
Questions and Answers
Is it safe to delete files in the FontCache folder?
Yes, as long as the Windows Font Cache Service is stopped first. The folder holds only disposable cache data, and Windows rebuilds it automatically from installed fonts.
Where is the font cache stored in Windows 11?
In %WINDIR%\ServiceProfiles\LocalService\AppData\Local\FontCache — usually C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache. Deleting its contents with the service stopped is the standard fix.
Why do I get access denied when deleting FontCache files?
The files are owned by the LocalService account and locked while the font service runs. Stop the FontCache service, close apps that use fonts, or do the deletion from Safe Mode.
Know what is included before you buy.
The one-time 30-minute trial covers core tools. PRO-labelled features stay locked until a paid license is activated.
Read next
Write to us: [email protected]