Skip to main content

Allow percentages for line height

  • April 17, 2024
  • 182 replies
  • 21388 views

Show first post

182 replies

Maria96
  • New Member
  • July 7, 2025

+1!!


Leo_Vogel2
  • New Participant
  • July 7, 2025

+1


Benjamin_Margoux1

Still waiting


Soren_Runge
  • New Member
  • July 10, 2025

 

This is on our radar. I’ve moved your reply to this topic to better gauge the overall impact we’re seeing here in the community.

Do you need a mechanic? Looks like the radar is broken. ^.^

Jokes aside … What makes me sad is that this request feels like the request for percentages for width and height specifications back then, where it seemed that the topic was simply hushed up. 
Let's face it, typography without percentages or multipliers is unfortunately only half the battle. there is no alternative here, no workaround ... just a lot of painful work when working with customizable design systems that quickly require up to 300 font definitions spread over 4 breakpoints, which quickly destroys a good development. ... What the batch styler used to do, figma could now suddenly do itself, faster and more responsive.
As a former developer, I am well aware of the limitations and challenges of data types. However, as a designer who has always appreciated figma's flexibility and open ear, I also think that a dedicated community like this would have deserved at least 2 updates after more than a year. ... before figma becomes a soulless money-making machine like other once innovative tech companies. cheers


Nicolas_Prieto

Can we please get this thing ready? It’s been a while and it might be super useful! 😁

On a side note, size / line-height variables are not updated on the Text Style List if you switch variable modes that alter those sizes, like from Desktop to Mobile: the text style change happens but the values on the text style list remain the same, making it super confusing.


Kestas
  • New Member
  • July 24, 2025

Please update the feature.

We need an option to define which value the variable should be “%”, “rem”, “em”, “px” …

@seni 


Matthias Fritsch

+100 Push this! Please update/add this! 


Mark_Wyner1
  • New Member
  • July 31, 2025

Yep. 100%.


Dieter
  • New Member
  • August 25, 2025

We also need this for our design system.


Kallichore
  • New Member
  • August 25, 2025

I’m surprised this hasn’t been available since the very start of variables in Figma. Definitely a feature we needed yesterday! +1


djv
Figmate
  • Community Support
  • August 28, 2025

Hey All, thank you so much for continuing to share your thoughts and experiences around this feature request! 


We hear how important this feature is to so many of you, and we truly value the time you’ve taken to advocate for it.

 

We’ve already passed this feedback along and shared the impact it could have with the team. That said, to be fully transparent, the teams ultimately decide how features are prioritized, and we don’t yet have a concrete timeline for when or if this one will be implemented.

 

We know it can be frustrating to wait without a clear answer, and we really appreciate your patience and understanding as the team works through priorities. Please know your voices are being heard and do make a difference.


Nadia Carmo
  • New Member
  • September 26, 2025

I also need this!


Matthias Fritsch

Common Figma, it’s been a year and this is really blocking modern design practices!
Like it’s cool to have all the fancy AI stuff but not allowing % in tokens is embarrassing...


Aki Fukai
  • New Member
  • October 19, 2025

+1 as well. Why? Single source of truth (in the code) is the rule to go. Then keeping it in sync with the Figma library — and vice versa.

Ideally this single source of truth can move from Figma library to encoded design system/FE UI-kit.


Peter_Muller
  • New Participant
  • November 10, 2025

Adding my +1


Cassie Anderson

+1 

Would also love to use percentages in a variable for letter spacing. 


Mats1
  • New Member
  • November 11, 2025

+1


Christos
  • New Member
  • November 13, 2025

I don't mean to sound rude, but I don't understand your policy regarding the development environment. For almost 1.5 years, we've been requesting the ability to enter percentages as values ​​in variables. It's already possible in the styles; you can enter percentages or even perform simple calculations with multiplication, addition, etc. You keep rolling out updates, and one of the most important features, as we can see in this forum, is the ability to enter percentages for line height. You can't sell Figma as a mega design system tool if it doesn't offer essential mechanisms for the people who actually create design systems. I repeat: we're talking about the ability to enter percentages! We're not talking about cutting-edge AI features! Please prioritize this ticket. Make it a spike, a hotfix, or whatever. After 1.5 years and an increasingly busy thread, it should have sunk in by now!


Frank Culshaw
  • New Member
  • November 17, 2025

Huge +1


ThomasAlkmaar072

This would make my design proces a lot easier, +1 🙏🏻


Stewbot
  • New Member
  • December 5, 2025

Would’ve taken this over extended collections any day. The presenter who drops this during Config is going to bring down the house.


Design System
  • New Member
  • December 10, 2025

If this limitation is blocking your workflow, we recently released a solution that might help: Line Height Tokens, a Figma plugin designed specifically to bring true proportional line-height (unitless → %) into Figma — exactly the way it works in CSS.

https://www.figma.com/community/plugin/1577516978004090936/line-height-tokens

Figma currently treats all number-type variables as absolute pixels, which prevents using tokens like 1.4, 1.5, or 150% consistently.
The plugin solves that gap by converting unitless values into real visual percentages while keeping the connection to your original variable.

Why this plugin helps

• True proportional line height (CSS-accurate)
You can define 1.5 in your tokens, and the plugin will apply a visual 150% in the canvas — perfectly matching line-height: 1.5; from CSS.

• Works with existing typography tokens
It plugs directly into your current font-size, line-height, leading, or type-scale variables.

• Clean, scalable Design Systems
You no longer need huge lists of redundant px-based height tokens.
One unitless token = infinite scalability.

• Full visibility in Dev Mode
Thanks to Codegen, developers see the actual token name + the final CSS snippet when inspecting text.

• Smart bulk updates
Update a variable (e.g., from 1.51.6), run “Sync Page”, and every text element updates instantly.

🚀 How to use it

1. Create your tokens
In Local Variables → Numbers, define unitless values like:

lh-base: 1.5 lh-tight: 1.3 lh-loose: 1.7

2. Apply the token
Select your text → open the plugin → click the token you want.
The plugin converts 1.5 → a visual 150% line height.

3. Inspect in Dev Mode
Developers will see the exact CSS:

line-height: 1.5;

4. Sync changes globally
If you change a variable value, run “Sync Page” and everything updates across the file.

If you're building Design Systems or matching UI ↔ CSS behavior precisely, this plugin fills the missing piece until Figma supports %-based line-height natively.

Happy to share more if helpful!


Barry Lachapelle

Not having this makes tokenizing type in any meaningful way impossible.


Leo4411
  • New Member
  • December 11, 2025

This is needed! Also seems to be similar to these threads about %:

Hello. I was wondering if it is possible to have percentage values in variables, like setting percentage value for frame widths or shape sizes (etc.) that have variable modes applied to them? Percentage values could respond better to content that varies within a frame or frames within frames.
This makes it easier to use components in designs for different screen sizes. And then you don’t have to calculate every time what 40% or 60% of the width is. This also makes it easier to design scalable applications that grow with the width of the screen.

Totally agree, this is really needed. And yes, it ties in perfectly with those percentage-based variable requests. Having true % values for widths, heights, margins, and other properties would make responsive layouts so much smoother and remove all the manual calculations we do today.


m.zelis
  • New Member
  • January 8, 2026

A solution would be to simply allow a string input into the line-height.

Step   1  

   Allow string input variables for the line-height 

 

...End of Steps