Where Is the Fonts Folder on Windows, macOS and Linux?
System-wide and per-user font folders on Windows, macOS and Linux, and why a font you just installed can be missing from some apps.
Last updated
Every desktop OS keeps at least two font locations: one system-wide folder that needs admin rights, and one folder for the current user that does not. A font lands in whichever one the installer picked, usually without asking you.
This split is behind the classic complaint. A font installed per-user is invisible to programs running as administrator and to anyone else who logs in, and the reverse is also true. One folder looking right proves nothing about the other.
Both folders are merged in the OS's own font settings, which is why the list you see there does not always match what a folder browser shows. Decide which scope you need first, then the mystery mostly disappears.
Where Fonts Folder stores this, by platform
C:\Windows\Fonts
The system-wide folder, writable only by administrators. Since Windows 10 version 1809, double-clicking a font and pressing Install puts it in %localappdata%\Microsoft\Windows\Fonts instead (full path C:\Users\[Username]\AppData\Local\Microsoft\Windows\Fonts) with no admin prompt. Settings > Fonts and the old Control Panel view merge both folders, so the C:\Windows\Fonts view can list fonts that are not physically stored there.
/Library/Fonts
/System/Library/Fonts holds the fonts that ship with macOS and is protected by SIP, so treat it as read-only. /Library/Fonts is the machine-wide folder every account can use, and adding to it needs an admin login. The current user's fonts live in ~/Library/Fonts and need no permissions at all. Font Book installs into one of these depending on the scope you choose, and displays all three as one list.
/usr/share/fonts
Distro packages install here, sorted into subfolders by font type, and changes need root. /usr/local/share/fonts is the conventional spot for fonts you install system-wide by hand. User fonts go in ~/.local/share/fonts, which fontconfig reads with no configuration; ~/.fonts still works but is deprecated. After copying fonts by hand, run fc-cache -f so programs see them right away.
Frequently asked questions
I installed a font and some apps don't see it. Why?
It most likely went into the per-user folder: %localappdata%\Microsoft\Windows\Fonts on Windows, or ~/Library/Fonts on Mac. Programs running as administrator, and other user accounts, only read the system-wide folders, so reinstall it with the Install for all users option.
Where are fonts stored for one user only on Windows?
In C:\Users\[Username]\AppData\Local\Microsoft\Windows\Fonts, registered under the current user's registry key rather than the machine-wide one. Nothing is copied into C:\Windows\Fonts, which is why the same font is missing for anyone else who logs into the PC.
Should I delete font files from the Fonts folder directly?
Use Settings > Fonts on Windows or Font Book on Mac instead of deleting files by hand. Manual deletion can leave the registry or the font catalog pointing at a file that no longer exists, which shows up as a broken entry rather than a clean removal.
Notice an outdated path? Let us know.