Skip to content
Material Design 3
Main Navigation
v3
v2
v1

English

简体中文
繁體中文
Español
Français
Русский
Português – Brasil
Deutsch
日本語
한국어
Italiano
Polski
Türkçe
čeština
magyar

English

简体中文
繁體中文
Español
Français
Русский
Português – Brasil
Deutsch
日本語
한국어
Italiano
Polski
Türkçe
čeština
magyar

Appearance

Sidebar Navigation

Foundations

Accessibility

Overview: Principles

Overview: Assistive technology

Designing: Overview

Designing: Color contrast

Designing: Structure

Designing: Flow

Designing: Elements

Writing and text: Best practices

Writing and text: Text truncation

Writing and text: Text resizing

Building for all: User needs

Building for all: Co-design

Content design

Overview

Alt text

Global writing: Overview

Global writing: Word choice

Notifications

Style guide: UX writing best practices

Style guide: Word choice

Style guide: Grammar and punctuation

Customizing Material

Devices

Watches: Overview

Watches: Foundations

Watches: Styles

Watches: Layout

XR

Design: Overview

Design: Interaction

Design: Layout

Design: Accessibility

Components: Overview

Components: App bars

Components: Dialogs

Components: Nav bar

Components: Nav rail

Components: Toolbars

Design tokens: Overview

Design tokens: How to use tokens

Interaction

Gestures

Inputs

Selection

States: Overview

States: State layers

States: Applying states

Layout

Overview: Overview

Overview: Parts of layout

Overview: Adaptive design

Scaffold: Overview

Scaffold: Bars

Scaffold: Rails

Scaffold: Panes

Grids & spacing: Overview

Grids & spacing: Grids

Grids & spacing: Spacing

Grids & spacing: Density

Breakpoints: Overview

Breakpoints: Compact

Breakpoints: Medium

Breakpoints: Expanded

Breakpoints: Large & extra-large

Bidirectionality & RTL

Canonical examples: Overview

Canonical examples: Feed

Canonical examples: List-detail

Canonical examples: Supporting pane

Usability: Overview

Usability: Applying M3 Expressive

Material A-Z

Styles

Color

Color system: Overview

Color system: How the system works

Color roles

Color schemes

Choosing a scheme

Static: Baseline

Static: Custom brand

Dynamic: Choosing a source

Dynamic: User-generated source

Dynamic: Content-based source

Advanced: Overview

Advanced: Apply colors

Advanced: Define new colors

Advanced: Adjust existing colors

Color resources

Elevation: Overview

Elevation: Applying elevation

Elevation: Tokens

Icons: Overview

Icons: Designing icons

Icons: Applying icons

Motion

Motion physics system: How it works

Motion physics system: Specs

Easing and duration: Applying easing and duration

Easing and duration: Tokens & specs

Transitions: Transition patterns

Transitions: Applying transitions

Shape: Overview & principles

Shape: Corner radius scale

Shape: Shape morph

Spacing: Overview

Spacing: Applying spacing

Spacing: Tokens

Typography: Overview

Typography: Fonts

Typography: Type scale & tokens

Typography: Applying type

Typography: Editorial treatments

Components

App bars: Overview

App bars: Specs

App bars: Guidelines

App bars: Accessibility

Badges: Overview

Badges: Specs

Badges: Guidelines

Badges: Accessibility

Buttons

All buttons

Button groups: Overview

Button groups: Specs

Button groups: Guidelines

Button groups: Accessibility

Buttons: Overview

Buttons: Specs

Buttons: Guidelines

Buttons: Accessibility

Extended FABs: Overview

Extended FABs: Specs

Extended FABs: Guidelines

Extended FABs: Accessibility

FAB menu: Overview

FAB menu: Specs

FAB menu: Guidelines

FAB menu: Accessibility

FABs: Overview

FABs: Specs

FABs: Guidelines

FABs: Accessibility

Icon buttons: Overview

Icon buttons: Specs

Icon buttons: Guidelines

Icon buttons: Accessibility

Segmented buttons: Overview

Segmented buttons: Specs

Segmented buttons: Guidelines

