How to Add Fonts to Figma And Improve Your Designs

Most of the time you never think about fonts in Figma. You type a name into the picker, it shows up, you keep working. Then a client sends over their brand typeface and the picker has no clue what you mean.

Where the font actually lives is what decides that. Google Fonts and Apple’s system fonts sit inside Figma already. Everything else has to get onto your machine first, or get pushed out by someone with admin rights on the account.

Plan level matters less than people assume here. A Starter account and a full Organization account both handle local installs the same way. What changes is who can upload once and have it show up for everyone else.

One useful detail from Figma’s own troubleshooting docs: on Windows the background process is called figma\_agent.exe. If it isn’t running, the installer never ran properly, and no amount of restarting the picker will fix it (Figma Help Center).

What Fonts Can You Add to Figma?

Two file formats get through. TTF and OTF, nothing else.

Web font formats bounce, and there’s no clever workaround inside the app. A font is really just a data file describing glyph shapes, weights, and spacing, and Figma narrows that world down before it ever reaches your text layer.

Adding a font isn’t one process either. There are separate routes in, and they behave differently once the file lands.

Fonts already built into Figma, no setup required
Fonts installed on your own computer through the operating system
Adobe Fonts, synced through a Creative Cloud subscription
Fonts uploaded at the team or organization level by an admin

These don’t talk to each other. A font added through one route does not appear through another.

Install a custom typeface locally and only you see it in the font picker. Upload that same file at the organization level and every teammate sees it next time they open the app.

Google Fonts and Apple System Fonts Are Built Into Figma

Nothing to install here. The entire Google Fonts catalog and Apple’s system fonts load automatically.

Type a name into the font picker on any text layer and Figma searches that catalog live. Photutorial’s tracking of the library put it at 1,826 font families as of May 2025, and that number climbs every few months as new type foundries get added. Roboto is still the most-viewed of the lot, with 28 trillion all-time views across the library (Photutorial).

Apple’s side is smaller and quieter. SF Pro and SF Compact ship inside Figma by default, which covers most of what you’d want for iOS mockups without touching Font Book at all.

There’s a bigger reason to care about both, though.

They’re the only fonts a Chromebook or Linux machine will ever render inside Figma, since neither operating system supports custom local font installation there. If you want the mechanics of the library itself, our guide on how to use Google Fonts covers browsing, filtering, and pairing beyond what Figma’s picker shows you.

The scale of both libraries has become its own story worth tracking, and our breakdown of font statistics goes deeper into how fast these catalogs have grown.

How Do You Install Local Fonts for Figma?

Figma reads fonts from the same place every other app on your machine does. So installing a local font for Figma really means installing it on your operating system, then telling Figma to look again.

Downloaded fonts usually arrive zipped, sometimes with several weight variants bundled into one folder. Unzip everything before you install anything. Otherwise you end up with Regular and nothing else, and you won’t notice until you try to bold something.

On Mac: Install Through Font Book

Installing a font on Mac through Font Book for Figma

Font Book holds every installed typeface on macOS, and it’s the only door Figma has into your system fonts.

Double-click the downloaded TTF or OTF file
Font Book opens automatically with a preview of the typeface
Click Install Font in the preview window
Restart the Figma desktop app so it picks up the new system fonts

Our how to install fonts on Mac walkthrough covers edge cases like validating a font file before installing it, which matters more than people expect once a family stops rendering correctly.

On Windows: Install Through the Fonts Folder

Windows keeps installed fonts in a dedicated Fonts folder. Getting a file in there is basically drag and drop.

Right-click the font file and select Install, or drag it straight into the Fonts folder under Control Panel.

Locate the TTF or OTF file on your computer
Right-click it and choose Install
Close and reopen Figma to refresh the font picker

A font installed this way lives on that machine only. It never reaches a teammate automatically, no matter how many files you send them.

What Does the Figma Font Installer (FigmaAgent) Do?

FigmaAgent is the background service that lets Figma’s browser version read fonts installed on your computer.

Without it, the web app has no way to see what’s sitting in your Font Book or your Fonts folder. The desktop app already bundles this installer, so only browser users need to download it separately.

It runs a local HTTP and HTTPS server on localhost, and it only accepts connections coming from figma.com. Not the open internet. There’s no interface to open, no window, no tray icon doing anything interesting.

