Toast and Snackbar
Toasts and snackbars are brief, non-modal status messages; snackbars may also offer one concise action such as Undo.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/toast-and-snackbar/
01What it means
A toast is a transient notification that confirms or reports a result without taking focus. A snackbar is a closely related pattern that commonly permits one contextual action. Terminology varies across design systems, so teams should define behavior—urgency, duration, actions, queueing, and persistence—rather than rely on the label alone.[1][2]
02Why it matters
Transient feedback can confirm low-risk actions without interrupting work. If it disappears too quickly, stacks excessively, or carries critical information, users may miss the outcome or lose their only recovery path.
03When to use it
Use a toast or snackbar for brief, low-urgency feedback when the changed state is otherwise visible or recoverable. Use persistent inline status, a banner, or a dialog for critical failures, required decisions, lengthy explanations, or information users must revisit.
04How it works
- Classify the message by urgency, consequence, and whether it requires an action.
- Write concise status text and include at most one immediate contextual action.
- Place the message consistently without covering controls or moving keyboard focus.
- Announce it with an appropriate live-region priority and keep actionable content available long enough.
- Limit queueing, preserve important status elsewhere, and test repeated events and zoom.
05A practical example
After a user archives a conversation, a snackbar says “Conversation archived” and offers Undo. The list updates immediately, the message is announced without stealing focus, and the archived item remains recoverable from a persistent archive view after the snackbar disappears.
06Where it breaks
Timed messages are inherently easy to miss, especially during screen magnification, distraction, or assistive-technology output. An Undo action that vanishes may not provide sufficient recovery, and multiple simultaneous notices can become noise.
Common mistakes
- Using transient feedback for critical errors or irreversible outcomes.
- Moving focus to every toast or announcing routine updates assertively.
- Stacking many messages over important controls.
- Making a disappearing snackbar the only way to undo an action.