If a font appears in Font Book but not in Word, Photoshop, Pages, or another Mac app, start with the narrowest fix: confirm the font is installed and active, validate it, resolve duplicates, then completely quit and reopen the affected app. Repair Font Book or rebuild system caches only when the symptoms extend beyond one application.
Why a Mac app cannot see an installed font
macOS does not make every font file immediately available to every running application. Font Book controls installation, activation, validation, and duplicate handling; each app reads the available font list when it launches and may maintain its own cache or font settings.
As an Amazon Associate I earn from qualifying purchases.
That creates several different failure patterns:
- The file was never installed, is in an unsupported format, or failed validation.
- The font is installed in a user or computer library but is inactive.
- Two copies of the same family or face are installed and the app is using the wrong one.
- The app started before the font was installed or activated and has not refreshed its menu.
- A large active collection, particularly in Microsoft Office, prevents every font from loading.
- Font Book’s library or a system/application cache is damaged.
Identify which pattern fits before making a system-wide change. A font missing from one app calls for an app-level fix; a font missing from several apps calls for Font Book or cache troubleshooting.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Use Font Book as the first checkpoint
Confirm the font is installed
Open Font Book from Applications or Spotlight and search for the family name. Apple states, “To use fonts in your apps, you need to install the fonts using Font Book.” If the family is absent, install the original file rather than copying it into an arbitrary folder.
- Double-click the font file in Finder, or open Font Book and choose File > Add Fonts to Current User (the exact wording can vary by macOS release).
- Select the font file or folder and confirm the installation.
- In Font Book, check whether the font appears under the intended collection or library.
Font Book supports TrueType (.ttf), variable TrueType (.ttf), TrueType Collection (.ttc), OpenType (.otf), OpenType-SVG (.otf), and OpenType Collection (.ttc) formats. A file with a familiar extension can still be corrupt, incomplete, or an incorrectly packaged web font, so appearance in Finder is not proof that it is usable.
Check the library location and activation state
Font Book can install a font for your user account or for all users of the Mac. A user-library font is available only to that account; a computer-library font is available system-wide. In the Font Book sidebar, inspect both locations if you expected the font to be available everywhere.
Look at the font’s status in the preview pane or family list. If it is inactive, select it and choose Edit > Activate (or use the activation button shown by your macOS version). An inactive face will not appear in an app’s font menu even though Font Book retains its record.
Some families contain separate regular, bold, italic, condensed, or variable faces. Expand the family and verify the specific style you need is present and active; activating only one face does not guarantee that every companion face is installed.
Validate the file before troubleshooting applications
A damaged font can install partially, appear in Font Book, or work in one program while failing in another. Validate it before blaming the application.
- In Font Book, select the installed font or family.
- Choose File > Validate Selection.
- For a file that is not yet installed, choose File > Validate File and select it in Finder.
Font Book reports a color-coded result:
- Green: the checks passed.
- Yellow: a warning exists; the font may work, but inspect the warning before relying on it for production files.
- Red: the font failed validation and should not be trusted.
For a red result, remove the failed copy and obtain a clean, complete copy from the font’s legitimate source. Do not attempt to “repair” a binary font by renaming its extension. If a yellow warning coincides with the missing-font symptom, test a clean release of the same family rather than assuming the warning is harmless.
Resolve duplicate fonts without losing the working copy
Duplicates commonly arise after installing a new package over an older family, restoring a backup, or moving between design applications. Different copies can have different internal names, versions, or supported character sets.
- Select the family or the group containing duplicates in Font Book.
- Choose File > Resolve Duplicates.
- When Font Book offers a choice, retain the copy it marks Active.
After resolving duplicates, quit and reopen the application that was missing the font. If you need a particular release—for example, a variable version supplied by a design project—record which file you kept before removing alternatives. Deactivate or remove only the unwanted duplicate; deleting every copy leaves the app with nothing to load.
Rank #3
Restart the affected app completely
Most Mac applications build their font menu at launch. Installing or activating a font while Word, Photoshop, Affinity, Pages, or another program is open may not update that program’s list.
- Save your work.
- Choose the application’s Quit command, not merely the window’s close button. If it refuses to quit, use Option-Command-Escape to open Force Quit and end it.
- Wait a few seconds, then launch the app again.
- Check the font menu and test a new document or text layer.
If the font now appears in other applications but remains absent from one third-party app, treat it as an application-specific problem. Check that app’s own font-management, plug-in, document, or workspace settings and follow its developer’s support procedure. Apple specifically directs users to the third-party developer when a font is missing only from a third-party application.
Also verify that the document is not limiting the menu to fonts used in the file, a selected script, or a filtered favorites list. Such filters can make an installed family look absent without indicating a macOS installation failure.
When Microsoft Office does not load every font
Microsoft says Office for Mac “may not be able to load all the fonts” when a large number of fonts are installed. Microsoft does not publish a universal numeric threshold, so do not treat any fixed font count as a guaranteed limit.
Rank #4
Use a controlled test instead:
- In Font Book, resolve duplicates.
- Deactivate fonts you do not need for the document, especially old families and multiple versions.
- Leave the required family active and quit every Office application.
- Reopen Word, Excel, or PowerPoint and check the font list.
- Reactivate additional families in small groups until the failure returns.
This approach identifies whether collection size or a particular family is responsible. Keep a record of deactivated fonts so you can restore the original setup after testing. If Office alone is affected while other apps show the font, use Microsoft’s Office support path rather than resetting all macOS fonts.
Repair an empty or damaged Font Book library
If Font Book itself shows no fonts, or its library is clearly damaged, Apple documents a built-in reset. This is more disruptive than restarting an app or deactivating a duplicate.
Back up custom fonts first
Before resetting, copy font files that you installed yourself to a separate folder or note their original locations. Include fonts in both your user and computer libraries. A reset moves installed fonts out of the active folders, so you will need those copies to reinstall them.
Recommended Free Tools
Reset the font libraries
- Open Font Book.
- Choose Font Book > Settings (called Preferences in some older releases).
- Open the Advanced pane.
- Click Reset Fonts and confirm.
Apple’s reset moves installed fonts to /Library/Fonts (Removed) or ~/Library/Fonts (Removed). Fonts in those folders are unavailable until you install them again. System fonts supplied by macOS are handled separately, but custom fonts, activated families, and carefully organized collections should be treated as removable during this operation.
Reinstall selectively
After the reset completes, restart the Mac, open Font Book, and install only a known-good subset of your custom fonts. Validate each group and test the affected app before adding the next group. This prevents a single corrupt file or duplicate family from recreating the problem immediately.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Decide whether a cache reset is justified
Font caches let macOS and applications avoid rebuilding font data on every launch. A stale or damaged cache can produce symptoms across multiple applications, particularly after extensive installation, removal, or activation changes. However, cache clearing is a later diagnostic, not the default response to one missing font.
| Fix | Scope | Reversibility | Evidence and risk |
|---|---|---|---|
| Quit and reopen the app | One application | Fully reversible | Low risk; appropriate when the font was installed while the app was open |
| Activate or deactivate a font | Font Book and apps using that library | Fully reversible | Low risk; confirms whether status is the cause |
| Resolve duplicates | A family or selected collection | Usually reversible if copies are retained | Apple-documented; keep the Active copy and back up alternatives |
| Reduce the active Office collection | Office applications | Reversible | Supported by Microsoft’s warning about large collections; no universal count is stated |
| Reset Fonts | Font Book libraries across the Mac | Requires reinstalling custom fonts | Apple-documented but disruptive; fonts are moved to “Removed” folders |
| Safe Boot or a documented cache-reset procedure | System-wide caches | Generally reversible after a normal restart | Vendor/community guidance is weaker than Apple’s built-in repair steps; avoid deleting unknown system files |
Safe Boot as a diagnostic
Safe Boot starts macOS with a reduced set of extensions and performs maintenance that can rebuild certain caches. The exact entry method depends on whether the Mac has Apple silicon or an Intel processor, so use Apple’s instructions for your hardware and macOS release. After entering Safe Mode, restart normally and test the apps again.
Safe Boot is most reasonable when the same font failure affects several unrelated applications after many font changes. It is unlikely to fix a font that is absent from Font Book, an inactive face, or a problem confined to one application’s own cache.
Be cautious with command-line cache deletion
Some administrators use a documented font-cache utility followed by a restart. Procedures and available commands vary by macOS release, and deleting arbitrary files under system or Library folders can damage permissions or remove data needed by other services. Do not follow a command that does not identify the macOS versions it supports, explain what it removes, and provide a recovery path. Prefer Font Book’s reset and Safe Boot before manual deletion.
Quick Recap
Follow this decision path
- Font absent from Font Book: confirm the extension, install the original file through Font Book, and validate it.
- Font present but inactive: activate the family and the specific face you need.
- Duplicate warning: use File > Resolve Duplicates and retain the copy marked Active.
- Font visible in Font Book and other apps but not one app: quit and relaunch that app, remove any app-level font filter, and contact its developer if the problem persists.
- Many fonts missing in Office: deactivate unnecessary families and duplicates, then restart Office.
- Font Book is empty or corrupted: back up custom fonts, use Font Book > Settings > Advanced > Reset Fonts, restart, and reinstall validated fonts.
- Several apps fail after extensive font changes: only after backing up custom fonts, try Safe Boot or a documented cache-reset process, then restart normally.
Checks that prevent the problem from returning
- Keep one authoritative copy of each family and archive older releases outside the active font libraries.
- Install fonts through Font Book so activation and validation are visible.
- Use descriptive folders for project fonts and deactivate them when a project ends.
- After replacing a font, quit and relaunch every app that must use it.
- Back up licensed custom fonts before any reset or bulk cleanup.
- When troubleshooting, change one variable at a time and test in a simple new document.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
