same issue here

I am experiencing something similar.

I have interactive dropdowns that use the same text font as all our files (taking them from the design system), yet… when I share the prototype with people that don’t have the font installed, they don’t see the texts 🤷‍♀️ , they are not replaced, but invisible.

This doesn’t help for user testing.

Figma, please help!

P.S. The weirdest thing of all is that on my machine I see everything working perfectly fine, but when I share the prototype… things go south.

This is STILL an issue and unacceptable as prototypes are used for stakeholders presentations. @Figma_Support do you have any update on when this will be resolved? Really losing my trust in Figma’s prototyping if this continues.

same issue here. trying to make a prototype for a tutorial video and my fonts are all miss match and wont let me fix

This is still an issue, and you can’t use the outline workaround as I noticed it occurring when I use the Set Variable prototyping functionality, font displays fine at first, then once I click the element that sets a string variable to another value, the font immediately breaks.

Same here… do realise these advanced features are in beta- fingers crossed this is fixed soon.

same here. i am using the variables for translations in different languages and when the prototype is set in another language and i click on a dropdown component to change the value it is resetting to the default language saying the font is missing and i am losing the translation.

this was working last month when i originally created the prototype, but now its getting more buggy.

I’m having the same issue. Very frustrating.

Yep! Big help is needed here.

Still a big L Figma

Same issue here! Super annoying

This is also happening to me. Huge issue, as embedding is crucial for our documentation. Can we have any word about when can this be fixed?

Yep an issue we’ve run into with sharing a prototype with a client. Our only way around it at this point is outlining all our text in the mockup which defeats the purpose of many features and requires duplicating artboards to maintain versions with live text in. Would be good to know if there is anything on the roadmap for solving it.

This is insanity. 2 years and no solution, completely makes Figma prototyping useless. Not sure if shared fonts under an org plan solves the issue. Would happily upgrade plans, but then there is a 3 seat requirement?? For any solo-entreprenuer / designer this doesn’t work. If shared, non-local fonts do indeed work, this feature must be added to the base plans or offer a $45 single seat plan that includes it.

Still there 😦

December 2023 - Still the same issue. I don’t want to have to be giving the client a big list of "bear with"s and "excuse the bug"s when we show them the prototype! Pls find a solution

Same issue, it’s incredible bug. Two years and still not fixed?!?

Still having issue.

First time today. WTF? Over two years, a bug in the presenting feature that is shown to clients? This is unacceptable. I work with interactive components since the feature is out and never had this. It depends on the used font I found. It’s a licensed adobe font in my case. Perhaps that helps

Same error here, using variables in my prototype always having Missing fonts

Still exists. Still ruins your day. 😃

Having the same issue. Worked fine forever, now all of a sudden all my fonts are breaking on hover. What is going on here??? please help

Not a fix but maybe helpful,

This happened to me - After a ton of trial and error I found that my interactive components in prototype were only breaking when I was doing a lot of trial & error to get the effect I wanted. (aka adding new elements to the different components, then deleting, etc.) When I redesigned and reattached the items and it worked again (with no missing fonts message)

Same here, the prototype has missing fonts in the browser and also in the Figma iOS App.

The problem was, that the prototype contained heavily modified components that Figma could not update but only restore. After detaching all these components and its children, it worked all perfectly and fixed the problem.

Just encountered this for the first time. Very disappointing bug to have to explain to a client. Disappointing to learn that it’s still here after 2 years. If it helps - this was with an adobe font that I have loaded locally.