Error Message Design: Character Counts and UX Principles
Error messages are a critical part of user experience. A well-designed error message helps users recover quickly, while a poorly written one causes frustration and abandonment. This article covers character count guidelines and design principles for effective error messages.
Recommended Character Counts by Error Type
| Error Type | Recommended Length | Example |
|---|---|---|
| Inline validation | 30–60 characters | "Please enter a valid email address" |
| Form submission error | 50–100 characters | "Unable to submit. Please check the highlighted fields." |
| Toast / Snackbar | 40–80 characters | "Changes saved successfully" / "Connection lost" |
| 404 Page | 100–200 characters | Brief explanation + navigation options |
| Server error (500) | 80–150 characters | "Something went wrong. Please try again later." |
| API error response | 50–200 characters | Machine-readable code + human message |
Design Principles
- Be specific: "Password must be at least 8 characters" is better than "Invalid password"
- Offer a solution: Tell users what to do, not just what went wrong
- Use plain language: Avoid technical jargon like "Error 422: Unprocessable Entity"
- Be polite but direct: "Please enter your email" not "You forgot to enter your email"
- Don't blame the user: "That email address isn't registered" not "You entered the wrong email"
Conclusion
Effective error messages are concise (30–200 characters), specific, and actionable. They tell users what happened and how to fix it. Use Character Counter to ensure your error messages stay within optimal lengths.