Why does an empty state matter?

It is often a new user's first real screen. A blank table reads as broken, while a well-written empty state explains why it's empty and points to the one action that fills it — turning a dead end into an activation moment.

What's the difference between a first-use and a no-results empty state?

A first-use state appears when the user hasn't created any data yet, so it should encourage creation. A no-results state appears after a search or filter returns nothing, so it should suggest broadening the query rather than implying the user did anything wrong.

Should an empty state always have a CTA?

For first-use states, yes — a clear button to create the first item is the whole point. For no-results states a CTA like 'Clear filters' helps, while a hard error state should offer 'Try again' or a support link rather than a creation action.

How long should empty state copy be?

Brief. A short headline and one or two sentences of body are enough. The screen is already sparse, so a paragraph of explanation undercuts the calm, guided feeling a good empty state should have.

Is my input sent to a server?

No. Every piece of copy is assembled in your browser from your inputs. Nothing is uploaded, so you can draft copy for unreleased screens privately.

Empty State Copy Builder

Email me this result

Get this tool's output sent to your inbox, plus one useful tool a week. No spam, unsubscribe any time.

The Empty State Copy Builder writes the four pieces of text a good empty screen needs: an illustration note, a headline, a short body, and a CTA. Empty states are easy to overlook yet they’re frequently a new user’s first impression — a blank table with no explanation reads as a bug, while a guided empty state explains the blankness and points to the action that resolves it.

How it works

You choose the type of empty state — first-use (no data created yet), no-results (a search or filter matched nothing), or error (something failed) — and name the object the screen lists plus the action that fills it. The builder selects copy tuned to that intent: first-use states encourage creating the first item, no-results states suggest broadening the query without blaming the user, and error states offer a retry or support path. Each output includes a one-line illustration description so a designer knows what visual to pair with the words.

Tips and notes

Match the message to the cause. Never tell a user who just searched “Create your first project” — that’s a no-results state, not a first-run one.
One action, clearly labelled. First-use states earn their keep with a single obvious CTA; more than one button dilutes the activation moment.
Keep error states calm. Offer “Try again” or a support link rather than a creation prompt, and avoid blaming the user for a system failure.