What is an Error State?

TL;DR

• An error state appears when something prevents the intended task from succeeding.
• Good error states explain what happened, what changed, and what the user can do next.
• Error messages should use plain language and preserve user work when possible.
• Errors can be field-level, page-level, network, permission, or system-wide.
• Recovery is part of the design, not just the message.

What does an error state look like?

A payment fails. A file upload is rejected. A user loses permission during a task. An API request times out.

The product should not simply display “Something went wrong.” It should help the user understand what they can do next.

What should an error state communicate?

• what happened
• what the user’s current state is
• whether any work was saved
• what action can recover
• whether the problem is temporary or permanent

Error state vs. validation

Validation prevents or explains invalid input before a larger operation completes. An error state can describe a broader system or task failure.

Both should be specific and actionable.

Error state vs. edge case

An edge case is a condition. An error state is one possible UI response when that condition blocks success.

How do teams design good error states?

1. Identify likely failure conditions.
2. Decide what the system can recover automatically.
3. Preserve user input whenever safe.
4. Explain the issue in plain language.
5. Offer the next best action.
6. Show support or escalation paths for unrecoverable cases.
7. Test the recovery flow, not only the message.

Common mistakes

Showing technical codes without explanation

The user needs product meaning, not internal diagnostics.

Blaming the user

Use neutral language and explain constraints clearly.

Erasing entered data

Recovery should not create more work than the original task.

Creating a dead end

When possible, provide retry, edit, alternate method, or support.

The bottom line

An error state asks: what failed, what is still safe, and how can the user recover?

Related terms

Edge case · Loading state · Product state · Interaction design

Relevant Figr resource

Read Prototyping UX Design for failure and recovery examples.