Skip to content
UX Atlas
UI foundationCraft conventionIntermediate

Density

How much information occupies a given area, which should follow the user's expertise and task rather than a house style.

Definition

Density is the amount of information presented per unit of screen area. It is a deliberate trade between scanning ease and the amount visible without scrolling, and different users legitimately need different points on that trade.

Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.

On this page
  1. Definition
  2. Choosing a density
  3. Density is a user preference, not only a design decision
  4. In practice
  5. Continue from here

Choosing a density

ContextDensityWhy
Marketing and landing pagesLowOne message at a time, first-time readers, no repeated use.
Consumer applicationsMediumOccasional use, mixed expertise, touch targets matter.
Professional toolsHighDaily use, learned layout, scrolling is more expensive than tightness.
Data tables and monitoringVery highComparison across many rows is the entire task.
MobileMedium regardlessTouch target minimums set a floor that density cannot cross.

Density is a user preference, not only a design decision

Mature professional tools offer a density setting because the correct value differs by user, screen and task. Offering compact, comfortable and spacious variants driven by a single spacing token multiplier is a small implementation cost with a large payoff for power users.

The constraint is that touch targets have a hard floor. Density can compress visual spacing without compressing hit areas below the accessible minimum.

In practice

Density settings

Enterprise tables

A row-height control with three options, implemented as a spacing multiplier, lets analysts fit twice as many rows while keeping the same component code.

Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.

Applied through

Where this shows up as a concrete interface decision.

Principles behind this

The reasoning this solution is an application of.

Relied on by

Entries that assume this is already in place.

  • Data TableComponent

    How many rows fit on one screen decides whether the table can be compared at all.

Practical example

A worked decision where this was the deciding factor.

Check your work

Review passes that test whether this was done properly.

Related concept

Connected closely enough to change how you apply this.