I think im getting the same problem, i’m always a bull in china shop when it comes to new updates and always regret it.

Regrettably, we’re experiencing similar challenges.

I’ve introduced only five text variables across eight brand modes (utilizing Roboto and Open Sans) for testing purposes, yet the system has slowed to the extent of being unusable.

I’ve dedicated an entire day to investigating potential issues with my computer, internet connection, Figma application, Figma server status, and ISP.

It’s reassuring to learn that others are encountering the same problem.

Additionally, since the latest release, there’s been another issue: Most files consistently display the cloud icon in the top right corner, indicating unsaved changes, despite my stable internet connection. Even the Figma “Check network” quick action reassures me each time that the file has access to all necessary Figma servers.

Hey all - thanks for your feedback on this.

I think at the moment, this isn’t necessarily a bug – I think this has more to do with memory capacity, which can affect files with or without variables. We often see similar comments on this when it comes to larger files (especially ones with very complex design systems).

You may have reviewed this page already, but wanted to highlight an article we have on reducing memory usage. This may help things render better: https://help.figma.com/hc/en-us/articles/360040528173-Reduce-memory-usage-in-files

I also want to acknowledge that in instances like these, some of the recommendations in the above article may not be ideal.

For @Michael_Klein - I think the unsaved changes issue is separate, but it’s possible it could be related to memory (maybe because the file is large, and the cloud saving is being impacted by this). Do you use Figma on the web or desktop app? Does it become an issue on both?

@ksn

Thank you for your input on the matter.

Indeed, our design system is rather intricate, particularly with regard to variable utilization. We have eight collections comprising approximately 4-8 modes each, alongside numerous variables and cross-referencing collections. Up until the integration of typography variables, the system functioned reliably and efficiently.

The issue at hand directly pertains to typography variables in our scenario. Upon reverting to the version predating the implementation of typography variables into the design system, everything resumes smooth operation.

This issue manifests within both the Figma application and any web browser, exhibiting consistent behavior across platforms. I’ve also attempted to troubleshoot by logging out and clearing the Figma application cache, albeit without success.

Figma’s memory consumption stands at approximately 8% with typography variables enabled, compared to 6% without (prior to implementation). Concurrently, the MacBook’s system memory usage registers around 50%.

I’ve had the same problem using type variables on the app on a MacBook. Troubleshooting everything with my department. Nothing worked until I unlinked all my type variables. The Internet is good, memory is good. 🙂

Thanks @Michael_Klein – I saw some updates on my end that actually point to these issues as a bug that engineering is actively working on. There seems to be something causing these performance issues with typography on our end.

I saw that you also filed a support ticket on this, and I escalated it to have it reviewed faster.

For @Martin_Hill – can you also file a support ticket at this link and let me know when you’ve done so? If you can include the ticket number you get assigned, I’ll also have it escalated.

@Weirdo could you also do the same as well? ^^ Our tech quality team is actively working on this issue, and it would be super helpful to take a look at your accounts and/or files if possible.

For anyone else that stumbles across this topic, please do file a support ticket and post here with your case number. I will update as things progress.

Ive just submitted a ticket, but couldn’t see a ticket number. i also couldn’t add a shared link as the file has unreleased IP.

not a problem - totally understand. I was able to locate your ticket, and I’ll escalate it within support + note you’re being affected by this as well.

@ksn

Thank you for the update on this matter. It’s reassuring to have clarity.

I’ve already submitted a ticket regarding the persistent offline issue. Additionally, I intend to file another ticket addressing the typography issue, which is impeding the efficiency of our design system.

Sure, but I don’t know how to open a ticket, if you can guide me that will be helpful. Thanks!

Sorry if I was unclear! You can file a ticket using the link I posted in another message here

It’s a form that will ask you for additional details 😊

This is definitely a bug that is related to the new typography variables. Me and my team all experiencing the same. There was a temporary solution which was to create a new piece of text and apply a variable to the font size. Kind of random, but it stopped working, so now we are back to just having a slow file. I hope this is resolved soon, but it sounds like a complex bug.

Jumping in there, I have been barely able to produce anything since adding the typography variable to my library. This feature is complete game changer for my project and I was really looking forwards to it, but I’m considering reverting the changes to be able to work again until this gets fixed.

The weirdest part is that my library file is perfectly fine, it’s every file that’s using the library that becomes unusable, even with just one frame and 3 components, that’s so infuriating T_T

This week has been a nightmare after implementing the typography variables.

Unfortunately, we realized too late that the file was slowing down significantly, and now we can’t use our main library since it’s already running with the new variables.

What’s happening is that every action related to variables triggers an endless loop of “unsaved changes” prompts and loading/lagging.

I’ve already opened a ticket with more details and examples, but it’s clear that there’s a bug/performance issue related to the typography variables update.

I personaly made a copy of my current library and stripped all typography variables from it. Solid step back and very frsutrating but the only way I could keep on working 😦

I’m also glad I have a back up prior to introducing variables as well to recover components and style handling different fonts and style, but it’s gonna be a pain for maintenance until they solve the issue.

This is also happening for us. After applying typography variables and publishing those updates into a current file, our prototype is unusable. Will not load, interactions as basic as clicks take 30+ seconds or freeze the entire prototype. We’ve tried everything else to resolve speed/memory issues to no avail. It seems like this only started to occur after introducing typography variables.

Hey everyone here, and anyone else who comes across this issue – I’ve spoken to the team that work on variables, and they are asking those who haven’t already to please do the following:

• Share edit access to the files you’re working with typography on to support-share@figma.com. You will not be charged for this. We understand that you may have disclosures in place that prevent you from sharing, but if there is anything you can share (potentially in it’s own individual file with slight differences).


• Second, please file an official ticket here – I will then be able to escalate it so it can be reviewed more quickly. Please let me know if you’ve done that as a reply here with the case number you are assigned.

It is still being actively worked on and investigated, and doing the above will help immensely.

We’re also experiencing the same issues. Figma is barely useable for us since we’ve added typography variables. I’ve added a support ticket and gave Figma access to our file. Hoping for a quick fix! 🙂

Update: thanks everyone for hanging in there.

Our engineering team is still actively working on this, and there are some solutions being discussed and tested now. I will drop another update when potential fixes get pushed out.

Can everyone here try restarting/reloading your Figma tab/file (or just hard resetting the app/browser window) and see if this seems fixed? Engineering believes that this has been mitigated, but want to confirm.

If you’re still having issues, let me know in a reply here.

Are we simply turning off and on again to initiate an update/fix? Or are you simply saying the solution is to turn it off and on again?

Can confirm this has now been resolved on my side. Thanks to the team for the speedy fix, it was pretty bad!

Hey everyone!

I am Celine and I am working closely with Kim.

Thanks @Gareth for letting us know, glad to hear it works now 🙂

@Martin_Hill , yes please just refresh the tab (or force-quit and open Figma in a new browser window, or force-quit the Figma Desktop app and restart it.) Thank you!

Unfortunately, after I reload the tab, app and PC - on my side it is still pretty bad.

Deleting objects takes few seconds, prototype does not work at all (freezes) and overall navigation in the app is slow.

I’m using the desktop app and tried it with chrome and still no difference. Also switched from my work PC to my home PC which is a beast, and got the same slow performance.