Design & UX21 categories
Rewrite these error messages
Your interface says "An error occurred" and support is fielding the fallout.
Rewrite these error messages. Each must say what failed in the user's terms, whether their work is safe, and one thing they can do right now. No blame, no system internals, no error code unless support will genuinely ask for it. Flag any error that should be designed away rather than reworded. Errors:
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Interface copy. Every word inside the product: button labels, error messages, empty states and what things are called.
Related prompts
Rewrite the microcopy on this screenBefore shipping a screen where the words started as placeholders you never revisited.Pick the right words for this buttonWhen the options are "OK / Cancel" and nobody is sure what OK does.Design the empty state for this screenThe screen looks great with data and blank the first time anyone opens it.Rewrite these error messages for humansYour UI says "An error occurred" and support is fielding the fallout.Name this thing in the interfaceNaming a feature, tab, or object that users will have to learn and repeat.A better label for this buttonWhen the options are "OK" and "Cancel" and nobody is sure what OK does.
Keep this one
Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser — free