We value your privacy

    We use cookies to enhance your browsing experience and analyze our traffic. By clicking "Accept", you consent to our use of cookies. Learn more

    The Complete Guide to UX Writing
    Design

    The Complete Guide to UX Writing

    Filtedev

    Filtedev

    WE CARE

    8 min read

    How to write microcopy that guides users and improves experience.

    Words That Work

    UX writing is the craft of writing the text that appears in digital interfaces. From button labels to error messages, every word shapes the user experience. Good UX writing is invisible—it helps without being noticed.

    The Principles of UX Writing

    Clarity Above All

    Users should never wonder what something means:

    • Use familiar words
    • Avoid jargon unless audience expects it
    • Say exactly what happens
    • Don't prioritize cleverness over clarity

    Concise by Default

    Digital interfaces aren't novels:

    • Every word must earn its place
    • Shorter is usually better
    • Get to the point immediately
    • Edit ruthlessly

    Helpful and Actionable

    Text should enable action:

    • Tell users what to do
    • Explain why when helpful
    • Provide next steps
    • Reduce uncertainty

    Button Labels That Work

    Action-Oriented

    Start with verbs:

    • "Save changes" not "OK"
    • "Send message" not "Submit"
    • "Create account" not "Sign up"
    • "Add to cart" not "Buy"

    Specific Over Generic

    Say what happens:

    • "Delete photo" not "Delete"
    • "Download invoice" not "Download"
    • "Cancel subscription" not "Cancel"

    Avoid Ambiguity

    Users shouldn't hesitate:

    • "Save draft" vs "Publish" (clear difference)
    • "Yes, delete" for destructive actions
    • Include object in label when helpful

    Error Messages That Help

    What Happened

    Be specific about the problem:

    • "Password must be at least 8 characters" not "Invalid password"
    • "Email address not found" not "Login failed"
    • "Credit card expired" not "Payment error"

    What to Do

    Guide toward resolution:

    • "Please enter your email address"
    • "Try refreshing the page"
    • "Contact support if this continues"

    Maintain Tone

    Errors are frustrating—don't make it worse:

    • Avoid blaming the user
    • Stay calm and helpful
    • Use "we" for system issues
    • Never use ALL CAPS

    Form Labels and Help Text

    Clear Labels

    Label every field:

    • State what's needed
    • Use sentence case
    • Don't rely on placeholder text
    • Include format expectations

    Helpful Placeholders

    Use appropriately:

    • Show example input
    • Indicate format (MM/DD/YYYY)
    • Disappear on focus (not a replacement for labels)

    Microcopy

    Small text, big impact:

    • Explain why you're asking
    • Clarify requirements
    • Reduce anxiety about privacy
    • Guide correct input

    Confirmation and Feedback

    Success States

    Celebrate accomplishments:

    • "Message sent" (clear confirmation)
    • "Changes saved" (instant feedback)
    • "Welcome to [App]" (warm greeting)

    Progress Indication

    Keep users informed:

    • "Uploading... 45%"
    • "Processing your payment"
    • "Just a moment..."
    • "Almost there!"

    Destructive Actions

    Confirm the irreversible:

    • "Delete this conversation? This can't be undone."
    • "Are you sure you want to leave? Your changes won't be saved."
    • Require typing confirmation for serious actions

    Tone and Voice

    Defining Voice

    Your brand's personality in words:

    • Friendly or formal?
    • Playful or professional?
    • Technical or accessible?
    • Consistent across touchpoints

    Adapting Tone

    Same voice, different situations:

    • Error messages: empathetic, helpful
    • Success: celebratory, brief
    • Onboarding: welcoming, encouraging
    • Serious actions: clear, deliberate

    Writing for Different Contexts

    Onboarding

    Welcome and guide:

    • Simple, encouraging language
    • Clear benefit statements
    • Progressive complexity
    • Celebrate progress

    Empty States

    Turn nothing into something:

    • Explain what will appear
    • Provide clear action
    • Add value with suggestions
    • Use appropriate imagery

    Loading States

    Make waiting pleasant:

    • Explain what's happening
    • Show progress when possible
    • Rotate messages for long waits
    • Inject personality appropriately

    Common Mistakes

    Being Too Clever

    Humor that confuses helps no one. Clever 404 pages are fun until you actually need to find something.

    Inconsistent Terminology

    If you call it "workspace" once, always call it workspace. Don't switch to "project" or "folder."

    Assuming Knowledge

    Users don't know what you know. Explain abbreviations, provide context, never assume.

    Passive Voice

    "Your password was reset" vs "We reset your password" vs "You reset your password." Active voice is usually clearer.

    Testing UX Writing

    Methods

    • A/B test different copy
    • Observe users completing tasks
    • Ask users to explain what they expect
    • Track support tickets about confusion

    Iterate

    Writing improves with feedback:

    • Monitor analytics
    • Collect user questions
    • Update confused copy
    • Maintain a style guide

    Words in interfaces do heavy lifting—guiding, reassuring, explaining, celebrating. Every piece of text is an opportunity to help users succeed or a potential point of confusion. Choose words carefully.

    Share this article:

    Ready to Start Your Project?

    Let's discuss how we can help bring your vision to life.