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

Toolbars: Guidelines ​

Toolbars display frequently used actions relevant to the current page


5 toolbars of various colors, elements, and actions.
Toolbars can be used for a wide variety of use cases

Usage ​

Use a toolbar to provide actions related to the current page.

Toolbars can contain many actions and can scale to show more actions in larger windows.

Vibrant toolbar at bottom of mobile screen.
A toolbar provides actions related to the current page

There are two variants of toolbars:

  • Docked toolbar
    Spans the full width of the window. It’s best used for global actions that remain the same across multiple pages.
  • Floating toolbar
    Floats above the body content. It’s best used for contextual actions relevant to the body content or the specific page.

The baseline bottom app bar is no longer recommended, but is still supported.

Docked toolbar example.
Docked toolbar shows global controls
Floating toolbar example.
Floating toolbar show controls relevant to the current page

When actions don’t fit in a toolbar, add a menuMenus display a list of choices on a temporary surface.More on menus.

Toolbar showing local navigation.
Toolbar actions can open a menu

There are two color configurations:

  • Standard
    A low-emphasis color scheme best used for focusing attention on the body content.
  • Vibrant
    A high-emphasis color scheme that draws attention to the controls. It can also indicate a temporary change in the page behavior, such as entering edit mode.

Consider using alternative color roles to create greater or lesser emphasis depending on the needs of the app. Experiment with different color roles to achieve different effects.

Toolbar with low-emphasis controls.
Use the standard color scheme to draw focus to content outside the toolbar
Toolbar with high-emphasis controls.
Use the vibrant color scheme to emphasize controls or actions

Toolbars & navigation bars ​

The toolbar and navigation barNavigation bars let people switch between UI views on smaller devices.More on navigation bars are both placed at the bottom of the window, so should not be shown at the same time. Show the navigation bar on primary pages, and toolbars on subsequent pages with actions.

A navigation bar shown on the main email Inbox page, and a toolbar shown when reading the email.
  1. Navigation bar on a primary page
  2. Toolbar on a secondary page with contextual actions

Floating toolbars can be used as tabs between related subsequent pages in the product hierarchy.

This helps group similar pages together, and shows that the selection affects the body content underneath.

Floating toolbar with secondary navigation labels.
Do Keep navigation distinct, and use a toolbar to display local navigation on a specific page

Consider the existing app hierarchy when using a toolbar for local navigation.

Avoid redundant or confusing navigation combinations in the same view.

Floating toolbar with secondary navigation labels displaying above a bottom navigation bar.
Don’t Don’t show a navigation bar and a toolbar with navigation controls at the same time

Anatomy ​

Diagram of toolbar layouts.
  1. Container
  2. Elements

Container

The docked toolbar’s container spans the full width of the window.

Avoid applying rounded corners to the container. This can imply the container expands or changes upon interaction.

Docked toolbar with square corners.
Do Use straight corners for docked toolbars
Docked toolbar with rounded corners.
Don’t Avoid modifying the container shape

As long as there's a minimum of 16dp padding on the leading and trailing edge, arrange controls inside however you see fit. The 32dp padding between items is just the default.

All elements need a minimum 48x48dp target area to be accessible.

Be cautious of including too many controls as it can be overwhelming.

Docked toolbar with too many controls.
Don’t Don’t overwhelm people with too many controls

The floating toolbar’s container should be fully visible on screen. If more actions are needed, use an overflow menu.

Floating toolbar with overflow menu icon.
Do Choose the most essential actions to show on screen by default
Floating toolbar that expands off edge of screen.
Don’t Floating toolbars shouldn’t exceed the edge of the window or pane

Elevation

Floating toolbars have elevation by default.

If the content beneath the toolbar is visually distinct, elevation can be removed.

Vibrant floating toolbar that's easy to see in front of a neutral text background.
The elevation on floating toolbars can be removed if on a visually distinct background

Flexibility & slots

When configuring a toolbar, think of it as a container with several slots.

