Alerts and Toasts

Alerts and toasts are the two shapes a short status message takes: an alert holds a place in the layout and waits to be dealt with, while a toast arrives over the page and leaves on its own. The five blocks in this family cover both ends, from a one-line alert that dismisses itself, through one carrying a primary and a secondary action, to one that keeps a longer notice folded behind a chevron, and toasts in a compact label row and a richer attachment form.

The drawing is the easy half. The clock is the hard one, because an auto-dismissing message is a bet on how fast somebody reads, and you lose that bet for anyone who looked away. Pausing the countdown on hover and on focus buys the bet back, and stopping it while an expanded message is open does the same thing. Anything carrying an action should not dismiss itself at all: a person reaching for Undo and finding it gone learns not to trust the pattern.

18 blocks

Simple Alert

Confirmations, quick status, anything that should self-dismiss

Simple Alert, ring

Quiet confirmations where the control that closes it should say when

Simple Alert, wash

Status notes that should read as part of the page, not float over it

Alert with Actions

Update prompts, confirmations that need a choice, background job results

Alert with Actions, ring

Alerts whose actions sit beside the text on wide screens

Alert with Actions, wash

A job the alert itself carries from start to finish

Expandable Alert

Longer notices that default to a preview, with an option to keep reading

Expandable Alert, ring

Notices with structured detail

Expandable Alert, wash

Notices that read like a receipt

Toast

Transient system messages, background status, compact banners

Toast, island

Apps that want one calm message at a time

Toast, lifecycle

Uploads, exports and syncs that report once

Attachment Toast

File/attachment notices, richer background-job results

Attachment Toast, upload tray

Uploading several files at once

Attachment Toast, peek

Checking an export without leaving the toast

Insight banner

Telling someone something the data noticed, at three volumes

Insight banner, volume

One insight that can be played louder or quieter

Insight banner, queue

Dashboards that notice several things at once

01

Using Alerts and Toasts

Reach for it when

  • A background job finished while the person was somewhere else in the app
  • A submission failed for a reason no single field can explain
  • A change applied and you want to offer a few seconds of Undo
  • System status shifted: a connection dropped, a sync resumed

Reach for something else when

  • The person must answer before continuing: use a modal, which blocks until they do
  • The error belongs to one field: put it under that field, where the eye already is
  • The condition persists, like read-only mode. That is a banner in the layout, not a message that leaves
02

Where it shows up

01

Background job results

A report finishes generating while the person is on another screen. A toast announces it with a link to the file, and disappears if they do not want it, without stealing the click they were about to make.

02

Undo after deleting

A row is removed from a list and a message offers to put it back. Countdown and action are in tension here, so the message holds its place in the layout instead of timing out on someone mid-reach.

03

Form submission errors

A server rejects a submission over something no field owns: a duplicate account, an expired session, a payment declined upstream. An alert above the form carries the explanation and, where one exists, the action that resolves it.

04

Connection status

A sync drops and the app falls back to read-only. That condition persists rather than passing, so it belongs in an alert that stays until the connection returns, not a toast that leaves while the problem does not.

03

Questions

What is the difference between an alert and a toast?

An alert occupies space in the page layout and stays there until it is dismissed or the condition clears, so it can be read at leisure and can carry actions. A toast is layered over the interface, usually near a corner, and removes itself after a short time. Use an alert when the message must be read, and a toast when it is a courtesy.

How long should a toast stay on screen before it disappears?

All blocks
The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.