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

Applying density ​

Material Design offers guidance on high-density spacing for use cases where increased density improves the user experience.

Usage ​

These guidelines describe how and when to apply density.

Principles ​


Applying density principle: scannable

Scannable

Dense UIs improve the ease of viewing and navigating large amounts of content.

Applying density principle: prioritized

Prioritized

Dense UIs help users focus by reducing the space between actions.

Applying density principle: visible

Visible

Increasing density allows more content and actions to fit on a single screen.

Density guidelines ​

How to apply ​

Material density guidelines are a resource for understanding when and why applying density can improve user experiences. Supported by code, Material Component density can be adjusted cohesively on a scale. Guidance on using the density scale is explained in component density and platform support can be found in implementation.

When to apply ​

How users interact with a component should determine whether or not you increase the density in a UI. When users view and interact with large amounts of information, high density components can improve the experience.

By making more content available on-screen, increasing the density of lists, tables, and long forms makes information easier to scan, view, and compare.

Diagram of increasing the density of a data table, increasing the density of a form
1. Increasing the density of a data table
2. Increasing the density of a form

When not to apply density ​

Tasks and alert-based components should not increase density.

Focused tasks ​

Don't increase the density of components that involve focused tasks, such as interacting with a dropdown menu or picker. Increasing density on components such as date pickers reduces usability by limiting tappable space.

Don't increase the density in components for focused tasks, such as date pickers

Don't

Don't increase the density in components for focused tasks, such as date pickers.

Alerts and messaging ​

Don't increase the density in components that alert the user of changes, such as snackbars or dialogs. Increasing the density of alerts makes them less effective at attracting user attention. In the example of dialogs, readability and prominence of a message are compromised when density increases.

Don't increase the density of alert and message components, such as dialogs

Don't

Don't increase the density of alert and message components, such as dialogs.

Layout ​

Grid and component density ​

Maintain balance between component density and the grid layout.

To create scannable groups of content, use a less-dense grid layout in combination with high-density components. The denser your components become, the larger the margins and gutter widths should be. Combining a dense layout grid with dense components can make differentiating groups of content harder for users.

Do: components with greater density should have lower density margins and gutters

Do

Components with greater density should have lower density margins and gutters.

Don't use a dense layout grid with dense components

Don't

Don't use a dense layout grid with dense components.

Components ​

Applying density to components ​

Component density should not be adjusted in isolation. Instead, apply density consistently to create a cohesive component set. When you adjust one component's density, consider how that change will affect other components in your app.

The tool below illustrates Material Components changing in coordination with three density settings: default, comfortable, and compact.

Interactive demo ​

Different densities across a set of Material Components.

Density scale ​

The density scale allows you to control the density of individual components when needed.

The density scale is numbered, starting at 0 for a component's default density. The scale moves to negative numbers (-1, -2, -3) as space decreases, creating higher density. Each increment represents a decrease in the height of a component by 4dps.

The density scale applied to a button
The density scale applied to a button

Don't select a number from the density scale that breaks your component.

Don't break components by increasing density too much

Don't

Don't break components by increasing density too much. The density of a chip at -4 breaks the component.

Spacing methods ​

When a component's density increases, the padding and alignment remains consistent, but the dimension changes.

Spacing methods: padding

Padding

Do not change the padding of a component when increasing its density. Component padding affects height and reducing padding can affect user interactions negatively.

Spacing methods: dimensions

Dimensions

Change dimensions when increasing the density of components. Component dimensions affect the length and height of the component or element.

Spacing methods: alignment

Alignment

Use a center specification to align elements within component containers. Center aligning elements allows component heights to be adjusted without additional alignment of elements.

Spacing multiple elements ​

When multiple elements are stacked vertically within a component, use 4dp increments to separate them. Center the grouped element within the component container.

Spacing multiple elements: elements separated by 20dp
1. Elements separated by 20dp.
2. Element group centered within the component container vertically.

Accessibility ​

Touch targets ​

Touch targets apply to any device that receives both touch and non-touch input. To balance information density and usability, the touch target for default density components should be at least 48 x 48 dp, with at least 8dp of space between each target. Note: on iOS, 44 x 44 dp is the recommended touch target.

Touch target minimum of 48 x 48 dp
Touch target minimum of 48 x 48 dp
1. 40dp element, 48dp touch target
2. 24dp element, 48dp touch target
3. 36dp element, 48dp touch target

48 x 48 dp minimum touch targets should be the default experience in your product, with the exception of iOS products. Users must opt in to high density component experiences because higher density components do not meet accessibility requirements.

A pattern for users to opt in to a denser component experience
A pattern for users to opt in to a denser component experience

Typography ​

Line height ​

Line height is the space between lines of text. Line height can be used as a way to create density in typographic layouts.

Diagram of larger line height: 44dp, 40dp, 44dp, 32dp, smaller line height: 36dp, 32dp, 40dp, 20dp
1. Larger line height: 44dp, 40dp, 44dp, 32dp
2. Smaller line height: 36dp, 32dp, 40dp, 20dp

Implementation ​

Density support for each platform is indicated below.

PlatformStatus
AndroidPlanned
iOSPlanned
WebAvailable
FlutterPlanned
Pager
Previous pageComponent behavior
Next pageUnderstanding navigation

Released under the Apache-2.0

Copyright © 2018-Present Google

https://m2.material.io/design/layout/applying-density.html

Released under the Apache-2.0

Copyright © 2018-Present Google