These slots can be populated by buttonsButtons let people take action and make choices with one tap.More on buttons, icon buttonsIcon buttons help people take minor actions with one tap.More on icon buttons, images, text fieldsText fields let users enter text into a UI.More on text fields, or any kind of custom component.

Icon buttons provide an even hierarchy of controls. Mixing in a filled icon button can help add emphasis to a single action.

5 toolbars with slots, and various combinations of buttons, icon buttons, filled icon buttons, and text fields.
Toolbars are made of slots that can contain many kinds of actions

Visually emphasizing a single action more than others is an effective way to create hierarchy and guide people to controls they use most often. Avoid emphasizing more than one action at a time.

Some common ways to add emphasis to toolbar actions include:

  • Use different icon buttonIcon buttons help people take minor actions with one tap.More on icon buttons color styles, such as filled, tonal, and standard
  • Customize the color rolesColor roles are assigned to UI elements based on emphasis, container type, and relationship with other elements. This ensures proper contrast and usage in any color scheme.More on color roles of a single action, such as a primary or secondary palette
  • Use wide and narrow icon buttons
  • Pair the toolbar with a FABFloating action buttons (FABs) help people take primary actions.More on FABs
2 floating toolbars, 1 with a filled action button and 1 paired with a FAB.
Two different ways to create a high emphasis action in toolbars
Floating toolbar with primary action and FAB.
Don’t Don’t emphasize multiple buttons with bold, primary colors, such as a button and FAB together. Emphasize one action at a time.
Floating toolbar with different control designs.
Don’t Avoid mixing too many different controls in the same toolbar. A consistent control design keeps things clear.

Avoid using square icon buttons in floating toolbars. Their square shape conflicts with the fully-rounded shape of the floating toolbar container.

Square buttons can be used in the docked toolbar.

A floating toolbar, which is rounded, with squared icon buttons inside.
Don’t Don’t use square filled icon buttons in floating toolbars

Floating toolbar with FAB

A FABFloating action buttons (FABs) help people take primary actions.More on FABs can be placed next to a floating toolbar to present one high-priority action alongside a unified set of toolbar actions.

Use a FAB for the highest-priority action in the view, or to complement the controls.

3 toolbars paired with FABs.
Floating toolbars can be paired with FABs

Position & orientation ​

Only place docked toolbars at the bottom of the window.

If using other bottom-aligned elements, such as a navigation bar, don't use a docked toolbar.

Docked toolbar on mobile.
Docked toolbars are always at the bottom of the window

Floating toolbars can be horizontal or vertical.

Horizontal toolbars should have a minimum 16dp margin from the edge of the window.

Floating toolbar on mobile.
Horizontal floating toolbars should be at least 16dp from the edge of the window

In larger breakpoints, floating toolbars can be vertical and placed on either side of the screen.

Vertical toolbars should have a minimum 24dp margin.

Vertical floating toolbar with 24dp margin.
Maintain at least a 24dp margin for vertical toolbars

To keep vertical toolbars compact, don’t use wide icon buttons.

Use narrow or default icon buttons instead.

Toolbar showing local navigation.
Don’t Using wide buttons with vertical toolbars can unnecessarily widen toolbar containers and hide other UI elements

Vertical toolbars should be positioned opposite the navigation railNavigation rails let people switch between UI views on mid-sized devices.More on navigation rails to balance out the screen and keep actions easy to access.

When showing a navigation rail and vertical floating toolbar at once, use the centered configuration of the navigation rail.

Large screen UI showing both a navigation rail and vertical floating toolbar.
When a nav rail is visible, the floating toolbar should be vertical on the opposite edge of the window

Adaptive design ​

Adaptive design allows an interface to respond or change based on context, such as the user, device, and usage. More on adaptive design

Resizing ​

Docked

The docked toolbar should always span 100% of the screen width.

In compact breakpointsWindow widths smaller than 600dp, such as a phone in portrait orientation.More on compact breakpoints, elements in the toolbar should be evenly spaced.

