Chunking

What it is

The concept comes from George Miller's 1956 paper 'The Magical Number Seven, Plus or Minus Two', which found that working memory can hold roughly 7±2 discrete items at once. Later research revised the ceiling downward to 4±1 for genuinely independent items, but the underlying insight held: memory has a small buffer, and design should respect it.

In UX, chunking shows up as visual grouping (spacing, borders, whitespace), semantic grouping (form sections with headings), and process grouping (multi-step flows broken into stages). The goal is to reduce what the user has to hold at once.

Why it matters

Users don't finish forms when the form is a single 40-field wall. They don't remember settings when settings are one flat list of 60 toggles. Chunking makes complex information tractable. It's especially important for anyone with cognitive load or working-memory pressure — new users, users under time pressure, users on mobile, users with cognitive disabilities.

When to use it

Any time the user needs to process more than 4-7 discrete pieces of information at once. Long forms, complex dashboards, product configuration flows, navigation systems, comparison tables, onboarding sequences. The heuristic: if a screen has more than 5-7 groups of things, chunk the groups themselves.

What it looks like in practice

A checkout flow broken into shipping, payment and review — three chunks, each fitting on one screen — outperforms a single-page checkout with all fields visible at once. An enterprise dashboard grouped into 'This week', 'Compared to last month' and 'Trends' outperforms the same metrics presented as an unstructured grid.

Chunking also applies to text: three short paragraphs are easier to skim than one long one carrying the same content, because each paragraph is a chunk the reader can navigate.

What people get wrong

• Chunking arbitrarily — putting things together because they look tidy, without semantic connection. False chunking misleads users about what belongs to what.
• Not naming the chunks. A visual group with no heading forces the user to infer what unites the elements — which negates the benefit.
• Over-chunking. Six items each in their own labelled box takes up more space and adds more cognitive overhead than the six items would in a plain list. Chunk when it reduces load; don't chunk for the sake of it.
• Ignoring chunking on mobile. Vertical space is scarcer, so bad chunking hurts more.

Learn next

Chunking sits inside the wider cognitive load framework, and it's the mechanism behind why gestalt principles (proximity, common region) work. It appears throughout information architecture and form design.

Reviewed 29 September 2026 · Editorial standards