Answer 27 of 50
How Insufficient Whitespace Harms User Experience in Web Design
Too little space between elements makes people work harder to see what belongs together, what matters most, where a line of text continues, and which control they are about to tap. Nielsen Norman Group’s form research states the core principle in five words: “items near each other appear related.” Crowd a layout and the groups people rely on blur. The fixes have concrete values: a spacing scale, line and paragraph spacing, and space between touch targets.
Four ways crowding hurts
| What crowding breaks | What the visitor experiences | What fixes it |
|---|---|---|
| Grouping | Cannot tell which label goes with which field, or which items belong to one section | More space between groups than within them |
| Hierarchy | Headlines and calls to action blend into surrounding content | Space around the elements that matter most |
| Reading | Eyes lose their place moving to the next line; long blocks feel tiring | Line spacing, paragraph spacing, and a sensible line length |
| Tapping | Taps land on the wrong control | Target size and space between targets |
Grouping: space does the work of boxes
In Gestalt terms, proximity implies relationship: things close together read as related, things far apart as separate. The Interaction Design Foundation’s overview of Gestalt principles lists proximity among them. Space can define a form section or a card as clearly as a border can, and when everything is equally spaced, nothing reads as a group.
Marieke McCloskey’s Nielsen Norman Group article on grouping form elements with white space shows the effect on a long form: “Increasing the white space between form elements makes this 15-field form less overwhelming and therefore more likely to be completed.” In the redesigned version, users see a three-part form with four to six fields each. The same article warns that a large gap between a label and its field makes it hard to tell what to enter where. How to design the fields themselves is covered in designing user-friendly and error-free form fields.
Hierarchy: isolation signals importance
An element surrounded by space has nothing competing with it; an element packed among neighbors becomes one of many things the eye might land on. Headlines need space above and below to read as section markers rather than as part of the text around them, and a call-to-action button needs room around it to stand out. Using space together with size, contrast, and position is covered in visual hierarchy principles for directing user attention.
Reading: line and paragraph spacing
When lines sit too close together, readers can lose their place returning to the next line, and paragraphs without space between them read as a wall. WCAG gives two concrete reference points:
- Text Spacing, 1.4.12 (Level AA), does not set your default. It requires that nothing breaks when users raise line height to at least 1.5 times the font size, paragraph spacing to at least 2 times, letter spacing to at least 0.12 times, and word spacing to at least 0.16 times.
- Visual Presentation, 1.4.8 (Level AAA), asks that “Line spacing (leading) is at least space-and-a-half within paragraphs,” with larger spacing between paragraphs, and that lines be no wider than 80 characters, or 40 for Chinese, Japanese, and Korean text.
A line height of about 1.5 for body text is therefore a safe default. Typography choices beyond spacing are covered in how typography shapes brand perception and readability.
Tapping: size and separation
Touch targets need room as well as size, so a tap lands on the intended control:
| Source | Size | Spacing |
|---|---|---|
| WCAG 2.2, Target Size (Minimum), 2.5.8 (Level AA) | At least 24 by 24 CSS pixels | Smaller targets pass if a 24-pixel circle centered on each does not intersect another target or its circle; listed exceptions apply |
| Google, Android accessibility guidance | At least 48 by 48 dp | At least 8 dp between targets |
| Apple, Human Interface Guidelines | 44 by 44 pt default on iOS | About 12 pt of padding around bezeled controls, about 24 pt around controls without a bezel |
The WCAG criterion and its exceptions are set out in the Understanding document for Target Size (Minimum). Google’s touch target guidance says to consider “making touch targets at least 48x48dp, separated by 8dp of space or more,” and Apple’s accessibility guidelines say to “Consider spacing between controls as important as size.”
Micro and macro whitespace
Mark Boulton’s 2007 A List Apart article Whitespace separates two scales: macro whitespace, the space between major elements of a composition, and micro whitespace, the space between small ones, down to letters, lines, and the padding inside a component. Both need attention: generous section spacing does not rescue cramped text, and well-spaced text does not rescue sections jammed together.
A spacing scale keeps both consistent. For example, a scale of 4, 8, 16, 24, 32, and 48 pixels lets designers use the small steps inside components and the large steps between sections, and lets developers implement the same named values. How tokens like these are managed across products is covered in the long-term benefits of design systems.
Small screens need spacing more, not less
Desktop-sized gaps can take too much of a phone screen, so spacing can scale down at smaller breakpoints; a 48-pixel section gap on desktop might become 24 pixels on a phone. Some values should not shrink: touch-target spacing has to hold at every size, and line spacing should stay readable. Define spacing per breakpoint deliberately rather than letting it collapse.
Making the case to stakeholders
Empty space can look like unused screen to someone who wants more on the page. Two kinds of evidence help:
- Grouping research, such as the NN/g form example above, which shows space changing how hard a page feels to complete.
- Your own comparison. Test two versions of one template, one with the current density and one with your spacing scale applied, and compare task success, time, and the conversion that template exists for.
Set content limits per section in the design specification, so additions become a discussion about what to remove rather than a slow loss of space.
Too much space is a problem too
Excessive distance between related elements breaks their connection, and very long scroll distances to reach content can frustrate people. Dense data tables need different spacing than a storytelling hero section. Aim for space that shows the structure of each area, not for a single amount everywhere.
Questions teams ask
Stakeholders keep adding content until the space disappears. How do we stop it?
Agree content limits up front, such as a maximum word count per section, write them into the design specification, and when a request arrives, decide together what existing content it replaces.
Our competitors use dense layouts and seem successful. Is whitespace overrated?
Some audiences, such as people working with data, may expect density. Even dense layouts need grouping and hierarchy, which spacing provides. A competitor’s success may have other causes, so test density with your own users.
How much whitespace is right?
There is no single formula. Start from a spacing scale, body line height around 1.5, layouts that survive WCAG’s text-spacing adjustments, and touch targets that meet the size and spacing values above, then test the result on your own pages.
Use space to show which elements belong together and which matter most, set line spacing near 1.5 and keep layouts intact under WCAG’s text-spacing values, separate touch targets by the platform minimums, and measure the change by testing two versions of one template.