Skip to main content
Question

Old variable mode name persists after change

  • February 24, 2025
  • 10 replies
  • 213 views

Matthew25

In a library file our team set up collections of variables and created two modes, one for Desktop and one for Mobile. We then decided that we wanted Mobile to be the default mode. As a workaround to make Mobile the default mode, we renamed the modes, swapping their names (so, Desktop → Mobile, and Mobile → Desktop). We then swapped all the variable values so they were under the correct mode.

The problem is that now any pages or frames that were set to a specific variable mode before we renamed and swapped the modes still show the old naming even though they now have the correct styles based on what is supposed to be the default mode (Mobile). So, if I chose Mobile for the variable mode for a page or frame before the swap, it now reads Desktop when the styles are correct for Mobile. Also, new pages or frames created do not have this issue, so I can have two frames right next to each other, one that says “Auto (Mobile)” and one that says “Auto (Desktop)” and they both look correct.This same issue applies to pages, frames, and any other elements that modes can be chosen for.

Is there a way to reset the references to variable modes or another way to solve this issue?

10 replies

Mika_Kaki
  • New Member
  • 1 reply
  • March 17, 2025

We have the same problem. Any ideas how to correct it?


Matthew25
  • Author
  • New Member
  • 1 reply
  • March 18, 2025

@figma_admin ​@Figma_Bot what is the next step in escalating this?


Alex Dmitriev
  • New Member
  • 1 reply
  • March 19, 2025

Second this!


Angelika_Zwolinska

Same problem. Figma displays the old name "Mode 1" and updating the file does not fix the problem. 


Adam Howard
  • New Member
  • 1 reply
  • July 29, 2025

I ran into a similar issue and found a possible work around…

Issue:

  • Published 4 modes from file A
  • Used modes from file A in file B
  • Updated names of all 4 modes in file A, republished
  • Updated modes in file B
  • Old names from file A persisted in file B 🙁

Fix:

  • Removed a mode from file A, republished
  • Updated modes in file B
  • New names propagated in file B 😀

I realize everyone cant delete a mode (I happened to have one I wasnt using) but maybe try adding a new mode to force changes to propagate in file B.

Hacky, but effective for now?

 

 

 


KennLucas
  • 228 replies
  • September 22, 2025

Anyone ever figure this out? Figma support is useless.


KennLucas
  • 228 replies
  • September 22, 2025

@Adam Howard This absolutely worked! Thank you for thinking of this one.

 

I was fortunate to have an empty mode available and did exactly as you said. I created a new mode, published, and it updated everything. Then was able to delete the extra mode.

 

Now all we have to do is get Figma to 1, make more modes available to regular people, and 2 fix their bug!


Melissa Miller
  • New Member
  • 1 reply
  • October 7, 2025

How do we get this escalated? 

 


djv
Figmate
  • Community Support
  • 5211 replies
  • October 20, 2025

Hey All, thanks for flagging this! 


And thank you ​@Adam Howard for sharing your workaround.

As a first troubleshooting step ​​​​​, can you please try using the quick action "Regenerate all instances (slow)" or "Repair variable mode values" to see if that helps. You can access quick action by using the keyboard shortcut command + /.  If that doesn't help, can you try making a “silent” change to the collection where the variable mode is located, and then publish and accept the update?
 
To do this, make a slight edit to the collection name by adding an extra value, then publish and accept the update. Once you've done that, you can edit the collection name back to its original value. 


ksn
Figmate
  • Community Support
  • 2041 replies
  • October 20, 2025

Hey ​@Melissa Miller - apologies for the delay in response. I wanted to check on if you were still having trouble, since this is a bit of an older thread.

Does the naming still remain the same within after being changed? Let me know if that’s the case.