Skip to content

Design

Notifications tell users about system status, the result of an action, or a change that needs their attention. The same component serves four uses, which share a visual language and differ in persistence, placement and how much they interrupt.

Title Description Link

Body text that adds context.

Link
  1. Notification
  2. Icon
  3. Title
  4. Description
  5. Inline link
  6. Close
  7. Body
  8. Actions
  • Toast: a quick confirmation of low importance, such as “Changes saved”. The user doesn’t need to do anything.
  • Inline: feedback tied to a specific element, such as a form validation error or a warning inside a card.
  • Standalone: a system message that affects the whole page or session, such as being offline or scheduled maintenance.
  • Actionable: the user must decide or act to continue, such as “Your session expires in 2 min — Renew session”.

Avoid a Notification when:

  • The user needs to reference the content later — use a page or an email.
  • The update is a micro-action that needs no acknowledgement. Too many notifications teach users to ignore them.

Type

Error, Info, Warning, Success and Neutral. Type sets the fill, the border and the bar along the leading edge. Use one colour and icon per severity across the whole product.

Optional parts

Every part can be left out: icon, title, description, inline link, body, standalone link and tertiary button. Remove both the link and the button to drop the whole actions row.

Desktop

Keep standalone notifications in a predictable zone, such as the top of the page, and inline notifications as close as possible to the element they refer to.

Tablet

Same placement as desktop. Leave room for the 40 px close button so it stays comfortable to tap.

Mobile

The title, description and inline link wrap onto several lines, so keep them short. A toast should still fit on one or two lines.

Keep each notification to a single idea, and let users act on it or dismiss it at their own pace.

Do

  • Group or queue several notifications rather than showing them all at once.
  • Give toasts enough reading time: 3–5 s for a simple success, 6–10 s for informational or reversible messages, and pause on hover and focus.
  • Remove an inline notification automatically once the issue is resolved.
  • Let non-critical standalone notifications be dismissed, and don’t bring them back unnecessarily.
  • Make clear what happens if the user doesn’t act, and limit actions to one primary plus one secondary.

Don't

  • Don’t rely on colour alone to communicate severity. Pair it with an icon or text.
  • Don’t put critical or irreversible information only in a toast, or use one for an error that needs action.
  • Don’t stack more than 2–3 toasts at once.
  • Don’t use an inline notification for a message about the whole page, or leave it behind when its field changes.
  • Don’t block the main content with a standalone notification unless strictly necessary.
  • Don’t hide the way out of an optional action, or turn a notification into a multi-step flow.
  • Title: what happened, in 3–8 words of simple present or past tense.
  • Body: optional. Why it happened or what the user can do, in 1–2 sentences.
  • Action: a verb and a clear object, such as “Retry submission” rather than “Retry” or “OK”.
  • Length: a toast is one line of about 80 characters at most; inline is 1–2 lines; standalone is a title and 3–4 sentences; actionable is a title, a short body and its actions.
  • Tone: direct and human, without jargon. Never blame the user: “That email format isn’t valid”, not “You entered the data wrong”.
  • Errors: be specific about the cause when known, and say whether and how the user can recover.
  • Style: lead with the most important information and use active verbs: “We couldn’t process your payment”. Avoid all caps and exclamation marks.