Original pattern library

8 Error Message Examples

Use these examples to study structure, specificity, tone, and variation. They are demonstrations—not claims about a real person or organization unless the example itself makes that explicit.

Before you copy

What to notice in the examples

Effective error messages identify the failed task in plain language, avoid blame, preserve important user input, and provide a specific recovery path instead of exposing technical jargon.

  • State the problem from the user's point of view.
  • Explain the next action when recovery is possible.
  • Include technical detail only when the user can act on it or support staff need a reference.
1

We couldn't upload the file. It exceeds the 10 MB limit. Choose a smaller file and try again.

2

Your payment wasn't submitted. No charge was made. Check the card details or use another payment method.

3

That email address is already linked to an account. Sign in or reset your password.

4

We lost the connection before saving this change. Your previous version is still available.

5

The date range ends before it begins. Choose an end date after September 7.

6

We couldn't verify this address. Check the apartment number or continue with the address as entered.

7

This link has expired. Request a new verification email.

8

The report couldn't be generated because one source is unavailable. Try again later or exclude that source.

Turn an example into your own writing

Keep the underlying decision or pattern, then replace the subject, evidence, relationship, constraints, and tone with details that belong to your situation. If your final line still works after swapping only one noun, it may be too close to the example.