Skip to main content
Nereida
May 13, 2021
Question

Missing fonts in prototype - Interactive components

  • May 13, 2021
  • 163 replies
  • 21351 views

Hi, I created an interactive component that worked fine until one week ago (more or less). Now, when you hover on it the font changes and shows the message “Some missing fonts were replaced”

163 replies

Claire_Z
September 27, 2024

Thank you Nellya!! You really enlighten me!!! 👏 👏

Emmanuel8
September 30, 2024

Hello, can we get an update on this?

Alessandro_Suraci1
New Member
October 18, 2024

Just started seeing this too. It happens with Google Fonts, randomly.
In my prototype I have a set of variables (font family, weight, size) and 3 modes. When in prototype I switch mode some fonts randomly get replaced.

Michelle_Trostel1
October 22, 2024

Can we get an update on this issue? This problem makes it difficult to share with clients that do not have these fonts installed. Almost makes sharing prototypes useless.

Jannick_Utke
December 4, 2024

Same for me, font switches to another weight in prototype.
Is there a solution?

Peter_Angelov2
New Member
December 9, 2024

Hello everyone,

I encountered the same issue during remote usability testing of the Figma prototype in (respondent’s) browser. In our scenario, we have some text string which needs to be changed to another string using a variable and as the interaction was triggered, “some missing fonts were replaced” and on the top, not every text using this variable was updated (which caused logical issues in the test scenario).

This seems to be problem when using local fonts, and apparently as the browser uses “canvas” element where everything is drawn by javascript, Figma prototype in browser can not change the text to other string on the fly. I filed a bug report and hopefully will hear about it soon.

As a workaround, we did the following: since we only need the text to be either “string A” or “string B”, we created a component with both strings as variants. Then, using interaction we only change that component variant, not the string variable. That way Figma can “draw” the text layer (in the background probably just vector/outline of the original text).

I can update you with information from Figma team once I hear back about the bug report.

Dominik11
New Participant
April 10, 2025

Still not working with Font Awesome in current Figma app for Android... My icon button is switching its status/color, but its icon turns into plain text.

Scott McLean
New Member
April 17, 2025

Had this issue come up in one project file and now another completely different project file that was working fine before is also having this issue

Mia14
New Member
July 16, 2025

Running into this issue as well with variable numbers replacing the font on number changes. I can’t simply outline the font or create components for every state, because these variables use math to calculate the output.

Viet_Le1
New Member
July 24, 2025

Just ran into this issue. My component variants break selectively on interaction and revert to replacement fonts. Hey Figma, do you have any idea how embarrassing it is for a client to point this out to us? For a design tool, breaking fonts that significantly impact the visual aesthetic is absurd…..especially when looking at the original date of the OP’s post. 4 years for a major bug without resolution? WTF are you guys doing over there?