What is microcopy?

Microcopy is the short functional text embedded in a product interface: button labels, error messages, placeholder text, tooltip copy, confirmation prompts, and empty state explanations. It is the writing that users encounter not while reading, but while doing.

Because microcopy operates at decision points, its quality directly affects whether users complete the action in front of them or stop. A button that reads 'Submit' gives users no information about what will happen next. A button that reads 'Save and publish' does. That distinction, multiplied across dozens of interface moments, shapes whether users feel confident or confused inside a product.

Where microcopy appears

• Buttons and CTAs: the most consequential microcopy in any product. Specific, action-oriented labels outperform generic ones in every context.

• Error messages: explain what went wrong and, more importantly, what the user should do next. 'Invalid input' is not an error message. 'Password must be at least 8 characters' is.

• Placeholder text: the greyed text inside an empty input field. Can clarify the expected format or give an example. Disappears when the user types, so it cannot carry essential information.

• Tooltips: The copy inside a tooltip is microcopy, and brevity is its primary constraint.

• Confirmation and success states: the message that appears after an action completes. Confirms what happened, and can direct the user toward the logical next step.

• Empty state copy: The explanation and CTA inside an empty state are among the highest-impact microcopy moments in onboarding.

• Onboarding prompts: the instructional text inside product tours, checklists, and hints. Clarity here directly determines whether users complete the guided flow.

Principles of effective microcopy

Be specific

Generic microcopy (Submit, Click here, Learn more) provides no information about what will happen. Specific microcopy (Start free trial, Go to your dashboard, Read the setup guide) reduces the cognitive work required to decide whether to act.

Write for the user's goal, not the product's structure

'Create workspace' describes the product action. 'Set up your team' describes the user's goal. In most contexts, the user's goal is the more motivating frame.

Use the user's vocabulary

If your users call it a 'project', the interface should call it a 'project', not a 'workspace' or a 'board' because that is how the engineering team named the database entity. Vocabulary mismatches create user friction without any visible cause.

Be honest about consequences

Deletion confirmation dialogs that say 'Are you sure?' leave users guessing about what 'yes' will remove. 'Delete this project and all its tasks? This cannot be undone.' is honest, specific, and respectful of the user's ability to make an informed decision.

Microcopy and onboarding

During user onboarding, microcopy quality is particularly consequential because users are forming their first impression of the product. Confusing button labels, vague error messages, or empty states with no explanation all generate user friction at the moment when users are most likely to abandon if the product does not immediately feel intuitive.

Improving microcopy across the onboarding sequence is often one of the lowest-cost, highest-return optimizations a product team can make: no engineering work, immediate impact, measurable through funnel drop-off rates before and after the change.