Add space until it feels wrong, then step back
The usual workflow is to add white space until a layout looks acceptable, then stop. That produces designs that are merely not cramped — the bare minimum.
Try flipping it. Give every element far more breathing room than feels necessary, then remove space until the layout starts to suffer. The stopping point usually lands in a more generous place — and for most designs, that’s an improvement.
Drag until it feels right. Most people land higher than they expect.
DESIGN SYSTEMS
Build once, ship everywhere
One source of truth for your components, tokens and docs — synced from design to production.
Request accessWhy the instinct undershoots
Designs usually start dense — a browser default, a rough sketch, a pile of content dropped onto a page. From a dense starting point, every bit of added space feels like an improvement, so it’s easy to stop too early.
Starting sparse reverses the reference point. Now the question isn’t “does this look better than cramped?” but “does removing this space actually help?” — a much higher bar.
Where the extra space goes
The places that most commonly need more room than they get: padding inside cards and buttons, the gap between a section’s end and the next section’s heading, margins around standalone images, and the space between a heading and the content above it.
That last one matters: a heading should sit close to the content it introduces and far from the content it follows. Equal spacing above and below is one of the most common grouping mistakes.
Same total space around each heading. Weighting it upward is what organizes the page.
The first section ends here, wrapping up its final thought before the page moves on to something new.
Shipping your first release
A heading owns the content below it. When it sits close to its section and far from the previous one, the page organizes itself into visible chunks.
Monitoring what happens next
The same rule repeats down the page — every heading hugging its own section, keeping the structure legible at a glance.
Dense is a decision, not a default
None of this means every screen should be airy. Dashboards, data tables and pro tools often should be dense — when users live in an interface all day, compactness is a feature. And some visual styles fill the frame on purpose; that’s a valid aesthetic, not a mistake.
The difference is intent. A dense design chosen deliberately looks tight and efficient. A dense design that happened by never questioning the spacing tends to look unfinished. Decide the density; don’t inherit it.
The takeaway
Start with too much space and remove it, rather than adding space until things look passable. Weight spacing so elements sit near what they belong to. And when a design needs to be dense, make that a choice — almost never an accident.