Quick answer
UX writing is the craft of writing the words inside a product or website, such as buttons, labels, form hints and error messages. Good UX writing is clear, short and helpful, guiding people to finish tasks without confusion, which supports conversions and trust.
Key takeaways
- Clear beats clever, every time.
- Describe the action, not the technology.
- Error messages should explain the fix.
- Test wording with real users.
What is microcopy?
Microcopy is the small text that guides a user: button labels, form hints, confirmation messages and empty states.
It is easy to overlook, yet people read it at the exact moment they make a decision.
How do you improve your buttons?
| Weak | Better |
|---|---|
| Submit | Send my enquiry |
| Click here | Download the guide |
| Continue | Review my order |
| OK | Got it, thanks |
How should you write error messages?
- Say what went wrong in plain words.
- Explain how to fix it.
- Keep the tone calm and never blame the user.
- Point to the exact field.
- Offer help if the fix is not obvious.
Which rules apply everywhere?
- Use everyday words, not internal jargon.
- Keep sentences short.
- Put the most important word first.
- Be consistent with terms, such as always using "sign in".
- Write for screen readers by using meaningful link text.
A quick example
Compare "Invalid input" with "Your phone number needs 10 digits. Please check and try again." The second reduces frustration and saves a support call. Strong UX writing makes this kind of improvement across the whole journey.
How do you test it?
Show a page to five people and ask them to complete a task. Note where they hesitate, then rewrite those words.
Words to retire
- "Oops, something went wrong" with no detail.
- "Please try again later" when you can say when.
- "Invalid" without saying why.
Replace each with a specific, kind and useful sentence. Your support team will thank you.
Ask them which messages generate the most calls. That list is your starting point.
Bottom line
Write for the moment the person is in. Be clear, be brief and say what happens next. Test your words with real users, not just your team.
Sources and further reading
- Nielsen Norman Group: UX writing
- Material Design: Writing
- W3C: Web Content Accessibility Guidelines 2.2
Checked against the sources above and our own project experience. Last reviewed 7 October 2026.
