Toast

Toasts display brief notifications that appear towards the bottom of the screen. They provide feedback or information to users without interrupting their current workflow.

When to use

Low priority update

Toasts are good for low priority updates regarding a task the user has taken or is being taken

Low priority update

Toasts are good for low priority updates regarding a task the user has taken or is being taken

Low priority update

Toasts are good for low priority updates regarding a task the user has taken or is being taken

Minimal interruption

Use toasts to give updates with little interruption to the user’s workflow such as: successful updates, errors messages, and confirmation like saving or deleting items

Minimal interruption

Use toasts to give updates with little interruption to the user’s workflow such as: successful updates, errors messages, and confirmation like saving or deleting items

Minimal interruption

Use toasts to give updates with little interruption to the user’s workflow such as: successful updates, errors messages, and confirmation like saving or deleting items

When to avoid

Urgent / critical action

Avoid using toasts for critical alerts that require immediate attention or user action, as they can be easily missed or dismissed without notice. Instead, use banners

Urgent / critical action

Avoid using toasts for critical alerts that require immediate attention or user action, as they can be easily missed or dismissed without notice. Instead, use banners

Urgent / critical action

Avoid using toasts for critical alerts that require immediate attention or user action, as they can be easily missed or dismissed without notice. Instead, use banners

Long-term information

Don’t display persistent information that users may need to reference later. Toasts are best suited for transient messages that can disappear after a short period

Long-term information

Don’t display persistent information that users may need to reference later. Toasts are best suited for transient messages that can disappear after a short period

Long-term information

Don’t display persistent information that users may need to reference later. Toasts are best suited for transient messages that can disappear after a short period

Specifications

Message

With Action

Asset A

Without Action

Asset A

With Action

Asset A

Without Action

Asset A

With Action

Asset A

Without Action

Asset A

With Action

Asset A

Without Action

Asset A

Types

Information

Asset A

Success

Asset A

Error

Asset A

Information

Asset A

Success

Asset A

Error

Asset A

Information

Asset A

Success

Asset A

Error

Asset A

Anatomy

Asset A

1

Icon

Provides immediate visual context for the message type, such as success, error, or warning.

2

Message

Should be a brief, clear, and concise statement confirming the result of the user's recent action.

3

Action button

Optional and can be included to offer the user a single, contextual follow-up, such as "Undo" or "View details."

4

Close icon

Allows the user to manually dismiss the toast, overriding the default auto-dismiss timer.

Value

Toast

Toast

© 2025 Border LLC. All rights reserved.

A proud product of the Border UX team.

© 2025 Border LLC. All rights reserved.

A proud product of the Border UX team.

© 2025 Border LLC. All rights reserved.

A proud product of the Border UX team.

© 2025 Border LLC. All rights reserved.

A proud product of the Border UX team.

© 2025 Border LLC. All rights reserved.

A proud product of the Border UX team.