Skip to content
Material Design 2
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

Material System

Introduction

Material studies

About our Material studies

Basil

Crane

Fortnightly

Owl

Rally

Reply

Shrine

Material Foundation

Environment

Surfaces

Elevation

Light and shadows

Layout

Understanding layout

Pixel density

Responsive layout grid

Spacing methods

Component behavior

Applying density

Navigation

Understanding navigation

Navigation transitions

Search

Color

The color system

Applying color to UI

Color usage

Text legibility

Dark theme

Typography

The type system

Understanding typography

Language support

Sound

About sound

Applying sound to UI

Sound attributes

Sound choreography

Iconography

Product icons

System icons

Animated icons

Shape

About shape

Shape and hierarchy

Shape as expression

Shape and motion

Applying shape to UI

Motion

Understanding motion

The motion system

Speed

Choreography

Customization

Interaction

Gestures

Selection

States

Communication

Confirmation & acknowledgement

Data formats

Data visualization

Empty states

Help & feedback

Imagery

Launch screen

Onboarding

Offline states

Writing

Machine learning

Machine learning patterns

Object detection: live camera

Object detection: static image

Barcode Scanning

Material Guidelines

Material Theming

Overview

Implementing your theme

Usability

Accessibility

Bidirectionality

Platform guidance

Android bars

Android fingerprint

Android haptics

Android icons

Android navigating between apps

Android notifications

Android permissions

Android slices

Android split-screen

Android swipe-to-refresh

Android text selection toolbar

Android widget

Cross-platform adaptation

Components

App bars: bottom

App bars: top

Backdrop

Banners

Bottom navigation

Buttons

Buttons: floating action button

Cards

Checkboxes

Chips

Data tables

Date pickers

Dialogs

Dividers

Image lists

Lists

Menus

Navigation drawer

Navigation rail

Progress indicators

Radio buttons

Sheets: bottom

Sheets: side

Sliders

Snackbars

Switches

Tabs

Text fields

Time pickers

Tooltips

On this page

Bottom navigation ​

Bottom navigation bars allow movement between primary destinations in an app.

Bottom navigation hero image

Usage ​

Bottom navigation bars display three to five destinations at the bottom of a screen. Each destination is represented by an icon and an optional text label. When a bottom navigation icon is tapped, the user is taken to the top-level navigation destination associated with that icon.

Principles ​


Bottom navigation principle: ergonomic

Ergonomic

The bottom navigation bar is easy to reach on a handheld mobile device.

Bottom navigation principle: consistent

Consistent

When used, the bottom navigation bar appears at the bottom of every screen.

Bottom navigation principle: related

Related

Bottom navigation bar destinations should be of equal importance.

When to use ​

Bottom navigation should be used for:

  • Top-level destinations that need to be accessible from anywhere in the app
  • Three to five destinations
  • Mobile or tablet only

Bottom navigation shouldn’t be used for:

  • Single tasks, such as viewing a single email
  • User preferences or settings
Don’t use a bottom navigation bar for fewer than three destinations (use tabs instead)

Don't

Don’t use a bottom navigation bar for fewer than three destinations (use tabs instead).

Don’t use more than five destinations

Don't

Don’t use more than five destinations. For those cases, try tabs or a navigation drawer.

Caution: combining bottom navigation and tabs may cause confusion, as their relationship to the content may be unclear

Caution

Combining bottom navigation and tabs may cause confusion, as their relationship to the content may be unclear. Tabs share a common subject, whereas bottom navigation destinations are top-level and disconnected from each other.

Image is 50% scale.

Tabs

Tabs organize high level content in an app content, such as switching between views, data sets, or functional aspects of an app.

Related article

Navigation drawer

Navigation drawers provide access to the navigation destinations of your app.

Related article

Anatomy ​

There are three destinations in this bottom navigation, each with an icon and text label
There are three destinations in this bottom navigation, each with an icon and text label.

1. Container
2. Inactive icon
3. Inactive text label
4. Active icon
5. Active text label

Representing destinations ​

The way bottom navigation destinations are represented can depend on how many are used:

  • Three destinations: Display icons and text labels for all destinations.
  • Four destinations: Active destinations display an icon and text label. Inactive destinations display icons, and text labels are recommended.
  • Five destinations: Active destinations display an icon and text label. Inactive destinations use icons, and use text labels if space permits.
There are three destinations in this bottom navigation, each with an icon and text label
There are three destinations in this bottom navigation, each with an icon and text label.

