Skip to main content
Begis Orinbaev
New Member
August 3, 2026

Inside stroke increases Auto Layout frame size

  • August 3, 2026
  • 15 replies
  • 680 views

Hi everyone,

Has anyone else experienced this?

When I apply an Inside stroke to an Auto Layout frame that contains content (for example, a text layer), the frame size increases by the stroke width.

For example:

  • 36 × 36 → 38 × 38 with a 1px Inside stroke
  • 36 × 36 → 40 × 40 with a 2px Inside stroke

I expected the frame dimensions to stay the same because the stroke is set to Inside.

I'm using Figma Desktop on macOS.

Is this a bug, a recent change in Figma's behavior, or is there a setting I'm missing?

Thanks!

15 replies

mountx
New Member
September 14, 2026

Even changing “Inside stroke” from “Included” to “Excluded” on every instance (and f*ck me if I forget that in one of the 1000s of instances I need it I guess) it still doesn’t solve a major issue introduced by this change:
If I want to place elements with varying border width inside an auto layout container and have them fill out the space, there is currently no way to make sure that they occupy the same amount of space. This is something I need to do constantly and is also a very common thing to do in general (it’s trivial to do in CSS) and is no longer possible to do in Figma period.

The only workaround I found is to use a grid layout instead, but man do I hate grids in Figma, so not really an option for me (but also because it’s not a suitable alternative in some cases).

 

So to me there needs to be an option to actually get back the old behavior, preferably as a project wide configuration or user preference.

apretov
Active Member
September 15, 2026

We're waiting for the Figma guys to realize that this option should be configured globally, not for each element. I think it will take about two years.

Aleksiej Tuboltsev
New Member
September 15, 2026

what REDADCTED decided to make this new logic? Strokes dont work like that in CSS

Celine_ just decided to straight up lie in her response 

Also FIGMA LEARN contradicts this new logic, check it out yourself:

 

simon.kinslow
New Member
September 17, 2026

Colleagues I’m working with are also finding this puzzling working on web based projects. Same question when I tell them its a forced change via Figma… “Why?” is their answer.

For any designer working considering users this change doesn’t make sense from Figma