GIMP Not Showing Newly Installed Fonts: Fixes

If you install a new font and GIMP doesn’t show it in the font list, the usual cause is that GIMP only scans its font directories at startup, or the font file is in a format it can’t read. The fix is to restart GIMP completely, then refresh the font list from within the Text Tool; if that fails, check the font file’s format and permissions, and confirm it’s installed for your user account, not just the system.

Why GIMP Doesn’t See New Fonts

GIMP does not watch your operating system’s font folder in real time. It builds an internal font cache when it launches, so any font added after that moment is invisible until you restart the application. Even then, GIMP may cache the list again on exit, so a simple restart usually works, but sometimes you need to force a full refresh.

Another common reason is the font file itself. GIMP relies on the FreeType library to render fonts, and while it supports TrueType (.ttf), OpenType (.otf), and many others, it can stumble on variable fonts, color fonts (like COLR/CPAL), or fonts with broken metadata. If the font appears in other programs but not GIMP, the file is likely fine; if it doesn’t appear anywhere, the installation is the problem.

How GIMP Loads Fonts on Each OS

The font directories GIMP scans depend on your operating system:

Windows: GIMP reads from C:\Windows\Fonts and the per-user %LOCALAPPDATA%\Microsoft\Windows\Fonts folder. Fonts installed via right-click “Install for all users” go to the system folder; “Install for current user” goes to the local folder.
macOS: GIMP uses the system font registry through Fontconfig, which checks /Library/Fonts, /System/Library/Fonts, and ~/Library/Fonts. Fonts added via Font Book normally appear after a restart.
Linux: GIMP uses Fontconfig, so it reads ~/.fonts, ~/.local/share/fonts, and system paths like /usr/share/fonts. The exact order is defined in /etc/fonts/fonts.conf.

On all three, GIMP also looks in its own private font folder inside the GIMP profile directory (e.g., ~/.config/GIMP/2.10/fonts on Linux, %APPDATA%\GIMP\2.10\fonts on Windows). You can drop font files there manually, and they will be picked up on the next start.

Step-by-Step Fixes That Work

Try these in order, testing after each step:

Restart GIMP completely. Close all GIMP windows, not just the image. On Windows, check the system tray for a lingering GIMP icon. Relaunch and open the Text Tool.
Refresh the font list. In the Text Tool options dock, click the small circular arrows icon next to the font dropdown. This forces GIMP to rescan its font directories without a full restart. If you don’t see the icon, click the font dropdown’s “Refresh” option in some versions.
Check the font file format. If the font is a .ttc (TrueType Collection), .dfont, or a webfont like .woff2, GIMP may ignore it. Convert it to .ttf or .otf using a free converter like FontForge, then reinstall.
Verify permissions. On Linux, ensure the font file is readable (chmod 644 font.ttf) and that the folder is not restricted. On macOS, check that the font isn’t quarantined (right-click > Open to bypass Gatekeeper).
Clear the font cache. GIMP stores a cache file (e.g., fonts.cache in the profile folder). Delete it while GIMP is closed, then restart. On Linux, you can also run fc-cache -f to rebuild the system font cache.
Install for your user only. If the font was installed for all users and still doesn’t appear, try installing it for your user account. This avoids permission issues, especially on managed Windows machines.
Check the font name. Sometimes the font’s internal family name differs from the filename. Open the font in a viewer like Font Book or Windows Font Viewer to see the exact name, then search for that in GIMP’s list.

Common Problems and Misconceptions

A frequent mistake is assuming that “install” means the font is immediately available everywhere. On Windows, the font service may lag, and on some Linux desktops, the font daemon needs a refresh. Another misconception is that GIMP’s font list is alphabetical by filename—it’s actually sorted by the font’s internal family name, so a file named “MyFont-Regular.ttf” might appear under “My Font” or even under the foundry name.

Variable fonts are a growing issue. A variable font contains multiple weights and widths in one file, and while GIMP 2.10.18 and later have partial support, older versions may only show the default instance. If you downloaded a variable font from Google Fonts, try downloading the static instance instead.

Also, GIMP’s font preview can be misleading. The dropdown shows a sample of each font, but if the font has no Latin characters, the preview may look blank even though the font is loaded. Test by typing text in the font’s native script.

How to Install Fonts Correctly on Each OS

To avoid the problem entirely, install fonts the standard way:

Windows: Right-click the font file and choose “Install” (for your user) or “Install for all users” (requires admin). You can also drag the file into the Fonts control panel.
macOS: Double-click the font and click “Install Font” in the Font Book preview. This adds it to ~/Library/Fonts by default.
Linux: Copy the file to ~/.local/share/fonts (create it if needed) and run fc-cache -f. For system-wide install, use sudo cp font.ttf /usr/share/fonts/truetype/ and then refresh the cache.

After installing, restart GIMP. If you are using a portable version of GIMP (e.g., on a USB stick), it may not read the system font folders at all—you must put fonts in the portable profile’s fonts directory.

When the Font Still Doesn’t Appear

If you’ve done all the above and the font is still missing, the issue may be deeper:

Corrupt font file: Download the font again from the original source. A truncated download is common.
GIMP version too old: GIMP 2.8 and earlier have limited font support. Update to GIMP 2.10.x or the 3.0 release candidate if you need modern font features.
Conflict with another font: Two fonts with the same family name can cause one to be hidden. Rename the file or remove the duplicate.
Antivirus or security software: Some tools block font installation. Temporarily disable them to test.

If nothing works, try using the font in another application like Inkscape or LibreOffice. If it works there, the problem is specific to GIMP’s fontconfig integration; you can try resetting GIMP’s preferences (rename the GIMP profile folder) to force a fresh font scan.

Frequently Asked Questions

Why can I see the font in other apps but not GIMP?

GIMP may have cached an older font list, or the font is in a format GIMP’s FreeType build doesn’t fully support (like .woff2). Restart GIMP, then click the refresh icon in the Text Tool. If it still doesn’t show, convert the font to .ttf or .otf.

Do I need to restart GIMP after installing a font?

Yes, GIMP only scans fonts at startup. A full restart is required. You can also use the refresh button in the font dropdown, but that only works after the initial scan has run.

How do I add fonts to GIMP without installing them system-wide?

Place the font files in GIMP’s profile fonts folder. On Windows, that’s %APPDATA%\GIMP\2.10\fonts; on Linux/macOS, it’s ~/.config/GIMP/2.10/fonts. Restart GIMP and the fonts will appear.

Why does GIMP show a blank box for my font?

The font may not contain glyphs for the characters you’re typing, or the preview in the dropdown is just showing a sample that doesn’t match your text. Type your actual text and see if it renders. If it’s still blank, the font is likely broken or a symbol font.

Can I use Google Fonts in GIMP?

Yes, download the font from Google Fonts (choose the static .ttf files, not the variable font), install it normally, and restart GIMP. Variable fonts may work partially in GIMP 2.10.18+, but static instances are safer.

What if GIMP crashes after I install a new font?

This is rare but can happen with a corrupt font. Remove the font from the system, restart GIMP, and then reinstall a fresh copy. If the crash persists, reset GIMP’s preferences by renaming the profile folder.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →