Skip to main content

We are experiencing a critical issue affecting our team and our clients:

Out of nowhere, when trying to edit a text layer, Figma suddenly shows a “Missing Font” warning. The file had been working perfectly for months — no changes were made to fonts, library, or system settings before the error appeared.

When we relink the missing font to the correct local font, all connected text styles lose their hierarchy. Text reverts to default settings, and we have to manually reapply all styles across the entire file.


Critical for us as a service provider because our clients rely on Figma’s stability for ongoing projects and working with libraries.
 

Context:

  • System: macOS, Figma Desktop App, latest version

  • Fonts are correctly installed locally on all machines

  • Figma Font Helper is running on all devices

  • No changes to font versions or system configuration before the issue started

  • Trigger: Simply selecting and editing text in a long-working file

 

Right now, we can only tell our client to not update the missing font, to avoid him from hours of reworking the complex file. 

Hello @figma - can you please help?

Hi ​@Janina_Braun — welcome to Figma Forum, and thanks for taking the time to flag this along with all the details you’ve shared.

I did a review for related reports but haven’t seen a pattern come up. Are you and your team still running into this issue? It sounds like you’ve already covered most of the common causes, but to make sure we’re aligned, could you confirm the following:

  • You’re on Figma Desktop App version 125.6.5 or later.

  • If you’re on an Organization or Enterprise plan, fonts are uploaded to your team or org settings so all members can access them without installing locally. To do this, go to: File browser → Admin → Resources → Fonts → Upload font. More here: Missing font alert in Figma Design → Font styles are missing (see the Organization and Enterprise plans section).

If all of that checks out and the issue persists, the best next step is to loop in our Product Support team so they can dig into the specific file. When you reach out, please include:

  1. the link to this Forum thread for context
  2. a link to the affected file
  3. make sure support-share@figma.com has edit access.

Keep me posted on how it goes — I’d love to know if your team was able to get this sorted, or if anything else comes up along the way.

Reply


Terms & ConditionsCookie settings