Segmented buttons: Accessibility

Split button: Overview

Split button: Specs

Split button: Guidelines

Split button: Accessibility

Cards: Overview

Cards: Specs

Cards: Guidelines

Cards: Accessibility

Carousel: Overview

Carousel: Specs

Carousel: Guidelines

Carousel: Accessibility

Checkbox: Overview

Checkbox: Specs

Checkbox: Guidelines

Checkbox: Accessibility

Chips: Overview

Chips: Specs

Chips: Guidelines

Chips: Accessibility

Date & time pickers

Date pickers: Overview

Date pickers: Specs

Date pickers: Guidelines

Date pickers: Accessibility

Time pickers: Overview

Time pickers: Specs

Time pickers: Guidelines

Time pickers: Accessibility

Dialogs: Overview

Dialogs: Specs

Dialogs: Guidelines

Dialogs: Accessibility

Divider: Overview

Divider: Specs

Divider: Guidelines

Divider: Accessibility

Lists: Overview

Lists: Specs

Lists: Guidelines

Lists: Accessibility

Loading & progress

Loading indicator: Overview

Loading indicator: Specs

Loading indicator: Guidelines

Loading indicator: Accessibility

Progress indicators: Overview

Progress indicators: Specs

Progress indicators: Guidelines

Progress indicators: Accessibility

Menus: Overview

Menus: Specs

Menus: Guidelines

Menus: Accessibility

Navigation

Navigation bar: Overview

Navigation bar: Specs

Navigation bar: Guidelines

Navigation bar: Accessibility

Navigation drawer: Overview

Navigation drawer: Specs

Navigation drawer: Guidelines

Navigation drawer: Accessibility

Navigation rail: Overview

Navigation rail: Specs

Navigation rail: Guidelines

Navigation rail: Accessibility

Radio button: Overview

Radio button: Specs

Radio button: Guidelines

Radio button: Accessibility

Search: Overview

Search: Specs

Search: Guidelines

Search: Accessibility

Sheets

Bottom sheets: Overview

Bottom sheets: Specs

Bottom sheets: Guidelines

Bottom sheets: Accessibility

Side sheets: Overview

Side sheets: Specs

Side sheets: Guidelines

Side sheets: Accessibility

Sliders: Overview

Sliders: Specs

Sliders: Guidelines

Sliders: Accessibility

Snackbar: Overview

Snackbar: Specs

Snackbar: Guidelines

Snackbar: Accessibility

Switch: Overview

Switch: Specs

Switch: Guidelines

Switch: Accessibility

Tabs: Overview

Tabs: Specs

Tabs: Guidelines

Tabs: Accessibility

Text fields: Overview

Text fields: Specs

Text fields: Guidelines

Text fields: Accessibility

Toolbars: Overview

Toolbars: Specs

Toolbars: Guidelines

Toolbars: Accessibility

Tooltips: Overview

Tooltips: Specs

Tooltips: Guidelines

Tooltips: Accessibility

On this page

Buttons: Guidelines ​

Buttons prompt most actions in a UI.


Buttons in various shapes and sizes.
Buttons and icon buttons come in many shapes, styles, and sizes

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.

Use visually-prominent filled buttons for the most important actions

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.

1 button placed on bottom right of screen.
Do Use buttons for discrete actions
3 buttons side by side on bottom of screen.
Don’t Don’t clutter your UI with too many buttons. Consider presenting low-priority actions in overflow menus or as icon buttons.
Filled button on menu screen.
Do A button container’s width is dynamically set to fit its label text
Filled button as wide as layout grid.
Do Button container width can be responsive, which allows it to stretch horizontally
Filled button with label text overflowing the container.
Don’t A button container’s width shouldn’t be narrower than its label text
Diagram of button styles and toggle behaviors.

A: Default button; B: Toggle (unselected); C: Toggle (selected) for five button styles, in order of emphasis:

  1. Elevated button
  2. Filled button
  3. Filled tonal button
  4. Outlined button
  5. 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.

More on button groups

Audio app with play, next, and back buttons.
Different sized buttons in a button group help emphasize the main action from secondary actions

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.

Use toggle buttons for binary actions

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.

Toggleable “start” and “reset” buttons.
Do When using toggleable buttons, keep the label character count a similar length for both states
Toggleable “start” and “reset back to beginning” buttons.
Don’t The label length shouldn’t change dramatically to be longer or shorter

Anatomy ​

3 parts of a button.
  1. Label text
  2. Container
  3. 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.

Button with label text “See all recipes.”
Do Use sentence case for button label text, capitalizing the first word and proper nouns
Button with wrapped label.
Don’t Don’t wrap text. For maximum legibility, label text should remain 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.

Chips next to an outlined button, highlighting their similarities.
Caution The outlined button style is very similar to chips. Consider using a filled or tonal button instead.

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.

Round button.
Round buttons have containers with fully rounded corners

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

Square buttons with different radii.
Square buttons have square containers and change radius as the button size changes
Button with the label text “Edit playlist” within the container.
Do A button’s width dynamically adjusts to the label text
Button with text larger than its container.
Don’t Avoid setting a fixed width smaller than the label text

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.

Filled button with the icon to the left of the label in a left-to-right language.
Do Place the icon to the left of the label in buttons with text in left-to-right languages
Filled button with the icon to the right of the label in a right-to-left language.
Do Place the icon to the right of the label in buttons with text in right-to-left languages
Button with shopping cart icon and text label “Add to cart”.
Do Use icons that clearly communicate their meaning
Button with Plus icon vertically above the text label “Add to watch list”.
Don’t Don’t vertically align an icon and text in the center of a button
Button with two icons.
Don’t Don’t use two icons in the same button

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.

Elevated button on a scrim background.
Elevated buttons provide 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.

Elevated button in a shopping experience.
Caution Higher elevation increases the emphasis of a button

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.

Filled button reading “Make payment.”
Filled buttons have high visual impact when used for important actions

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.

Filled “pause” button in a music app.
Filled buttons can be responsive to the layout grid and help emphasize main actions

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.

Shopping app with 2 tonal-style filled buttons.
The tonal style has less emphasis than filled or emphasis

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 for less important actions, including a back button and a button that reads “Next movie.”
Outlined buttons contain less important supporting 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.

Outlined button for “add to cart” in shopping app.
Outlined buttons display a stroke around the button container
Outlined button labeled Add to calendar on a pink/purple background.
Do Outlined buttons can be used on backgrounds with a color gradient
2 photos, each with an outlined button with a custom fill.
Caution Use caution when placing outlined buttons on top of images. Customizing the button to have a contrasting container fill can help ensure legibility of label text. Or, use a filled button instead.

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

Example calendar screen with 2 text buttons and 1 split button.
Use text buttons for the lowest priority actions

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.

Text button labeled “Retry” in a snackbar.
Text button in a snackbar
Text button labeled “View album” on an album cover background.
Text button against an image background

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

Text button labeled “Learn more” in an information card about sourdough bread.
Text button in a card

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.

Modal dialog with the title “Subscribe to our newsletter?” and trailing buttons “Cancel” and “Subscribe”.
Text buttons in a dialog

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.

Flights app in compact screen with buttons below flight information.
Filled buttons are end-aligned below flight information in a compact window
Flights app in large screen with buttons to the left of flight information.
Filled buttons are start-aligned beside flight information in a large window

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

2 buttons with horizontally centered text labels.
Do Keep the icon and label text grouped and centered
1 button with centered text label, 1 button with icon and label aligned to opposite edges.
Don’t Don't ungroup the icon and label text or let them anchor to opposite sides of the button

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.

Button width is over-stretched with screen width.
Don’t Don’t allow the button to stretch in a way that creates long, flat buttons with very little content inside

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.

2 buttons scaling to accommodate different device sizes.
Buttons can move in the layout, but elements should remain in the same order
Pager
Previous pageButtons: Specs
Next pageButtons: Accessibility

Released under the Apache 2.0 or CC BY 4.0

Copyright © 2018-Present Google

https://m3.material.io/components/buttons/guidelines

Released under the Apache 2.0 or CC BY 4.0

Copyright © 2018-Present Google