Skip to main content
Question

Variable browser (and API) is getting value of alias variables from first mode always

  • July 7, 2025
  • 1 reply
  • 35 views

claus.stadel

It seem that the variable browser inside Figma is getting the wrong value when you hover over an alias. It then gets the value from the first mode, instead of the value for the mode it is referenced in. This error seem to also propagate to the Plugin API for reading the variable values. This file demostrates the issue explained below.

“Header padding” in the Medium mode seem to have the value 48 when you hover over it. Which is the value from the Large mode, not the 24 from the Medium mode.

However when you apply the value in the design it works as expected and the value is actually 24, when the mode is set to Medium.

Even more, if you go to the variable browser and unlink the value if also gets the value 24.

My main issue is not the hover in the variable browser, but the fact that also the Plugin API is getting the wrong values.

1 reply

ppolol
  • New Member
  • November 27, 2025

I’m experiencing the same issue and it’s extremely critical for our workflow.
We rely heavily on multi-level aliasing for our design tokens, and the current behavior breaks our dark/light theme structure in production handoff.
Figma is a premium tool and we pay a significant amount of money for it, so it’s really frustrating to see such a fundamental feature for design systems remain unstable.
Can you please prioritize fixing this bug or at least give us a clear update and timeline? This is blocking our team from using variables the way they were intended.