---
title: "Message"
slug: message
category: component
type: documentation
version: 20.0.0
tokens: 2346
source: https://ovh.github.io/design-system/v20.0.0/llms/react-components-message--documentation.txt
---
# Message
_**Message** component helps to communicate with users providing feedback or information._
## Overview
**Message** component communicates information to the user.
It grabs the user's attention in a prominent way.
| | |
|---|---|
| Name | Message |
| Also known as | Notifier, Notification, Banner, Alert, Feedback |
| Design | https://www.figma.com/design/9jDDTcR4a9jPRFcdjawAlf/ODS---UI-Kit?node-id=44-8300 |
| Source | https://github.com/ovh/design-system/tree/master/packages/ods-react/src/components/message |
## Usage
**Messages** are used as notification status.
There are four different subtypes of standard **Messages**, in order of priority:
- **Information**: Provides info to users in context. Shouldn't be overused to replace regular content.
- **Success**: Reserved to provide to a success message. They are displayed as a snackbar.
- **Warning**: Reserved for **Messages** that need the user attention and acknowledgment but might not cause errors.
- **Critical**: Reserved for errors, malfunctions, as well as critical issues. Inform the user that a problem requires immediate intervention or correction before the process continues.
### Message vs Toast
**Message**
- Persistent or semi-persistent information banner.
- Usually appears inline or at the top of a page as part of the content flow.
- Designed for status communication (success, warning, critical error, info) that’s tied to a specific screen or context.
- Remains visible until dismissed or until the state changes.
**Toast**
- Ephemeral notification that appears for a short time (usually overlay in a corner of the viewport)
- Designed for lightweight, transient feedback ("Action succeeded", "File uploaded"), except for toast with actions.
- Auto-dismisses after a few seconds.
### Dos & Don'ts
**Do**
- Write Message in a clear, concise, and affirmative tone that aligns with the user's task
- Place Message in a visible and relevant area of the page, ideally close to the triggering element if any or top of the section
- Use the correct status (e.g., information, success, warning, critical) and emphasis to match the context and urgency
- Use non-dismissible Message for critical warnings or errors that require immediate resolution
- Allow content selection (e.g., to copy error messages)
**Don't**
- Don't use Message to highlight static or decorative content, prefer components like Card for that
- Don't write overly long or complex Message that could overwhelm or confuse users
- Don't rely solely on color to convey meaning, always keep the Icon for clarity
- Don't use vague or generic text, always provide helpful context or guidance
- Don't overload the interface with multiple simultaneous Messages unless absolutely necessary
### Best Practices in Context
1. **Message**
2. **Icon**
3. **Close button** - optional
4. **Content**
## Placement
**Messages** show up during a task to notify users of the status of an action. In every page, it is possible to display one or more **Messages** to inform the user.
They are positioned near their related items or right after the header and before the page title and page content.
## Behavior
Based on its informational manner, the component default behavior is being read-only. You can only select its content if needed.
When a **Message** is dismissible, a click on the `xmark` icon button will dismiss the **Message**.
## Variation
### Status
- **Accent**: highlighting content tied to the brand, such as a new feature announcement, without conveying any particular status.
- **Neutral**: conveying general content without any particular status or urgency.
- **Information** _(default)_: informing users of specific content, providing global feedback to the user.
- **Success**: confirming that an action has been completed successfully, providing positive feedback to the user.
- **Warning**: alerting users to potential issues or cautionary information, prompting them to take preventive actions.
- **Critical**: highlighting severe and potentially catastrophic issues that demand urgent and decisive action to prevent significant negative consequences.
### Emphasis
- **High**: tinted background with a light colored border, for important information that must be seen by the user.
- **Medium** _(default)_: neutral background with a colored border, for information that should be noticed without competing with the content around it.
- **Low**: colored text and icon only, without background nor border, for non-urgent information in a subtle and less prominent manner.
The close button looks the same in every emphasis.
The blue-jeans theme keeps the v19 tinted look in high, without border.
```tsx
<>