# Buttons: How Action Buttons Show Priority, States, and Clear Labels

> The main button types, the states people see, and how to choose between a button and a link, with a payment screen worked through step by step.

**In short:** Buttons are action controls in a design system that show priority through main types, visible states and clear labels, so people know what to press next.

From "Design systems", a free course by Venkat R. Murty: https://designervenkat.online/learn/design-systems/buttons

## What you will learn

A button is the control a person taps or clicks to make something happen. It can submit a form, save a change, delete a file, or go back one step. In a design system, the button is a shared part. Teams define it once, with fixed types, states, and rules, so every screen in a product behaves the same way. This lesson explains what a button is made of, the main types and when to use each, the states people see, the difference between a button and a link, and how to write and place labels.

- **Design system:** A shared set of parts, rules, and examples that a team uses to build every screen the same way.
- **Component:** One reusable part of a design system, such as a button, that is defined once and reused.
- **Button:** A control that starts an action when a person selects it.
- **Action:** Something the product does because a person asked, such as saving or paying.
- **Variant:** A version of the same component with a different look or role, such as a primary or a secondary button.
- **Hierarchy:** The order of importance among actions, shown through how strong each button looks.
- **State:** The condition a button is in right now, such as ready, pressed, or loading.
- **Label:** The words on a button that say what it does.
- **Container:** The shape around the label, such as a filled box or an outlined box.
- **Destructive action:** An action that removes or damages something, such as deleting a file.
- **Link:** A piece of text or an element that takes a person to another place, such as another page.
- **Focus:** The state of being selected by keyboard, so a person can see where they are on the screen.

## What is a button?

A button is more than a colored box. It is a promise. When a person sees it, they expect that pressing it will do one clear thing. Good buttons make that promise easy to read. Bad buttons look alike, so people hesitate or press the wrong one. A design system fixes this by giving every button the same parts, the same few types, and the same behavior.

### What are the parts of a button?

Anatomy means the named parts of a component. A button is made of a few parts that fit together. Each part has a job, and a design system names each one so everyone uses the same words.

- **Label:** The words that say what will happen, such as Pay or Save changes. Most buttons need one. Without a clear label, the button has no meaning.
- **Icon (optional):** A small picture, such as a plus sign or a trash can. It can sit before the label, after it, or stand alone. An icon helps when a picture is easy to recognize, but the label should still carry the meaning.
- **Container:** The shape around the label. A filled container has a solid background color. An outlined container has a border and no fill. A text button has no container at all.

Designers should decide all three before they draw a button. The role is the most important of the three, because it tells the person how much weight the action carries.

> **Tip:** When you design a button, write down its role first. If you cannot say whether it is the main action, a cancel action, or a destructive one, the style will be guesswork.

## Button variants and hierarchy

A design system does not have one button. It has a small family of button variants. Each variant has a different visual weight, and that weight tells people how important the action is. This is called hierarchy. Hierarchy helps a person see what matters most on a screen at a glance.

Many teams describe hierarchy in three levels of emphasis, from strongest to weakest. Material Design, for example, uses filled buttons for the most important action, outlined buttons for medium emphasis, and text buttons for the lowest emphasis. Material 3 adds more styles between these, such as filled tonal and elevated buttons, but the same idea holds.

### What are the four main variants?

- **Primary:** The main action on a view, such as Submit, Save, or Pay. It is usually filled with a strong color so it stands out. Red Hat says it is the most prominent button and should be used for the most important action on a page.
- **Secondary:** A supporting action that works beside the primary button. Carbon describes it as the other choice in a pair, such as Cancel or Back. Outlined buttons often play this role because they look lighter than filled ones but still look like buttons.
- **Tertiary or ghost:** The lowest emphasis. Ghost buttons have little or no fill and no heavy border. Carbon uses ghost buttons when an action does not need to dominate the page. Material's text buttons work the same way and suit low-priority actions.
- **Destructive:** A button for actions that remove or damage data, such as Delete, Remove, or Stop. Good Practices and Carbon both say this type needs its own clear look, so a person sees the risk before they press it. Some systems use red for this, but the meaning matters more than the color.

Sources do not agree on every detail. Carbon's older guidance let a page have one or two primary buttons, while Red Hat and PatternFly-style guidance say one per page. Carbon also changed how a standalone danger button should look over time. When you read a system, check its own rule and follow the one used in your product. The lesson rule is the meaning of each type, not one exact color or position.

> **Tip:** Ask one question for each button: what happens if the person presses this by mistake? The answer tells you whether the button should be primary, secondary, ghost, or destructive.

### Why have one primary action per view?

The most common rule is to give each view one primary button. Red Hat advises limiting primary buttons to one per page, and Fernando UX reports that Carbon asks for one primary button per page, with an exception for temporary flows. The reason is simple. If three buttons all look strong, none of them looks like the main one, and people have to read every label to decide.

