An empty state is any part of an interface that has nothing to display: a project list before the first project, a search with no results, or an inbox after everything is handled. For new users, empty states appear constantly during onboarding. A blank table with no explanation leaves people unsure what to do, while a well-designed empty state explains what will appear and offers the action that fills it.
Types of empty states
Each type needs a different message.
- First use: nothing has been created yet; explain the value and give the first action.
- User cleared: everything has been completed or deleted; confirm and offer the next step.
- No results: a search or filter returned nothing; suggest changes or alternatives.
- Error or permission: something failed or is restricted; explain why and what to do.
What a good first-use empty state includes
A short headline about what this area is for, one sentence on the benefit, and a clear primary button to create the first item. Many products add a secondary option: import existing data, load a template or watch a short video. An illustration can soften the screen but should not replace the explanation.
Why it matters for conversion
In a trial, a new user's first screens are often empty states. If those screens do not lead to the activation action, the trial can stall before it starts. Sample data or templates let users see what a full account looks like, which can make the value clear before they invest time setting things up.
Example
From blank table to first import
Hypothetical contact manager Wrenhaven used to show new users an empty table with column headers. Its new empty state says “Your contacts will live here”, with a button to import a CSV, an option to connect a mailbox and a link to load sample contacts for exploring. The team tracks how many trials reach their first import.
Common mistakes
Leaving it truly empty
A blank screen gives no direction. Every empty state should tell the user what to do next.
Jokes instead of guidance
A playful illustration is fine, but the copy still needs to explain the next step plainly.
Questions
It can help users understand the product faster. Make sample data easy to remove so it does not clutter a real account.
