--- title: "Microcopy" description: "The short pieces of interface text, such as labels, hints and error messages, that help people complete tasks." category: "Editorial craft" canonical: "https://contentlexicon.com/microcopy" updated: "2026-10-11" --- # Microcopy _Editorial craft_ > The short pieces of interface text, such as labels, hints and error messages, that help people complete tasks. Microcopy is the small text in an interface that helps people act: button labels, form hints, error messages, confirmations, empty states, tooltips and the line under a password field explaining what it needs. Each piece is short, but together these words carry much of what a product tells people about what to do next and what just happened. Their meaning depends on what the system does, so microcopy has to be designed alongside the flow rather than added at the end. Joshua Porter popularised the term in a 2009 blog post, “Writing Microcopy”. He described a checkout form whose transactions kept failing because people entered an address that didn't match their card; one added line, “Be sure to enter the billing address associated with your credit card”, made the errors go away. Kinneret Yifrah's Microcopy: The Complete Guide (2017) later gave the practice a book-length treatment. ## Why it matters for content Microcopy is where content and behaviour meet most directly. A clear label can reduce uncertainty; a specific error can help someone recover without contacting support; a confirmation can prevent a second payment attempt when it explains what happened and what comes next. A button that says “Apply” and one that says “Submit” may imply different next steps even when they look identical, so decide what the action does before choosing the words. Testing the effect of changes rather than assuming better wording guarantees completion is the safe approach. Microcopy is also where [tone](https://contentlexicon.com/tone) is tested hardest. [Voice](https://contentlexicon.com/voice) is easy to maintain in an article and difficult in a failed payment message, where breeziness is insulting and coldness is worse. Microcopy shows whether a voice and tone guide works under pressure. For money, eligibility or personal data, ambiguity can carry serious consequences. A cancellation message needs to distinguish ending a service now from stopping its next renewal. A consent checkbox needs to say what someone is agreeing to, not just that they agree. ## How AI changes the picture AI can generate plausible microcopy instantly, which is both helpful and risky. Drafting twelve variants of an error message is tedious work a machine can do well. But microcopy depends on system context: what failed, what the person can do about it, what happens next. A model that doesn't know those things will write something confident, tidy and wrong. Interface language is also increasingly generated. As products add assistants and conversational flows, many of the words doing the work are responses composed on the spot rather than fixed labels. Documented voice, tone and style rules can guide that generation as well as human writing, if the system is configured to use them, though guidance doesn't enforce permissions or guarantee compliant answers. AI can support consistency checks across a product: finding fourteen different phrasings for the same action, spotting labels that contradict the help text, flagging [jargon](https://contentlexicon.com/jargon) in field hints. Review what it flags, since different wording sometimes reflects a different action. ## Questions people ask **Is microcopy the same as UX writing?** Microcopy is the text; [UX](https://contentlexicon.com/ux) writing is the discipline of producing it alongside design and research. [UX writers](https://contentlexicon.com/ux-writer) also work on flows, naming and content structure, so the job reaches beyond the words on any one screen. **Should designers or content people write it?** Either can, provided they're involved while the flow is being designed. Microcopy written after the screens are finished can only tidy up problems the words might have prevented. **Does it need a style guide entry?** Yes. Button conventions, error message patterns and how to address the user are the kinds of decisions a [style guide](https://contentlexicon.com/style-guide) exists to settle once. Patterns with worked examples tend to help more than abstract rules. **Can microcopy be tested?** Through task-based research or a controlled experiment. For a label change, check whether people understand the action as well as whether completion changes. Reliable comparisons may need enough participants, traffic and time, so they're not always cheap or quick. ## Learn more - [Writing Microcopy](https://web.archive.org/web/2010/http://bokardo.com/archives/writing-microcopy/) – Joshua Porter's Bokardo post, via the Internet Archive, with the billing address story and other examples of small copy making a large difference. - [What is UX writing?](https://uxcontent.com/what-is-ux-writing) – microcopy placed in its proper context as interface design. - [5 Microcopy & UX Writing Best Practices We Can Learn from Lemonade](https://blog.prototypr.io/5-microcopy-ux-writing-best-practices-we-can-learn-from-lemonade-e26f1d2adea9) – a design account of Lemonade’s interface wording; concrete observations, not a controlled demonstration that those words caused performance gains. - [Error message guidelines](https://www.nngroup.com/articles/error-message-guidelines/) – evidence-led guidance on making failure states useful. Related terms: [Call to action](https://contentlexicon.com/call-to-action), [Content](https://contentlexicon.com/content), [Content design](https://contentlexicon.com/content-design), [Conversational design](https://contentlexicon.com/conversational-design), [Frontend](https://contentlexicon.com/frontend), [Tone](https://contentlexicon.com/tone), [UX writer](https://contentlexicon.com/ux-writer) This page was last reviewed in October 2026.