Microcopy that sounds like a person wrote it

Microcopy examples

What makes good microcopy

• Say what happens, not what the button is

  “Create account” beats “Submit” because people scan buttons to predict the result. The verb and object should tell them exactly that.

• Be specific when things go wrong

  Vague errors make people guess. Name the field, the rule and the fix. If you can't say what happened, at least say what's safe (“your edits are still here”).

• Cut until it breaks, then add one word back

  Microcopy is read in half a second. Delete filler like “please”, “successfully” and “in order to” unless the tone really needs it.

• Match the moment's emotion

  Celebration can be playful. Errors, billing and deletion should be calm and plain. The same voice works at different volumes.

• Keep it consistent

  If it's “workspace” in the nav, it's “workspace” in the error. Pick one word for each concept and use it everywhere.

• Write for the screen reader too

  “Click here” and “Learn more” mean nothing out of context. Links and buttons should make sense when read alone.

You are a senior UX writer. Rewrite the UI text below as microcopy.

Rules:
- Identify the type (button, error, empty state, confirmation, tooltip, form label, notification) and follow its conventions.
- Be specific and concrete. Say what happens or what to do next.
- Plain, human language. No jargon, no blame, no exclamation marks unless it's a celebration.
- Cut filler words ("please", "successfully", "in order to").
- Keep buttons to 1–3 words, verb first.
- Keep the original meaning; don't invent product facts. Use {placeholders} where specifics are missing.
- Every variant must be clearly better than the original, not just shorter.

Return 3 variants, shortest first, in exactly this format and nothing else:
1. {variant}
   {3–5 word note on why it works}

Want only the best variant pasted back in place? Remove the “3 variants” line and Snippetbar pastes a single result.

Use it where you work

• In Figma

  Select the text inside a text layer, press the snippet's shortcut, and it's rewritten in place. You never leave the canvas or open a chat tab.

• In Linear or Jira

  Copy the error string from a bug ticket and run the snippet. Paste three options into the ticket, so engineering ships better copy along with the fix.

• In your codebase or CMS

  Select a string in your i18n file or CMS field and run the snippet. Keep the variant you like and the string is ready to ship.

• Landing page copy generator

  Paste your product notes, pitch or an existing page that isn't working, and get landing page copy section by section, from the hero to the final CTA.

• Simplify text

  Paste anything dense, like a contract clause, a technical explanation or a policy, and get a plain-language version that keeps the meaning.