You will not see FigmaAgent do a single visible thing, and that’s the point.

It just sits there bridging your operating system’s font list to whatever tab you have Figma open in. A browser restart, or closing and reopening the font picker, is often the fix when a font you just installed refuses to show up.

How Do You Add Adobe Fonts to Figma?

Creative Cloud does the work. It activates fonts locally on your system, and Figma’s Typography panel then finds them the same way it finds anything else installed.

You never download an Adobe font file by hand. Activation is the whole mechanism.

Open the Adobe Creative Cloud desktop app and sign in with your Adobe ID
Go to the Fonts tab and browse or search the library
Click Activate Fonts or toggle Add Family on the typeface you want
Restart the Figma desktop app, or refresh your browser if you’re using the Font Installer
Search the font name directly inside Figma’s Typography panel

The upside is genuine. One synced library across an entire Creative Cloud subscription, no manual downloads, no zip folders to unpack, and it gets refreshed regularly with major foundry additions.

The catch is that none of it is yours. It requires an active paid subscription rather than a one-time purchase, a font vanishes from Figma the moment it gets deactivated in Creative Cloud, and browser access still depends on the Figma Font Installer being installed anyway.

Adobe’s own announcement in April 2025 pushed the library past 30,000 fonts, adding more than 1,500 new typefaces from Monotype in a single update, its biggest expansion in five years.

That update covered proper font licensing for names designers had chased for years, Helvetica and Gotham among them, at no extra cost to existing subscribers.

Whether that library beats the free option depends entirely on what your project needs, and our Google Fonts vs Adobe Fonts comparison lays out where each one actually wins.

How Do You Upload Fonts to a Figma Organization?

Uploading at the organization level puts a custom typeface in front of every member of a team without asking a single person to install anything locally.

Permissions are strict about this. An organization admin uploads at the organization level, a team admin uploads at the team level, and that’s it. The restriction exists because the moment a font uploads, everyone under that account can see and use it.

Figma disclosed 13 million monthly active users in its 2025 IPO filing, with 95% of the Fortune 500 running on the platform. At that kind of scale, asking every designer to individually install the same brand typeface stops being realistic.

Open the file browser and select the team or organization
Click the dropdown next to the name and choose View settings
Select View team’s fonts, then click Upload fonts
Choose the TTF or OTF file and confirm you hold the license to use it
Click Upload, resolving any naming conflict Figma flags

Figma ran into the same problem internally. It commissioned Swiss-American type foundry Grilli Type to design its own custom brand typeface, Figma Sans, as part of a 2024 identity refresh, which is exactly the situation an organization upload is built for: one typeface, everyone on it, no separate local installs drifting apart.

Local Fonts vs Organization Uploaded Fonts in Figma

The deciding question is boring but useful. How many people need this font tomorrow?

Attribute	Individually Installed Font	Organization Uploaded Font
Who can add it	Any individual user	Organization admin only
Visible to	Just that person, on that machine	Every org member automatically
Needs FigmaAgent for browser	Yes	No, once uploaded
Works on Chromebook or Linux	No	Yes

A one-off personal project rarely justifies going through an admin.

Install it locally, use it, move on. Brand typography is a different case entirely, especially once it ships as a variable font with multiple weight axes baked into a single file, since an organization upload keeps every designer on the exact same build instead of five slightly different local installs slowly going out of sync.

Local installs are fast and need no permissions. Organization uploads take more setup but remove the dependency on any one person’s machine.

Why Is a Font Missing or Replaced in Figma?

Open a file on a machine that doesn’t have the font and Figma swaps it for a generic substitute. Silently.

No permission dialog, no warning banner you’d actually notice. It picks a default and keeps the file open, which is how a design ships with the wrong typeface and nobody catches it until a client does.

The usual culprits are dull ones. The font picker hasn’t refreshed since you installed something new. FigmaAgent isn’t running, so the browser can’t see a font that’s plainly sitting on your system. Or a teammate opened the file on a machine that never had the custom typeface in the first place.

Scale makes this worse before it makes it better.

The average marketing or design team’s font collection now runs to 4,500 fonts, and effective auto-activation workflows save the typical designer 34 hours a year that would otherwise go toward chasing down exactly these kinds of gaps (Extensis).

