Variables for text styles make the file really slow

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.