Skip to main content
Question

Icons render incorrectly in component instances until clicked (forced re-render needed)

  • April 23, 2026
  • 4 replies
  • 37 views
Melda Cevikel

I’m running into a recurring issue where icons inside component instances appear at the wrong size or scale, but only visually. The actual properties seem correct.

The only way to fix it is to:

  • Click directly on the icon, or
  • Cmd/Ctrl + click into the instance

As soon as I do that, the icon “snaps” back to the correct size which suggests it’s a rendering issue rather than a constraint/setup issue.

  • It happens across multiple components and screens
  • The issue persists until each instance is manually interacted with
  • Updating or publishing components doesn’t consistently fix it
  • It seems like instances are not recalculating layout until forced

I have the same issue both on desktop app and browser.

Is anyone else experiencing this?
Would love to know if this is a known bug or if there’s a reliable fix.

4 replies

M4rcin
  • M4rcin
  • New Member
  • April 24, 2026

Hey!
Same here. The problem is visible for the whole team working on the file. The rendering issues covers mostly components, like buttons. But also frames with autolayout on, where many components were put - now in few places looks scattered, like ignoring autolayout settings.

Doing what ​@Melda Cevikel said works miracles, so I just need to click through every instance/autolayout, where problem appears. But it works only for a current session. After reopening the file, problem persist. Though while viewing the prototype, everything looks ok.

The strange thing is that while reviewing the file versions, problems seems to start after April 22nd, so on file versions:
22nd April - ok,
23rd/24th - problems.

But yesterday (23rd) we’ve seen no problem while working on it all day. So it looks like it appeared out of nowhere today.

    adamsmasher
    Figmate
    • adamsmasher
    • Figmate
    • April 25, 2026

    Hi ​@Melda Cevikel and ​@M4rcin! 

     

    Sorry to hear that you are seeing this with your files - thank you for for the feedback. You’re using slots, right?  I did some digging on our end and team is aware of this issue and is working on a fix. Additionally, our team is working to improve the slots experience while it's still in open beta.

     

    If I hear anything in the meantime, I will update the thread.

    Melda Cevikel
    • Melda Cevikel
    • Author
    • New Member
    • April 27, 2026

    Hi ​@Melda Cevikel and ​@M4rcin! 

     

    Sorry to hear that you are seeing this with your files - thank you for for the feedback. You’re using slots, right?  I did some digging on our end and team is aware of this issue and is working on a fix. Additionally, our team is working to improve the slots experience while it's still in open beta.

     

    If I hear anything in the meantime, I will update the thread.

    Hello, 

    The issue happens also on the main components and instances that are not using slots too. I’m adding another screen recording here which this issue happens in a component instance that doesn’t use slots at all. 

      M4rcin
      • M4rcin
      • New Member
      • April 27, 2026

      Hi ​@Melda Cevikel and ​@M4rcin! 

       

      Sorry to hear that you are seeing this with your files - thank you for for the feedback. You’re using slots, right?  I did some digging on our end and team is aware of this issue and is working on a fix. Additionally, our team is working to improve the slots experience while it's still in open beta.

       

      If I hear anything in the meantime, I will update the thread.

      Hey, thanks for reply!

       

      Altough, slots are used in my project, the rendering problems occur across whole project, not only in slots frames.

      Terms & ConditionsCookie settingsAccessibility statement