Adobe’s documentation confirms the same mechanism on its end. When a font gets removed from the Adobe Fonts library, any document referencing it locally shows a missing fonts warning and substitutes a default from the program, and once that font is deleted from the project it cannot be re-added.

Before you go hunting, close the font picker and reopen it. Figma sometimes just needs a nudge to re-scan what’s actually installed.

When Font Installation Does Not Work in Figma

ChromeOS held roughly 2.71% of the US desktop operating system market and 1.25% worldwide as of June 2025 (StatCounter). That slice of users hits Figma’s hardest wall: no custom font installation, ever.

The other walls are format-related. TTF and OTF get accepted, WOFF and WOFF2 get rejected with no exceptions, and Linux joins ChromeOS in the no-local-installation column. Google Fonts and Apple system fonts still work on those machines, since nothing needs installing for either one.

A lapsed Creative Cloud subscription and a missing license are two different failure modes, and only one of them is purely technical.

Uploading a font you don’t hold a license for breaks Figma’s Terms of Service the same way it would break any software EULA. Subscription or no subscription.

More than 80% of designers admit they do not read font license agreements at all, and 78% of those who do call the language confusing (Extensis).

That gap between what people install and what they’re actually allowed to use is where organizations get exposed.

France’s anti-piracy agency learned this the hard way. Hadopi rolled out a new logo in January 2010 built on a typeface it had no rights to, and had to pull it within days.

None of this makes Figma’s font system fragile. Every route in just has a hard edge somewhere, and knowing where that edge sits keeps a rebrand from turning into a legal headache.

FAQ on How To Add Fonts To Figma

Do You Need an Adobe Creative Cloud Subscription to Use Adobe Fonts in Figma?

Yes. Adobe Fonts only works inside Figma through an active Creative Cloud subscription, since fonts activate in the Creative Cloud desktop app before Figma’s Typography panel can find them.

Cancel the subscription, and every synced font deactivates immediately.

Is It Safe, Licensing Wise, to Upload a Custom Font to Figma?

Only if you hold the rights to that font.

Figma requires confirming a license before any upload, whether at the individual, team, or organization level, and uploading an unlicensed typeface breaks Figma’s Terms of Service regardless of file format.

Can You Apply a Font to Text Right After Installing It?

Not always immediately. A freshly installed font often needs the Figma desktop app restarted, or the font picker closed and reopened, before it appears in the Typography panel and can be applied to a text layer.

Does Figma Support Variable Fonts?

Yes. Figma reads variable fonts the same way it reads any TTF or OTF file, exposing weight and width axes in the Typography panel, so one file replaces what used to require separate weight files for bold, regular, and light.

Can You Use Fonts Downloaded from a Site Like DaFont?

Technically yes, since Figma only checks file format, not source.

Legally, it depends entirely on that specific font’s license. Sites like DaFont mix public domain, freeware, and commercial-restricted fonts on the same page, so check before shipping client work.

What Should You Set Up First In How To Add Fonts To Figma?

Start by checking whether Google Fonts and Apple’s system fonts already cover what you need, because a lot of the time they do and the rest of this becomes irrelevant.

Brand typefaces belong at the organization level. Get an admin to upload them once. Local installs are the last resort, for one-off personal work nobody else will ever open.

Google Fonts and Apple system fonts, already available
Organization upload, for brand typefaces everyone needs
Local install, for one-off personal fonts only

Doing it in that order costs setup time upfront. Confirming a license and waiting on an admin takes longer than double-clicking a font file on your own machine, obviously. What you get back is a typeface that opens correctly for every teammate from day one.

Once a typeface renders correctly for everyone, the next question is how it reads next to a second typeface, which is the ground covered by pairing fonts within the same brand system.

Author
Recent Posts

Bogdan Sandu

Bogdan Sandu is a seasoned designer who has been designing websites since 2008.

Renowned for his expertise in logo design and visual branding, Bogdan has developed a multitude of logos for various clients.

His skills extend to creating posters, vector illustrations, business cards, and brochures. Additionally, Bogdan's UI kits were featured on marketplaces like Visual Hierarchy and UI8.

He also wrote in the past years on sites like Design Your Way, WebDesignerDepot, WPDean, Designmodo, Speckyboy, Slider Revolution, and more.