How to Install Fonts in Google Docs (And Expand Beyond the Default List)
Google Docs comes loaded with a respectable selection of fonts — but if you've ever wanted something more distinctive for a presentation deck, brand document, or creative project, you've probably noticed the default dropdown feels limited. The good news: Google Docs has a built-in mechanism for accessing hundreds of additional fonts, and with the right add-on, you can push that even further.
Here's how it all works, what your actual options are, and what determines which approach makes sense for your situation.
What "Installing" a Font Actually Means in Google Docs
Google Docs is a cloud-based application, which means it doesn't interact with your operating system's font library the way desktop software like Microsoft Word or Adobe InDesign does. You can install a font on your Windows or Mac system and it will appear in Word — but that same font won't automatically show up in Google Docs.
Instead, Google Docs draws from Google Fonts, a library of open-source typefaces hosted on Google's servers. "Adding" a font to Google Docs means making it available within your document's font dropdown — it's a browser-side selection, not a system-level installation.
This distinction matters because it affects what's possible, and what isn't, depending on how you're working.
Method 1: Adding Fonts Through the Built-In Google Fonts Browser
This is the native method — no add-ons required.
- Open any Google Docs document
- Click the font name dropdown in the toolbar (it typically shows "Arial" by default)
- Scroll to the top of the dropdown and select "More fonts"
- A dialog box opens showing the full Google Fonts library — hundreds of typefaces organized by category, script, and popularity
- Use the search bar or filters (Serif, Sans Serif, Display, Handwriting, Monospace) to find what you want
- Click any font to add it to your active font list, then click OK
The selected fonts now appear in your toolbar dropdown for that account across all documents. They're tied to your Google account, not a single file, so they persist across sessions and devices as long as you're logged in.
🎨 Filters worth knowing: the "Show" dropdown in that dialog lets you browse fonts by script (Latin, Cyrillic, Arabic, etc.), which is useful if you're working in multiple languages.
Method 2: Using the Extensis Fonts Add-On
For users who need a more powerful font browsing experience — or access to fonts outside the standard Google Fonts library — the Extensis Fonts add-on (available in the Google Workspace Marketplace) is the most widely used solution.
To install it:
- In Google Docs, go to Extensions → Add-ons → Get add-ons
- Search for "Extensis Fonts"
- Click Install and grant the necessary permissions
- Once installed, access it via Extensions → Extensis Fonts → Start
The add-on opens a sidebar that lets you preview and apply fonts directly without digging through the More Fonts dialog. It also displays fonts in real time as rendered text — not just font names — which is significantly more useful when you're trying to match a visual style.
Important caveat: Extensis Fonts still draws from the Google Fonts library. It doesn't give you access to commercial typefaces like those from Adobe Fonts or Monotype unless those fonts happen to overlap with the open-source catalog.
What You Cannot Do Natively
There's a hard limitation worth understanding clearly: you cannot upload a custom .ttf or .otf font file directly into Google Docs. If your brand uses a proprietary typeface licensed from a type foundry, it won't appear in Google Docs — period — unless Google has independently included that typeface in their library.
Workarounds that some teams use include:
- Embedding text as images — designing text in Canva or Figma with the custom font, then inserting it as an image into the doc (workable for headers, not body text)
- Using Google Slides instead, which has similar limitations but sometimes fits visual-heavy workflows better
- Exporting to Word or PDF from a desktop app that does have the font installed, if the final deliverable doesn't need to be a live Google Doc
None of these are perfect substitutes, and each introduces formatting tradeoffs.
Factors That Affect Your Font Options
| Variable | How It Affects Things |
|---|---|
| Google account type | Personal and Workspace accounts both access Google Fonts; no meaningful difference here |
| Browser vs. mobile app | The Google Docs mobile app has a more limited font interface; the full "More fonts" dialog is only available on desktop browsers |
| Document sharing | Fonts you've added appear for you; collaborators see the font rendered correctly, but won't automatically have it in their own dropdown |
| Custom/proprietary fonts | Not uploadable natively; requires workarounds |
| Add-on permissions | Extensis Fonts requires account access permissions; some organizations restrict add-on installation via admin policy |
How Collaborators and Shared Documents Work
One thing that trips up teams: adding a font to your Google Docs account doesn't push it to collaborators. If you use a font another user hasn't added, they'll still see it correctly rendered in the document — Google handles that server-side. But if they try to apply that font themselves, they'll need to add it through the More Fonts dialog on their own account.
For organizations using Google Workspace with admin controls, IT admins can manage which add-ons are permitted. If Extensis Fonts isn't showing up in the Marketplace for you, that's likely why. 🔒
The Gap Between Library Fonts and Professional Typography
The Google Fonts library is genuinely large — over 1,400 font families as of recent counts — and includes high-quality options across every major category. For most general-purpose documents, blog drafts, reports, and educational materials, it covers a lot of ground.
Where it falls short is in brand-specific and licensed typography. If your organization has invested in custom or premium typefaces to maintain visual consistency, Google Docs isn't built to accommodate that — at least not without the workarounds described above.
Whether that gap is a dealbreaker, a minor inconvenience, or completely irrelevant depends on what kind of documents you're producing, who's reading them, and how tightly your workflow is tied to a specific visual identity.