Buttons: Guidelines
Buttons prompt most actions in a UI.

Usage
Buttons communicate actions that people can take. They are typically placed throughout the UI, in places like:
- DialogsDialogs provide important prompts in a user flow.More on dialogs
- Modal windows
- Forms
- CardsCards display content and actions about a single subject.More on cards
- ToolbarsToolbars display frequently used actions relevant to the current page.More on toolbars
They can also be placed within standard button groupsStandard button groups add interactions between adjacent buttons when they're pressed.More on button groups.
Buttons are just one option for representing actions in a product and shouldn’t be overused. Too many buttons on a screen can disrupt the visual hierarchy.
Consider placing additional actions in a navigation railNavigation rails let people switch between UI views on mid-sized devices.More on navigation rail, set of chipsChips help people enter information, make selections, filter content, or trigger actions.More on chips, text links, or icon buttonsIcon buttons help people take minor actions with one tap.More on icon buttons.






A: Default button; B: Toggle (unselected); C: Toggle (selected) for five button styles, in order of emphasis:
- Elevated button
- Filled button
- Filled tonal button
- Outlined button
- Text button
A button groupButton groups organize buttons and add interactions between themMore on button groups is a collection of buttons that relate to each other and can respond to one another. Both buttons and icon buttons can be used inside a button group.
In some cases, there are primary and secondary actions within a button group. Buttons with primary actions should have a higher visual emphasis through size, color, or shape.

Toggle buttons
Toggle buttons should be used for binary selections, such as Save or Favorite. When toggle buttons are pressed, they can change color, shape, and labels.
Toggle buttons should use an outlined icon when unselected, and a filled version of the icon when selected. If a filled version doesn’t exist, increase the weight instead.
By default, toggle buttons change from round to square when selected.
If the label changes on selected or unselected states, be mindful of the character count. Changing the label significantly is disruptive to the user and the page layout.


Anatomy

- Label text
- Container
- Icon (optional)
Label text
Label text is the most important element of a button. It describes the action that will occur if someone taps a button. It should be very brief, ideally 1–3 words.
Use sentence case, which only capitalizes the first word and proper nouns. This allows the text to distinguish proper nouns, for example: Book with Flights, not BOOK WITH FLIGHTS.
Don’t truncate or wrap label text. It should always be fully visible on a single line.


Buttons with the outlined and text color style depend on the colors to be recognizable from other text and elements. Use caution when putting these buttons next to visually similar elements, such as chips or large text.

Container
Button containers hold the label text and optional icon. Buttons with the text color style have a visible container only when hovered, focused, or pressed.
Buttons with a round shape have containers with fully rounded corners.

Buttons with a square shape have containers with more subtle rounding that changes based on button size.



Icon (optional)
Icons visually communicate the button’s action and help draw attention. They should be placed on the leading side of the button, before the label text.





Color styles
Elevated style
The elevated button style is the same as the tonal button, but with a shadow.
To avoid overusing shadows, use the elevated style only when absolutely necessary, such as when the button requires visual separation from a visually prominent background.

Buttons at higher elevations typically have more emphasis in a design, and should be used sparingly. For high emphasis, consider the filled style instead.

Filled style
The filled button style has the most visual impact after the FABFloating action buttons (FABs) help people take primary actions.More on FABs, and should be used for important, final actions that complete a flow, like Save, Join now, or Confirm.

Since they have such strong emphasis, the filled style should be used sparingly, ideally for only one action on a page.
In some cases, filled buttons can use tertiary colors.

Tonal style
The tonal button style is useful in contexts where a lower-priority button requires slightly more emphasis than an outline would give, such as Next in an onboarding flow. Tonal buttons use the secondary color mapping.

Outlined style
The outlined style is ideal for medium-emphasis buttons which contain actions that are important, but aren’t the primary action in a product.
Outlined buttons pair well with filled buttons to indicate alternative, secondary actions.

Outlined buttons display a stroke around the button container, and have no fill by default.
They should be placed on simple backgrounds, not visually prominent backgrounds such as images or videos.



Text style
The text button style should be used for the lowest priority actions, especially when presenting multiple options.
They should be placed on simple backgrounds, not visually prominent backgrounds such as images or videos. The container isn’t visible until someone interacts with the button.
Don’t underline the text button. Use hyperlinked body text instead to emphasize links. More on hyperlinks

Text buttons are often placed within components such as cardsCards display content and actions about a single subject.More on cards, dialogsDialogs provide important prompts in a user flow.More on dialogs, and snackbarsSnackbars show short updates about app processes at the bottom of the screen.More on snackbars. Since text buttons don’t have a visible container in their default stateStates show the interaction status of a component or UI element.More on states, they don’t distract from nearby content.
However, since there’s no container, the label text color must always be recognizable from non-button text and elements.


In cards, text buttons help maintain an emphasis on card content.

Dialogs use text buttons because the absence of a container helps unify the action with the dialog text.
Align text buttons to the trailing edge of dialogs, on the right for left-to-right languages and on the left for right-to-left languages.

Adaptive design
Resizing
When scaling layouts for large screen devices, buttons can adapt their visual presentation, size, alignment, and arrangement to fit different contexts and user needs.
Choose the best button position based on screen size.


The icon and label text in a button stay centered and grouped as the button's width changes.


Buttons can be customized to change size and scaling behavior across different breakpointsBreakpoints are opinionated window sizes where a layout changes to match available space, device conventions, and ergonomics (previously window size classes).More on breakpoints.
To avoid creating very long buttons in large windows, constrain button width or place buttons beside other elements.

Presentation
The size and placement of buttons can change as parent containers, such as cards, adapt for larger screens.
Keep items, including buttons, in the same order between large and small screens to provide a consistent experience for screen readers and keyboard navigation.
