Empty state

An empty state is what users see when there is no content to display. Well-designed empty states explain the context, guide the next action, and prevent users from feeling lost or confused.

What is an empty state in UX design?

An empty state is the screen or component state that users see when there is no content to display. This happens during a user's first experience with a product before they have created any data, after they have deleted or completed everything, or when a search or filter returns no results. Empty states are one of the most overlooked moments in interface design and one of the highest-impact opportunities to guide, reassure, and retain users.

What are the types of empty states in UX?

First-use empty state appears when a user has just signed up and the product contains no data yet. The goal is to orient the user, explain what will appear here, and motivate them to take the first action. This is often the single most important screen in the onboarding flow.

User-cleared empty state appears when the user has deleted or completed everything, such as an emptied inbox or a finished task list. The goal is to acknowledge the state positively and offer a clear next step.

No results empty state appears when a search or filter returns nothing. The goal is to explain why nothing was found and suggest what the user can do next, such as adjusting filters or broadening the search.

Why do empty states matter in UX design?

A blank screen with no guidance reads as broken. Users don't know whether something went wrong, whether the product is empty by design, or what they should do next. Poor empty states are one of the fastest ways to lose new users during onboarding before they have experienced the product's value. A well-designed empty state reduces cognitive load, sets correct mental model expectations, and turns a potential dead end into a starting point.

How to design effective empty states

Always explain why the state is empty using plain language. Always provide a clear, specific call to action that moves the user forward. Use supportive visuals if they add clarity, but not if they replace context. Keep the tone encouraging rather than clinical. Avoid generic messages like "No data" or "Nothing here" that leave users with no path forward.

Related terms

Related guides