Loading…
Loading…
Empty states occur when a page, list, or component has no data to display — first use, cleared lists, no search results, or filtered-out content. Rather than showing blank space or a generic 'Nothing here' message, effective empty states use copy and design to onboard, motivate, and guide users.
stellae.design
Empty states are the blank canvases of your product. They appear on first launch, in unused features, after searches return no results, and when users clear data. Each type needs different copy: first-use states should onboard, no-results states should guide, and cleared states should reassure.
Before/after examples: • Before: 'No items' → After: 'No projects yet. Create your first project to start collaborating with your team.' • Before: 'No results found' → After: 'No results for "designsystem". Try "design system" or browse popular topics.' • Before: '0 notifications' → After: 'You're all caught up! We'll notify you when something needs your attention.'
Empty state copy is the text and guidance displayed when a screen, list, dashboard, or component has no content to show — whether because the user is new, has applied filters that return no results, has completed or deleted all items, or has encountered an error — and it represents one of the most underutilized conversion and retention opportunities in product design because it appears at precisely the moments when users are most likely to feel confused, lost, or unmotivated to continue. A blank screen with no guidance communicates nothing, while a well-crafted empty state communicates what the feature does, why it is valuable, and exactly how to populate it with content, transforming a potential moment of abandonment into an onboarding touchpoint that drives activation. The quality of empty state copy is particularly consequential for new users experiencing a product for the first time, because every feature they encounter will initially be empty, and their decision to invest time in populating those features — or to leave and never return — is heavily influenced by whether the empty state makes the value proposition clear and the first action obvious.
When a new Notion user opens their workspace, each section presents thoughtfully crafted empty states that explain what the feature does, provide pre-built templates as starting points, and include a prominent action button — the empty 'Pages' sidebar says 'This is your workspace. Use it to organize everything' with quick-start template buttons that populate the first page with useful structure rather than a blank canvas. This approach transforms the potentially overwhelming experience of an empty productivity tool into a guided setup that immediately demonstrates value, and the templates serve as both content and education, showing users what is possible before asking them to create from scratch. Notion's empty states are widely cited as best-in-class because they combine clear copy, visual warmth, and actionable next steps.
Slack differentiates its empty state copy based on context — an empty channel says 'This is the very beginning of the #design channel' with an invitation to set the channel's purpose, an empty search says 'No results found for 'xyzzy' — try different search terms or check your spelling,' and an empty direct message thread invites users to start the conversation with a message prompt. Each empty state includes contextually appropriate guidance and actions that match the user's likely intent, rather than displaying a generic 'Nothing here' message that provides no path forward. This contextual approach means users always know what to do next, regardless of which empty state they encounter.
A SaaS analytics dashboard loads for a new user and displays six empty chart containers with axis labels but no data, no explanation of what metrics each chart will track, no guidance on how to connect data sources, and no indication of how long it takes for data to begin appearing — just white rectangles with faint grid lines that look like the page failed to load properly. Users who sign up for a trial, see an apparently broken dashboard, and cannot determine their next step have a churn probability that is three times higher than users who encounter an onboarding-oriented empty state with clear setup instructions. Replacing the empty charts with contextual messages like 'Connect your first data source to see real-time conversion metrics here — it takes about 2 minutes [Connect data source]' transforms the same screen from a dead end into an activation funnel.
• The most common mistake is treating empty states as edge cases that do not require design attention — teams build features assuming data will be present and only discover during QA that the empty state shows a blank screen or a cryptic 'No data' message, which means every new user's first impression of the feature is the experience that received the least design investment. Another frequent error is writing generic empty state copy that is reused across all contexts — 'Nothing to see here' works for neither the new user who needs onboarding guidance nor the search user who needs query suggestions nor the power user who cleared their inbox and deserves a moment of celebration. Teams also forget to design empty states for filtered or searched views separately from first-use empty states: telling a user 'You have no messages' when they actually have hundreds but their filter returned zero results is factually wrong and erodes trust in the interface.
Was this article helpful?