Understand Different Types of Empty States
Feedback & States · empty states
Updated 2026-07-28
- Not every empty screen means the same thing. The interface should explain why there is no content and what the user can do next.
- Design different patterns for different situations:
- First run empty state
- The user has never used the feature.
- Explain what the feature does.
- Show how to get started.
- Provide a clear first action.
- No results empty state
- The user searched or filtered but found nothing.
- Suggest alternatives.
- Help users adjust their search.
- Provide ways to continue.
- Error empty state
- Something failed while loading or processing.
- Explain what happened.
- Provide recovery actions.
- Filtered empty state
- Content exists, but current filters hide everything.
- Help users remove or adjust filters.
- Do not treat empty states as dead ends. They are opportunities to teach, guide, and move users forward.
- A good empty state answers:
- Why is this empty?
- What can I do now?
- What happens next?
Related guides
UX Handbook