How to Import Fonts Into Google Slides (And What Actually Works)

Google Slides doesn't support font imports the way desktop design tools like Illustrator or Figma do. There's no "Upload Font" button, no local file browser, and no way to drop a .ttf or .otf file directly into the platform. But that doesn't mean you're stuck with the default list — the options are just different from what most people expect.

Understanding how font access actually works in Google Slides saves a lot of frustration.

How Google Slides Handles Fonts

Google Slides runs entirely in the browser, which means it relies on web-safe fonts and Google Fonts — not fonts installed on your local machine. When you open the font picker inside a presentation, you're seeing fonts that Google's infrastructure can serve to any viewer, on any device, without requiring anything to be installed.

This is by design. A presentation viewed on someone else's laptop or a shared screen needs to look the same everywhere, so the font rendering depends on the platform, not the individual device.

The practical result: you can only use fonts that Google Slides can access natively — unless you work around the system using third-party tools or add-ons.

Accessing More Fonts Through the Built-In Font Picker

The default font dropdown in Google Slides shows a limited selection, but it's not the full library. To see everything available:

1. Click the font name in the toolbar while text is selected
2. Scroll to the top of the dropdown and click "More fonts"
3. A dialog opens where you can search, filter by category (Serif, Sans Serif, Display, Handwriting, Monospace), and sort by popularity or alphabetical order
4. Select any font and click OK — it's added to your working font list

This gives you access to the entire Google Fonts library, which currently includes over 1,400 font families. Most users who think they need to "import" a font actually just need to find it here. 🔍

Using Third-Party Add-Ons to Expand Font Access

If you need a font that isn't in Google Fonts — a premium typeface, a brand font, or a custom design file — the most commonly used workaround is Extensis Fonts, a Google Workspace add-on.

Extensis Fonts connects to a broader font library and lets you browse, preview, and apply fonts directly within Google Slides. The workflow looks like this:

• Install the add-on from the Google Workspace Marketplace (via Extensions → Add-ons → Get add-ons)
• Open it through the Extensions menu while working in a presentation
• Browse and apply fonts from within the add-on panel

Key limitation: Fonts applied through Extensis or similar add-ons are still web-hosted fonts from their own library. You still cannot upload a custom .ttf or .woff file. What you gain is access to a larger catalog than Google Fonts alone provides.

Other add-ons exist in the Marketplace with similar functionality, each with their own font catalogs and licensing terms.

The Workaround for Truly Custom or Brand Fonts

If your organization uses a proprietary typeface that isn't available through any web font service, you have a few practical paths:

Convert text to images or SVGs. Render your custom-font text in a design tool like Canva, Figma, or Adobe Express, export it as a PNG or SVG, and insert it into your Google Slides as an image. The font displays correctly because it's baked into the graphic — not rendered live by the browser. The tradeoff is that the text is no longer editable as text.

Use Google Slides via linked Google Drive with embedded design files. Some teams embed Figma frames or other design assets directly into presentations rather than relying on native text rendering for brand-critical type.

Switch to a Chromebook with Linux enabled. On Chromebooks running the Linux development environment, it's possible to install fonts at the OS level — but whether those fonts appear inside the browser-based version of Google Slides is inconsistent and not officially supported behavior.

What Affects Which Approach Makes Sense

A Note on Font Rendering for Collaborators 🖥️

Even when you successfully add a font to your presentation, collaborators viewing or editing the file need the same font to be accessible. Google Fonts are safe here — they're served by Google and render consistently. Fonts added via add-ons are only active for users who also have that add-on installed. If a collaborator opens the file without it, the font may substitute with a fallback — typically Arial or a similar system default.

This is one of the most common points of confusion in team environments: the presentation looks perfect for the creator and inconsistent for everyone else.

Where the Variables Come In

How well any of these approaches works depends on the specific font you're trying to use, whether your Google account allows add-on installation, how much the text in question needs to remain editable, and whether your audience will be viewing the file in Slides or as an exported PDF or video. Each of those conditions changes which method is actually viable — and which creates more problems than it solves.