Skip to main content
Question

Layout Differences between Admin and Dev Mode

  • May 11, 2026
  • 3 replies
  • 27 views
Tobi FRDMSK

Hey there,

 

we’ve experienced some layout issues over the last couple of weeks between our design and dev team. Multiple developers commented, that some designs seem to be broken – however they are displayed correct when our designers enter the figma file with their admin account.

 

I’m not sure how far the discrepancy goes, but what I can say is that it has to do with auto layouts that seem to get stuck in dev mode. If designers update components, the auto layout within the file updates as well. However, sometimes the same component in dev mode looks like it is stuck in a fixed size frame and will be cut at the edges. The only solution that fixes this problem is, that you delete the auto layout and create the same auto layout again.

 

As mentioned, this is pretty annoying as there is no chance for our designers to see the problems that the devs are experiencing. And on the other hand if the layout is not clearly a mistake, the Devs might as well implement components where they might not see everything due to this issue.

 

I hope this bug will be solved soon.

 

Attached you see a comparison between what the designer and what the dev experiences in the same file (in this case, there are no branches involved in the figma file)

 

 

3 replies

Celyn_L
Figmate
  • Celyn_L
  • Figmate
  • May 12, 2026

Hi ​@Tobi FRDMSK, Celyn from Figma Community Support here.

Thanks again for the detailed explanation and the comparison screenshots, those are really helpful. Looking at what you shared, it seems like the layout is updating correctly in Design, but in Dev Mode some components appear “stuck” and clipped until Auto Layout is recreated.

I’ve gone ahead and created a support ticket so the team can take a closer look, your case number is #1897228. I’ve also passed along all the details you’ve shared here so the team has full context - someone will be reaching out soon, so please keep an eye on your inbox.

In the meantime, here are a couple of quick checks that can help narrow things down:

  • When this happens, if you insert a new instance of the same component, does it display correctly in Dev Mode?
  • Does this issue typically show up right after a component has been updated, or does it also happen without recent changes?
  • For affected components, do they appear in Dev Mode as if they have a fixed height (content cut off) even though they’re set to Hug in Design?

It would be really helpful if you could reply to the ticket with a link to the affected file, and share it with support-share@figma.com with “Can view” access (this won’t affect your billing).

A short recording from the developer side showing the clipping would also be really helpful if possible.

I know how disruptive it can be when Design and Dev Mode aren’t reflecting the same layout, and we’ll work to get this back on track for you 🙏

Tobi FRDMSK
  • Tobi FRDMSK
  • Author
  • New Member
  • May 12, 2026

Hi Celyn,

thanks for your response. The three times this issue occured with different devs, it was always inside the same figma file - maybe this problem might really be connected to a problem within the file itself.

We’ve duplicated another design file (with variables, components, component blocks…) and started working with this file in order to have a base structure. This however is our usual use case, so nothing ordinary here.

The updates of components within the auto layout are updating, also from a Dev point of view. However, in some cases the auto layout doesn’t seem to be adapting to them.

We do use Figma for 4+ years now and this issue has only appeared in the last month.

I do need to have a quick word with our team, if it’s okay to share the file link as of non-disclosure agreements with the client, but if it’s okay, I will add you with view-rights.

Thanks

Tobi

Celyn_L
Figmate
  • Celyn_L
  • Figmate
  • May 13, 2026

Thanks so much for the additional context here, ​@Tobi FRDMSK - this is really helpful, especially noting that it’s been isolated to the same file and only started occurring recently.

I’ve passed everything you shared along to the team on your existing ticket so they have the full picture. I also saw that someone has already followed up there with next steps. When you have a moment, it’d be great to take a look and continue from there.

I understand if sharing the file link isn’t possible due to NDA constraints. The team can continue working with you based on what’s available and help narrow things down from there.

For now, please continue the conversation directly on the ticket so the team can stay closely aligned and support you more effectively.

Thanks again for taking the time to share these details, we’ll continue working closely with you on this. 

Terms & ConditionsAccessibility statement