Empty states
One style, one reason, one action.
Every list, chart and folder starts out empty. Plenty end up empty again.
Each of those moments gets designed on its own screen, so a product slowly collects styles: an illustration here, a lone icon there, “No data found” with two buttons somewhere else. This read covers the seven styles, what an empty state is for, and the rules I use to make them feel like one product.
Seven ways to show it
Most empty states use one of seven styles. They all say the same thing. The only difference is how much space the picture above the words takes up.
No activity in this range
Charts fill in once your team closes its first task this week.
- Illustration: a drawn scene. Warm on a first visit. Every new screen needs a new drawing.
- Spot: one small object on a soft wash of colour. Lighter than a scene, warmer than an icon.
- Icon tiles: a few small icons that hint at what will land here.
- Badge: one icon with a small mark for the state: a count, a check or an arrow.
- Preview: a faint copy of the row or card that will show up.
- Icon: one small grey icon. Cheap, and quick to turn generic.
- Text only: a title, one line and an action. Fits rows, tiles and menus.
None of them is wrong. The trouble starts when one product uses all seven.
The style you pick is also part of your brand. An empty state is one of the few places in a product with room for a visual, so its colour, shape and detail show up on every screen that has nothing to show yet. Used the same way everywhere, it reads as yours.
Say why it’s empty and what comes next
An empty state has three jobs: say why there’s nothing here, say what will show up, and offer a way to fill it. Nielsen Norman Group calls them system status, learning cues and direct pathways. “No data found” does none of them. It doesn’t even say whether the system is still working.
The title names what’s missing. The line below says what makes it appear. That line adds something. It never repeats the title.
No invoices yet
Paid invoices show up here.
Where it goes wrong
Most products I look at have the same five problems:
- Every screen has its own style, because each one was designed on its own.
- “No data found” and nothing else. No reason, no next step.
- The action is unclear: “Get started”, two buttons of the same weight, or a button the person can’t use.
- It flashes up while the data is still loading, or after the request failed.
- A chart draws a line at zero when nothing was measured.
Each has a simple fix. The sections below go through them.
One component, three sizes
The same empty state appears on a full page, inside a card and in a single table row. I pick one style, keep it as one component and let the container decide the size. Drawing a new one for each place is how the styles multiply. Primer, PatternFly and SAP Fiori all work this way. Fiori even picks the size from the container’s width.
- Page: visual, title, one line and one action.
- Card: the same with less padding. The action is often a text link.
- Inline: one line of text and no icon. For a table row, a dashboard tile or a menu.
No deploys this week
Each push to main shows up here.
Connect a repositoryKeep the visual small, whichever style you pick. A big illustration pushes the content down, needs a new drawing for every screen, and gets loud when three panels on one dashboard are empty at once. Save illustrations for a full page on first use, where people see them once.
| System | Sizes |
|---|---|
| Primer | Small, medium, large |
| PatternFly | Extra small, small, large, extra large |
| SAP Fiori | Base, dot, spot, dialog, scene |
| GitLab | Compact, regular |
| Atlassian | Narrow, wide |
Keep the frame
Only the area where the content would be changes. An empty table keeps its header, an empty chart keeps its axes, and an empty folder keeps its path. People still see where they are, and nothing jumps when the first row arrives.
Charts need one more rule: missing isn’t zero. If nothing was measured, draw no line and leave the number out. A line at zero says something happened and the value was zero. Datawrapper and Grafana both leave gaps for missing data instead of joining the points across them.
One action, or none
An empty state gets one main action, named with a verb and a noun: “Create project”, “Upload”, not “Get started”. Docs go in a text link below it. Two buttons of the same weight make people choose before they’ve started.
Some need no button at all. An inbox someone has cleared is done, so it says so and stops. When the person isn’t allowed to fill the space, a button they can’t use is worse than none. Say who can, and offer to ask them.
You’re all caught up
Mentions and replies show up here.
Show the search and the way back
No results is different: the person did something. So the message repeats exactly what they searched for, in quotes, and offers the next step. Search somewhere wider, clear a filter or check the spelling.
If a filter hides results, name it and say how many it hides. “3 tasks are hidden by Status: Open” beats a blank list that looks like there’s nothing at all.
No results for “march invoice”
Nothing in Logos matches.
Don’t show it while loading
Show the empty state only when the request came back with nothing. Until then, show a skeleton. “No projects yet” flashing up for half a second before the projects load is the most common empty state bug.
Errors get their own message. “Couldn’t load projects” with a retry button is not the same as having no projects. The person needs to know which one it is.
Write it short
Empty states get seen often, so the words stay plain:
- A title of up to five words, without a full stop.
- One sentence below. It adds to the title instead of repeating it.
- Say what’s missing: “No invoices yet”, not “Nothing here”.
- No blame and no jokes. A joke is fun the first time and tiring by the tenth.
- The button names the action and the thing.
Copy for each type
One component, six situations. Only the title and the action change.
| Type | Title | Action |
|---|---|---|
| First use | No projects yet | Create project |
| No results | No results for “march invoice” | Search all files |
| All done | You’re all caught up | None |
| No access | Only owners can see billing | Request access |
| No data in range | No requests this week | None |
| Failed to load | Couldn’t load projects | Try again |
All of this is my own reading of empty states, not a rulebook. Take what fits your product, change what doesn’t, and disagree where you see it differently.
Sources
- Nielsen Norman Group, Designing Empty States in Complex Applications
- Primer, Blankslate
- PatternFly, Empty state design guidelines
- SAP Fiori, Illustrated Message
- GitLab Pajamas, Empty states
- Atlassian Design System, Empty state
- Carbon Design System, Empty states pattern
- Datawrapper Academy, Patchy data
- Grafana, Standard options: No value