UX Glossary · M

Microcopy

Also: UX writing

The small text that does the heavy lifting: labels, hints, errors, empty states, button text.

Microcopy is the short text embedded in an interface: field labels, helper text, error messages, button labels, empty states, confirmations. It is usually written last, by whoever is nearest, and it is often the highest-leverage change available.

Why so much of it is bad

It falls between roles. Designers treat it as copywriting, copywriters never see the interface, and developers write placeholders that ship. The result is text that describes the system rather than helping the person.

It is also invisible in review. A screenshot in a design review is judged on layout, and “Submit” passes without comment.

What good microcopy does

Answers the question at the moment it arises. A field asking for a customer number is improved more by “Nine digits, on the top right of your invoice” than by any visual treatment.

Sets expectations before an action. “You can change this later” removes hesitation on a choice that feels permanent.

Names outcomes rather than mechanisms. “Book the pickup” over “Submit”.

In practice

Write the interface’s words before its layout, at least in draft. It surfaces missing decisions early, because it is very hard to write a clear label for a control whose purpose nobody has settled.

Knowing the words is the easy part.

If you'd rather have someone apply them to your product, that's what I do.