Content·Updated January 3, 2026

UI Microcopy Writing

Write effective microcopy for UI elements including buttons, error messages, tooltips, and empty states.

Use Case

Writing UI copy, creating microcopy guidelines, or improving interface text for better UX.

Prompt

Write microcopy for [UI element/feature]. Include:

1. Button Labels
   - Primary actions (clear, action-oriented)
   - Secondary actions
   - Destructive actions
   - Loading states
   - Disabled states

2. Form Labels and Helpers
   - Field labels (concise, clear)
   - Placeholder text
   - Helper text
   - Error messages
   - Success messages
   - Validation feedback

3. Navigation Labels
   - Menu items
   - Breadcrumbs
   - Tab labels
   - Link text

4. Empty States
   - No content messages
   - No results messages
   - Empty list messages
   - First-time user messages

5. Error Messages
   - System errors
   - Validation errors
   - Network errors
   - Permission errors
   - Recovery instructions

6. Tooltips and Help Text
   - Feature explanations
   - Usage instructions
   - Contextual help
   - Onboarding hints

7. Notifications
   - Success messages
   - Warning messages
   - Info messages
   - Toast notifications

8. Writing Principles
   - Clear and concise
   - User-friendly language
   - Action-oriented
   - Helpful and supportive
   - Consistent tone

Format all microcopy with context and usage guidelines.

How to use

1Identify the UI element: Replace [UI element/feature] with your specific element (e.g., "login form", "delete confirmation dialog", "empty state for user dashboard")
2Add context about your product: Before the prompt, write 1-2 sentences about your product's tone and audience. Example: "We're a B2B SaaS tool with a professional but friendly tone. Users are product managers."
3Specify the use case: Tell the AI what situation this microcopy is for. Example: "This is for a delete button in a project management tool. Users need to understand the action is permanent."
4Paste the modified prompt into your preferred AI tool, like ChatGPT or Claude
5Review the generated microcopy: Check each section (buttons, error messages, tooltips) and refine as needed
6Ask for variations: Request multiple options for key elements like "Give me 3 variations of the primary CTA button text"
7Test with real users: Use the generated copy, but validate with actual user feedback when possible

Pro Tips

• Provide examples of existing copy you like: "Write error messages similar to Stripe's style - clear, helpful, actionable"
• Specify length constraints: "Button labels should be max 3 words" or "Error messages under 20 words"
• Include brand voice: Mention if your tone is casual, formal, friendly, or technical - it affects all microcopy
• Request a style guide: Ask "Create a microcopy style guide based on these examples" for consistency
• Test multiple options: Generate 3-5 variations for important copy (like CTAs) and A/B test them