How to Add Fonts to Figma — Install, Import & Change Font Size

“I installed the font, but Figma doesn’t show it.” “Where do I even add a font in Figma — there’s no Import button.” “The font works on my desktop but my teammate in the browser sees a different one.” Adding fonts is one of the first walls people hit in Figma, because it works differently from most design tools: there is no font-import dialog inside the editor. Fonts reach Figma through a few distinct routes, and knowing which route you’re on solves most of the confusion.

This guide covers every route in order of effort: Google Fonts (zero setup) → installing local fonts → importing Adobe Fonts → uploading custom fonts on Organization plans. Then it covers the everyday task that follows — changing font size, including several layers at once — and the font pitfalls to expect when your file comes from an Adobe XD migration.

Looking for Japanese-font specifics?

This article covers adding fonts in general. For picking between Japanese families (Hiragino, Yu Gothic, Noto Sans JP) and digging into the “I installed it but it won’t show up” cases, Using Japanese Fonts in Figma goes deeper. Use this article for the setup steps, that one for the Japanese-font detail.

What you’ll get from this article

  • The routes fonts take into Figma, and which one fits your case
  • Step-by-step: installing a downloaded font so Figma can use it (desktop and browser)
  • How Adobe Fonts and Organization custom fonts fit in
  • Fast ways to change font size — single layer, multiple layers, shortcuts
  • Why fonts go missing after an XD → Figma migration, and what to do about it

🗺️ The routes fonts take into Figma

Almost every font you can use in Figma arrives through one of these routes — the first three cover the vast majority of cases:

RouteSetup neededBest for
1. Google FontsNone — preloaded in FigmaShared files, cross-platform teams, quick starts
2. Local fontsInstall on your OS (+ Figma font installer for the browser)Purchased fonts, foundry fonts, system fonts
3. Adobe FontsActive Adobe plan + activationTeams already on Creative Cloud
(4.) Custom font uploadOrganization / Enterprise planCompany-wide brand fonts
(5.) Account font uploadUpload the file in your account settingsUsing one font across every file you open yourself

The fourth row is a special case of “local fonts solved at the team level” — covered in its own section below.

🎁 Add fonts from Google Fonts (no setup)

Figma ships with the Google Fonts library preloaded. Open the font picker in the text settings and the Google Fonts catalog is already there — no download, no installation, nothing to configure.

This route has one underrated advantage: everyone who opens the file sees the same thing. A Google Font renders identically in the browser version and the desktop app, on macOS and Windows, for you and for every collaborator. That makes it the safest default for shared files.

When in doubt, start with Google Fonts

If your project doesn’t require a specific licensed typeface, picking from Google Fonts eliminates an entire class of problems — missing fonts for teammates, browser-vs-desktop differences, and license questions. Move to the other routes when a brand or purchased font requires it.

📦 Before you start: what you need

Most “the font won’t show up in Figma” problems start before Figma is even involved — with the file itself. Three things to check first.

1. The file format. Figma’s help centre is explicit that .TTF and .OTF are the only two formats it supports1. A .woff / .woff2 (web font) or a .ttc collection will not work, even though they’re all “fonts”. If a foundry gives you a web bundle, look for the desktop bundle instead.

2. The ZIP. Font downloads almost always arrive zipped. Extract the archive first — installing from inside a compressed folder is a common cause of a font that appears to install but never shows up.

3. Your platform. ⚠️ ChromeOS and Linux cannot use local fonts at all. Per the help centre, users on those platforms can only use the Google fonts and Apple fonts (SF Pro / SF Compact) that ship with Figma1. If that’s your setup, skip ahead to the org-level custom fonts route — for you it is not one option among several, it is the only one.

Where the font comes from doesn't change the steps

Google Fonts, a paid foundry, a marketplace, or a brand font handed to you by a client — once you have a .ttf or .otf on disk, the installation steps below are identical. The source only changes the licence you’re bound by, not the workflow.

💾 How to install fonts in Figma (local fonts)

“Installing a font in Figma” actually means installing the font on your operating system — Figma then picks it up from there. The flow for a font you’ve downloaded (from a foundry, a marketplace, or a free-font site):

  1. Download the font files. You’ll typically get .ttf or .otf files, often inside a ZIP. Per Figma’s help centre, .TTF and .OTF are the only two formats Figma supports1.
  2. Install them on your OS. This is the step that differs by platform — see the walkthrough below.
  3. Restart or reload Figma. Restart the desktop app, or reload the browser tab.
  4. The font now appears in Figma’s font picker, listed alongside everything else. To find it quickly, set the font menu filter to Installed by you1.

Browser version? One extra tool is required

The desktop app reads your installed fonts directly — steps above are all you need. The browser version cannot see local fonts on its own: you must install the Figma font installer (also called FigmaAgent) — the download link lives in Add a font to Figma1. Without it, locally installed fonts simply won’t appear in the browser’s font list. The desktop app already bundles the installer, so this step is browser-only1.

If a font still doesn’t show up after installing, the cause is usually one of a few known ones — a missing reload, the font installer not running, or a file-format issue. The fonts not showing guide walks through the fixes symptom by symptom.

🖱️ Installing the font on your OS (Mac / Windows)

Step 2 above is the one people get stuck on, because it happens outside Figma and the steps differ per platform. Figma reads whatever your operating system has registered, so getting this right is what makes the font appear.

macOS

  1. Extract the ZIP and locate the .ttf / .otf files.
  2. Double-click a font file. A preview window opens with an Install Font button.
  3. Click Install Font. Font Book opens and validates the file. If it reports a problem with the file, the font is damaged or in an unsupported format — go back to the source rather than forcing it.
  4. To install a whole family at once, select every file, right-click, and choose Open — Font Book queues them together.
  5. Restart the Figma desktop app (or reload the browser tab).

💡 Fonts installed this way land in your user account only. If several people share the Mac and everyone needs the font, install it into Computer rather than User from Font Book’s sidebar.

Windows

  1. Extract the ZIP. ⚠️ Windows lets you preview and even click Install from inside a compressed folder, but the result is unreliable — extract first.
  2. Right-click a font file → Install. For all users on the machine, choose Install for all users instead (this needs admin rights).
  3. To install a family at once, select every file, right-click, and choose Install.
  4. Alternatively, drag the files into Settings → Personalisation → Fonts.
  5. Restart the Figma desktop app (or reload the browser tab).

Installed, but Figma still can't see it?

In almost every case it’s one of three things: the app wasn’t restarted, you’re on the browser version without the font installer (see below), or the file wasn’t extracted from the ZIP. Work through those before assuming the font is broken. The fonts not showing guide covers the rest symptom by symptom.

🔤 How to import fonts into Figma from Adobe Fonts

There is no direct “Adobe Fonts” tab inside Figma, but the route is simple: Adobe Fonts activation works like a local font install.

  1. With an active Adobe plan, activate the fonts you want in Adobe Fonts (via Creative Cloud).
  2. Activated fonts are registered on your system, the same way installed fonts are.
  3. Figma picks them up — directly in the desktop app, or through the Figma font installer in the browser version. Figma’s help centre recommends restarting your Adobe and Figma apps (or reloading the browser tab) after installing new Adobe fonts2.

This is worth knowing for XD users in particular: if your XD designs were built on Adobe Fonts, activating the same families before opening the migrated file in Figma prevents a wave of missing-font warnings.

🏢 Upload custom fonts (Organization / Enterprise)

Figma’s Custom Fonts feature (officially “Upload custom fonts to an organization”) lets an admin upload font files once and make them available to everyone in the organization — no per-machine installs, identical rendering in browser and desktop.

The catch: it’s available on Organization and Enterprise plans only — not Starter or Professional, and only organization admins (org-wide) or team admins (per team) can upload, in .TTF / .OTF format only3. If your team is on those plans and shares licensed brand fonts, this is the cleanest route — and the only one that reaches Chromebook and Linux members. For smaller teams, the practical equivalent is “everyone installs the same font locally” — which works, but requires each member to do it.

You can also upload fonts to your own account

You don’t need an org plan to upload a font file to Figma. Figma’s help centre documents an account-level route: your avatar → Settings → Account → Your uploaded fonts → Upload fonts. Uploaded fonts become available in any file you view or edit and appear under Uploaded by you in the font picker1.

