Usually yes, and usually not where you think. Cramped designs are rarely short of space around the edges. They are short of space between related things and between unrelated things, in the wrong proportions. Fixing that is a matter of measurement rather than taste, and there are published standards that tell you the numbers.
White space is the part of design clients push back on hardest. It looks like nothing, so it looks like wasted room, and the instinct is to fill it. We spend a lot of early conversations explaining why the empty part of the page is doing work.
The good news is that this is one of the few design arguments with real evidence behind it. The W3C publishes specific spacing figures as accessibility requirements, and those figures happen to describe what good typography looks like anyway.
White space is any area of a layout with no content in it. That includes margins, padding, the gaps between columns, the space between lines of text, and the space between letters. It does not have to be white, and it is not empty in any useful sense. It is the thing that tells a reader what belongs with what.
Nielsen Norman Group describes white space as a principle for achieving balanced design that makes it easier for users to scan and read. That framing is worth holding onto, because scanning and reading are different tasks and spacing serves both.
The distinction designers make is between large scale and small scale spacing. Large scale is the gap between sections, the page margins, the room around a hero. Small scale is line height, letter spacing, and the gap between a label and its input. Most sites get the large scale roughly right and the small scale badly wrong.
The mechanism underneath all of it is proximity. Things placed close together read as related, and things placed far apart read as separate. Nielsen Norman Group names the proximity principle directly as the thing to design against. Every spacing decision is really a statement about what belongs together.
At least 1.5 times the font size. That figure comes from the W3C rather than from taste. WCAG success criterion 1.4.12 requires that content stays readable and functional when a user sets line height to at least 1.5 times the font size, and criterion 1.4.8 asks for at least space and a half within paragraphs.
Most sites ship with tighter line height than that, usually because a default was never changed. Body text at 1.2 or 1.3 looks fine to a designer reading one paragraph and becomes genuinely tiring across a long article.
WCAG 1.4.12 gives you three more numbers in the same place. Paragraph spacing of at least 2 times the font size, letter spacing of at least 0.12 times the font size, and word spacing of at least 0.16 times the font size. Those are the values your layout must survive when a reader applies them, not values you must use by default.
The distinction matters and gets missed constantly. You are not required to set letter spacing to 0.12em. You are required to build a layout that does not break when someone else does. If a reader increasing their spacing causes your text to overflow its container or clip, that is the failure the criterion is aimed at.
No more than 80 characters per line. WCAG 1.4.8 states the width should be no more than 80 characters or glyphs, and 40 for Chinese, Japanese, and Korean text, because those characters are roughly twice as wide. That is an upper bound rather than a target, and comfortable reading usually sits well below it.
The reason given is specific rather than aesthetic. The W3C explains that people with reading disabilities have trouble keeping their place and following the flow of text, and that narrower blocks make it easier to continue to the next line. Long lines make your eye lose its return point.
This is the single most common typography error we find on otherwise well built sites. Someone sets a content area to full width on a large monitor, and body text runs to 140 characters a line. It looks tidy in the browser window the designer used and becomes unreadable on a wide screen.
The fix is a maximum width on the text container, set in a unit tied to the text itself rather than to the viewport. Constrain the measure, then let the surrounding layout be as wide as it likes. Our guide to choosing fonts for a website covers how this interacts with typeface choice.
No. White space is a typographic term for unoccupied area, not a colour instruction. A dark section with generous padding has exactly as much white space as a light one. The word is a leftover from print, and it confuses people into thinking the technique requires a pale background.
What matters is that the area is genuinely unoccupied. A background pattern, a faint watermark, or a decorative gradient sitting behind your text reduces the effective breathing room even though the layout measurements have not changed. Visual noise consumes space that measurements say is empty.
This is why busy backgrounds so often make a design feel cramped when nothing about the spacing changed. You have not lost any pixels. You have lost the quiet that made the pixels feel like room.
The practical rule we use is that anything sitting behind text should be low enough in contrast that you stop noticing it within a second. If the background competes for attention, it is content, and it needs its own space rather than sharing the text's.
Use a scale, not individual judgments. Pick a base unit, commonly 4 or 8 pixels, and only ever use multiples of it. Every gap in the design becomes a choice from a short list rather than a number someone typed, which is what makes a layout feel deliberate rather than assembled.
Nielsen Norman Group's guidance points the same direction, recommending a consistent spacing system as the way to achieve balanced use of white space. Consistency is doing more work here than any individual value. A layout using five spacing values consistently looks better than one using thirty values chosen carefully.
The scale also settles arguments. When a gap looks wrong, the question stops being how many pixels it should be and becomes whether it should be one step larger or one step smaller. That is a question a team can answer in seconds.
Spacing tokens belong in your design system alongside colour and type. If your spacing lives as numbers typed into individual components, it will drift within a month of the first person joining the project, which is one reason we treat building a design system as infrastructure rather than polish.
Yes, and the failure is different from what people expect. Too much space does not look sparse. It looks disconnected, because elements that belong together stop reading as a group. A label floating too far from its input is not elegant. It is ambiguous.
The rule that prevents this is that spacing should be relative, not uniform. The gap inside a group must be smaller than the gap around the group. Get that ratio wrong and no amount of generosity helps, because the reader can no longer tell what is grouped with what.
Scroll cost is the second real limit. Space you add pushes everything below it further down, and on a long page that adds up to real work for the reader. A section break of 200 pixels repeated fifteen times is 3,000 pixels of scrolling that carries no information.
Where we do push for more space is around the things that matter most. A primary call to action with room around it reads as important, which is the same mechanism behind everything in our piece on visual hierarchy. Space is one of the few ways to signal importance without making something bigger or louder.
Because the layout was built in fixed pixels rather than relative units. When a reader increases text size or applies their own spacing, text grows but a fixed height container does not, so content overflows, clips, or overlaps. This is the exact failure WCAG 1.4.12 exists to prevent.
Fixed heights are the usual culprit. A card with a set height looks perfect with the copy it was designed around and breaks the moment the copy is longer or the text is larger. Setting a minimum height instead of a height costs nothing and removes the whole class of problem.
Buttons and navigation items are the next offenders. A button sized to fit its label exactly will clip that label at larger text sizes. Padding based sizing grows with the content. Fixed width sizing does not.
Testing this takes about a minute. Zoom your browser to 200% and set text spacing higher, then look for overlapping text and cut off labels. It is a faster check than most accessibility testing and it catches a genuinely common failure.
Horizontal space shrinks and vertical space matters more. On a narrow screen you cannot afford wide margins, so the side padding compresses, but the vertical rhythm between sections should stay generous because that is what keeps a long scroll navigable.
The common mistake is scaling every spacing value down proportionally. That produces a cramped mobile layout where nothing is distinguishable from anything else. Horizontal padding can drop a long way. Line height should not drop at all.
Line length usually fixes itself on mobile, since a narrow screen naturally produces a reasonable measure. The problem inverts. On mobile you are fighting for room, and on a wide desktop you are fighting to stop text sprawling to the full window width.
Touch targets add a constraint that does not exist on desktop. Interactive elements need space around them so people do not hit the wrong one, and that spacing is functional rather than decorative. Crowded mobile navigation is a usability failure before it is an aesthetic one.
Check three numbers on your own site. Is body line height at least 1.5. Does your longest line of body text stay under 80 characters on a wide monitor. Do your spacing values come from a scale or from whatever felt right. Those three cover most of what is wrong on most sites.
Then zoom to 200% and read a page. If something overlaps or clips, you have found a real bug rather than a preference, and it is affecting people right now who are not going to email you about it.
If you are getting pushback on white space from someone who wants to fill it, the W3C figures are a useful thing to have on your side, because they move the conversation from taste to requirement. And if you want a second pair of eyes on a layout that feels cramped but you cannot say why, we are happy to take a look. Come find us at phoenix.studio.
Tell us where you want to go. We'll tell you how we'd get you there.