UX microcopy bench

Does your interface text sound like one voice?

Paste buttons, errors, links and empty states, one per line. The bench checks each string against a plain, specific, verb-first house voice and against the other strings, and explains every miss. It runs in your browser; nothing is uploaded.

00 · How it works

Apps are full of small texts: buttons, errors, links, empty screens. Written by different people at different times, they start to sound like different companies. The bench shows where your interface text disagrees with itself, and why.

Step 1

Paste your text

One piece of interface text per line. After a | say what it is, for example Save changes | Button. The type matters: a button is judged differently from an error.

Step 2

Check the strings

Each line is compared with simple voice rules, and with the other lines. Plain, specific, verb first, no exclamation marks. Switch rules off to fit your own voice.

Step 3

Read the reasons

Every line is On voice or Needs a look. A flag comes with its reason and, where the fix is simple, one alternative. Your text is never changed for you.

Example

Oops! Something went wrong! as an Error: it has an exclamation mark, a filler opener, names no cause and gives no next step. A clearer version: Your file couldn't be saved. Check your connection and try again.

01 · Your strings

draft.txt

Your strings, one per line

One per line. Add “| where” to name the type: Button, Error, Link or Empty state. Up to 300 lines.

02 · House voice

Plain, specific, verb first, no exclamation marks. Switch rules off to fit your own voice.

Longest stringcharacters

A rule-based check, not a verdict. It flags patterns that usually read badly in interfaces; judge each flag in context. Your text stays in this browser tab.