The font has to be switched on inside Creative Cloud first. That single step is where most walkthroughs get vague, and it’s the reason a typeface you can plainly see on fonts.adobe.com refuses to appear in Figma’s dropdown.
Figma never talks to Adobe directly. It reads whatever font list your operating system reports, and activation is what puts an Adobe font on that list. Once it’s there, the desktop app and the browser version both see it, which is what keeps a licensed brand typeface consistent for everyone working off the same file.
One catch before you start. Activation only works on Windows and macOS, because the Creative Cloud desktop app it relies on doesn’t run anywhere else, per Adobe’s subscription documentation updated in October 2025.
What Is Adobe Fonts in Figma?
There’s no integration panel to open, no plugin to install, no Adobe login buried in Figma’s settings. Activated fonts land in your system font list, and Figma picks them up from there like any other installed font.
Which makes it different from dragging a font file into a project. Nothing gets installed inside Figma. The real work happens somewhere else entirely, before Figma is even involved.
Adobe’s library ships more than 30,000 typefaces from over 150 type foundries as part of a Creative Cloud membership (Adobe, 2025). That’s a lot of type to have sitting behind a toggle.
You can activate from fonts.adobe.com or from the Fonts tab in the Creative Cloud desktop app. Both routes end up in the same place, registering the font with your machine.
- The activated font joins your operating system’s font list
- Figma’s dropdown shows it after the app or browser tab refreshes
- Every other Creative Cloud app on that device gets it too
No plugin sits between Adobe and Figma. The operating system does the handoff.
Adobe Fonts vs Google Fonts vs Custom Uploaded Fonts in Figma
Non-default type gets into Figma a few different ways, and each one asks something different of you before the name shows up in the dropdown menu.
| Font Source | Setup Step | License Scope | Collaborator Requirement |
|---|---|---|---|
| Adobe Fonts | Activate in Creative Cloud | Tied to Creative Cloud subscription | Needs own activation |
| Google Fonts | Built into Figma, no setup | Open source, free to use | None, works for everyone |
| Custom uploaded font | Install the font file locally | Depends on the font’s own license | Needs the same file installed |
Google Fonts asks for nothing at all beyond an internet connection, since Figma bundles that library directly.
Have you seen the latest Figma statistics?
Discover comprehensive Figma statistics including revenue growth, market share, user demographics, and funding data.
Check them out →Custom uploads usually arrive as an OpenType or TrueType file, the two formats most independent foundries sell.
The full process for adding fonts to Figma, uploads and Google’s library side by side, gets its own detailed walkthrough.
- Reach for Adobe Fonts when the brand typeface is already licensed through Creative Cloud
- Google Fonts is the fast, license-free option, and there’s genuinely nothing to configure
- A custom upload covers anything proprietary or purchased that lives outside both libraries
How Does Adobe Fonts Sync With Figma?
Activating a font in Creative Cloud registers it with your computer’s operating system. Figma reads that same list the way it reads any locally installed font.
It keeps no separate database of Adobe fonts. It just checks what your machine already reports as available.
So activation matters more than downloading here. A font can sit on Adobe’s servers indefinitely without ever touching your machine’s font list until that toggle flips.
Figma won’t notice the change on its own, either. It has to re-read the list, which is why a restart or a browser refresh always follows activation.
FigmaAgent handles the browser side. It runs a small local server so browser-based Figma can read the same font list the desktop app already sees.
That local server accepts connections only from figma.com and resolves through the loopback address 127.0.0.1, according to Figma’s help documentation.
Not every platform works this way. WordPress sites built on Adobe Fonts pull the typeface through an embed code instead, a setup covered separately for adding Adobe fonts to a WordPress site.
Figma just borrows whatever local font access the operating system already grants it.
Do You Need a Paid Creative Cloud Plan for Adobe Fonts in Figma?
Yes for the full catalog. Technically no for a trimmed one. Adobe splits font access into tiers, and only the free tier caps what you can activate.
- Free Creative Cloud accounts get a basic library of roughly 5,500 fonts (Adobe, October 2025)
- Paid Creative Cloud, Adobe Express, and single-app plans unlock the complete catalog (Adobe, October 2025)
- Adobe has run three separate access levels, Free, Standard, and Pro, since Fall 2022 (Adobe)
Every level needs you signed into the Creative Cloud desktop app with a named-user subscription. A device license or a site-wide license won’t activate fonts at all, per Adobe’s own documentation. That trips up a lot of agencies running shared machines.
None of this touches what you pay Figma. A comparison of Figma’s free and professional tiers covers seat limits and file storage, which is a completely separate decision from your font access.
Two subscriptions, two bills, two unrelated reasons to upgrade.
How Do You Set Up the Figma Font Installer (FigmaAgent)?
FigmaAgent is the small helper program that lets browser-based Figma read fonts installed on your computer, Adobe or otherwise. The desktop app already includes it, so the download only matters if you work in the browser.
Desktop users have it easy. The installer ships inside the app, and fonts appear automatically once Creative Cloud finishes activating them.
Browser users need the separate download for Windows or macOS, plus a tab reload afterward before new fonts register.
Desktop App Method
Installing the Figma desktop app is the whole step. The font installer comes bundled, so there’s nothing extra to configure once Creative Cloud has activated your font.
- Download and install the Figma desktop app for macOS or Windows
- Sign into Creative Cloud and activate the fonts you need
Browser Installer Method
Browser-based Figma needs FigmaAgent installed once per computer before any local or Adobe font becomes selectable.
- Go to Figma’s downloads page and get the font installer for your operating system
- Open the downloaded file from your Downloads folder
- Click through the install prompt, labeled Install on Windows or Install Figma Agent on Mac
- Reload any open Figma browser tab to pick up the newly available fonts
You run the installer once and forget about it. FigmaAgent stays active in the background and keeps checking your system font list on its own.
How Do You Activate an Adobe Font Before Using It in Figma?
Activation happens in Creative Cloud, not in Figma, and it has to happen before the font appears anywhere on your device. Skip it and you’ll spend twenty minutes reinstalling things that were never broken.
- Open the Creative Cloud desktop app and sign in with your Adobe ID
- Select the Fonts tab, or go to fonts.adobe.com in a browser
- Search for the typeface and open its font family page
- Click the activation toggle next to the specific font weight you need
- Wait for the confirmation that the font moved to your active list
It usually finishes in a few seconds, since the font installs locally in the background.
Weights and styles activate individually, which catches people out constantly. Turning on Regular does nothing for Bold or Italic, and you’ll only find out when the dropdown shows one weight and nothing else.
Variable fonts behave differently. A single activation can cover the entire weight range inside one file.
How Do You Apply an Adobe Font to Text in Figma?
Once activation and syncing are sorted, this part is unremarkable. It works exactly like selecting any other installed font.
- Restart the Figma desktop app, or hard refresh the browser tab with Ctrl+Shift+R on Windows or Cmd+Shift+R on Mac
- Select an existing text layer, or create one with the text tool
- Open the font dropdown menu inside the text properties panel and type the font’s name to filter the list
- Click the font to apply it to the selected text
That refresh has to come first, not after. Refreshing once the font is already missing from the dropdown doesn’t help.
The mechanics of selecting and editing text in Figma stay identical no matter which font source you’re pulling from, and that process gets its own separate walkthrough.
If the font still isn’t in the dropdown after all that, the problem sits upstream in activation or syncing.
Why Is an Adobe Font Missing or Not Showing in Figma?
A missing font in Figma is almost never a Figma bug. The cause is somewhere behind it, and the fixes don’t overlap, so working through them as one problem wastes a lot of time.
| Cause | Where to check | Quick fix |
|---|---|---|
| Font not installed on this device | Creative Cloud active fonts list | Activate the font locally |
| Font deactivated from inactivity | Removed tab in Creative Cloud | Re-add the font family |
| Conflicting font versions | Font name in the dropdown | Remove the duplicate, keep one |
| Cache not refreshed | Figma app or browser tab | Restart or hard refresh |
Font Not Installed on This Device
Text a collaborator set in an Adobe font won’t render on a machine that never activated that exact family. Figma flags it with a missing-font warning inside the text layer and offers to swap in a substitute, which is usually the moment somebody accidentally accepts the substitute and ruins the file.
- Open Creative Cloud and check the active fonts list for that exact family
- Activate it there, then restart Figma
Font Deactivated From Inactivity
Adobe quietly cleans house. Fonts left untouched for several months expire from your system, though they stay visible in your Adobe Fonts selections until you remove them for good (Adobe, 2023).
This happens on fully paid, perfectly active subscriptions. It’s maintenance behavior, not billing.
- Open the Removed tab in Creative Cloud or on fonts.adobe.com
- Select Add family next to the expired font to bring it back
Conflicting Font Versions
Two copies of the same family, one from Adobe and one you installed manually years ago, can register under slightly different internal names.
Figma then treats them as separate entries. Text set with one won’t recognize the other as a match, and the dropdown shows what looks like the same font twice.
Pick one source and delete the other. Keeping both is how the problem started.
| Version | Managed through |
|---|---|
| Adobe-activated | Creative Cloud |
| Manually installed | Operating system font folder |
Cache Not Refreshed
Sometimes the font is completely fine and Figma just hasn’t reread the list.
A stale browser cache, or a Figma session you left open since yesterday morning, will hold onto an outdated font list and hide something that’s already active on your machine.
Hard refresh the tab, or quit and reopen the desktop app. Takes ten seconds and solves it more often than it should.
Do Collaborators Need the Same Adobe Font Installed in Figma?
Yes. Everyone who needs to see the correct font has to activate it on their own machine. Doing it once on the file owner’s computer covers exactly one person.
This isn’t Figma being restrictive. It’s licensing.
Adobe’s font terms don’t allow an activated font to be transferred to another user or computer. A collaborator needs their own Creative Cloud subscription or a separate desktop license before the font renders for them (Adobe, 2026).
- Confirm every teammate has an active Creative Cloud subscription, not just the file owner
- Share the exact family and weight name, because somebody will otherwise activate a close match and swear it’s identical
A shared file can look perfect on one screen and broken on the next, purely because of who’s signed into what.
Can You Use Adobe Fonts on a Published Figma Sites Website?
Not directly, and not through the activation you use for design files.
Figma Sites needs an actual web font file or embed code. A published site has no way to read fonts sitting on your computer.
Native custom font support arrived in Figma Sites on September 18, 2025, though it still expects a .woff or .woff2 file rather than an activated Creative Cloud font (Figma, 2025).
Adding the Font via Custom Code
Adobe Fonts won’t hand you a .woff file. You get a link and style code snippet instead, the same thing you’d drop into any regular website.
- Copy the embed code from your font’s page on fonts.adobe.com
- Open your Figma Sites file and go to Site settings
- Find the Custom code section in the site settings sidebar
- Paste the code into the start or end of the head section
Figma’s own support team points users to this method, which tells you plenty about how close native Adobe Fonts integration for Sites actually is.
Licensing for Web Embedding
Embedding Adobe Fonts on a live website falls under a different license from the desktop one you’re using inside Figma’s editor.
- The desktop license covers fonts used inside Figma’s design canvas
- The web font license covers the embed code running on a published site
Worth knowing before you plan a rollout: organization-wide shared custom fonts in Figma Sites are only available on Organization and Enterprise plans. Everyone else uploads their own font file per project (Figma).
And if the underlying Creative Cloud subscription lapses, the web font license goes with it. That breaks the embed code on a live site, not just the design file.
When Does Adobe Fonts Not Work in Figma?
The failures are predictable rather than random.
- With no active Creative Cloud subscription, nothing activates and previously activated fonts stop updating
- Cancel the subscription and already-applied fonts stop rendering in editable files
- A collaborator without their own license sees a substitute font instead of your actual choice
- Figma Sites without the embed code or web font file falls back to a system font on publish
- An offline device leaves Creative Cloud unable to confirm activation, since it can’t reach Adobe’s servers
- Packaging a font for a print bureau or another user isn’t allowed at all under Adobe’s license
Cancellation hits two places at once. Desktop documents show a missing-fonts warning and drop to a default font, and any published site using the web font embed falls back to whatever’s next in the font stack (Adobe, 2026).
Reactivating the font, or resubscribing, reverses both. No extra setup required.
FAQ on How To Add Adobe Fonts To Figma
What Font Format Does Adobe Fonts Use in Figma?
The format never surfaces to you, because Creative Cloud handles activation. A custom upload still needs an OpenType or TrueType file, but an activated Adobe font just appears in Figma’s dropdown once Creative Cloud syncs.
Is Adobe Fonts Worth It for a Solo Freelancer Versus a Team?
A solo freelancer activates once and never thinks about license portability again. Teams pay the same subscription price per seat, and every collaborator needs their own activation, so the real cost scales with headcount rather than how many fonts you use.
Can Adobe Fonts Be Used for Commercial Client Work in Figma?
Yes. Adobe’s font terms cover personal and commercial use, client projects delivered as rasterized files included.
Your client only needs their own Creative Cloud license if they plan to edit the live text layer and access the activated font.
Does Reinstalling Figma Fix a Missing Adobe Font?
Only sometimes. It clears a stuck cache, which handles fonts stranded on an old font list.
It does nothing for a font that was never activated, one that expired from inactivity, or one conflicting with a second copy installed outside Creative Cloud.
What Should You Fix First in How To Add Adobe Fonts To Figma?
Start with activation, always. A font that was never activated in Creative Cloud stays invisible no matter which installer you reinstall or which browser setting you poke at afterward.
Work through it in this order: activation status in Creative Cloud, then the font installer or desktop app sync, then the browser cache or a Figma restart. Most setup problems die somewhere in the first two.
Adobe restricts desktop font activation to Windows and macOS, and Figma’s browser version separately requires its own installer.
Put those two facts together and you get one hard limit. Chrome OS and Linux devices cannot run Adobe Fonts inside Figma at all, whichever client you try.
Once the font renders properly, the useful next move is folding it into text styles as part of a design system in Figma.
