Banners: The Prominent Top-of-Page Messages That Stay Until Someone Acts
Learn what a banner is in a design system, the types it comes in, its parts, and the rules that keep it useful instead of annoying.
In short
A banner is a prominent top-of-page message in a design system that stays until someone acts, and it needs clear rules so it stays useful instead of annoying.
14 min readFree
What you will learn
Every product talks to its users. Some messages can wait. Others must stay in view until someone deals with them. A banner is the design system part built for that second job. In this lesson you will learn what a banner is, the types it comes in, the parts it is made from, and the rules that keep it helpful.
By the end, you should be able to pick the right banner type for a message, name each part, and explain why a team should show only one banner at a time. Read the key words first, because the rest of the lesson uses them.
Key words
- Design system
- A shared set of parts, rules, and examples that a product team reuses so that its screens look and behave alike.
- Component
- One reusable part of a design system, such as a button or a banner. It is built once and used many times.
- Banner
- A wide strip at the top of a page or section that shows a prominent message. It stays visible until the issue is resolved or the person closes it.
- Persistent
- Stays on screen until something changes or someone acts. It does not fade away by itself.
- Dismiss
- Close or hide a message so that it leaves the screen.
- Anatomy
- The list of parts that a component is made of, and what each part does.
- Token
- A named design choice, such as a color called danger, that teams use in place of a raw color value. Tokens are covered in their own lesson.
- Contrast
- How clearly text stands out from the background behind it. Low contrast makes text hard to read.
- Toast
- A short message that slides in. When it has no action button, it shows for a few seconds and then fades away on its own.
- Modal
- A window that sits on top of the page and blocks the rest of the screen until the person responds.
- Inline message
- A message that sits next to the part of the page it describes, such as a form field.
- Screen reader
- Software that reads the screen out loud for people who cannot see it well.
What are the parts of a banner?
The anatomy of a banner is a short list of parts. Not every system uses every part, but these are the names you will see most often. Each part has a job, so do not add one unless it helps the message.
Container
The outer box that holds everything else. It is usually the full width of the layout, and its background color often shows the banner type.
Icon
A small symbol that signals the type, such as an exclamation mark for an error. Atlassian allows only its error and warning icons on banners. When used, the icon needs a text label that a screen reader can speak.
Title
An optional short heading, such as 'Your payment failed.' Some systems include it and Atlassian's banner does not. The title should name the problem in a few words.
Message
The words that explain what happened, how serious it is, and what the person can do. Atlassian asks that the message include the problem and any action to fix it.
Action
An optional link or button that leads to a fix or next step. Orange allows up to two text buttons. NewsKit says a banner should have no more than one action.
Dismiss control
A close button, often an X, that lets the person hide the banner. Baymard lists it as optional. Whether your banner gets one depends on the rules you set, as explained below.
Systems also describe variants. A variant is a version of the same component with a different setting, such as a banner with an icon and one action, or one with only a message. Documenting variants stops teams from inventing a new banner each time they need a small change.
Placement and width
Placement means where the banner sits. Most systems put banners at the top of the page, below the main header and above the content. Material places a banner below the top app bar. Orange places it directly under the global header. Atlassian says banners push the content below them down when they appear. Nord advises putting the banner at the top of the section it applies to.
Width is usually full width, which makes the banner read as a system message rather than as page content. Text can wrap onto more lines, so the banner grows taller on a narrow phone. Base recommends keeping the content to about two lines on most screens.
Should a banner be persistent or dismissible?
Persistent or dismissible is a separate choice from placement. A persistent banner stays until the cause is resolved. A dismissible banner has a close control, so the person can hide it. Systems set these differently. Atlassian's banners are not dismissible: they appear when needed and disappear when no longer required. Base's system banners stay until dismissed or until the state that caused them is resolved. NewsKit lists a close button as optional.
Tip
Ask one question: if the person closes this banner, will the problem still be there tomorrow? If yes, the banner should come back, or it should not be closable at all. A dismissed promotion can stay closed. A failed payment should not vanish with no way back.
Worked example: a 'Your payment failed' banner
This is a teaching example built from Atlassian's documented banner rules. It is not a screenshot of a real Atlassian screen. The app is made up, and the message is a payment failure the person must fix to keep their plan.
- 1
Choose the type
The payment has already failed, so this is an error, not a warning. A warning would be for a payment that might fail soon. Atlassian uses error banners for problems that have happened and block something important.
- 2
Choose the icon
Use the error icon, since Atlassian allows only the error and warning icons on banners. Give it a text label a screen reader can speak. Do not rely on red alone, because some people cannot tell colors apart.
- 3
Choose the color token
The container uses the danger color token, a named choice for errors, not a raw red value typed by hand. The token keeps every error banner in the product the same. Check that the text has clear contrast with its background.
- 4
Write the words
Use the heading 'Your payment failed.' Then one message: 'We could not process your last payment. Update your payment method to keep your plan active.' It names the problem, the effect, and the next step.
- 5
Add one action
Place a single link, 'Update payment method,' after the message. The label says exactly what happens next, so the person does not have to guess.
- 6
Set persistence and placement
A failed payment should stay visible until it is fixed, so this version has no close control. Place it at the top of the account page, under the page header and above the content. Make sure no other banner is showing.
Tip
Review every banner in order: type, icon, color token, words, one action, and how it goes away. If any check is missing or unclear, the banner will not work for everyone who sees it.
Usage rules for the design system
A design system turns good habits into rules that every team follows. The rules below cover the most common banner mistakes, and each one connects to the types and parts you have just read about.
When should you use a banner?
Use a banner for essential, system-level news that people should see before they carry on. NewsKit's examples include internet connection problems, subscriptions about to expire, payment failures, and major product changes. Atlassian reserves banners for critical messages, such as warnings about lost data or lost functionality.
Do not use a banner for every piece of information. Base says banners should rarely be used. Baymard warns that always-on information weakens a banner's power to catch attention when something urgent happens. For a quick confirmation, use a toast. For a form error, use an inline message.
Color tokens and readable contrast
Each banner type gets its own color token, and designers pick the token that matches the meaning. Carbon says the color should match the intent of the message, and icons can help show that intent too. Atlassian asks teams to choose the right color role, because yellow usually suggests a warning and green usually suggests success.
Contrast matters because a banner is often read quickly, on a small screen, in poor light. Base says system-level banners should use only high-contrast colors. Check text against its background before you sign off. Color alone is never enough. Pair every color with an icon and clear words.
Why keep one banner visible at a time?
Show only one banner at a time. Material Design, Orange, and Atlassian all give this rule. Baymard suggests that when several messages must appear, show the most urgent one and hold the rest back until the first is resolved or dismissed. Base suggests merging several form errors into one banner, so the person sees one clear message instead of a stack.
Moon Design System goes further and allows only one banner per page. When banners stack, people stop reading them, and the important one gets lost. Ranking by severity keeps the most serious message on top and the rest in a queue.
Write short, clear, actionable copy
A banner has very little room, so every word must earn its place. Atlassian asks for concise language that states the problem. Keep the message to one or two short sentences, and avoid jargon. Moon's banner pattern uses one short heading, one sentence of description, and at most one main action.
Name the action with a clear verb, such as 'Update payment method' or 'Renew plan,' instead of a vague word such as 'OK.' Atlassian asks for action labels of one or two words, such as Save or Remove. When the problem is on your side, use 'we' rather than 'you,' because 'you' can sound like blame. Avoid 'sorry' and 'please' in error messages, since they can make the problem sound bigger than it is.
Tip
Read the banner out loud. If you need more than a few seconds to understand it, cut words until the problem and the next step are both clear.
Check your understanding
Try these two short scenarios. Each one needs the ideas from this lesson, not just the definitions.
Quick check
Your app must tell a user that their subscription ends in 3 days. The message should stay on screen until the user acts or closes it. Which choice fits best?
Quick check
Your design system allows one banner at a time. An informational banner about scheduled maintenance is showing. Then a payment error arrives. What should happen?
Key takeaways
Match the type to the meaning
Use informational, success, warning, error, or promotional based on what the message says, and keep the color, icon, and words in agreement with it.
Keep it short and show one
Use one or two plain sentences, one clear action, and only one banner on screen. If several messages compete, show the most urgent one first.
Decide how it goes away
Choose persistent or dismissible based on whether the problem still matters after the person closes it. Use a toast, modal, or inline message when a banner is the wrong tool.
Sources
- Atlassian Design System: Banner usage guidance
- Atlassian Design System: Designing messages
- Atlassian Design System: Error messages
- Baymard Institute: What is a banner UI element?
- Material Design: Banners
- IBM Carbon Design System: Notifications pattern
- Nord Design System: Banner component
- NewsKit: Banner component
- Orange Unified Design System: Alert banner
- Orange Design System: Banners
- Base Design System (Uber): System banner
- Base Design System: Banner
- Courier: What is a toast message?
- Userpilot: Modal examples and when not to use one
- Mobbin: Banner UI design glossary
- Moon Design System: Introduction to dialogs and notifications
Last updated on 17 November 2026
Related lessons
Learn with me
Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.