Home / Primitives / Toast

Toast

Brief, auto-dismissing confirmation of a background action. Always non-blocking; never asks for input. Use it to confirm "we heard you" — not to make the operator decide.

Stable .toast 4 tones · 5 s default

Default

Dark surface, white text, 380 px max. Anchors bottom-right with a 16 px gutter.

Draft saved
Recovered automatically — keep editing.
Default neutral toast .toast

Tones

Four canonical tones. Neutral is by far the most common; danger reserved for actual failure.

Receipt R-19281 printed
Default
.toast
Shift S-2841 closed
Reconciled against $1,247.40 in cash.
Success
.toast.success
Working offline
4 pours queued · syncs on reconnect.
Warn
tone-warn fill
Couldn't reach NMB Bank
Reconciliation paused. Retrying in 30 s.
Danger
.toast.danger

With action

A single action — Undo, View, Retry. Never more than one. If you need two actions, use a confirmation modal instead.

3 receipts archived
They can be restored from the archive.
Toast with single Undo

Stacking

Up to three toasts stack vertically with 8 px gap. The oldest dismisses first.

Pour P-2840 logged
Tariro M. signed in to Till 02
Sync failed · 2 records
3-toast stack · bottom-right

Parts

PropertyValueNotes
max width380 pxLong titles wrap
padding12 px 14 px
icon18 × 18 pxAlways present
positionfixed · bottom-right16 px gutter
duration5 s default · 8 s with actionSticky on hover
stack limit3Older slides out

Do & don't

Do

Use toast for fire-and-forget confirmations — "Saved", "Printed", "Sent". The action already happened.

Don't

Ask the operator to decide inside a toast — "Discard or save?" That's a confirm modal.

Do

Pair destructive confirmations with Undo. "3 receipts archived. [Undo]"

Don't

Use toast for error messages the operator must act on. Surface a persistent inline alert instead.

Related

For persistent in-page notices, see Alert. For the bell-icon inbox, see Notifications.