How to write better form error messages

When a form shows a generic error message — “There was an error” or “Invalid input” — users know something is wrong but not what, or how to fix it. This forces them to guess: was the email format wrong? Did a field get missed? That uncertainty costs time and erodes confidence in the form. For users already hesitant about submitting, an unexplained error is often the final reason to abandon.

The reliable fix is inline error messages that are specific and instructive. Rather than a blanket error, attach the message to the exact field that failed. State what went wrong and, where possible, show an example of what valid input looks like. “Use a valid email like [email protected]” tells the user precisely what the field expects — no guesswork required. This keeps the user on task instead of sending them searching for what “error” means.

When writing error messages, think of the message as a prompt, not a penalty. The user isn’t being told off — they’re being guided. Use plain language — “Your email address doesn’t look right” is clearer than “Input validation failed”. Give the format example as a hint, keep it brief, and position it directly under the field it applies to.

• Show errors inline, directly below the field that failed — not in a banner or at the top of the page.
• Name the field in the message: “Email address must include an @ symbol” is clearer than “Invalid field”.
• Include a correct-format example where input format is the likely error — “like [email protected]”.
• Use plain language — no technical terms like “validation error” or “malformed input”.
• Trigger errors at the right moment — on blur or on submit, not on every keystroke.

Specific, well-placed error messages can significantly reduce form abandonment at the validation stage. Users who understand exactly what to fix are far more likely to correct the entry and complete the form than users confronted with a message that offers no direction.