What is Error state?
An error state is the condition of an interface when something has gone wrong, such as invalid user input, failed server requests, or system malfunctions. How errors are communicated determines whether users can recover or give up.
How it works
Effective error states follow several principles: they appear immediately (not after the user has continued working), they explain what went wrong in plain language (not error codes), they tell the user specifically how to fix it, and they preserve the user’s work (never clearing a form on error). Error messages should be placed near the source of the error, use a distinct visual style (typically red with an icon), and be written in a constructive tone. Inline validation (checking input as the user types) prevents many errors entirely.
Applied example
A payment form displays ‘Error 422: Unprocessable Entity’ after a user submits an order. Redesigning the error state to show ‘Your card was declined. Please check the card number and expiration date, or try a different card’ alongside the specific field that failed increases successful payment completion by 15%.
Why it matters
Error states define the experience of failure, and since every user eventually encounters errors, how a product handles failure is as important to overall experience as how it handles success.