⚠️ It is not a way to distribute fonts to other people. The upload is tied to your account; the only fonts that reach collaborators automatically are Google Fonts and org-level custom fonts. Google Fonts remains the safe default for shared files.

🚀 Fonts intact when migrating from XD — Pixel Fine Converter

The Free tier includes font resolution and baseline correction for migrated text. Convert your own file and judge the quality before deciding.

📏 How to change font size in Figma

Once the font is available, the most common day-to-day operation is changing its size. The options, from simple to batch:

  • Single layer. Select the text layer and set the size in the Typography section of the right-hand panel — Figma’s help centre confirms that the most common text properties, font size included, live there4. Selecting part of the text with the text cursor changes only that part.
  • Multiple layers at once. Shift-click or drag-select several text layers — the size field in the panel now applies to all of them. This is the quickest “make everything bigger” move.
  • Keyboard shortcut. With text selected, decrease / increase font size with Shift + Cmd + < / > (macOS) or Shift + Ctrl + < / > (Windows). Note that key combinations can vary with keyboard layout.
  • Same-font bulk edits. The exact command is Edit → Select all with → Select all with same font5; select every layer using that font, then change the size once. ⚠️ The selection is scoped to the current page, so multi-page files need one pass per page.

For recurring sizes, define text styles so a size change in one place updates every layer using the style — that’s the maintainable version of bulk size editing. For renaming-scale operations across a whole file (changing every font, not just sizes), see the bulk font change guide.

🖥️ Browser version vs desktop app — where fonts differ

Almost every “the font isn’t there” report traces back to this difference:

  • Desktop app: reads OS-installed fonts directly. Local fonts, Adobe Fonts activations, and Google Fonts all appear with no extra tools.
  • Browser version: Google Fonts work out of the box; local fonts (including Adobe Fonts activations) require the Figma font installer. No installer, no local fonts — and Figma silently falls back instead of erroring.

If your team mixes both, prefer fonts everyone can resolve (Google Fonts, or org-level custom fonts) for shared files. A file that depends on one designer’s locally installed font will substitute for everyone else.

🔍 The font won’t show up — 5 causes

Installing a font and not seeing it in Figma is common enough that it deserves its own checklist. Work down this list — the causes are ordered by how often they turn out to be the culprit.

#CauseQuickest check
1The font isn’t actually installed on the OSOpen Font Book (Mac) or Settings → Fonts (Windows) and search for it there, not in Figma
2Browser version without the Figma font installerDoes the font appear in the desktop app but not the browser? Then it’s this
3The name doesn’t match — common after an XD → Figma migrationCompare the exact family name in the file against the one in your font list
4A shared file, and your teammate doesn’t have the fontIt renders for you and not for them — the font is local to your machine
5The font cache is out of syncRestart Figma completely (quit, don’t just close the window)

⚠️ Before any of the above: did you restart Figma? A font installed while Figma is open will not appear until the desktop app is restarted or the browser tab is reloaded. This alone accounts for a large share of cases.

Why Figma fonts aren’t showing takes each of these five causes apart symptom by symptom, and includes a flow for narrowing it down in about five minutes.

🔄 Fonts when migrating from Adobe XD

Migrated files add one more thing to watch in font management: every text layer in the XD file references a font by name, and that reference has to resolve correctly on the Figma side.

  • If the font is available (installed locally, activated via Adobe Fonts, or a Google Font), the text lands with its original family.
  • If it isn’t, Figma flags missing fonts and substitutes — and substitution can shift metrics, weights, and line breaks across the whole file. Clicking the missing font icon in the left sidebar opens the Missing fonts modal, which lists what’s missing and which layers are affected6.

The practical order of operations: add the fonts to Figma first (using whichever route above fits), then import the design. That “what comes first” question applies to the migration as a whole, so if you haven’t mapped out the sequence yet, the step-by-step XD → Figma migration guide sets the order up front and heads off the rework that isn’t font-related too. For CJK text the stakes are higher still — substitution can land on the wrong regional glyph shapes; the CJK fonts guide covers that angle, and the Japanese text fidelity guide goes deep on how conversion accuracy is verified. Pixel Fine Converter reads the XD file directly and resolves fonts and baselines as part of the conversion, so migrated text needs less manual cleanup.

