Skip to main content
Sean_Sands
March 16, 2021

Define default padding for Auto Layout (or set to 0)

  • March 16, 2021
  • 77 replies
  • 17337 views
  1. Describe the problem your experiencing and how your idea helps solve this
    When you create an autolayout frame, it always defaults to 10px. Many design systems call for an 8px grid and in many cases, users don’t want ANY padding especially where edge-to-edge designs are concerned.

  2. Ask questions to bring the community into the conversation
    What are everyone’s thoughts about the following solutions?:

  • Default autolayout padding based on the big nudge amount in your settings
  • Allow for tokenization of padding/margin grids and offer up autolayout parameters based upon those tokens
  • Allow users to override the padding to 0px at the creation of the autolayout frame by using an alternative key command like ctrl+shift+a (command on mac)

77 replies

d_greg
New Participant
May 21, 2026

Yes, using Shift + A on a single item should default all spacing to 0px

on multiple nodes that works with 0 padding (and whatever the gap is between them), but on a single element it doesn’t

Lea.P
New Participant
July 10, 2026

+1 - would be very helpful for design systems to define default tokens could also be defined for auto layout specs …

Wawa
New Participant
July 22, 2026

This could be very useful.. can’t believe it’s still an issue 5 years later 

Nick_Man
July 29, 2026

Yes, using Shift + A on a single item should default all spacing to 0px

Hitting Shift+A on a single item in my canvas adds auto-layout and 10px of padding all around it

Nick_Man
July 29, 2026

OMG this is 4 years old?!
Whoever thought that 10 px would be the most common value users would want? 🤔

 

But look at all the new features they have like being able to generate stupid AI images and iterate on them as they are generating! BRILLIANT 😒

Nick_Man
July 29, 2026

Still can’t believe not ONE Figma account or partner has responded to this thread… blows me away. So many small usability issues they have that could be fixed in ONE sprint and they’re just like,

“nah… users don’t know what they want. They want complex functionality that literally no one asked for. Let’s give them that…. the feature they’ve been asking for for 5 years and have a consensus across the community…. put that on the backlog - priority zero”

September 9, 2026

Even after 5 years… we need it!