Empty State Design Examples

Browse real empty state UI designs from Linear, Notion, Slack, Airtable, Intercom, and 50+ products. Study zero data states, first-run experiences, filtered views, and onboarding prompts from shipped SaaS apps. These empty state examples show how leading teams turn blank screens into opportunities for action and education.

All Empty State UI Examples

197+ real empty state UI screenshots from 107+ products — zero data views, first-run prompts, and filtered empty results.

Featured Empty State Designs

Explore empty state designs from these hand-picked SaaS products. Each showcases a unique approach to zero data states and first-run experiences.

Empty State Design Checklist

Use this checklist when designing or evaluating an empty state. These principles come from studying top empty state designs from Linear, Notion, Slack, and Airtable.

Explain why the state is empty

Don’t just say “No data.” Explain the context: “No issues yet,” “No tasks match your filter,” or “Your inbox is all clear.” Linear and Slack do this exceptionally well.

Provide a clear call to action

Every empty state needs a next step. Use a prominent button: “Create task,” “Invite teammates,” or “Browse templates.” The CTA should be the most obvious element on the screen.

Use encouraging, not negative copy

Frame empty states positively. Instead of “Nothing found,” say “Ready to create something?” Use encouraging phrases like “All clear!” or “You’re all caught up!” Positive framing feels motivating, not discouraging.

Add illustrations thoughtfully

Illustrations can add personality, but they’re not required. Use simple, on-brand visuals that clarify the state without adding noise. Avoid generic stock illustrations. Linear uses minimal icons, Notion uses friendly illustrations.

Differentiate first-run from recurring states

First-run empty states should educate and onboard. Show templates, examples, or tutorials. Recurring empty states (filtered views, completed lists) should be brief and functional. Use rich content for first-time users, minimal states for filtered views.

Make it fast to act

Users should understand and act in under 3 seconds. Keep copy short: one headline, 1-2 sentences, one CTA. Remove any friction from the next action. The best tools let you take the first action directly from the empty state.

Frequently Asked Questions

What makes a good empty state design?

A good empty state design turns a blank screen into an opportunity. The best designs explain why the screen is empty, show users what they can do next, and provide a clear call to action. Linear uses encouraging copy like "No issues yet" with a prominent "New issue" button. Notion suggests templates and shows example pages. Airtable offers template galleries for empty bases. Good empty states combine explanation, motivation, and action — they never just say "No data found."

What should an empty state include?

An empty state should include three things: context (why is this empty?), encouragement (this is normal, here's what you can do), and action (a clear next step). Use an illustration or icon to add personality, a headline that explains the state, body text with encouragement or instructions, and a prominent CTA button. Asana shows an illustration, explains "No tasks yet," and offers "Create task." Slack shows "No messages yet" with a "Send a message" input. Keep it simple: users should understand and act in under 3 seconds.

What are the best empty state UI examples?

Top empty state UI examples include Linear for its clean, encouraging empty project views, Notion for suggesting templates and examples, Slack for contextual empty channel messages, Airtable for template galleries in empty bases, Intercom for empty inbox states, Asana for project setup guidance, HubSpot for empty pipeline states, and Stripe for zero-transaction dashboards. Each excels in different areas: Linear for simplicity, Notion for templates, Slack for context, and Airtable for inspiration.

Should empty states use illustrations?

Illustrations work well for empty states but aren't required. Use them when they add personality or clarify the state without adding noise. Linear uses minimal icons. Notion uses friendly illustrations. Slack keeps it text-heavy. Illustrations should be simple, on-brand, and culturally neutral. Avoid clipart or generic stock illustrations — they feel cheap. If your product has a playful brand, illustrations work. If it's enterprise or data-heavy, a clean icon or text-only state may be better.

How do you design first-run vs recurring empty states?

First-run empty states (new users) should educate and onboard. Show what the feature does, offer templates or examples, and guide users to their first action. Notion excels here with template galleries. Recurring empty states (filtered views, deleted items, completed tasks) should be brief and functional. Just show a message and a way to change the view or take action. Many tools use educational empty states for first-time users, but minimal states for empty filtered lists. Context matters: first-run is about learning, recurring is about getting back to work.

What copy works best for empty states?

Empty state copy should be encouraging, not negative. Avoid "No results found" or "Nothing here." Use positive framing: "All caught up!", "No issues yet" (Linear), "Ready to get started?" works for most tools. Explain why it's empty if needed: "No tasks match your filter" with a link to clear filters. Keep it short: one headline and 1-2 sentences of body text. Add personality if it fits your brand, but clarity always comes first. Users should know what to do without reading twice.

Explore More Empty State and Onboarding Patterns

Browse empty state, onboarding, and dashboard UI patterns from 100+ SaaS products — organized by pattern type and software category.