Toast: Small Temporary Messages That Confirm Actions Without Blocking Users
A toast is a brief message that confirms something and then leaves on its own. Learn when to use one, how to set its rules, and how to keep it usable for everyone.
In short
A toast is a brief message that confirms something and then leaves on its own, with rules for when to use it and how to keep it usable for everyone.
14 min readFree
Start Here: What You Will Learn
This lesson teaches the toast, a small part that appears in many design systems. A design system is a shared set of reusable parts and rules that a product team uses on every screen. A toast is one of those parts, and it has its own rules for look, placement, timing, and behavior.
By the end, you should be able to decide whether a message should be a toast, describe the rules a toast needs, and check that it works for people who use screen readers and keyboards. You will not write code. You will make design decisions about words, placement, time, and what the user can do.
Key words
- Toast
- A small message that appears over the screen to confirm something, then leaves on its own.
- Design system
- A shared set of reusable parts and rules that keeps a product looking and behaving the same way.
- Component
- One reusable piece of a screen, such as a button or a toast.
- Non-blocking
- Does not stop the user. The user can keep working while the message is visible.
- Auto-dismiss
- The message goes away by itself after a set time.
- Variant
- A version of the same part that signals a different meaning, such as success or error.
- Screen reader
- Software that reads the text on a screen out loud for people who cannot see it well.
- Live region
- A container on a page that a screen reader watches, so it reads any new text placed inside.
- Focus
- The part of the screen that receives keyboard input at that moment.
- Snackbar
- A similar pattern. Google's Material Design uses this name for brief feedback at the bottom of the screen, often with one action.
What is a toast?
A toast is a brief message that appears over the interface, usually near an edge of the screen. It says that something happened, such as a file being saved or a link being copied. After a short time it leaves, and the user does not have to click it away.
The key idea is passive confirmation. The user sees the message, takes it in, and carries on. A toast should never be the reason a user stops what they are doing.
Names differ between teams. Some say toast, others say snackbar. Material Design uses snackbar for brief feedback about an operation at the bottom of the screen. So when you read another team's rules, check what the pattern does, not only what it is called.
When should you use a toast?
A toast fits a message that is helpful but not critical. Ask whether the user needs this information to keep going. If they do, a toast is the wrong pattern. If they do not, a toast may be a good fit.
Confirm a finished action
Use a toast after the user saves a setting, copies a link, or sends a form. The text confirms what already happened, such as 'Settings saved' or 'Link copied'.
Report a background event
A toast can say that a slow job has started or finished, such as an export that will be ready later. Keep the message short, and keep the real status on the page as well.
Offer a quick way back
When an action can be reversed, the toast can carry an Undo button. The user fixes a mistake in one tap. Material Design allows a snackbar to contain a text action.
A toast is always an extra. It should reinforce a result the page already shows, so someone who misses it can still see what happened.
Tip
Ask one question before you choose a toast: if this message vanished and the user never saw it, would anything go wrong? If yes, do not use a toast.
When should you not use a toast?
Some messages must stay visible until the user deals with them. A banner is a message bar that sits at the top of a page until it is resolved or closed. A dialog is a box that takes over the screen and waits for an answer. Other lessons in this course cover these in depth.
Errors that need action
A declined card, a wrong password, or an empty required field asks the user to do something. The message should stay on the page near the problem until it is fixed. Several guides say toasts are a poor choice for errors and recommend a banner or an inline message.
Critical warnings
Messages about lost data, a session about to end, or a safety risk must not fade before the user reads them. Use a banner, an inline message, or a dialog that waits.
Long or complex information
A toast should carry a few words, not a paragraph. If the user needs an explanation, put it on the page or in a dialog.
Tip
Do not show a toast on page load to repeat what the page already shows. Show one when something changes because of the user's action or a background event.
Quick check
A shopper submits a payment form and the card is declined. A teammate suggests a toast that disappears after 4 seconds saying 'Payment failed'. What is the best call?
What are the toast variants?
A variant is a version of one part that signals a different meaning. Your design system should name each variant and say when to use it.
Success
Confirms that something worked, such as 'Saved'. Teams often use a positive color such as green. It can close on its own after a few seconds.
Info
Shares a neutral fact, such as 'Export started. We will email you.' Use a calm color and plain wording. The same fact should also be findable on the page.
Warning
Points to a risk that may need attention soon. It should stay a little longer than a success message.
Error
Reports a small, non-critical problem that can be explained in a few words, such as a dropped internet connection. Errors that need a fix belong on the page, and critical errors should never close on their own.
Tip
Never rely on color alone. Pair each variant with a clear word, and with an icon where your system allows icons.
What is the anatomy of a toast?
Anatomy means the named parts of a component. Naming the parts helps a team build the same thing every time, and helps a reviewer check a screen against the rules.
Message
One short line that says what happened, in plain words. Some teams add a short title for the category and a short detail for the specifics.
Optional action
One text button, such as Undo or View. Material Design allows only one action per snackbar and says the action should not be Dismiss or Cancel. Use a close control for dismissing.
Close control
A small x button that lets the user close the toast early. Several guides say to include one even when the toast times out, because some people read slowly or need more time.
Container and icon
The box that holds the text. Icons are optional, and guides disagree. Material Design says snackbars cannot contain icons. Decide once for your system and write it down.
Where a Toast Sits
Placement should be the same every time, so users learn where to look. Material Design places snackbars at the bottom of the screen, in front of the main content, and says they appear above most elements and sit at the same elevation as a floating action button.
Avoid covering what the user needs. A bottom-right toast can cover a chat input or a floating Save button. Top-right placement needs extra care. Use top-right only when your platform and testing clearly support it.
Tip
Pick one home for toasts, such as bottom center, write it into your placement rules, and check that the toast does not cover the main button on your busiest screen.
Behavior Rules
Behavior rules decide what a toast does over time and what happens when several toasts meet. Set them once in the design system, then reuse them everywhere.
Timing and Auto-Dismiss
Timing is how long a toast stays before it closes on its own. A short message needs less time. A message with an action needs more, because the user must read it and reach the button. Material Design says snackbars can close after a timeout or remain until the user acts.
Sources do not agree on one number. Some accessibility guides suggest at least 10 seconds for reading. Pick a range, test it with real people, and write the reason down.
Tip
Pause the timer while the user hovers over the toast or has keyboard focus on it, so the message does not vanish mid-read.
Stacking and Queueing
Stacking means showing several toasts at once in a pile. Queueing means showing them one at a time, in order. Material Design says consecutive snackbars must appear one at a time and should not be stacked on top of one another.
When several events fire together, queue the toasts or combine them. Five files saved can become one message that says five files saved. Too many messages teach users to ignore them, so keep the number low.
Never Hiding Important Content
A toast must never be the only place where important information lives. If a message matters later, show it on the page too.
Check the screen under the toast. A toast that covers a field, a button, or a list item blocks the user from what is underneath.
Worked Example: Gmail's Archive Toast
This example follows an archive toast that confirms a conversation was archived and offers an Undo action. Walk through the rules from this lesson, one at a time.
- 1
Decide the pattern
Archiving is finished, low stakes, and reversible. The user does not need to act to finish the job, so a toast fits, not a dialog.
- 2
Write the message
'Conversation archived' is short and names the result, not the system's internal steps.
- 3
Add one action
The Undo link is the single action. It reverses the archive. It is not a Dismiss or Cancel button.
- 4
Place it consistently
The toast sits at the bottom left, away from the message list the user is reading, so it does not hide the list or the main toolbar.
- 5
Set the timer
The toast fades after several seconds, longer than a plain confirmation, because the user may want to press Undo. The team should set this time as a rule, not guess it.
- 6
Keep Undo reachable
A keyboard user should be able to reach Undo before the toast fades. Hovering over the toast should pause the timer, so a reader does not lose the chance to act.
- 7
Announce the message
The text should sit in a live region that already exists on the page. A screen reader then reads 'Conversation archived' without moving focus away from the list.
Tip
Test your toast with the keyboard only. Tab to the action before the toast fades. If you cannot reach it in time, the timer is too short or does not pause.
Making Toasts Accessible
A toast appears without anyone clicking it. A sighted user may notice it, but a screen reader user will hear nothing unless the toast is built to be announced. Accessibility is part of the toast's rules, not an add-on. ARIA is a set of labels that tells assistive technology what a part is. Assistive technology means tools, such as screen readers, that help people use a page.
Announcing to Screen Readers
A toast is announced correctly when its container is a live region that existed before the message appeared. Place one empty live region on the page when it loads, then put each toast's text into it. If the container and the message appear together, many screen readers never speak the message.
role status (polite)
Use it for confirmations and results, such as Saved or Link copied. A polite region waits until the screen reader finishes what it is saying, so it never interrupts.
role alert (assertive)
Use it only for errors and urgent, time-sensitive warnings. An assertive region interrupts current speech, so standard toasts should never use it.
Tip
In your browser's developer tools, check that the live region exists on page load and carries its role before any toast text is added.
Time to Read, Pause, and Close
A toast that fades on a timer limits how long people can read it. Under accessibility rules, people need enough time to read and act on content. A message that must be read and acted on should not sit on a timer. It should stay in a banner or wait in a dialog.
Give every auto-dismissing toast a close control, and let the timer pause on hover or keyboard focus. These choices let slow readers and people with cognitive differences act on their own schedule.
Keyboard Reach and Focus
A keyboard user must be able to reach the Undo link and the close button. Both should be real buttons or links, so the keyboard reaches them in normal order. A toast should never take focus when it appears. If focus jumps into the toast, the user loses their place in the task.
Make sure a fixed toast does not cover the control that holds keyboard focus, or the user cannot see what they are operating.
Do Not Rely on Color Alone
A success toast and an error toast must differ in more than color. Use a clear word, such as 'Saved' or 'Payment failed', so the meaning survives for people who cannot see color. The text should also have enough contrast against its background. The accessibility guidance used for this lesson asks for at least 4.5 to 1 for normal text.
Common Mistakes
Using a toast for a decision
A question such as 'Delete this project?' needs confirmation before the action. A toast can report the result afterward, but it should not ask the user to decide.
Timer set too short
A message that vanishes too fast is missed. Users cannot act on it, and may not know something went wrong.
Too many toasts
Flooding the screen teaches users to stop noticing toasts, so the one that matters gets ignored. Keep toasts for key moments only.
Check Your Understanding
Try this scenario. It uses the timing and accessibility rules from this lesson.
Quick check
A web app finishes a file upload. The designer shows a toast reading 'Upload complete' that closes after 4 seconds and has no close button. A keyboard user is still tabbing through the page when it fades. Which change does the most good?
Key Takeaways
A toast is a short, non-blocking message for low-stakes feedback. Use it to confirm a finished action or share a brief update. Choose a different pattern when the user must read, decide, or fix something. Give every toast a clear variant, a short message, an optional single action, a consistent place, a fair timer, a close control, and a queueing rule. Finally, make it reachable: announce it through a live region, let people pause it, keep focus off it, and never use color alone.
Sources
- Snackbar, Material Design 3 guidelines (Google)
- Snackbars and toasts, Material Design 1 components (Google)
- Accessible Notifications and Toasts: A Complete Guide (accessibility.build)
- WCAG 4.1.3 Status Messages, ARIA live regions guide (accessibility.build)
- Toast Notification Accessibility Guide (Design System Problems)
- Accessible Toast and Status Messages example (a11yman)
- Toast UI Design: Best practices, variants and examples (Mobbin)
- Toast notification glossary entry (Subux)
- What Is a Toast Message? Toasts vs. Snackbars (Courier)
- Toast Notification UX: When to Use a Toast and When to Skip It (ERAG)
- Do you know when and where to use toast notifications? (SSW)
- Toast UX: Dismissal, Stacking and Accessibility Guide (BuiltUX)
- Toast Notifications: Anti-Patterns to Avoid (BuiltUX)
- The UX of notification toasts (Benoit Rajalu)
- What Is a Toast Notification? Examples and Best Practices (MagicBell)
- What Is a Toast Notification and How to Use It Right (Dom Studio)
- Mastering Toast Notifications: Best Practices, Accessibility, and Modern Implementation (HowInsights)
- Material Design Snackbar in Android: How and When to Use (Suleiman)
Last updated on 17 November 2026
Related lessons
Learn with me
Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.