💬 FAQ

Q: Why doesn’t my installed font show up in Figma? Most often: the browser version without the Figma font installer, or Figma wasn’t reloaded after the install. Install the font installer (browser) or restart the app (desktop), then reload. If it still doesn’t appear, see the fonts not showing guide.

Q: Can I add a font to Figma without installing it on my computer? Yes — three ways: pick it from Google Fonts (preloaded), activate it via Adobe Fonts (with an Adobe plan), or have an admin upload it as an organization custom font (Organization/Enterprise plans).

Q: Do fonts I add appear for my teammates too? Only Google Fonts and organization custom fonts are automatically shared. A locally installed font is visible only on machines that have it — teammates without it will see a missing-font notice and a substitute.

Q: How do I change the font size of many text layers at once? Select multiple text layers and edit the size field once, or use Edit → Select all with → Select all with same font5 for font-wide sweeps. For systematic control, move recurring sizes into text styles.

Q: My fonts were fine in XD but broke after moving to Figma. Why? The migrated layers reference fonts that aren’t available in Figma yet. Add the fonts first (install locally / activate in Adobe Fonts), then re-import — or use a migration-focused converter that resolves fonts and baselines during conversion.

Q: How do I upload a font to Figma? There are two upload routes, plus the classic install route. For yourself, go to Settings → Account → Your uploaded fonts → Upload fonts; the font then works in any file you view or edit1. For a whole team, an admin on an Organization or Enterprise plan can upload custom fonts for everyone3. And you can always skip uploading entirely by installing the font on your operating system (plus the Figma font installer in the browser). Note that an account-level upload does not distribute the font to collaborators.

Q: How do I add a downloaded font to Figma? Install the downloaded .ttf / .otf file on your OS (double-click → Install on macOS, right-click → Install on Windows), then reload Figma. In the browser version, also install the Figma font installer so the downloaded font appears in the picker. The install local fonts section above has the full flow.

🎯 Recap

Adding fonts to Figma comes down to picking the right route and knowing the one browser-version catch:

#PointWhat to do
1Default to Google FontsZero setup, renders the same for everyone — the safest shared-file choice
2Local fonts = OS installInstall on macOS/Windows, reload Figma; desktop app needs nothing else
3Browser needs the font installerLocal and Adobe fonts won’t appear in the browser without FigmaAgent
4Share fonts at the right levelOrg custom fonts for company brand fonts; otherwise everyone installs the same files
5Fonts before migrationAdd the fonts first, then import the XD design — substitution is harder to undo than to prevent

Get the route right and fonts in Figma become a one-time setup instead of a recurring mystery. And if your file history starts in Adobe XD, preparing the fonts carefully before the move is a reliable way to keep the conversion safe.

🚀 Install Pixel Fine Converter from Figma Community

One-click install from Figma Community

Everything in this article that describes Figma’s own behaviour is cited to Figma’s official documentation (see below). Everything about Pixel Fine Converter’s font resolution and baseline correction is first-hand: it comes from our own source code and hands-on testing.

Sources

  1. Add a font to Figma — the supported .TTF / .OTF formats, the Figma font installer (FigmaAgent) being browser-only and bundled with the desktop app, the lack of additional font support on ChromeOS / Linux, and the account-level upload flow (Settings → Account → Your uploaded fonts) with the Installed by you / Uploaded by you filters (verified 2026-08-19) ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8

  2. Access and troubleshoot missing Adobe fonts in Figma Design — reaching Adobe fonts from Figma, and the recommended app restart / tab reload after installing (verified 2026-08-19) ↩

  3. Upload custom fonts to an organization — Organization / Enterprise plans only, uploads restricted to org and team admins, .TTF and .OTF only (verified 2026-08-19) ↩ ↩2

  4. Explore text properties — font size and the other common text properties living in the Typography section of the right sidebar (verified 2026-08-19) ↩

  5. Select layers and objects — the options in the “Select all with” submenu and how to reach it (verified 2026-08-19) ↩ ↩2

  6. Missing font alert in Figma Design — the missing font icon and the Missing fonts modal (verified 2026-08-19) ↩