Microcopy is the short, functional text around interactive elements: the label on a button, the hint under a password field, the line explaining why you need a phone number, the error message after a failed upload. Each piece is small, but together they shape whether people understand what to do and feel confident doing it. Good microcopy is specific, brief and written for the moment it appears.
Where microcopy matters most
Microcopy carries the most weight at moments of uncertainty or commitment.
- Buttons: say what happens, such as “Create workspace” rather than “Continue”.
- Form hints: explain format and purpose before the user types.
- Errors: say what went wrong and how to fix it, without blame.
- Reassurance: “No credit card required”, “We will never share your email”.
- Empty states and confirmations: what to do next.
- Tooltips: define terms the user may not know.
Writing it well
Write in the user's words, not internal product names. Be consistent: if the button says “Invite”, the confirmation should not say “Shared”. Keep it short, but not so short that meaning is lost. Read it aloud in context, because a phrase that works alone may sound odd beside the surrounding interface.
Error messages deserve particular care. WCAG requires that input errors are identified and described in text, and that suggestions for correction are given where known. That is good practice for everyone, not only for accessibility.
Testing microcopy
Button and reassurance text are among the easiest things to A/B test on high-traffic pages. On lower-traffic flows, user tests and support ticket analysis show which words confuse people.
Example
Explaining a field
Hypothetical field service app Tidewell asks for a phone number at signup, and many users skip the form there. The team adds a hint below the field: “Used only for job alerts to your technicians. You can turn these off.” It then compares completion at that step.
Common mistakes
Generic errors
“Something went wrong” gives users nothing to act on. Say what failed and what they can do.
Inconsistent terms
Calling the same thing a project, a board and a space in different places makes users wonder if they are different.
Questions
Ideally a UX writer or content designer working with product designers. In smaller teams, designers and marketers share it, using a simple style guide for consistency.
