Skip to main content
New Member
April 7, 2025
Solved

Issues with nested component scaling

  • April 7, 2025
  • 32 replies
  • 1773 views

Hey Figma team,

I wanted to report a problem that’s been bugging our team for the past few months. 

We have an Icon Library in our design system, as well as a separate glyph library. These icons are used in different sizes across the product (16px, 24px, etc.). The master components of each icon and glyph contain elements which are all set to ‘scale’.

However, within our larger components, whenever we want to swap an instance of an icon with a different one from our library, the scaling (of dimensions, stroke width, and border radius) is not properly applied, resulting in a broken view. 

One example is:

  • We have a nested icon component scaled to 16x16px;
  • We replace the instance with another icon from either library (original component of which is 24x24 but all elements set to scale) and expect it to scale properly to the 16x16 dimensions. However, the swapped icon appears broken in terms of the scale of elements inside, stroke width and border radius;
  • We have to resort to a workaround like: 1) Detaching from the master components, 2) Resetting the icon to its original size, 3) Scaling it again to the desired size. Which works for now but it’s frustrating we can no longer make use of the flexibility of the overall component’s properties.

It would be great if these scaling issues are fixed in future updates.

Appreciate your time looking into this!

 

 

Best answer by Celine_

Hey everyone! Good news, our engineering team has shipped a fix! 🎉

Please refresh your tab or app to get the updated behavior. If you're still running into any issues after refreshing, feel free to let us know. Thanks so much for your patience while the team worked on this! 🙏

32 replies

Celine_
Figmate
Community Support
April 29, 2025

Hey Alex,
Thanks for sharing all the details — I understand how tricky this scaling behavior can be, especially with nested components!

I saw that you've already contacted our support team. (Your support ticket is  #1314238.) The agent is currently waiting for your response to continue the investigation. (For your information, once you respond, your support ticket will automatically re-open.)

If you can, please reply to the support ticket with a brief video recording showing the issue. Make sure the full Figma window is visible, including properties and layers panels with relevant layers expanded. This will help the team to reproduce and better understand what’s happening. Thanks again!

Julien Blanchet
New Member
May 15, 2025

Hello!

I have the same issue, do you finally find a solution?

Thx !

Julien Blanchet
New Member
May 16, 2025

Hey, problem seems to be solved with the latest update :)

Robin B.
New Member
June 3, 2025

@Julien Blanchet Nah the problem still exists. At least for me, the components in other states are still displayed in the original size when they are changed via the nested instances…

Celine_
Figmate
Community Support
June 3, 2025

Hey ​@Robin B. , sorry to hear you are still having issue on your end. For visibility here, we are still waiting for ​@Alex A ‘s response for further investigation.

I’d recommend submitting a bug report directly so our support team can take a closer look and investigate the root cause on your end: Submit a bug report here

Please use your Figma email account,  and in the form, share a direct link to the file, and invite support-share@figma.com with "can edit" permission to your file so the team can look into this further. Note that users with @figma.com emails on your team do not count towards your billing. 

Thank you!

Julien Blanchet
New Member
June 3, 2025

My bad, ​@Robin B. is right, the issue still exists… ​@Celine_ I will submit this bug report too

Celine_
Figmate
Community Support
June 23, 2025

Hi everyone! Just wanted to share a quick update here for visibility in case others are running into something similar.

@Julien Blanchet, I saw that our technical specialist were able to take a closer look at your report. Here’s what they found:

This is a known issue we’re actively tracking: right now, when swapping nested instances, the scale factor isn’t being applied correctly. While the fix may take some time, here are some solutions that can help in the meantime:

  • Instead of using scale, try applying size overrides directly to the nested instances. As you mentioned, another way to have it work is to set auto layout on every variant, and detaching the instance causing the issue.

  • For the icon width specifically, we recommend having auto layout set to “hug” for all variants in your component set. Here's a video showing what that looks like in your example.

Thanks again for flagging this, and we really appreciate everyone’s patience as we work on a more permanent fix 🙏🏼

Carlos_Robledo_Puertas
New Member
October 23, 2025

Hello team!
We’re having the same issue, causing a major problem with our workflows and prototypes. Is the team working on any long term solution? For us, it’s not scalable to detach the components causing the isue.

Thanks a lot!

Julian_Castano1
New Participant
October 25, 2025

Hi, I’m experiencing the same issue and is causing problems on the handoff. Please let us know when this will be fixed so we can have an estimated date/time.

Rachelle Huizinga
New Member
October 27, 2025

I’m experiencing the same issue