Skip to main content
Question

Missing Fonts Issue

  • May 28, 2026
  • 27 replies
  • 698 views

Rich Dean

Everything was working absolutely fine yesterday, but when I started work today, I now have an issue where I can’t edit any of the text layers in my project.

If I double click within the text to edit it, I get a ‘missing fonts’ popup where it asks me to relink the fonts. I do this, but it doesn’t take effect - it just keeps looping the same thing whenever I try to edit any text.

I’m on a MacBook Air running Tahoe 26.5, and I’m getting the same issue on both the desktop app and the browser version.

The fonts in question are Avenir, which is a Mac system default font, and Font Awesome Pro Plus 7.2.0, which I’ve purchased, but when I try and choose other fonts, some (but not all) are also affected, for example, Gill Sans, which is also a system default installed font.

I’ve tried deleting and reinstalling Figma, and I’ve also tried the same fonts in other apps like Textedit and Microsoft Word, and the fonts work fine in those apps, so this is definitely a Figma-specific issue.

At the moment, I can’t use these fonts and I’m having to update all my font styles to use other system fonts that look very similar, but that’s not a long-term solution. The client project I’m working on requires Avenir as their brand font, so this needs fixing ASAP.

I’m a freelancer and I’ve just wasted nearly two hours of my working day trying to figure out why the fonts that worked perfectly fine only yesterday, now don’t. This is clearly a Figma issue, perhaps related to an overnight update that wasn’t properly tested, but please can you fix this!

27 replies

Gayani_S
Figmate
  • Community Support
  • May 28, 2026

Hey Rich, thanks for reaching out and for the detail you've already shared!

A few things worth trying:

  1. Check Font Book for duplicates or conflicts. Open Font Book (Applications > Font Book), search for Avenir and Gill Sans, and look for any entries flagged with a yellow warning dot. If there are duplicates, resolve them (right click > Resolve Duplicates). A conflict here can stop Figma from reading the font correctly even though it works fine elsewhere.
  2. Validate the fonts in Font Book. Select the font, then go to File > Validate Font. If anything comes back with a warning or fail, try removing and reinstalling the font from a clean source.
  3. For Font Awesome Pro specifically, check that the exact version installed matches what was originally used in your file. Figma is sensitive to version differences, and even a minor update to a purchased font can trigger the missing font loop.
  4. Check your macOS Tahoe privacy permissions for Figma. Go to System Settings > Privacy and Security > Full Disk Access and make sure Figma and FigmaFontHelper are both listed and enabled. On Tahoe, tightened permissions can silently block font access.
  5. Reinstall the Figma Font Helper. Even on the desktop app, the font helper can get out of sync after an OS update. You can find the latest version and reinstallation steps in Troubleshoot the Figma Font installer.

A couple of other Help Center articles that are worth checking:

 

Let me know how you get on, happy to help further!


Rich Dean
  • Author
  • New Member
  • May 28, 2026

Hi ​@Gayani_S thanks for your response, but unfortunately this hasn’t resolved it.

In answer to your points:

  1. I’ve checked in Font Book and there are no duplicate versions of any of the affected fonts. No warnings etc.
  2. I’ve also validated the fond and get the green tick, so no issues there.
  3. For Font Awesome Pro, and indeed all the fonts, nothing has changed since yesterday. They were all working fine then, but something has changed overnight.
  4. I’ve checked the MacOS privacy settings. Initially, neither Figma or FigmaFontHelper were on the list of allowed apps. I was able to add and enable the main Figma app, but I couldn’t locate FigmaFontHelper to add that as its not in the applications folder that the Full Disk Access setting allows you to access.
  5. I’ve reinstalled the Figma Font Helper multiple times today, but it still doesn’t resolve it.

From checking further, this is actually affecting many fonts from other design files for other client projects, i.e., when I open other Figma projects from the last few days/weeks, they all seem to be affected, for other fonts too.

From just trying again, I went through this process:

First, I tried again to relink what Figma thinks are the missing fonts in the desktop app, but it still doesn’t work:

I then tried the web browser version in Chrome, but here, it wouldn’t even allow me to select Avenir from the list of fonts - it wasn’t in the list:

I then followed the blue link below to install the font installer again. I already have the desktop app and that’s working fine, so I just installed the font installer. Once that was installed, I went to try and connect:

But then I got an error saying that it thinks the font installer and desktop app aren’t running, so it couldn’t connect. But both definitely are:

I even opened Figma’s settings and got the following:

So the fact that Figma won’t load these fonts, and browser version can’t connect to either the font installer or the desktop app, feels like it’s related.

Something has definitely changed overnight, and this is definitely a Figma-specific issue, but please can you look into this further, as I’m having to use a hacky workaround whereby I’m having to use another font that looks similar to Avenir for the parts that I need to edit, but that’s not a long-term solution, and to be honest, I moved over to Figma from Sketch over a year ago, have been very impressed so far, but this is majorly putting me off, and if I can’t make basic text edits, I may need to consider whether I keep using Figma.


Pavel_Gerda
  • New Member
  • May 28, 2026

Hello! I have identical problems and yes, I tried all the suggestions above. It also happened exactly today.


Ryan_Battles

I have this problem today as well on MacOS Tahoe. Seems that an update caused it. I cannot edit any text across projects without being prompted for missing fonts.


Rich Dean
  • Author
  • New Member
  • May 29, 2026

@Gayani_S this is clearly a new and consistent issue with Figma, please can your developers look into this as a matter of urgency, as more users are now experiencing the same issue.


Louis Duflos

Just updated Figma and facing the same issue. Can’t work at all since none of the fonts are working.


Pavel_Gerda
  • New Member
  • May 29, 2026

Hello guys! Not sure if this will help you, but I fixed this issue for myself. First, I noticed that FigmaAgent wasn't running, so this might be the key symptom. Then I deleted Figma with a 3rd-party cleaner (I used PearCleaner) and reinstalled it. After that, FigmaAgent launched normally and the issue is now gone.

Even though deleting and reinstalling is the most common advice, I believe the key point here is to delete it with a cleaner that also removes all associated files. Simply dragging Figma to the Bin won't help.


Gayani_S
Figmate
  • Community Support
  • May 29, 2026

Hey everyone, thanks for your patience while I look into this further and a huge thank you to ​@Rich Dean for the incredibly detailed breakdown and screenshots, that's really helpful and I've made sure to share it all with our internal team.  Also big props to ​@Pavel_Gerda who shared the PearCleaner workaround!

I'll be back as soon as I hear from the team.


jamiehabanero

Not sure if this will help ​@Rich Dean but I had the same issue and I updated my OS to Tahoe 26.5… It seems to have resolved the issue. Best of luck!


FarshadY
  • New Member
  • May 30, 2026

I have the exact same problem and encountered it right after the new Figma update.
I’ve also upgraded macOS to Tahoe 26.5 but the problem still persists.


sonianines

I had the same issue after the Figma update.

What I tried (but didn't work):

  • Updated to macOS 26.5

  • Deleted and reinstalled Figma

  • Reinstalled fonts

  • Restarted Mac

What worked:

  • Figma desktop app menu bar: Help > Troubleshooting > Reset Figma and Restart

Hope this helps.


Rich Dean
  • Author
  • New Member
  • June 1, 2026

Thanks ​@sonianines, unfortunately I just tried resetting and restarting the Figma desktop app, but that didn’t work for me.

@Gayani_S any updates on a fix for this?


FarshadY
  • New Member
  • June 1, 2026

Many Thanks @sonianines but it didn’t work for me too.
I believe I started experiencing this issue after the latest Figma update, so I'm eagerly looking forward to a new update.


jojobanks
  • New Member
  • June 1, 2026

I’m experiencing this issue as well… All the font links are broken, text fields uneditable.

I spent the whole day working off the Web browser app instead which was quite slow and clunky at times. There is definitely a problem with the latest Figma update. Is there a way to roll back perhaps?


amirhpanahi
  • New Member
  • June 1, 2026

I’m experiencing exactly the same issue and it’s becoming a serious blocker.

Everything was working perfectly. Yesterday, suddenly, I can no longer edit text layers. Whenever I try to edit text, Figma reports missing fonts and asks me to relink them. After relinking, nothing changes and the same dialog appears again in an endless loop.

 The fonts are installed correctly and work without any problems in other applications, so this appears to be a Figma-specific issue.

I’ve already tried:

  • Restarting Figma
  • Reinstalling Figma
  • Verifying the fonts are installed and working in other apps

Nothing has resolved the problem.

This is extremely disruptive because it affects existing production files and makes it impossible to work normally. I’ve already lost several hours trying to troubleshoot something that was working perfectly less than 24 hours ago.

If anyone from the Figma team is monitoring this thread, please investigate this issue. It seems like multiple users are experiencing the same behavior, which suggests it may be related to a recent update rather than individual font installations.

Any workaround or update would be greatly appreciate


Rich Dean
  • Author
  • New Member
  • June 1, 2026

Okay so something else I’ve spotted today: the issue seems to happen differently depending on what the font is.

So to explain what I mean by this, for the client project I was working on last week that used Avenir as the brand font, this still doesn’t work on either the browser or desktop version of Figma. On both, if I try to edit any text layers using that font, it gives me the looping relinking dialogue where I relink the fonts but it doesn’t take effect.

But this week, I’m working on another project for a different client, where this time the brand font is Fig Tree. This isn’t a Mac system default font like Avenir; it’s a free font from Google fonts, but in this instance, I still get the looping relink issue in the desktop app, but I can edit the text layers fine in the browser version.

This suggests the issue could be something to do with the way Figma recognises and/or links fonts via the internet. Perhaps because Avenir is a fully locally installed font for me, the issue in Figma is that some kind of internet-linked connection to recognise the font isn’t there, but with Fig Tree, because it’s available online via Google Fonts, perhaps Figma can recognise it via the browser version (which is also online) but not the desktop version??

Either way, it’s something that the Figma developers need to resolve.

@Gayani_S again, is there any update on when this will be fixed? It’s been days now. Editing text is a fundamental requirement of a design app, so this really isn’t acceptable.


FarshadY
  • New Member
  • June 2, 2026

Hi ​@Gayani_S , Do you have any new information about fixing this issue?
It's hard for my clients to understand how editing a few simple texts in their project can take more than five days!!!
 


amirhpanahi
  • New Member
  • June 3, 2026

He @Gayani_S , I’ve had tasks pending for the last four days that haven’t been completed solely because I’m unable to edit these texts. I have no visibility on when this critical issue will be resolved. Please follow up and fix this as soon as possible, as clients are waiting and I don’t think they can be expected to wait any longer.


Gayani_S
Figmate
  • Community Support
  • June 3, 2026

Hey everyone, thank you for your continued patience! I know this has gone on longer than it should. 

 

Thanks ​@sonianines for sharing the Help > Troubleshooting > Reset Figma and Restart tip, worth trying if you haven't already!

 

Our engineering team is actively investigating, and to help them move faster, there are two things I'd like everyone to try and report back on:

  1. Check your desktop app version, go to Figma menu bar > Figma > About Figma and drop the version number in a reply here.
  2. Try the Figma beta app, download it from Figma downloads and let us know whether switching to the beta resolves the font issue for you.

 

@jojobanks on rolling back, unfortunately there isn't a way to revert to a previous version of the Figma desktop app directly. The beta app is the best alternative path right now while the team works on a fix, so that's the one I'd point you towards.

 

@amirhpanahi I hear you, and I want to be clear that the team is taking this seriously. A bug that blocks text editing across production files is not something we'd treat lightly. The beta app is your best shot at an unblocked workflow while we work towards a proper fix.

 

To everyone in this thread, I'll update this thread as soon as I hear back! 


FarshadY
  • New Member
  • June 3, 2026

Hi ​@Gayani_S
Thank you for following up on this issue. I installed the beta version, and the problem has been resolved.

Best regards,


P.S. After encountering this issue, I assumed that a very large number of Figma users would run into the same problem. However, the number of people who shared their experiences in this thread was far lower than I had expected.
I realized the answer when I had a phone call with one of my colleagues today. Even though we are using the same version of macOS, Figma app and the same Font, she is not experiencing this issue!

macOS: Tahoe 26.5
Figma Desktop App version 126.4.11


amirhpanahi
  • New Member
  • June 3, 2026

Thanks for your follow-ups, @Gayani_S. I downloaded the beta version a few minutes ago, and it worked!

My Figma version is: Figma Desktop App 126.4.11
My macOS version is: 15.3.1


Ryan_Battles

Reset Figma and Restart didn’t fix the issue for me, but the beta is working fine.

My Figma version is: Figma Desktop App 126.4.11
My macOS version is: Tahoe 26.5

 


Rich Dean
  • Author
  • New Member
  • June 4, 2026

Hi all,

 

So good news, looks like we have a proper fix… almost!

 

In addition to this forum post, I raised a proper support ticket a few days ago, and earlier today, Anju from the support team came back to me with the following email:

 


Thank you for your patience while we looked into this.
 
I checked with our engineering team, and they believe they understand the issue.
 
As a short-term workaround, could you please either:

The team believes either of these versions should resolve the issue.

 

 

So I tried deleting the version of Figma I had installed, re-downloading the standard version (126.5.x) from the main Figam website, and installing that version… but it DIDN’T work.

 

So, I deleted that version and then downloaded the beta version (126.6.x), and that seems to have fixed the issue.

 

In terms of next steps, I’ve replied to Anju stating that the 126.5.x version is still broken but that the beta 126.6.x version seems to be fine, so hopefully whatever the difference is, they will roll out to the standard version.

For now, I’m going to carry on using the beta version until the standard version is properly fixed.


Lance Malbon

I just did the update today, and am now locked out of text edits, why is this update still being pushed out!? Figma beta fixed it but not before I wasted half an hour I really needed reading through this thread.


Gayani_S
Figmate
  • Community Support
  • June 5, 2026

Hey everyone, really glad to hear the beta is working for those of you who've tried it. And thank you @FarshadY, @amirhpanahi, and @Ryan_Battles for reporting back so quickly.

And a huge thank you to @Rich Dean for raising a support ticket on top of everything here, and for sharing our team’s response with the whole thread. Also really useful to know that 126.5.x didn't work for you even after a clean reinstall, I'll made sure the team is aware.

Our engineering team has now confirmed that this is affecting to users on desktop app version 126.4.x where FigmaAgent isn't running correctly. Here's what to do:

Download the beta app (126.6.x or newer). You can get it from Figma downloads. Note: updating to the stable 126.5.x version doesn't appear to fully resolve the issue for everyone, so we'd recommend going straight to the beta for now.
 

@Lance Malbon, really sorry you got hit by this today, the beta should get you unblocked.

 

The team is working on getting a proper fix into the stable version, I'll update this thread as soon as that's available.

Thank you for your patience in the meantime!