Error message

An error message is a system response that informs users something went wrong and tells them what to do next. Done well, error messages recover the situation. Done poorly, they create confusion and abandonment.

What is an error message in UX design?

An error message is a system response that communicates to users that something went wrong and provides guidance on what to do next. Error messages are not just notifications. They are a moment of trust between the product and the user. When an error is handled well, the user stays in the flow and completes their task. When it is handled poorly, they lose confidence in the product and often abandon the task entirely.

What are the types of error messages in UX?

Inline validation error appears directly next to the field or element where the problem occurred, in real time as the user interacts. This is the most effective type for form validation because it gives users immediate, contextual feedback without requiring them to submit and wait.

Form submission error appears after the user attempts to submit a form and one or more fields contain invalid data. Effective submission errors identify every problematic field and explain what needs to be corrected, ideally with a summary at the top for long forms.

System error communicates a broader failure such as a lost connection, a server error, or an action that couldn't be completed. It requires a clear explanation of what happened and a specific recovery path, such as a retry button or a link to support.

Why do error messages matter in UX design?

Vague error messages are one of the most common sources of user frustration and form abandonment. When users see "Something went wrong" or "Invalid input" they have no way to fix the problem and no reason to trust the product. Every unhelpful error message increases cognitive load, damages the user's mental model of the product, and increases the probability of abandonment.

How to write good error messages in UX

Be specific about what went wrong. Be constructive about how to fix it. Use plain language and avoid technical terms or error codes. Place the error message close to the element that caused it. Never blame the user. Use a non-blaming, supportive tone. Add an icon or visual indicator so the error is perceptible without relying on color alone, which is essential for accessibility.

Related terms

Related guides