← Go Back

Microcopy

What is microcopy?

Microcopy is the small, functional text in your interface: button labels, form labels, placeholders, error messages, success messages, hints, and tooltips. It’s not marketing or long-form content; it’s the copy that appears when users need to act or understand what’s happening.

Use it when: you’re designing or building any screen with actions, forms, or feedback. Good microcopy improves usability, reduces errors, and supports accessibility when it’s clear and consistent.

Copy/paste checklist (microcopy basics)

  • [ ] Buttons – Verb or clear action (“Save changes”, “Add to cart”). Not vague (“Submit”, “OK”) unless context is obvious.
  • [ ] Labels – What the field is (“Email address”, “Phone number”). Visible, not only placeholder.
  • [ ] Errors – What went wrong + what to do next (“Enter a valid email” not “Invalid input”).
  • [ ] Success – Short confirmation (“Saved” or “Changes saved”).
  • [ ] Help/hints – Only when needed; one line. Don’t repeat the label.
  • [ ] Consistent terms – Same wording for the same action or concept across the product.

Why microcopy matters

  • Reduces confusion and errors so users know what to do and what went wrong.
  • Supports usability and task completion.
  • Works with accessibility when labels and errors are clear and associated (e.g. for screen readers).
  • Builds trust when tone is consistent and helpful.

What good microcopy includes

Checklist

  • [ ] Clear – Plain language; no jargon unless your users use it.
  • [ ] Actionable – Errors and hints tell users what to do next.
  • [ ] Concise – Short; no filler. Buttons 1–3 words where possible.
  • [ ] Consistent – Same term for the same thing (e.g. “Save” not “Save” in one place and “Update” in another).
  • [ ] Accessible – Labels and errors are programmatically associated; no “click here” or “this” only.
  • [ ] Tone – Matches your product (calm, direct, friendly) without sacrificing clarity.

Common formats

  • Buttons: “[Action]” or “[Action] [object]” (e.g. “Save draft”, “Add to cart”).
  • Errors: “[What went wrong]. [What to do].” (e.g. “Password is too short. Use at least 8 characters.”).
  • Empty states: What’s missing + one clear next action (e.g. “No projects yet. Create your first project.”).

Examples

Example (the realistic one)

Button: “Save changes” (not “Submit”). Label: “Email address” with hint “We’ll use this for sign-in and recovery.” Error: “That email is already in use. Try signing in or use a different address.” Success: “Profile updated.” You keep the same terms elsewhere (e.g. “Save” for saving everywhere). You test with usability testing to see if users understand and recover from errors.

Common pitfalls

  • Vague buttons: “Submit”, “OK”, “Click here.” → Do this instead: Use the action (“Save”, “Add to cart”, “Continue to payment”).
  • Unhelpful errors: “Error” or “Invalid input.” → Do this instead: Say what’s wrong and what to do (“Enter a valid email address”).
  • Labels only in placeholder: Placeholder disappears when typing; screen readers may not get the label. → Do this instead: Use visible labels; placeholder is optional extra.
  • Inconsistent terms: “Save” here, “Update” there for the same action. → Do this instead: Pick one term per concept and use it everywhere.
  • Tone over clarity: Clever or funny at the cost of understanding. → Do this instead: Be clear first; add personality only when it doesn’t obscure meaning.
  • Microcopy vs content design: Content design covers strategy, structure, and longer content; microcopy is the small, in-context UI text. They overlap; microcopy is a subset.
  • Microcopy vs UX writing: UX writing often includes microcopy plus other product copy (e.g. onboarding, emails). Microcopy is the in-UI, functional slice.
  • Microcopy vs design systems: Design systems can include microcopy guidelines (tone, patterns, examples) and design standards for copy.

Next step

Audit one flow (e.g. sign-up or settings): check every button, label, error, and hint against the checklist (clear, actionable, consistent). Rewrite the weakest three and test with usability testing or a quick review. Add microcopy rules to your design standards if you have them.

Related Terms