Empty State
Also known as: zero state, zero-data state
What Is an Empty State?
An empty state is what users see when a screen has no content to display — before any data exists, after content has been deleted, or when a search or filter returns no results.
It's a moment most products encounter regularly, and most treat as a design afterthought. That's a mistake.
What Types of Empty States Are There?
Not all empty states arise from the same situation, and each warrants a different response.
First-time use — a new user opens the product for the first time. Nothing has been created yet. This is one of the highest-stakes moments in onboarding: motivation is high, and a blank screen with no guidance can kill that momentum fast.
User-cleared state — the user has deleted or archived all their content. Unlike first-time use, this person already knows the product and just needs a prompt to add new content.
No results — a search, filter, or query returned nothing. The empty state here should help users understand why nothing came back and what they can do about it.
Error state — data couldn't load due to a connectivity or system issue. This type requires a clear explanation and a recovery action, not just a blank space.
What Makes a Well-Designed Empty State?
A strong empty state does three things: it explains what belongs here, sets an expectation for what the space will look like once populated, and gives the user a direct path to get started.
An illustration, a short line of copy, and a clear action button are usually enough.
What it should never be is a blank screen. A screen that shows nothing communicates nothing, and users who can't figure out what to do next rarely return to try again.
What Are the Benefits?
Onboarding guidance — a first-use empty state is one of the most direct opportunities to guide users toward their first meaningful action in the product.
Reduced early drop-off — users who see a clear next step are far more likely to stay than users who hit a blank interface with no direction.
Brand presence — a well-crafted empty state maintains product personality even when there's nothing to display. That consistency matters.
Fewer support requests — clear, specific copy in empty states answers questions before users think to ask them.
What Are the Challenges?
Treated as an edge case — empty states are designed last, if at all, which means they reflect none of the thought invested in the primary UI.
Multiple variants required — different causes require different responses. A single generic empty state reused across first-time, no-results, and error scenarios satisfies none of them well.
Copy is harder than it looks — the message needs to be helpful, concise, and specific to context. Generic placeholder copy ("Nothing here yet!") provides no actual guidance.
Where Do Empty States Have the Most Impact?
The stakes are highest in data-driven products, where users arrive expecting populated charts, tables, or pipelines and instead encounter blank space. In SaaS dashboard design specifically, empty states are among the most common screens new users encounter, making them a direct influence on how early engagement takes hold or stalls.