Text
Creative Error Message Generator
Error states get written last and shipped worst — which is why prototypes fill up with 'Something went wrong' placeholders that say nothing about the product's voice. This generator carries four curated sets of ten error messages each: friendly ('Hmm, we hit a snag. Give us a moment to sort things out.'), dramatic ('Connection lost. The digital void has claimed your request.'), technical ('Error 503: Service temporarily unavailable. Upstream dependency timeout.'), and humorous ('Error 418: I am a teapot. I cannot brew your request.'). Pick a tone and a count, and the tool deals out a shuffled, numbered selection with no repeats. Because each tone is a fixed list of ten, that's also the ceiling — asking for twenty returns all ten, and regenerating reorders the same set rather than inventing new lines. Use the batch to audition a voice across your 404 pages, toasts, and empty states, then adapt the survivors: add your product name, the real cause, and a next step before anything ships.
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Set the Number of Messages to however many variations you want — six works well for a design review, two or three for a quick prototype.
- Choose a Tone that matches your product's voice: friendly for consumer apps, technical for developer tools, humorous for casual or creative products.
- Click Generate to produce a batch of error messages across different error scenarios and phrasings.
- Scan the output and copy the messages that best fit your context — paste directly into Figma, a doc, or your codebase as placeholders.
- Regenerate with a different tone or count to expand your options if none of the first batch feel quite right.
Use Cases
- •Filling empty-state components in a Figma prototype with tone-matched microcopy before UX review
- •Generating six friendly 404 message variants to A/B test on a consumer SaaS product
- •Populating Storybook error-state stories with humorous placeholder copy for component documentation
- •Drafting dramatic or technical permission-denied messages for a developer tool's CLI output
- •Replacing generic 'Something went wrong' placeholders across a mobile app before stakeholder handoff
Tips
- →Generate a batch in 'friendly' tone first, then switch to 'humorous' and compare — the contrast quickly reveals which voice fits your brand.
- →Pair the generated message text with a specific HTTP status code when handing off to developers, so copy and code stay linked.
- →Use the 'technical' tone for internal admin dashboards and developer-facing tools, where users want precision over personality.
- →Run a batch of eight messages before a design crit — having options prevents the team from fixating on a single phrasing and speeds up decisions.
- →Avoid adapting a humorous error message for payment failure or data loss screens, even if the rest of your app uses that tone.
- →Combine the generated copy with a concrete action verb in your final version — 'Go back to dashboard' converts better than 'Something went wrong.'
FAQ
what tone should error messages use in a B2B SaaS product
Most B2B tools benefit from a friendly but professional tone — approachable enough to reduce frustration without undermining credibility with enterprise buyers. The friendly setting in this generator is a solid starting point; trim anything too playful once you have a shortlist.
can I use generated error messages directly in my product
Treat them as strong first drafts rather than final copy. They give you structure and tone direction, but you'll want to add your actual product name, the real cause of the error, and a concrete next action. They're especially useful for filling states during prototyping before final copy is approved.
should error messages be funny or is humor too risky
Humor works well in consumer apps and developer tools where users tolerate personality, but fails in medical, financial, or high-stress contexts. Even in casual apps, keep jokes short — a user who lost unsaved work doesn't want a punchline. Wit should soften friction, not dismiss it.
why do I see the same messages every time I regenerate
Each tone is a fixed set of ten hand-written strings; the tool shuffles and numbers them rather than composing new sentences, and counts above ten simply return the full set. If you've read all four tones, you've seen the entire catalog — from there, use the lines as patterns for writing your own.
You might also like
Popular tools from other categories that share themes with this one.
Try these next
More free tools from other corners of the catalog, picked by shared themes.