What is microcopy in UX?
Microcopy in UX is the small bits of text inside an interface, like button labels, hints and error messages, that guide people through a task.
also calledinterface text · UI copy · UX copy
Nobody sets out to read the words on a button. But "Submit" versus "Send my application" changes how confident you feel before you click. Microcopy is those tiny pieces of writing that sit right where someone has to make a decision, and they often do more work than the paragraph on the page above them.
- Microcopy is the small text that guides actions: labels, hints, errors, empty states.
- Good lines answer the question in the user's head at that moment.
- Be specific about what a click will do, and write errors as help.
- Draft the words together with the design, not afterward.
Where microcopy lives
Once you start looking, it is everywhere:
- Button and link labels
- Form field labels, placeholders and helper text
- Error and success messages
- Empty states, such as "No messages yet"
- Tooltips and short explanations
- Confirmation dialogs and loading messages
It is rarely more than a line or two. That is the point: microcopy has to be read in a glance, usually while someone is busy doing something else.
What good microcopy does
It answers the question in the user's head at that exact moment. Above a password field, the question is "What are the rules?" Below a card number, it is "Is this safe?" On a delete button, it is "What exactly will vanish?"
A good line removes doubt, tells people what happens next, and sounds like a person rather than a system. It can also lighten the mood: a friendly line on an empty inbox is a small gift, as long as it never gets in the way of the task.
How to write it
A few habits cover most cases. Say what the action does, so "Download report" beats "Click here". Use the words your users use, not the ones your database uses. Keep it short, but not so short that it turns cryptic. And write error messages as help: say what went wrong and how to fix it, without blaming.
For example, "Invalid input" is useless, while "Your password needs at least 8 characters" tells the person what to do. Read your text out loud. If you would not say it to someone standing next to you, rewrite it.
Mistakes that cost you
Vague labels such as "OK" or "Submit" leave people guessing. Cute copy in a serious moment, like a joke on a payment failure page, comes across as tone-deaf. Placeholder text that disappears when you start typing is a quiet usability trap, because people forget what the field was for.
Another habit to watch is writing microcopy last, after the design is done. The words shape the layout, so it is better to draft them together.
Testing the words
You can test microcopy like anything else. Show a screen to a few people and ask what they expect to happen after a click. Run an A/B test on a button label when you have the traffic. Often the most useful signal is the support inbox: repeated questions point to a line that is not doing its job.
Microcopy: your questions, answered
What is microcopy with an example?
It is the small pieces of text in an interface that help people act. An example is changing a button from "Submit" to "Send my application", or turning "Error 400" into "We could not save your changes, please try again."
What is the difference between microcopy and copywriting?
Copywriting usually persuades, like headlines or ads. Microcopy mainly guides and reassures within a product, helping someone finish a task. They share craft, but microcopy values clarity and brevity over persuasion.
Why is microcopy important in UX?
It sits at moments of decision and friction, such as forms, payments and errors. Clear wording reduces confusion, prevents mistakes and builds trust, often at little cost compared with redesigning a screen.
What makes good microcopy?
It is clear, specific, short and in the user's own language. It tells people what will happen, offers help when something goes wrong, and keeps a consistent tone that fits the situation.
Who writes microcopy?
It depends on the team. UX writers, content designers, product designers and sometimes developers all write it. The best results come when the writer works alongside the designer from the start.
More quick answers
What is the difference between microcopy and UX writing?
Microcopy is the output, the small text itself. UX writing is the broader discipline, including voice, structure and content strategy for a product.
How long should microcopy be?
As short as it can be while staying clear. Most is a few words or a single sentence, and a longer line is fine when the stakes are high.
Should placeholder text be used as labels?
No. Placeholders disappear as people type, so use a visible label and keep placeholders for optional examples.
What tone should microcopy have?
Match your brand but adapt to the moment. Playful is fine for a success message, while errors and payments call for calm and plain language.
Can microcopy affect conversion?
It can, since labels and reassurance near forms and buttons influence hesitation. Test changes rather than assuming, because results vary by audience.
UX writing is the craft of writing the words inside a product, such as buttons, labels and error messages, so people can understand it and get things done.
Onboarding in UX is the guided first experience that helps new users understand a product and reach their first moment of real value.
Usability in UX is how easily and satisfyingly specific users can reach their goals with a product, measured by learnability, efficiency and error rates.
A/B testing in UX means showing two versions of a design to different groups of users and measuring which one gets the better result.
Consistency in UX means similar elements look and behave the same way across a product, so users can apply what they learned in one place everywhere else.
Found this useful? A GitHub star helps other designers find it.