15 Empty State Patterns for Better SaaS User Experiences
Fifteen empty state patterns for SaaS products, from first use and no results to no access and errors, with what each should say and the action to offer.
What should a SaaS empty state do?
A good empty state tells people why the area is empty, what would normally appear there and what they can do next, with a direct action to do it. Empty states fall into three broad groups: no data yet (first use), empty because of something the user did (no results, cleared, completed) and empty because of a problem (no access, errors, missing setup). Each group needs different wording and actions.
This list is for product designers, product managers and founders working on B2B and SaaS products, where empty screens are common: new accounts, new workspaces, filtered tables and permission-restricted areas. The grouping follows IBM's Carbon Design System, and the core guidance follows NN/g's Kate Kaplan: show system status, provide learning cues, and give direct paths to key tasks. The examples are illustrative, not taken from specific products. For ecommerce, see ecommerce empty states.
First use: nothing here yet
1. First-use with a primary action. A new projects screen says what projects are for and offers "Create your first project". Carbon recommends a positive title, such as "Start by adding data assets", rather than "You don't have any data assets".
2. Starter content or templates. Offer a template or sample to start from: "Start from a template" next to "Start blank". Templates show what good looks like and shorten time to value. Label sample data clearly so it is never mistaken for real data.
3. Import instead of create. Many users already have data elsewhere. "Import contacts from CSV" or "Connect your calendar" can be the main action when re-typing would be the alternative.
4. Inline documentation. A short explanation of what the feature does, a link to help, or a short video, in place. NN/g calls this a learning cue, and it works better than a tour users must remember later.
5. Dependent setup. When a screen depends on a step elsewhere, such as "Reports appear once you connect a data source", say so and link straight to that step rather than showing an empty chart.
6. Team-dependent empty state. For collaborative features, the useful action may be inviting colleagues: "Invite your team to start assigning tasks."
Empty because of something the user did
7. No search results. Repeat the query, suggest checking spelling or broader terms, and offer a way forward, such as clearing filters, searching everywhere or creating the item they looked for.
8. Filters match nothing. Show which filters are applied and offer to remove the most restrictive one or clear them all. Never just say "No data".
9. Cleared or completed. An empty inbox or task list after the user finished their work is good news. Confirm it ("All caught up") and, if useful, point to what is next.
10. Archived or deleted content. When users empty a list by archiving or deleting, show where the items went and how to restore them.
11. Date range with no activity. Analytics and reporting screens should say "No activity between 1 and 7 March" and offer a wider range, rather than displaying an empty chart that looks broken.
Empty because of a problem
12. No permission. Explain that the content exists but the user cannot see it, who can grant access, and offer "Request access". Take care not to reveal sensitive details, such as titles of restricted records.
13. Plan or feature limit. If a feature is not in the user's plan, say what it does and how to get it without a hard sell, and make it clear the user has not lost data.
14. Loading failed. Distinguish "nothing here" from "we could not load this". NN/g's first guideline is to communicate system status: an empty area during or after a failed load confuses users. Offer "Try again" and say whether their data is safe.
15. Offline or sync pending. In apps that sync, say that content will appear once the connection returns, and show anything stored locally.
Designing a SaaS product's first-use experience?
ZSpace Labs designs SaaS interfaces, including empty, loading and error states, as part of UI/UX design projects.
Pattern table
| Pattern | Group | Message should say | Main action |
|---|---|---|---|
| First use | No data | What will appear here | Create the first item |
| Starter content | No data | Start from an example | Use a template |
| Import | No data | Bring existing data in | Import or connect |
| Inline documentation | No data | What the feature does | Learn more, then create |
| Dependent setup | No data | What must happen first | Go to the setup step |
| Team-dependent | No data | Who needs to join | Invite teammates |
| No search results | User action | What was searched | Broaden, clear or create |
| Filters match nothing | User action | Which filters apply | Remove a filter |
| Cleared or completed | User action | Work is done | Optional next step |
| Archived or deleted | User action | Where items went | Restore |
| Empty date range | User action | No activity in this period | Change the range |
| No permission | Problem | Content is restricted | Request access |
| Plan limit | Problem | Feature not in this plan | See plans |
| Loading failed | Problem | Could not load; data is safe | Try again |
| Offline or sync pending | Problem | Will appear when back online | Retry or wait |
Writing and design checklist
- Design empty states for every list, table, dashboard and search before development, not after.
- Lead with a short, positive title; explain in one or two sentences.
- Offer one primary action and at most one secondary link.
- Make loading, empty and error look different so users can tell them apart.
- Keep illustrations small enough that the message and action stay visible on small screens.
- Make empty states accessible: real text, not text inside images, and actions reachable by keyboard.
- Track how often users click the empty state's action; it is a useful onboarding signal.
Pro tip
First-use empty states are often the most effective onboarding you can build. See SaaS onboarding optimisation for defining activation and measuring the first session.
Conclusion
Empty states are moments when users are most likely to be confused, and also most open to guidance. Identify which of the three groups each one falls into, say why the area is empty, and give a direct action. For the words themselves, see UX writing and microcopy; for the wider product, product design for SaaS.
Sources
IBM Carbon Design System, empty states pattern. Nielsen Norman Group, Kate Kaplan, Designing Empty States in Complex Applications: 3 Guidelines (2021). Accessed 28 October 2026.
Common questions.
Any screen or area that has no content to show, whether because the user has not added anything yet, a search or filter found nothing, they cleared everything, they lack access, or something went wrong. Each of these needs a different message and action.