Skip to main content

[Bug] Figma Site doesn’t apply mode values when using typography variables inside styles


Mortyakard

While building a site in the new Figma Site, I ran into a typography issue:

When I use a typography variable with different font sizes for Desktop, Tablet, and Mobile, the correct value shows only if I apply the variable directly to the text layer.

But if I use the same variable inside a text style, the published site doesn’t respond to modes — it just shows the default (Desktop) size, even on smaller viewports.

This seems like a limitation or bug in how Figma Site handles mode-based variables inside styles.

Would love to know if this is expected behaviour or still under development. Happy to share screenshots or a test file if helpful.

Thanks!

 

4 replies

Yelnar_Bolatov

They also published text styles breakpoint creation that works. But I am not sure how I’d want to engage this case more: through variables and modes or through text style breakpoint additions. I guess it would be cool if they added some kind of variable collection type: breakpoint modes, as the large table of variables is easier to handle than the small text style menu.

 

https://help.figma.com/hc/en-us/articles/31242838116119-Customize-a-text-style-for-multiple-breakpoints


Scott_Olsen2

Just came across this issue myself. The modes work when looking at the fonts on the canvas, but previewing them they do not work. Connecting the variables to text breakpoints works, but it’s a hassle to have to add the values for something that shouldn’t need it.


ksn
Figmate
  • Community Support
  • 1688 replies
  • June 9, 2025

Hey all - thank you for reporting, and apologies for the delayed response.

I filed a bug ticket on my end to double check on if this was expected behavior, and from the information I received, it is a bug on the engineering side that they need to address. At the moment, I don’t have an exact timeframe on when that will happen, but can confirm it will be worked on.

In the meantime, ​@Scott_Olsen2 ‘s workaround may be helpful to try (if you haven’t already). For the time being, I’ll mark my response as the highlight, so anyone else who comes across this will have quick access to this info. Hope this helped clarify!


Mortyakard
  • Author
  • New Participant
  • 5 replies
  • June 11, 2025

Thank you ​@ksn following up.  🙏😊


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings