artifactExperience & interface

Empty State

An empty state explains why useful content is absent and, when appropriate, gives people a clear path to create, find, restore, or configure it.

Download Markdown (.md)

01What it means

An empty state is the interface shown when a collection, search, dashboard, or feature has no content. Different causes require different treatment: first use, no search results, filters, deleted data, lack of permission, and system failure are not the same condition. The state should identify the cause before proposing an action.[1][2]

02Why it matters

Blank space can look broken or final. A good empty state establishes context, teaches the product model, and directs the next useful action without inventing urgency. It improves onboarding and completion while preventing people from confusing an empty result with loading or failure.

03When to use it

Use an empty state wherever a component depends on data that may legitimately be absent. Define first-use, search, filter, permission, deleted-content, and offline conditions during component design rather than adding generic placeholder copy after implementation.

04How it works

  1. Detect and name the specific reason content is absent.
  2. Keep stable page structure and labels so the person knows where they are.
  3. Explain the condition briefly in language appropriate to its cause.
  4. Offer one primary next step when the user can change the state.
  5. Distinguish empty, loading, error, and permission states visually and semantically.

05A practical example

Example

A saved-reports page with no reports keeps its title and navigation, explains what saved reports are, and offers “Create report.” If filters hide existing reports, it instead says no reports match and offers “Clear filters,” avoiding an onboarding message that misdiagnoses the situation.

06Where it breaks

Empty states should not become promotional billboards or illustrations that push action below the fold. Some states have no remedy and need honest explanation, not a false call to action. Large imagery hurts performance, and decorative graphics need suitable alternative-text treatment.

Common mistakes

  • Using one message for first use, no results, errors, and permissions
  • Removing surrounding structure so the page appears broken
  • Adding several competing calls to action

07Sources

  1. Empty statesCarbon Design System · Institutional design systemEmpty states
  2. Empty stateShopify Developer Documentation · Platform design guidanceEmpty state
View saved topics

Start typing to search titles, definitions, categories, and frameworks.