In medium breakpointsWindow widths from 600dp to 839dp, such as a tablet or foldable in portrait orientation.More on medium breakpoints and larger, adjust the padding between controls to create a comfortable layout. This can be achieved by:

  • Centering all elements
  • Customizing to center a key action, and aligning other elements to the edges
Docked toolbar with evenly spaced elements.
Docked toolbar items should be evenly spaced in compact windows
Docked toolbar with centered elements.
In medium breakpoints and larger, create a spacious layout by centering all elements

Docked toolbar with central action and some elements pushed to the edge.
Align controls to the edge of the screen to make them easier to reach on tablets, and to better highlight a primary action in the middle

On web and large screens, the docked toolbar can be rounded. Dividers can be used to organize large amounts of items. Only shrink the height and use extra small buttons if vertical space is limited.

Docked toolbar with 15 actions for text editing on large screens, organized with dividers.
On web and other large screens, docked toolbars can be rounded and placed in different parts of the page

Floating

The container should only be as big as needed to hold the items inside before reaching the 16dp margin.

If there’s not enough space for all items, put them in an overflow menu in the trailing slot. As the breakpoint expands, more actions can be revealed.

The floating toolbar width can also be capped to keep it smaller and hide more elements.

Floating toolbar in compact window with excess padding.
Don’t Don’t add extra space to a toolbar beyond its necessary items
Floating toolbar in expanded window class.
At larger screen sizes, the container can display more controls before hitting the 16dp margin

Vertical toolbars aren’t recommended for compact windows.

They take up a significant area of the screen and may feel visually overwhelming, especially on screens with complex layouts.

Only use them when the screen is simple or when the toolbar has a few controls.

Vertical toolbar in a compact window.
Caution Vertical toolbars can cover important content in compact windows

Presentation ​

In larger breakpoints, floating toolbars can be aligned to opposite edges of the screen so they're easy to reach and group similar actions. For example, consider placing the undo and redo actions in one toolbar, and editing controls like highlight, erase, and select in another. Stylistic differences can help emphasize each toolbar’s purpose and clarify hierarchy.

2 toolbars, each with distinct stylistic treatment and actions.
Multiple toolbars with different stylistic treatments can create hierarchy and distinguish different kinds of actions

Don’t use multiple toolbars in compact windows. There typically isn’t enough room on screen.

Instead, use one toolbar for all actions.

Multiple toolbars in a compact window.
Don’t Avoid using multiple toolbars in smaller windows

Actions at the trailing edge of the toolbar can collapse into an overflow menu at smaller breakpoints, and become visible again at larger sizes.

Actions at the trailing edge collapse into an overflow menu

Right-to-left languages ​

In right-to-left (RTL) languages, mirror individual items that need it, like icons and text direction. If the order of actions is important, flip the order of the actions as well.

Next button is on trailing edge for a LTR language.
In LTR languages, the Next button is intentionally placed on the trailing (right) edge
Next button is now on the trailing edge, at left, for RTL language.
In RTL languages, reverse the order so Next remains on the trailing edge when flipped, now on the left. Text is not translated to illustrate mirroring.

Behavior ​

Scrolling

Docked toolbars can either remain on the screen during scroll, or animate offscreen.

Docked toolbars can animate offscreen

Floating toolbars can remain on the screen, animate offscreen, or collapse into a single, high-emphasis action on scroll.

Floating toolbars can animate off screen

On Jetpack Compose, the floating toolbar can collapse to a FAB or key action on scroll.

Floating toolbars can be customized to do other actions on scroll, like collapse into a single action

Don't collapse actions and scroll at the same time.

Don’t Toolbars shouldn't both collapse and transition off page
Pager
Previous pageToolbars: Specs
Next pageToolbars: Accessibility

Released under the Apache 2.0 or CC BY 4.0

Copyright © 2018-Present Google

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

Released under the Apache 2.0 or CC BY 4.0

Copyright © 2018-Present Google