Empty State Design: Patterns, Copy and Examples
Empty state design guide: the six types of empty screens, anatomy, layout specs and copy templates that turn blank screens into a clear next step for users.

This guide is for designers, PMs and founders who want every blank screen in their app to do a job. Empty states are some of the most viewed screens in any product, because every new user sees them first, yet they are often designed last. You will learn the six types, the anatomy of a good one, layout specs, copy templates and a checklist to audit your app.
TL;DR: An empty state should explain what belongs here, why it is empty and what to do next, with one clear action. Design different versions for first use, cleared content, no results, errors, missing permissions and locked features. Keep it short, keep the illustration small, and never leave a screen that is just blank.
Why empty state design matters
An empty screen creates doubt. A new user wonders if the app loaded; a shopper with zero results assumes the store lacks the item; a blank feed offline looks broken. Each is a point where people quit. Good empty state design replaces doubt with direction, and for new users it is often the first lesson in how the product works, which makes it part of onboarding. Our onboarding screen design guide covers the screens that come before it.
The six types of empty states
| Type | When it appears | Goal | Example copy |
|---|---|---|---|
| First use | New user, no content yet | Teach and prompt the first action | "No projects yet. Create one to get started." |
| User cleared | User finished or deleted everything | Reward and reassure | "All done for today." |
| No results | Search or filter returns nothing | Help recover | "No results for 'blu sneakers'. Check the spelling or try fewer filters." |
| Error or offline | Data failed to load | Explain and retry | "You're offline. Reconnect to see new messages." |
| Permission needed | Feature needs access the user declined | Explain value, link to settings | "Turn on location to see stores near you." |
| Locked or upgrade | Feature unavailable on current plan | Explain value without nagging | "Reports are available on Pro." |
Most apps need at least four. The mistake is designing one generic "Nothing here" screen and reusing it for all of them, because each has a different cause and a different next step.
Anatomy of a good empty state
From top to bottom, a well-designed empty state usually has:
- •Visual (optional): a small illustration, icon or product preview that signals the context.
- •Headline: what is missing, in plain language.
- •Body: one or two short lines explaining why, or what the user will get.
- •Primary action: one button that resolves the state.
- •Secondary action (optional): a link to learn more, import data or try a template.
Layout specs that work on mobile
| Element | Guideline |
|---|---|
| Vertical position | Optically centered, slightly above true center, or top-aligned under the header |
| Illustration | Roughly 120 to 200 pt wide; never push the button below the fold |
| Headline | Title style, around 20 to 22 pt, 1 to 2 lines |
| Body | Body or callout style, 15 to 17 pt, max about 2 to 3 lines, centered |
| Text width | Constrain to about 280 to 320 pt so lines stay readable |
| Primary button | Standard height (44 pt iOS minimum, 48 dp Android) |
| Spacing | 16 to 24 pt between groups; follow your spacing scale |
If your app has a tab bar, keep it visible on empty screens so users can still navigate elsewhere. For consistent gaps, use the increments from our mobile app spacing system.
How to design each type
1. First-use empty states
This is where you teach. Options, from simplest to richest:
- •Prompt: a headline and one button. "No habits yet → Add your first habit."
- •Starter content: pre-filled examples or templates the user can keep or delete. Notion and Trello-style tools often show sample pages or boards so the structure is obvious.
- •Ghost preview: a faded preview of what the screen will look like with data, such as skeleton cards or a sample chart, so users understand the value before they invest effort.
- •Guided checklist: three to five setup steps with progress, useful for apps that need configuration.
The best first-use states make the first action tiny. "Add your first expense" is easier than "Set up your budget."
2. User-cleared states
When a user empties their inbox or completes every task, the screen should feel like a reward, not a void. A short positive message and a light illustration work well. Todoist and many email clients celebrate inbox zero this way. Offer a gentle next step if one exists: "Plan tomorrow" or "View completed."
3. No-results states
These are recovery screens. Effective patterns:
- •Repeat the query so users can spot typos.
- •Suggest corrections ("Did you mean 'blue sneakers'?").
- •Offer to remove the most restrictive filter, ideally as a one-tap chip.
- •Show popular items or categories instead of a dead end.
- •Let users save the search or get notified when matches appear, if relevant.
Never show a no-results state while results are still loading. Use a loading or skeleton state first, then switch.
4. Error and offline states
Be specific and honest. Users need to know whether the problem is their connection, the server or something they did.
- •Offline: explain, show any cached content, and retry automatically when the connection returns.
- •Server error: apologize briefly, offer "Try again," and avoid error codes in the headline.
- •Partial failure: if one section fails, show an inline error in that section, not a full-screen takeover.
5. Permission-needed states
When a user declines camera, location, contacts or notifications, the feature should not just break. Show what they are missing and how to fix it. On both iOS and Android, once a permission is denied, you typically need to send users to system settings, so make the button say exactly that: "Open Settings."
6. Locked or upgrade states
Show the value, not a padlock. A preview of the locked report or feature, with one line about what it does and a clear upgrade button, feels fairer than a blank screen with a padlock. Keep a way back so it never feels like a trap.
Copy templates you can adapt
Good empty state copy is specific to your product. These templates are starting points:
| Situation | Headline | Body | Button |
|---|---|---|---|
| First use, list | "No [items] yet" | "[Items] you add will show up here." | "Add [item]" |
| First use, value | "Track your first [thing]" | "See [benefit] after a few days." | "Start tracking" |
| Cleared | "You're all caught up" | "New [items] will appear here." | "View archive" |
| No results | "No matches for '[query]'" | "Try a different spelling or fewer filters." | "Clear filters" |
| Offline | "You're offline" | "We'll refresh when you're back online." | "Try again" |
| Server error | "Something went wrong" | "We couldn't load your [items]. Your data is safe." | "Try again" |
| Permission | "Location is off" | "Turn it on to see [places] near you." | "Open Settings" |
| Locked | "[Feature] is on Pro" | "[One-line benefit]." | "See plans" |
Copy rules:
- •Use the user's vocabulary, not your internal names.
- •Lead with what they can do, not what is missing, wherever possible.
- •Keep body text to two lines on a phone.
Visual style: illustration or not?
Illustrations add warmth, but they are optional. Guidelines:
- •Use them for first-use and cleared states where tone matters.
- •Skip or shrink them for no-results and errors, where speed of recovery matters more.
- •Keep one style across the app: line weight, color palette and level of detail.
- •Make them decorative for screen readers unless they convey information, and make sure the headline and button carry the meaning.
- •Check contrast for any text or icons placed on tinted backgrounds using the contrast checker.
- •Support dark mode with illustration variants or colors that work on dark surfaces.
Worked example: a budgeting app
Here is how one app might cover all its empty states:
- •Transactions, first use: ghost list of three faded sample transactions, headline "No transactions yet," body "Connect your bank or add one manually," primary "Connect bank," secondary "Add manually."
- •Budgets, first use: three starter budget templates (Groceries, Eating out, Transport) as tappable cards.
- •Search, no results: "No transactions match 'netflx'," suggestion "Did you mean 'Netflix'?," chip "Remove date filter."
- •Offline: cached balances shown with a banner "Offline. Showing balances from 9:41."
- •Notifications denied: in the alerts screen, "Bill reminders are off," button "Open Settings."
- •Reports locked: a blurred preview of the monthly chart with "Monthly reports are on Pro" and "See plans."
You can generate a first draft of each of these states in floow by describing the screen and its empty condition, then compare versions side by side.
Empty state design checklist
- • Every list, feed, search and dashboard has a designed empty state
- • First-use states have one clear, small first action
- • No-results states repeat the query and suggest recovery
- • Error states distinguish offline from server problems
- • Permission states link directly to system settings
- • Locked states show value and a way back
- • Loading states appear before empty states, never instead of them
- • Copy is specific, short and uses the user's words
- • Navigation stays visible
- • Illustrations are consistent, optional and accessible
- • Works in dark mode and at large text sizes
Browse the templates library to see how complete apps handle these moments.
FAQ
What is an empty state in UI design?
An empty state is what a screen shows when there is no content to display, whether because the user is new, has cleared everything, got no search results, lost connection or lacks permission. Good empty states explain the situation and offer a next step.
Should every empty state have an illustration?
No. Illustrations help set tone in first-use and success states, but in error and no-results states a short message and a recovery action are more useful. Keep any illustration small so the action stays visible.
What is the difference between an empty state and a loading state?
A loading state shows while content is being fetched, often as a spinner or skeleton. An empty state shows once loading has finished and there is nothing to display. Showing an empty state too early misleads users into thinking there is no data.
How do I write good empty state copy?
State what belongs on the screen, explain briefly why it is empty and name the action in the button. Use plain, specific language, keep it to a headline and one or two short lines, and avoid humor when something has gone wrong.
Design it with floow
Design all of your app's empty states together in floow, so they share one visual language. Paste this prompt to start:
Design four empty state screens for an iOS budgeting app: a first-use transactions list with a faded ghost preview and "Connect bank" button, a no-results search screen with a spelling suggestion and filter chip, an offline banner over cached balances, and a locked reports screen with a blurred chart preview and "See plans" button.
Design your mobile app with AI.
Generate pixel-perfect iOS and Android screens in seconds, then export to Figma or code.
You might also like…
Guides22 November 2026Mobile App Accessibility: Designer and Founder ChecklistMobile app accessibility made practical: contrast, touch targets, Dynamic Type, VoiceOver and TalkBack labels, motion and a full pre-launch checklist.By floow.design
Roundups22 November 2026ScreensDesign Alternatives: 9 Places for Real App ScreensScreensDesign alternatives compared: Mobbin, Page Flows, Refero and more, with what each library is best for and how to turn references into your own screens.By floow.design
Insights21 November 2026Music App Design: Player, Library and DiscoveryMusic app design guide: home and discovery, search, library, mini player, now playing, queue and offline, plus lock screen, car and widget surfaces, with.By floow.design