Good Practices warns against overusing the variants reserved for primary actions. Other buttons should give clear alternatives without competing with the main one. Morningstar's guidance is to place the most important button at the top of the hierarchy and lower-priority buttons below it, in the order primary, secondary, then ghost.

> **Tip:** Before you add a second strong button, ask whether the person really has two equal choices. If one choice is the normal path, make the other one quieter.

## Button states

A state is the condition a button is in at a given moment. Clay describes states as what is happening right now. Buttons change their look as the person moves through them, and the changes help the person know what the button is doing. A design system should define every state for every variant, so no button is left to guess.

Sources count states differently. UXPin says at least four states are needed, and that most production systems define five to seven per variant. Dell lists five: rest, hover, press, inactive, and focus. Clay lists six that it says every button should ship with. The six below are the most common in web products.

### What are the six common states?

- **Default:** The resting look. The button is available and ready to be clicked. Every other state is measured against this one.
- **Hover:** The look when a mouse cursor sits over the button. It is a small change, such as a slightly darker fill. It tells the person the button can be pressed.
- **Focus:** The look when a person selects the button with a keyboard. A visible ring or outline shows where they are. Without it, keyboard users lose track of the screen.
- **Pressed:** The look at the moment of clicking or tapping. Dell says a pressed button changes color to show it is being pressed. Some systems call this active.
- **Disabled:** The look when the action is not available. It is faded, and it cannot be pressed. Disabled buttons need care, because people do not always know why they cannot press them.
- **Loading:** The look while the product is working on the action, such as sending a payment. It shows progress and stops a second press.

### Loading and disabled states in practice

Loading is needed when a button starts work that takes time, such as submitting a form or processing a payment. Aidxn says the label should be replaced with, or joined by, a spinner, which is a small circling icon that shows work is happening. It also says the button should be disabled during this time so a person cannot press it twice. The button should keep the same width, because a shift in size when the spinner appears looks broken.

Disabled buttons need care. Good Practices says they can confuse people who do not understand why the button is unavailable. Its suggestion is to keep the button enabled and show feedback, such as an error message, when a requirement is missing. Carbon, in contrast, says a disabled button fits when the person cannot go on until they have entered some input. Choose the state based on whether the person can learn what to fix.

> **Tip:** Test every state in a real screen. A button that looks correct in a static design can still fail when someone is typing on a keyboard or waiting for a payment.

## Worked example: a payment screen

This example follows a checkout screen. I could not open Stripe's own pages while preparing this lesson, so treat the Stripe details here as a model of the pattern, not as facts checked against Stripe. Open a live checkout page and compare it with these steps before you use the example in your own work.

1. **Find the one primary action:** The filled Pay button is the main action. Material 3 describes this kind of button as the one thing the page most wants the person to do, with labels such as Save, Continue, or Pay. On this screen, Pay is the only filled button.
2. **Check the lower-emphasis option:** A quieter option sits beside Pay, such as a Back or Cancel control. Carbon describes Cancel-style actions as the negative choice in a pair. The person can still leave, but the eye goes to Pay first.
3. **Read the default state:** At rest, the Pay button is filled, its label is easy to read, and it looks ready to press. The person sees one clear path forward.
4. **Move in with a keyboard (focus):** A person who uses the Tab key lands on Pay. A visible ring or outline appears around it. Without this focus look, the person cannot see that the button is selected, and the next key press could do the wrong thing.
5. **Press the button (pressed and hover):** While a mouse rests on Pay, the fill shifts slightly to show it can be pressed. When the person clicks, the button shows its pressed look for a moment.
6. **Wait while the payment processes (loading):** After the click, a spinner appears in or beside the Pay label. The button keeps its width so the screen does not jump. It is disabled, so a second click cannot send the payment twice. Morningstar notes that a loading state tells the user the system is working and helps stop duplicate actions.
7. **Move on when the work ends:** When the payment finishes, the screen changes to a result, such as a confirmation. The loading button is no longer needed, so the screen moves on rather than leaving the person to guess.

## Should you use a button or a link?

Buttons and links look similar, so people mix them up. The simple test is this. A link takes a person to another place, such as another page or a section further down. A button does something on the current view, such as saving a change, sending a form, or deleting a file. Red Hat's guidance is to use buttons for actions and keep the primary button style, so that buttons look different from calls to action in text.

- **Use a button when:** the action changes something: it saves, sends, deletes, pays, or opens a panel on the same page. People expect a button to act.
- **Use a link when:** the person only moves to a page or a place in the same product. People expect a link to take them somewhere, and they often open it in a new tab.
- **Be careful with:** actions that feel like navigation but change data, such as Log out or Mark as read. These usually belong on a button, because they do something, even though they may end at another page.

## How do you write and place button labels?

A button label should say what will happen when someone presses it. Carbon's guidance centers on this idea: the label should express the action that will occur. The label is the most important text on the button, so it has to be clear before the style is tuned. The rules below are a starting point. Lesson on microcopy goes deeper.

