Snackbar: Guidelines
Snackbars show short updates about app processes at the bottom of the screen

Usage
Snackbars inform users of a process that an app has performed or will perform. They appear temporarily, towards the bottom of the screen.
They shouldn't interrupt the user experience. People can browse the page content without being required to interact with the snackbar.
Frequency
Only one snackbar may be displayed at a time.
Actions
A snackbar can contain a single action. "Dismiss" or "cancel" actions are optional.

Similar components
DialogsDialogs provide important prompts in a user flow.More on dialogs are also designed to show important messages.
Choose the right component based on the importance of the message. This component messaging strategy can help avoid overusing snackbars.

When to use snackbars
Snackbars communicate messages that are minimally interruptive and don’t require user action.
| Component | Priority | User action |
|---|---|---|
| Snackbar | Low priority | Optional: Snackbars disappear automatically |
| Dialog | High priority | Required: Dialogs block app usage until the user takes a dialog action or exits the dialog (if available) |
Accessibility requirements for web
On web, auto-dismissing snackbars are inaccessible for people with low vision or who require additional time to perceive information. This can be solved in 2 ways:
1. Add inline feedback
Information in auto-dismissing snackbars must also be communicated using another accessible method inline or near the action that triggered the snackbar.
For example, update the label on a "Save" buttonButtons let people take action and make choices with one tap.More on buttons to “Saved”, and trigger an auto-dismissing snackbar that communicates the same message.
2. Make the snackbar actionable
Alternatively, add actions to the snackbar so it doesn't dismiss until acted on.

Anatomy

- Container
- Supporting text
- Action (optional)
- Close button (optional)
Text label
Snackbars contain a text label that directly relates to the process being performed. In compact breakpointsWindow widths smaller than 600dp, such as a phone in portrait orientation.More on compact breakpoints, the text label can contain up to two lines of text.





Container
Snackbars are displayed in rectangular containers with a grey background. Containers should be completely opaque, so that text labels remain legible.






Action
Snackbars can display a single text button that lets users take action on a process performed by the app. Snackbars shouldn’t be the only way to access a core use case, to make an app usable.




Placement
At the bottom of a UI
Snackbars should be placed at the bottom of a UI, in front of the main content. In some cases, snackbars can be nudged upwards to avoid overlapping with other UI elements near the bottom, such as FABsFloating action buttons (FABs) help people take primary actions.More on FABs or docked toolbarsDocked toolbars (formerly bottom app bars) are placed at the bottom of the page..
Avoid placing a snackbar in front of frequently used touch targets or navigation.


To ensure accessibility for keyboard users on the web, avoid positioning the snackbar in a way that completely obscures actionable elements. Blocking elements makes it difficult to know what is being focused and selected.


Snackbars can span the entire width of the screen only when a UI does not use persistent navigation components like app bars or navigation barsNavigation bars let people switch between UI views on smaller devices.More on navigation bars.
Snackbars that span the entire width of a UI can push up FABsFloating action buttons (FABs) help people take primary actions.More on FABs when they appear.

Snackbars and floating action buttons (FABs)
Snackbars should appear above FABsFloating action buttons (FABs) help people take primary actions.More on FABs.



Responsive layout
Compact breakpoint
In compact breakpointsWindow widths smaller than 600dp, such as a phone in portrait orientation.More on compact breakpoints, snackbars should expand vertically from 48dp to 64dp to accommodate one or two lines of text, while maintaining a fixed distance from the leading, trailing, and bottom edges of the screen.

Medium & expanded breakpoints
On mediumWindow widths from 600dp to 839dp, such as a tablet or foldable in portrait orientation.More on medium breakpoints and expanded breakpointsWindow widths 840dp to 1199dp, such as a tablet or foldable in landscape orientation, or desktop.More on expanded breakpoints, like tablet and desktop, snackbars should scale horizontally to accommodate longer text strings, keeping in mind that the ideal line length for text is typically between 40-60 characters.
Snackbars use a flexible distance from the trailing edge of the screen. Whenever possible, snackbars on medium and large displays should aim for a single line of text with an optional buttonButtons let people take action and make choices with one tap.More on buttons.

In wider layoutsLayout is the visual arrangement of elements on the screen.More on layout, snackbars can be left-aligned or center-aligned if they are consistently placed on the same spot at the bottom of the screen.




Behavior
Appearing and disappearing
Snackbars appear without warning, but they don’t block users from interacting with page content.
Snackbars without actions can auto-dismiss after 4–10 seconds, depending on platform. Avoid using auto-dismissing snackbars on web unless there's also inline feedback.
Snackbars with actions should remain on the screen until the user takes an action on the snackbar, or dismisses it.
Consecutive snackbars
Consecutive snackbars must appear one at a time.
Snackbars without actions appear and disappear automatically, while those with actions remain on screen until dismissed. However, a snackbar with updated information can immediately replace an outdated snackbar.