Icons ​

Bottom navigation destinations always include an icon. It’s best to pair icons with text labels, especially if the icon doesn’t have obvious meaning.

Icons paired with text labels in bottom navigation
Icons paired with text labels in bottom navigation

Text labels ​

Text labels provide short, meaningful descriptions of bottom navigation destinations.

Do: use short text labels

Do

Use short text labels.

Don’t truncate text

Don't

Don’t truncate text. The truncation may obscure important destination information.

Don’t shrink text to fit on a single line

Don't

Don’t shrink text to fit on a single line.

Caution: avoid wrapping text

Caution

Avoid wrapping text.

Icon & label colors ​

Active and inactive icons and text labels should have sufficient contrast with the container. The active destination’s icon and label should use your app’s Primary or a High-Emphasis “On” color depending on the component’s color scheme. Inactive icons and labels can use the Medium-Emphasis “On” color.

Do: use the Primary or High-Emphasis “On” color for the active destination in a bottom navigation bar

Do

Use the Primary or High-Emphasis “On” color for the active destination in a bottom navigation bar.

Don’t use multiple or low-contrast colors in a bottom navigation bar

Don't

Don’t use multiple or low-contrast colors in a bottom navigation bar, as they make it harder for users to distinguish the active item and navigate to other destinations.

Behavior ​

Navigation ​

Bottom navigation behaves differently on Android and iOS. When you select a bottom navigation item (one that’s not currently selected), each platform displays different outcomes:

  • On Android: the app navigates to a destination’s top-level screen. Any prior user interactions and temporary screen states are reset, such as scroll position, tab selection, and in-line search.
  • On iOS: the destination reflects the user’s prior interaction. If the user previously visited that section of the app, they return to the last screen viewed (with its prior state preserved, if possible). Otherwise, the app navigates to the top-level screen.

Default platform navigation can be overridden when needed to improve the user experience. For example, an Android app that requires frequent switching between sections can preserve each section’s state. Or, an iOS app can return users to the top-level screen (or reset their scroll position) if it better suits the use case.

On Android, revisiting a section resets the app, returning the user to its top-level screen.
On iOS, when a user revisits a section they return to where they left off in that section, such as a detail screen.

When moving downward in the app’s hierarchy (from a parent screen to a child screen), a bottom navigation bar can be displayed persistently for quick navigation between an app’s sections.

The bottom navigation bar in this music app remains in view when navigating to an album.

Android bars

The following guidance applies to Android only.

Related article

Badges ​

Bottom navigation icons can include badges in their upper right corner. These badges can contain dynamic information, such as a number of pending requests.

Diagram of badge, badge with a number, badge with a maximum character count
1. Badge
2. Badge with a number
3. Badge with a maximum character count

Scrolling ​


Upon scroll, the bottom navigation bar can appear or disappear:

  • Scrolling downward hides the bar
  • Scrolling upward reveals it
The bottom navigation bar can disappear to allow more space for content.

Transitions ​

A fade-through transition pattern is recommended for transitions between bottom navigation destinations. Lateral (side-to-side) transitions may imply a peer relationship between the items that does not exist, or mislead users into thinking they can use gestures to navigate between sections.

Do

Transition between active and inactive bottom navigation destinations using a cross-fade animation.

Don't

Avoid using lateral motion to transition between views. Lateral motion is reserved for navigating between peers.

Fade-through

A transition pattern in the Motion System

Related article

Scaling and adaptation ​

Only use bottom navigation on mobile and small tablet interfaces. On large screens, swap out bottom navigation bars for a component that’s better suited to large screen contexts.

Component swapping means that components with similar functions are swapped to make changes to an interface that enhance the ergonomics and functionality. Component swapping is triggered by pre-set device breakpoints. When a screen scales beyond a breakpoint, swappable components should change into a more appropriate component for a given screen size.

Component swapping can create a cohesive navigation system that adapts across screen sizes.

At medium breakpoints, replace the bottom navigation bar with a navigation rail.

At large breakpoints, replace the navigation rail with a navigation drawer.

Scaling and adaptation: small breakpoints

Small breakpoints: 360-599dp

For small devices like phones, horizontal space is at a premium; the content area of an app usually spans the entire width of a screen. In this case, smaller navigation components should anchor to the top or bottom of a layout, saving space while making primary destinations accessible.

Scaling and adaptation: medium breakpoints

Medium breakpoints: 600-1239dp

