The Difference Between a Copywriter and UX Copy

A piece of writing can be excellent in a document and unusable in a layout. Here is what actually separates copywriting from UX copy, and why it matters for your site.

I have been sent the same file more times than I can count. A document with headings, body text and a closing line that really lands. The writing is good. It has rhythm, it sounds like the brand, someone put real time into it. Then I place it into the design and it stops working. That is the moment the question of a copywriter and UX copy becomes concrete instead of academic.

It is almost never that the writing is bad. It was written for the wrong medium.

Two jobs solving different problems

A copywriter writes so that someone will feel something and then do something. Spark interest, build trust, sell. The craft is persuasion, tone and narrative, and it travels well across an ad, a newsletter, a brochure or a blog post.

A UX copywriter writes so that someone can finish a task. Find the right place, understand what happens next, feel confident enough to press the button. The craft is clarity under constraint.

The vocabulary here is messier than it looks, and the most useful boundary I have found comes from a Swedish handbook, Skriva UX-texter by Karin Guldbrand and Helena Englund Hjalmarsson. They separate microcopy, meaning the words sitting inside the interface itself, from UX text, the term above it. Buttons, link text, tooltips, page titles, menus, dialogs and checkboxes are microcopy. Error messages, confirmations, notifications, text messages and email sit in the wider bucket. The authors are careful to say the line is not a sharp one and that you do not always need to draw it. The book also gives its own section to exactly the question this post is about, headed "Copywriter eller ux-skribent?".

I use the word microcopy throughout this series because it is what most people search for. The distinction is still worth carrying, because it tells you how much surface area you are actually dealing with.

The usual explanation you find online is that copywriting serves the business while UX copy serves the user. That is true, and it is also a simplification that makes them sound like two departments doing separate work. In practice they sit inside the same sentence. A button that reads "Book my call" instead of "Submit" is both clearer and more persuasive. Nobody had to choose.

The real difference between a copywriter and UX copy

The difference is not who the writing serves. It is what the writing sits inside.

An article owns its own space. It can be as long as it needs to be, it gets read from the top down, and the only real constraint is the reader's patience. Web text shares space with everything else. It has to fit a component that changes width, it has to work equally well as the first thing someone sees and as the third, and it has to hold up when someone scans past it in fourteen seconds.

That is why brilliant writing can fall apart in a layout. The headline breaks across three lines on mobile. The opening paragraph that built the point sits below the fold. The button label that was elegant in the document turns ambiguous once it stands alone next to an image.

Nielsen Norman Group has been tracking how people actually read online since 2006, and the conclusion has held for twenty years. They do not read, they scan, often in an F shaped pattern where the first words on each line get the most fixations and the rest of the line gets almost none. Which means the load bearing words have to come first. Not in the middle of a well built sentence where they land most gracefully.

The writing is a component, not content

This is the part I see most clearly precisely because I both design and build the thing the writing goes into.

When I build a section, the text is not something I pour into a box afterwards. It is one of the box's properties. The headline has a character range it works within. The link text has to carry meaning even when it is read out in isolation by a screen reader. The field label cannot be swapped for placeholder text, because it disappears the moment someone starts typing.

Guldbrand and Englund Hjalmarsson put the same idea in their introduction, that the writing is one of the interface's elements. It sounds obvious until you notice how rarely projects are actually organised that way.

A copywriter who has never seen their words inside a layout cannot possibly know any of this. It is not a skills problem, it is an information problem. The writing was done before the constraints existed.

The best workflow I have found is simple. Never write final copy against an empty document. Write against a wireframe, even an ugly one, so that every piece of text has a place and a size from the start. You will catch in ten minutes what otherwise costs a full rewrite.

Storytelling does not disappear, it changes shape

This is usually where people get nervous. If web writing has to be short and functional, where does the story go?

It is still there. It is just distributed.

In an article, the story is carried in paragraphs. On a website, it is carried in sequence. The headline sets an expectation, the first paragraph confirms it, the example makes it credible, the button delivers on it. The reader still experiences an arc, but it is built from parts that each have to work alone.

That is harder, not easier. Writing four words that carry both tone and function takes longer than writing forty that only carry tone. It is also why it irritates me when UX copy gets described as the dry, technical version of writing. It is the most compressed form of writing I know.

Torrey Podmajersky, who has written UX content for Google and Microsoft among others, treats it as a strategic discipline with measurable business value rather than as polish applied at the end. That posture is what I find missing in most projects I join. The writing arrives last, once the layout is locked, and by then it is too late for it to influence anything.

How to tell which skill you need

The question of a copywriter and UX copy is easiest to answer if you start from the problem rather than the job title. If you have a site to build or rebuild, here is what I would ask myself.

Is the problem that people do not understand what you do? Then you need copy. Positioning, message, tone, a story that separates you from everyone else doing roughly the same thing.

Is the problem that people understand what you do and still do not get in touch? Then you need UX copy. Something between interest and action is unclear, and it almost always sits in buttons, forms, heading hierarchy and the small text around them.

Most projects need both, and usually it is the same person. A copywriter who has worked in digital projects picks up the constraints quickly. What does not work is ordering text as a deliverable in a document and then hoping it fits.

If you want a more structured way into that judgement, I have written about how to evaluate design using the same logic. If you would rather see how I work with this in practice, that is on what I do.

What I had to learn myself

I once wrote an opening paragraph for a home page that I was honestly proud of. Three sentences, good rhythm, an image that fit. It did not work. People read it, nodded, and left.

The problem was that I had written it to be read. Nobody read it. They scanned past it on their way to something that looked like it answered their question, and my carefully built opener gave them nothing to catch on, because the point arrived in the third sentence.

I rewrote it as one sentence. It was worse as writing and much better as an interface. That is the lesson I carry, and it is also why the second post in this series is about removing rather than adding.

When I talk about a copywriter and UX copy with a client, I usually land in the same place. These are not opposing disciplines. It is the same craft performed against different constraints, and the web has harsher constraints than almost anything else we write for.

The writing on your site does not have to be beautiful. It has to work. If it happens to be both, you have done a genuinely good job.

Further reading

Two books if you want to go deeper, one in Swedish and one in English.

Karin Guldbrand and Helena Englund Hjalmarsson, Skriva UX-texter: en komplett guide i att skriva texter för användarflöden (Morfem, 2023). The Swedish handbook. It works through interface microcopy component by component, then handles the broader UX texts such as error messages, confirmations and notifications separately. The practical chapters, from forms and headings through to error messages and confirmations, each close with a checklist.

Torrey Podmajersky, Strategic Writing for UX (O'Reilly, second edition 2025). The international reference. More focused on frameworks, voice strategy and how to measure the effect of UX content. The second edition adds material on what AI generated content does to the work, which the first did not have.