Skip to main content
Question

Auto layout not rendering correctly

  • June 12, 2026
  • 3 replies
  • 36 views

jgugler

Hi Figma Team


We are experiencing a bug where auto layout frames show incorrect dimensions on load. Any change to the frame triggers a recalculation and displays the correct result, which points to an initial calculation bug.

Description
When a page loads, some auto layout frames display incorrect dimensions despite being configured correctly. The issue appears randomly and we have not been able to identify a specific trigger. As soon as any change is made to the frame, the dimensions update to the correct values. Interestingly, copy-pasting an affected frame also produces a correctly calculated result in the pasted copy.


All of the following trigger a recalculation and temporarily resolve the issue:
- Changing the auto layout direction and switching it back
- Using "Regenerate all instances"
- Manually dragging the frame larger, then pressing Ctrl+Z to undo
- Copy-pasting the affected frame

Environment
- Affects both Figma web app and desktop app
- Affects multiple users on our team (not user-specific)

 

Would appreciate any help or a fix as soon as possible, as this is significantly impacting our workflow.

 

3 replies

adamsmasher
Figmate
  • Figmate
  • June 14, 2026

Hi, ​@jgugler. That’s unfortunate that this is causing significant impact for you and your team - I’m sure that’s frustrating.

 

Thank you for providing so much detail - it’s very helpful. I’m wondering about the frames that you copy and paste that display correctly… When you quit and reopen the app, do they still appear correct or do they also replicate the same behavior as the original? If those work correctly it gives you a way to resolve the issue, but if not I will help make a ticket with our Technical Quality team for you. Thanks!


jgugler
  • Author
  • New Member
  • June 15, 2026

Hi, ​@adamsmasher. It sadly persists even after closing the app and reopening. Together with my colleagues, we’ve done some more testing when it shows up and have opened a ticket #1958949 for it. I’d appreciate it, if you could check if it’s in the right spot? The tickets process wasn’t as straightforward as I’d hoped.


Celyn_L
Figmate
  • Figmate
  • June 16, 2026

Hi ​@jgugler, Celyn here stepping in for ​@adamsmasher

Thanks for the update, and I appreciate you and your colleagues taking the time to do some additional testing and document the behavior.

I was able to locate your ticket #1958949 and can confirm that it’s with the right team. I've gone ahead and escalated it with the team for review.

Please keep an eye on your inbox, someone from the team will follow up there shortly.

Thanks again for reporting this and for providing those additional findings! 🙏