Skip to main content
Klára Bárová
New Member
October 23, 2025
Question

After latest update, components in design system are broken size/scale wise.

  • October 23, 2025
  • 47 replies
  • 1729 views

I noticed that after the last update some of my nested components are broken in sizing/scaling. I would reload my library after publishing and half the instance across various screens would take off. Specifically the components are getting bigger somehow. 

For instance this image component, nested in a product card, should be as is in the version on the bottom, after reloading the component from the ds library the image is bigger. Or the stamp in the footer is correctly inserted in the beige space in DS itself but as an instance it seems to enlarge quite a bit. 

This happens with images, icons, other assets like stamps etc. It seems that it needs me to manually redo everything now (copy-pasting from DS library, editing etc) and i do not have that type of time/budget for this big of a project. 

 

This topic has been closed for replies.

47 replies

brc
New Member
December 4, 2025

​@djv I have shared a file with support-share@figma.com as well. I can’t work safely or share my files until this is fixed.

djv
Figmate
Community Support
December 4, 2025

Hi ​@Alex172, thanks for letting me know! 

I located your ticket #1623940 from Tuesday, and Ben from our technical quality team replied to you earlier today. Can you please confirm that you’ve already shared support-share@figma.com as an editor to your file? 

It looks like he tried to access it, and he was unsuccessful. Feel free to also respond to him directly via email for one-on-one support in the interim. 

djv
Figmate
Community Support
December 4, 2025

Hi ​@brc, thanks for chiming in here! 

I located your ticket #1628019, and it looks like you actually didn’t share a file with us stating “Everyone has this issue, you don't need a URL from me.”


For future bug reports, having an individual file is incredibly helpful. Even when many people are experiencing something similar, bugs can show up differently from user to user, so the unique details are often what help our team identify the root cause more quickly and accurately.
 

That said, the team does have this entire forum thread of screenshots and Alex’s file to reproduce the behavior, so they’re actively looking into it. I’ll make sure to provide an update here as soon as we hear more from them.
 

Thanks again for your patience and for bringing more visibility to the issue.

brc
New Member
December 4, 2025

​@djv My apologies, per the earlier comment I thought that adding support-share@figma.com as an editor to the file was sufficient. Thank you for the updates.

djv
Figmate
Community Support
December 4, 2025

No worries, @brc!


Just to clarify, support-share is a shared account our support and product teams use so they can review user files without adding extra Full seats to your team. Invite support-share@figma.com as an editor was correct. But on our side, we still need the direct file link. Since support-share is a shared handle used by multiple team members, the link ensures we’re looking at the correct file you’re referring to. Thanks again for your patience while we work through this!

Stein Olav Pettersen
New Participant
December 5, 2025

​@djv please add my ticket number #1626019 to the same issue. I added links but I have done some refactoring since then (added extra wrapper layers to the icons which should not have been necessary).

Please contact me as soon as possible if I can be of any help solving this issue. The only replies on my ticket are my own …

Aqilah
New Member
December 5, 2025

Hi, ​@djv I have shared my file to support-share@figma.com. Please add my ticket number to the same issue #1629429. Apologize for the late reply and thank you in advance.

djv
Figmate
Community Support
December 5, 2025

Hey All, thank you so much for your cooperation and patience while our team worked through this bug! 

The team just pushed a fix for this. Can you please refresh your tabs and try regenerating all instances again? 

Please let us know if you’re still running into issues. 

Stein Olav Pettersen
New Participant
December 8, 2025

Hi ​@djv 
Did some testing here. All seems to be fine on my side. Also restored our asset library to the version before this happened to remove the extra wrappers I added as a workaround. The assets work in all sizing modes now without breaking the constraints. Thank you for prioritizing this issue 🙌. Last week was rather frustrating 😅

Alex172
New Participant
December 9, 2025

Hi ​@djv I confirm what ​@Stein Olav Pettersen has shared, everything is working fine now.