What is UX writing? (and why it belongs in your brand guide)

TL;DR

• UX writing is functional copy inside an interface. Marketing copy sells, UX writing helps someone finish something.
• It covers buttons, errors, empty states, tooltips, form labels, confirmations and system messages.
• Your brand guide probably specifies logo clear-space but says nothing about how your product apologizes when something breaks.
• Mailchimp, Adobe and Google all publish UX writing standards as part of their design systems. It's a documented discipline, not a nice-to-have.
• You don't need to hire a UX writer to fix this. You need three pages in your brand guide.

Why every other guide on this topic is written for someone else

Search "UX writing" and you'll find excellent guides from the Nielsen Norman Group, Coursera and a handful of UX schools. Read past the definition and they turn into career advice: salary bands, portfolio tips, which certification to take, how to land your first role.

Useful, if you want to become a UX writer. Less useful if you run a company that already has a product, already has a brand guide, and has just noticed that the checkout error message says "Invalid input" while the onboarding screen says "Oops, that doesn't look right!"

This guide is for the second person.

What is UX writing?

UX writing is the practice of writing the functional text inside a digital product so that people can complete tasks without confusion. It covers every word a user reads while using the thing, as opposed to every word they read while deciding whether to use it.

The distinction matters because the two jobs pull in opposite directions. Marketing copy wants attention. UX writing wants to be invisible: read once, understood immediately, never thought about again.

The Nielsen Norman Group treats it as a core UX discipline rather than a writing specialty, which is the right framing. A badly worded error message is a design failure, not a copy failure.

Look at what changed. The weak versions state a system fact. The better versions tell the person what happened and what to do next, in that order.

The last row is the one worth studying. "OK" and "Cancel" force the reader to reconstruct the question to know which button is safe. "Delete" and "Keep it" can be understood without reading the sentence above them. That's the whole discipline in one example: reduce the work required to act.

Microcopy in forms deserves its own mention, because it's where most products lose people. Our complete guide to form design covers the layout side of that problem.

In a large company these are three people. In most companies they're the same person, usually a marketer, occasionally a developer typing whatever fits. That's fine, as long as somebody has written down the rules they're following.

Why UX writing belongs in your brand guide

A brand guide exists so that work produced by different people at different times still looks like it came from one company. That logic applies to words exactly as much as it applies to logo placement, and most guides stop before it gets there.

Think about the proportions. A customer might see your logo a few times a session. They will read your button labels, error messages and confirmation screens dozens of times, often at the moments they care most: paying, canceling, fixing something that went wrong. The words users encounter most often are usually the only brand asset nobody has documented.

The companies who take this seriously make it public. Mailchimp's Voice and Tone guide is a content style guide published as part of their brand standards, and it ranks on page one for brand voice guidelines a decade after they wrote it. Adobe's Spectrum design system carries a section on inclusive UX writing. Google publishes Material's communication principles as a formal part of the system. And there are many more great examples of brand guides to explore out there.

The most mature design organizations in the industry treat interface language as a system component, documented in the same place as color tokens and spacing rules. If you're building a brand guide and it has nothing to say about words in the product, it isn't finished.

What to put in the UX writing section of a brand guide

You don't need forty pages. Three or four will cover most of it.

• Voice attributes with an anti-example. "Friendly but not jokey" means nothing on its own. Add a line showing what crosses the line: "We say 'Something went wrong.' We don't say 'Whoops! Our bad!'"
• Button and action verbs. Decide whether you use "Save" or "Save changes", "Delete" or "Remove", and whether buttons describe the action or answer a question. Then never mix them.
• Error message structure. A repeatable pattern: what happened, why, what to do next. Include three worked examples so nobody has to guess.
• Empty states. Say what the space is for and what the first action is. This is the most common gap in most products.
• Terminology list. Pick one word per concept and record it. Is it a workspace, a project, or a board? Products drift into using all three within a year.
• Capitalization and punctuation rules. Sentence case or title case on buttons. Whether errors end in a full stop. Boring, and the fastest way to make a product feel unmaintained when it's inconsistent.
• Tone shifts by context. How the product sounds during onboarding versus during a failed payment. Mailchimp's guide is built almost entirely around this idea and it's the part most worth copying.

💡 The terminology list earns its place fastest. It costs an hour to write and prevents the specific kind of confusion where support, the marketing site and the product each call the same feature something different.

Who writes it if you don't have a UX writer?

Most companies under a few hundred people don't have one, and don't need one. What they need is for the rules to exist so that whoever writes the copy is making fewer decisions from scratch.

In practice this usually falls to whoever owns the brand: a marketing lead, a founder, or the designer building the screens. That's workable. A designer who has already decided the button hierarchy is well placed to decide the button verbs, and our guide to the golden rules of interface design covers the neighboring decisions.

If you're building or refreshing your brand identity with outside help, this is worth asking for explicitly, because it usually isn't included by default 

These UI/UX design companies are a good place to start. Or you can work with ManyPixels. Our designers build brand guidelines as a standard request, and a voice and interface-language section can be part of that document rather than a separate project.

{{BRAND_PORTFOLIO="/dev/components"}}

Is AI taking over UX writing?

Partly, and in a way that makes documenting your rules more valuable rather than less. Language models are good at generating twenty variations of an error message and bad at knowing which one sounds like you. That judgment comes from a documented standard.

The practical shift in 2026 is that interface copy is increasingly drafted by a model and edited by a human, which moves the bottleneck from writing to deciding. A team with a written voice standard can review a batch of generated microcopy in minutes. A team without one argues about tone every time.

Frequently asked questions

Bottom line

UX writing is the copy that does work rather than the copy that sells: buttons, errors, empty states, the words people read while trying to get something done. It belongs in your brand guide for the same reason your logo does, which is that consistency stops happening the moment more than one person is involved.

If your brand guide currently ends at typography, adding a voice and interface-language section is a few pages of work that pays out every time someone new touches your product.

See how the rest of a strong identity fits together, or explore ManyPixels plans if you want a design team to build the guide with you.