Empty States That Don’t Feel Broken: What to Show When There’s Nothing Yet

Three phone empty states in one illustration style: something went wrong, still searching and waiting for a reply

An empty screen is often the first thing a new user sees, and the moment most likely to make an app look unfinished. A good empty state explains what is going on, shows what will appear here and offers one clear next step.

For
Product designers, UX writers and founders designing apps, dashboards and web tools
Covers
First-use and onboarding screens, no-results pages and error states

What to avoid

These patterns show up in almost every product, and each makes an empty screen feel colder or more confusing than it needs to.

1A grey icon and “No data”

A faded folder or inbox icon with two words of system copy looks exactly like a loading failure. It tells the user nothing about why the screen is empty or what to do.

Try instead: one sentence explaining the state and a button for the next action.

2Astronauts, tumbleweeds and broken robots

Space scenes, deserts and sad robots are the stock answer for every empty or error screen. They are so familiar that users skip them, and they rarely connect to what your product actually does.

Try instead: a scene from your users' real context, such as a person writing their first note or setting up a first task.

3Jokes when something went wrong

“Oops! Our hamsters fell asleep” is charming once. On the third failed upload, or in a health or finance product, it reads as careless.

Try instead: a calm, human tone. Save humour for first-use screens, where nothing is at stake.

Three main kinds of empty states

Each kind starts from a different user feeling, so each needs different copy, a different action and a different picture.

1First use and onboarding

The user has just arrived and has not created anything yet. This is the empty state with the most potential, because it can teach the product while showing what success looks like.

Under-construction landing page empty state: We're still digging, with a hand-drawn illustration of two people at a building site and one Notify me button

2No results

The user searched or filtered and got nothing back. They did the work, so the screen should help them recover quickly rather than just report the outcome.

3Errors

Something failed: a connection dropped, a page is missing or the user lacks permission. The user is often frustrated, so clarity matters more than personality.

No-results empty state: We keep searching, with a hand-drawn illustration of two people searching with a telescope and magnifying glass
No results: the query, a way out and a quiet illustration.
Error empty state: Time for a new passport, with a hand-drawn illustration of a person holding a passport
Error: what happened and how to fix it.

Quick reference

State
How the user feels
What to show
First use
Curious, unsure where to start
The goal, one primary action and an optional template
No results
Mildly frustrated, ready to try again
The query, ways to widen the search and a small illustration
Error
Worried about their work
What happened, whether data is safe and a retry or help link

Keep one visual system across the states

Empty states are sometimes designed one at a time, by different people, months apart. That is how a product ends up with a flat icon on one screen, a 3D character on the next and a stock photo on the error page. Users notice, and the product feels pieced together.

Write the copy first

An illustration supports the message; it cannot replace it. Draft the headline, the one-line explanation and the button label before choosing a picture, then pick the scene that shows the same idea. If the screen still works with the image hidden, it is accessible, and the alt text can stay short or empty for purely decorative art.

Quick checklist

Try Friendly Onboarding or Vibrant HR

Both packs fit empty and error state UI, each in its own hand-drawn style. Easy-to-edit, with a personal or commercial licence.