practiceExperience & interface

Microcopy

Microcopy is the short, contextual text that explains controls, sets expectations, prevents errors, and helps users recover within an interface.

Download Markdown (.md)

01What it means

Microcopy consists of small units of interface language such as button labels, hints, placeholders, validation messages, consent explanations, status text, and empty-state prompts. Its size does not make it trivial: each phrase sits at a decision point and should provide the right information, influence ethically, or support an interaction without demanding unnecessary attention.[1][2][3]

02Why it matters

Well-designed microcopy answers immediate questions before they turn into hesitation, errors, or support requests. It can explain why data is needed, distinguish similar actions, state consequences, and provide a path forward after failure. Because it appears close to controls, it often has more practical impact than longer explanatory content elsewhere.

03When to use it

Use microcopy wherever users may wonder what a field means, what an action will do, whether a process succeeded, or how to fix a problem. Prioritize consequential, unfamiliar, irreversible, privacy-sensitive, and error-prone moments rather than adding helper text to every control.

04How it works

  1. Identify the exact uncertainty, risk, or decision at the interaction point instead of filling available space.
  2. Write a concise message that names the issue, relevant consequence, and next action in the user’s vocabulary.
  3. Place the message next to the control or state it explains, and do not rely on placeholder text as the only label.
  4. Check tone, accessibility, localization, dynamic values, and all states including loading, success, empty, and failure.
  5. Observe whether the copy prevents errors or supports recovery, then remove words that add noise without changing behavior.

05A practical example

Example

Before account deletion, a service labels the button “Delete account” and states that saved projects will be permanently removed after 30 days. If confirmation fails, the message explains that the account is unchanged and offers a retry. The copy is specific, calm, and tied to the exact consequence.

06Where it breaks

More text is not automatically more helpful. Repeated hints can create clutter, placeholders disappear during entry, and humorous errors may feel dismissive. Microcopy should not manipulate consent, disguise costs, or compensate for a misleading control. Legal review may be necessary, but legal completeness should be paired with usable presentation.

Common mistakes

  • Using placeholders as labels or instructions that disappear while typing.
  • Writing vague errors such as “Something went wrong” without a recovery step.
  • Using reassuring language to conceal consequences, defaults, fees, or data practices.

07Sources

  1. The 3 I’s of MicrocopyNielsen Norman Group · Professional frameworkThe 3 I’s of Microcopy
  2. The 3 C’s of Informational MicrocopyNielsen Norman Group · Research-based guidanceThe 3 C’s of Informational Microcopy
  3. Error-Message GuidelinesNielsen Norman Group · Usability guidanceError-Message Guidelines
View saved topics

Start typing to search titles, definitions, categories, and frameworks.