The Design of a Good Empty State

Nothing is still a state

An empty screen is easy to ignore during design reviews. There is no data, no table, no activity—nothing to show.

Yet empty states are often the first experience a new user has with a product.

That makes them important.

An empty state should not apologize for having nothing. It should explain what happens next.

The wrong approach

A weak empty state says:

No items found.

Technically accurate. Practically useless.

The user now has to guess whether they made a mistake, whether the system is broken, or whether they simply need to take an action.

Give the user a next step

A better empty state answers three questions:

• What is empty?
• Why is it empty?
• What can I do next?

For example:

No saved articles yet. Save anything you want to come back to later.

[Explore articles]

That is not merely friendlier copy. It reduces ambiguity.

Empty states teach product behavior

A new user does not know the rules of an unfamiliar product. Empty screens are opportunities to teach those rules without a tutorial.

The screen can introduce vocabulary, explain relationships, and invite the next action.

This is especially valuable in dashboards, file systems, project tools, and publishing platforms.

Tone matters

Good empty-state copy reflects the brand.

A serious financial tool may use restrained language. A creative community might be more playful.

But humor should never hide the action the user needs.

A tiny screen with a large job

The empty state is a reminder that interface design is not about filling space.

It is about helping people understand what the system is, what it can do, and what they can do next.

That makes an empty screen a surprisingly powerful piece of product design.

When there is nothing to show, the interface has to explain more—not less.