Skip to main content
Weirdo
Active Member
April 24, 2024
Solved

Variables for text styles make the file really slow

  • April 24, 2024
  • 43 replies
  • 2013 views

I have a big file (130K layers) and recently I add the new variables for text styles and boy the file running very slow, I can’t edit nothing, not mentioning play with the prototype.

It has nothing to do with my PC or memory usage (14%). I had to remove the variables for text styles to make the file run faster and it works.

This new feature is great but until this performance issue will not be resolved I will not add variables for text styles to my projects.

This topic has been closed for replies.
Best answer by ksn

Hey all - I know this has been a pain point for you, and I do want you to know I am hearing you.

 

From my end, I don’t have an update -- after the original issue with the text styles was addressed, any lingering/newer reports were determined to be part of a separate issue, and file review would be the best option in identifying the problem for everyone’s unique instance.

 

With that said, my best recommendation now is to do the following:

 

  • Share edit access to the file[s] you continue to have issues on with support-share@figma.com (you won’t be billed for this).
  • File a support ticket here if you have not yet done so.
  • When filing the ticket, please include the exact names of the files you have shared to expedite the investigation process

 

I’m going to close this topic since it is older + the original issue was resolved. If anyone who comes across this is experiencing any issues you believe are related, please create a new forum topic. Appreciate your understanding!

 

43 replies

Weirdo
WeirdoAuthor
Active Member
April 25, 2024

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

ksn
Figmate
Community Support
April 25, 2024

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 😊

Ortega_Matthew
April 26, 2024

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.

Astrid_Boivin
April 26, 2024

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

Riccardo_Marconato
April 26, 2024

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.

Astrid_Boivin
April 29, 2024

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.

Lindsey_Leanne1
New Participant
April 29, 2024

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.

ksn
Figmate
Community Support
April 29, 2024

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.

jmvanieperen
April 30, 2024

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! 🙂

ksn
Figmate
Community Support
May 1, 2024

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.