EmptyState
Centered, calm, never blame the user. Always tell them what could be here, and ideally how to get there.
No results found
Try adjusting your search filters.
iOS
No results found
Try adjusting your search filters.
Android
No results found
Try adjusting your search filters.
Web
tsx
Default
Bordered
Action
Compact
Success
Inside a table
Props
Do & Don’t
search
Don’t
Blaming the searcher for an empty result set makes a normal outcome feel like a mistake.
Do
No results found
Try adjusting your search filters.
State the result neutrally and point at the lever the user can pull (filters, query).
users
Don’t
A dead-end that only restates the emptiness leaves the user with nowhere to go.
Do
No users
Invite your first team member.
When the user can fix it, give them the one action that does (Invite, Create).
files
Don’t
Generic 'nothing here' copy never tells the user how files would get into the folder.
Do
No files
Upload or drag files here.
Name the gesture that fills the empty space so the next step is obvious.
activity
Don’t
An alarming red icon turns a calm, expected empty feed into a false error.
Do
No activity
Events will appear as they happen.
Keep a routinely-empty state calm: muted icon, reassuring copy, no urgency.
notifications
Don’t
Apologetic, sad-toned copy frames an inbox-zero win as a letdown.
Do
All caught up
No new notifications.
Celebrate a cleared queue: 'All caught up' reads as success, not absence.
errors
Don’t
A grey 'nothing found' disc reads as a failed query, not as a healthy, error-free system.
Do
No errors
Everything is running smoothly.
Signal the good news with a green check: zero errors is a passing state, not an empty one.
all-clear
Don’t
A green all-clear over copy that admits work is pending hides the action the user must take.
Do
All clear
No locked accounts or pending reviews.
Reserve the green all-clear for genuinely empty queues: nothing locked, nothing waiting.