Error State

An error state is the designed version of something going wrong, the screen or message that explains the failure and offers a way forward.

Without one, users meet a blank page, a frozen skeleton screen, or a code that makes sense only to the system that produced it. The useful version says what happened in ordinary words and gives the next action, such as Retry, Go back, or Contact support. An error state turns a dead end into a decision.

It is not the same as an empty state. Empty means there is nothing here yet. Error means something expected could not arrive or an action failed. A toast can carry a small temporary failure, while a full error state belongs to the part of the task that cannot continue.

You'll hear error screen, error message, failure state, something went wrong, and error page. Microcopy owns the wording, but the whole screen owns recovery: message, action, preserved work, and enough detail to avoid repeating the same mistake.

Never blame the user for information the interface failed to explain. Save technical codes for a details link or support reference. The best error message answers "what can I do now?" before anyone has to ask.