SystemRequires admin/root
System Font Cache
Linux stores a shared Fontconfig cache in /var/cache/fontconfig so applications can avoid rescanning every installed font file on each launch. These cache files contain serialized font metadata such as family names, style and weight mappings, language coverage, file paths, timestamps, and directory scan results used by GTK, Qt, browsers, office suites, and other desktop software. Kudu removes stale Fontconfig cache entries from this system cache so the font index can be rebuilt cleanly without touching installed fonts, user documents, settings, accounts, or passwords.
Why clean System Font Cache?
- Stale Fontconfig metadata after adding or removing fonts makes new fonts not appear or deleted fonts still show up in pickers until the cache is rebuilt
- Cached path and timestamp mismatches cause applications to substitute the wrong typeface, which users notice as unexpected fonts in browsers, editors, and office documents
- Corrupt cache files in /var/cache/fontconfig can trigger slow application startup while programs repeatedly rescan font directories before drawing text
- Outdated language and fallback mappings lead to missing glyphs, empty boxes, or the wrong fallback font for CJK, emoji, and symbol characters
- System-wide cache entries built before a package upgrade can leave GTK and Qt apps disagreeing about available font styles, showing inconsistent bold or italic variants
- Large, long-lived cache sets accumulate obsolete directory scan results, wasting disk space and making the first text-rendering pass noticeably slower after font changes
What gets cleaned
Cache paths Kudu targets
Linux
/var/cache/fontconfig |
Frequently asked
Common questions about System Font Cache
Related cleaners
Free & open source
Download Kudu and reclaim your disk space.
Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.