Microcopy on Buttons: Why "Submit" Is Rarely the Right Label
Most button labels get written last, in a hurry, after the layout is done. I include myself in that. You finish the form, drop in a button, type "Submit" and move on.
I think that's a mistake, because the button is the moment where a person commits. The label is the last thing they read before they act. It deserves more than a placeholder.
This post is my reasoning for how to write button labels in product UI, and where I think the common advice needs care.
01A button is a promise
When someone clicks a button, they expect something specific to happen. The label sets that expectation. If the result doesn't match, they feel tricked, even slightly.
"Submit" promises nothing. It describes the mechanics of the form, not the outcome. The person has to look back at the page to work out what will happen.
Compare these for the same hypothetical screen, a form where you invite a teammate:
- Submit
- Send invite
- Add member
"Send invite" tells you an email or notification goes out. "Add member" suggests they are added immediately. Those are different outcomes, and the label is where you decide which one you're communicating. If your label is vague, you haven't made that decision yet.
02Verb plus object
My default is a verb followed by the thing it acts on.
- Save changes
- Create project
- Download report
- Export CSV
The verb says what happens. The object says to what. Together they let someone scan a screen and understand each action without reading the paragraphs around it.
This matters most when a screen has several buttons. Say a settings page has three sections, each with its own "Save". They all look the same, and a person can't tell whether "Save" covers one section or the whole page. "Save billing details" removes that question.
When the object can go
Dropping the object is fine when the context makes it obvious. In a dialog titled "Rename file", a button reading "Rename" is clear. Repeating "Rename file" adds length without adding meaning.
My test: if someone read only the button, with no other text, would they still know what it does? If yes in the context they'll actually see it, shorter is fine.
03Describe the outcome, not the process
Some labels describe what the system is doing rather than what the person gets. "Process", "Execute", "Proceed" and "Continue" all fall here.
"Continue" is the most common and the most defensible. In a multi-step flow, it's honest. But I'd still ask whether a better label exists. On the last step before payment, "Continue" is weaker than "Review order" or "Go to payment", because it tells the person where they're headed.
The same goes for the final step. Rather than "Finish", something like "Create account" or "Place order" names the result. People hesitate at commit points, and a clear label lowers that hesitation.
04Destructive actions need exact words
This is where I'd be strictest. A destructive button should name the thing being destroyed.
Say a dialog asks, "Are you sure?" with buttons "OK" and "Cancel". Which one confirms the deletion? Many people would have to stop and think. And "Cancel" is ambiguous in its own right: does it cancel the delete, or cancel the dialog that's asking about the delete?
A clearer version:
- Heading: "Delete this project?"
- Body: a short line saying what will be lost and whether it can be undone
- Buttons: "Delete project" and "Keep project"
Now each button explains itself. Nobody needs to read the heading to know what they're clicking. Pairing it with a distinct visual style for the dangerous action helps too, but colour shouldn't be the only signal. WCAG asks that colour not be the sole means of conveying information, and a precise label handles that naturally.
If you're using an AI tool to generate dialogs, check this one in particular. Generic "Confirm" and "Cancel" pairs are an easy default for generated UI. I cover that kind of review in A Designer's Checklist for Reviewing AI-Built UI Before Shipping.
05Keep labels consistent across the product
Once you pick a verb, stick to it. If one screen says "Delete", another says "Remove" and a third says "Discard", people wonder whether those mean different things.
Sometimes they do. "Remove" can mean taking something out of a list while it still exists elsewhere, while "Delete" means it's gone. If that's your actual distinction, keep it and use each word for only one meaning. If it isn't, pick one.
A small team can handle this with a short list: the five or six core actions and the word you use for each. It's a lightweight piece of a design system and costs very little to maintain.
06Loading and disabled states
The label can also change while something is happening. "Save changes" becoming "Saving…" confirms the click registered. It's a tiny piece of feedback, and it prevents double-clicks.
Be careful with disabled buttons, though. A greyed-out "Create account" with no explanation leaves people guessing. I'd rather keep the button active and show what's missing when it's clicked, or place a short hint nearby. Disabled controls also tend to be skipped by keyboard focus and can be harder for assistive technology users to discover, so the explanation can't live only in the disabled state.
07A quick pass you can run
Before shipping a screen, I'd go through the buttons with these questions:
- Does each label start with a verb?
- If several buttons look alike, does each name its object?
- Does the label describe the outcome rather than the process?
- Do destructive buttons name what will be lost?
- Is the same action called the same thing everywhere?
- Does the label fit on one line at small widths and in other languages?
That last point is worth a thought. Longer translations can break a button that looked fine in English, so leave some room.
08The short version
Button text is small, but it's the point of commitment. A vague label pushes the person to hunt for meaning elsewhere. A specific one answers the question before they ask it.
None of this requires a writer or a big process. It requires treating the label as part of the design instead of something you fill in at the end.
09Frequently asked questions
Is "Submit" ever an acceptable button label?
Occasionally, in a very short, obvious form where the context already makes the outcome clear. Even then, a specific verb like "Send" or "Save" usually costs nothing and removes a small doubt. I'd treat "Submit" as a default to replace, not a rule to ban.
How long should a button label be?
As short as it can be while still naming the action and, where needed, the object. Two to four words covers most cases. If you need more, the surrounding text is probably doing a job the button should share.
Should destructive buttons use different wording from normal ones?
Yes. Name the exact thing being removed, such as "Delete project", and avoid vague pairs like "OK" and "Cancel". Pair the clear label with a visual style that separates it from the safe option.
Denny Pratama
Product designer in Indonesia. Since 2018 I’ve designed SaaS products, dashboards and marketing sites, and now I build my own designs too.