On medium-sized devices like tablets, move primary navigation elements into a navigation rail that is fixed to the leading edge of the layout.


Scaling and adaptation: large breakpoints

Large breakpoints: 1240dp+

On devices with 1240dp+ widths, present destinations in a permanently visible or dismissible navigation drawer. Assign hierarchy based on how frequently or quickly a user needs to move between destinations.

Placement ​

Elevation ​

Bottom navigation can be temporarily covered by dialogs, bottom sheets, navigation drawers, the on-screen keyboard, or other elements needed to complete a flow. They should not be permanently obstructed on any screen.

The search feature of the “Radio” screen triggers the on-screen keyboard, temporarily covering the bottom navigation bar until the search flow is completed.

Fixed navigation bar ​

Bottom navigation bar destinations have fixed positions. They don’t scroll or move horizontally.

Don't: bottom navigation bar destinations don’t scroll

Don't

Bottom navigation bar destinations don’t scroll.

Landscape view ​


Do: on mobile (in landscape mode) or tablet, bottom navigation destinations can retain the same spacing used in portrait

Do

On mobile (in landscape mode) or tablet, bottom navigation destinations can retain the same spacing used in portrait mode, rather than being equally distributed across the bottom app bar.

Do: on mobile (in landscape mode) or tablet, bottom navigation destinations can be positioned horizontally instead

Do

On mobile (in landscape mode) or tablet, bottom navigation destinations can be positioned horizontally instead of stacked. In this case, it’s recommended that destinations are evenly distributed across the entire bar.

States ​

Bottom navigation destinations may be active, inactive, focused or pressed.

Bottom navigation uses opacity and text to show when a destination is active. States are used to show pressed, focused, and unselected states.

Inactive destination states are represented with reduced opacities; active states have full opacity.

Diagram of inactive destinations, an active destination
1. Inactive destinations
2. An active destination

When text labels are not used persistently (at all times), only active destinations are given text labels.

Diagram of inactive destinations without text labels, an active destination with a text label
1. Inactive destinations without text labels
2. An active destination with a text label

States

Visual representations used to communicate the status of a component or interactive element.

Related article

Research ​

Material Design conducted research to understand the usability and design preferences for embedding a floating action button (FAB) in the bottom navigation bar. Preferences and rankings for the different designs were gathered from around 650 participants from the United States, twenty from India and ten from Brazil.

Research findings included:

  • Across all locations, participants liked the bottom navigation bar with an embedded, centered FAB because of the aesthetic and ergonomic benefits.
  • Across all locations, participants appreciated when navigation or common actions were incorporated in an easy-to-access area like the bottom navigation bar.
  • Design preferences for the shape of the bar varied by location. While many participants in the United States and Brazil favored the mini FAB, participants in India preferred an inset or overlapping FAB.

Theming ​

Owl Material Theme ​

This educational app’s bottom navigation bar has been customized using Material Theming. Areas of customization include color and typography.

Owl's customized bottom navigation bar
Owl's customized bottom navigation bar

Owl

Owl is an educational app that provides courses for people who want to explore and learn new skills.

Related article

The color system

Create a color theme that reflects your brand or style

Related article

Applying color to UI

In a UI, color has a variety of roles: from containing meaning, to expressing a look and feel.

Related article

Color ​

Owl's bottom navigation bar uses custom color on three elements: the container, activated items, and inactive items.

Owl Material theme: color
ElementCategoryAttributeValue
ContainerPrimary BlueColor
Opacity
#0336FF
100%
Active icon, active textOn PrimaryColor
Opacity
#FFFFFF
100%
Inactive iconsOn PrimaryColor
Opacity
#FFFFFF
76%

Understanding typography

Typography is critical in establishing hierarchy and expressing brand presence that supports an effective digital experience.

Related article

Typography ​

Owl's bottom navigation bar uses custom typography for text labels.

Owl Material theme: typography
ElementCategoryAttributeValue
Text labelCaptionTypeface
Font
Size
Case
Rubik
Regular
12
All caps

Specs ​

Mobile ​

Portrait ​


561202412121616

Minimum width


min-width: 80dp121256

Maximum width


56max-width: 168dp121281212

Landscape ​


56max-width: 168dp121224161681212
Pager
Previous pageBanners
Next pageButtons

Released under the Apache-2.0

Copyright © 2018-Present Google

https://m2.material.io/components/bottom-navigation

Released under the Apache-2.0

Copyright © 2018-Present Google