- **Start with a verb:** Use words such as Save, Send, Pay, or Delete. A verb tells the person the action. Create account is clearer than Account.
- **Keep it short:** One or two words are usually enough. Long labels make buttons hard to scan and can push the layout out of shape.
- **Be specific and consistent:** Delete project is clearer than OK. Use the same word for the same action across the product, so people learn it once. Carbon's modal guidance says both the title and the button should reflect the action that will occur.

Placement is about reading order. Carbon's older guidance pairs a negative action (secondary) with a positive action (primary), in that order. Carbon's modal guidance puts the secondary button on the left and the primary on the right. Fernando UX reports that Carbon places the primary button on the left in full-page layouts and on the right in wizards and dialogs. Dell places the primary action on the left in its empty-state examples. These sources differ, so choose one order for your product and apply it everywhere.

> **Tip:** Group related buttons together, and order them from the most important to the least important. Red Hat says buttons should be ordered by hierarchy from left to right. Put one primary button in each group.

## Check yourself

**Quick check:** A signup form has two equally styled filled buttons side by side: Create account and Cancel. Users keep pressing Cancel by mistake. Which change to the button hierarchy should you make, and why?

A. Make Cancel larger than Create account so it looks like the safe choice.
B. Keep both filled, but change Cancel to a bright red so it looks different.
C. Make Create account the only filled button, and style Cancel as a secondary or ghost button.
D. Remove Cancel entirely so users cannot press it by mistake.

**Answer:** C. Hierarchy tells people which action matters most. Only one primary action should look strong, so Create account keeps the filled style. Cancel becomes a quieter secondary or ghost button, so people stop mistaking it for the main choice. Red would suggest danger, and Cancel is not destructive. Removing it takes away a valid choice.

**Quick check:** On a settings page, a Save button takes about three seconds to respond. Some users click it several times, and the page saves duplicate entries. What should the design do?

A. Turn the Save button into a link so it does not look clickable.
B. Show a loading state on the button and disable it while the save runs.
C. Remove the label so the button looks lighter and people click less.
D. Make the button red so people hesitate before pressing it.

**Answer:** B. A loading state tells the person that the save is in progress. Disabling the button while it runs stops the repeat presses. Turning it into a link or hiding the label does not show progress. Red suggests danger, but the save is not destructive.

## Key takeaways

- **Define the role first:** Decide whether each button is primary, secondary, ghost, or destructive before you style it. The role controls the look.
- **Keep one strong action:** Give each view one primary button, and make the rest quieter, so people can see what matters most.
- **Design every state:** Plan default, hover, focus, pressed, disabled, and loading. Users rely on these changes to know what is happening.
- **Write clear labels:** Start with a verb, keep it short, and use the same words for the same action.

## Sources

- [Carbon Design System: Button guidelines](https://www.carbondesignsystem.com/building-blocks/core/components/button/guidelines)
- [Carbon Design System (v9): Button usage](https://v9.carbondesignsystem.com/components/button/usage/)
- [Carbon Design System (v10): Button usage](https://v10.carbondesignsystem.com/components/button/usage/)
- [Carbon Design System (v10): Modal usage](https://v10.carbondesignsystem.com/components/modal/usage/)
- [Red Hat Design System: Button guidelines](https://ux.redhat.com/elements/button/guidelines/)
- [Material Design 3: Buttons guidelines](https://m3.material.io/components/buttons/guidelines)
- [Material Design: Buttons](https://m2.material.io/components/buttons)
- [Good Practices: Buttons](https://goodpractices.design/components/buttons)
- [Morningstar Design System: Buttons](https://design.morningstar.com/systems/marketing/business-website/components/buttons)
- [Dell Design System: Button](https://www.delldesignsystem.com/components/button/)
- [UXPin: Button States Explained](https://www.uxpin.com/studio/blog/button-states/)
- [Clay: Complete Guide to Buttons in Web Design](https://clay.global/blog/buttons-web-design)
- [Aidxn: The Humble Button](https://aidxn.com/blog/button-component-design/)
- [InterLAB: UI component anatomy, button, input, card](https://interlab.app/en/blog/ui-komponenty-sostoyaniya)
- [Fernando UX: Button Hierarchy](https://www.fernandoux.com/en/wiki/techniques/button-hierarchy/)
- [Cieden: How should I organize buttons in a design system?](https://cieden.com/book/atoms/button/how-to-organize-buttons-in-design-system)
- [UX Design (Medium): Button differentiation done right](https://uxdesign.cc/button-differentiation-done-right-5553605ea08a)
- [Medium: Material Studies, Buttons](https://medium.com/@brianisrighthere/material-studies-buttons-69ca067eed62)
- [Medium: One Screen, One Primary Button (Material 3)](https://medium.com/@alikasem/one-screen-one-primary-button-material-3-button-hierarchy-in-angular-material-b8953ea58cad)
