Badge: Defining One Shared Status Mark for Counts, Dots, and States
Learn the three badge types, how to define one shared badge with sizes, anchors, and meaning-based variants, and how to keep it clear for every reader.
In short
A badge is a small shared status mark with three types, such as counts and dots, defined once with sizes, anchors and variants that map to meaning.
10 min readFree
What You Will Learn
A badge is a small label that sits on top of another item. That item might be an icon, a profile picture, a tab, or a row in a list. The badge shows a status, a count, or a category at a glance. In a design system, the badge is a core component: one shared version that every product team reuses instead of inventing its own.
This lesson covers the three kinds of badge, how to define one as a shared part, a worked example built on a mail app icon, and the habits that keep badges clear for people who use screen readers or cannot tell certain colors apart. Reading time is about ten minutes.
Key words
- Badge
- A small label attached to another element. It gives extra information, such as a count or a status.
- Anchor
- The element a badge sits on, such as an icon, a tab, or a list row.
- Non-interactive
- Something a person cannot tap or click to start an action. A badge only shows information.
- Core component
- The one official version of a shared part that every team must use.
- Variant
- A version of the same component made for a different meaning or look.
- Functional color
- A color that always carries one fixed meaning, such as red for error.
- Token
- A named design decision, such as a color name, stored once so many parts can reuse it.
- Cap
- The largest number a badge will show. Anything above it shows a symbol instead, such as 99+.
- Screen reader
- Software that reads screen content aloud for people who cannot see it well.
- Accessible name
- The words a screen reader announces when it reaches an element.
What are the three types of badge?
Most badges fall into three types. Choose one type for each badge. A badge that tries to show a count, a dot, and a word all at once confuses people, because the eye cannot tell which part matters.
Numeric count
A number, such as 4 or 27, that tells how many items need attention, such as unread messages. Use it when the exact amount changes what the person will do next.
Dot
A small filled circle with no words or numbers. It says that something is new or changed, but not how much. Use it for simple states, such as an online presence or a section with fresh updates.
Text status label
One or two short words, such as New or Beta. Use it to name a category or a state. Keep the words short so the badge stays small and easy to read.
How do you choose between a count and a dot?
Ask one question: does the exact number change what the person will do? If it does, show a count. If the fact that something changed matters more than the amount, show a dot. A dot says there is something new without the noise of an exact figure. Carbon's guidance follows the same idea. It uses a badge with a number when the count of new or updated items matters, and a badge without a number when the number is unknown or does not matter to the user.
Tip
Do not mix dots and numbers on the same navigation bar. Mixed styles make the signal harder to read. Pick one style for each bar and keep it.
Why cap large numbers?
Long numbers can stretch the layout and push neighbouring items out of place. A cap solves this. Many teams use 99+ instead, and some use 9+ in very small spaces. Choose one cap, write it in the component rules, and use it on every screen. Test the badge at its widest value, so you can see whether the items beside it move.
How do you define the badge as a core component?
A core component is the one version of a part that every team must use. To define a badge, write down its parts and its rules. A badge has four parts. The anchor is the element the badge sits on. The shape is the outline of the badge. The content is the dot, the number, or the word. The color role says what the color means, such as error, not just how it looks.
What sizes and shapes should a badge have?
A large badge holds label text, which is why it suits counts. Your rules should say which sizes can carry a number, and keep the list of sizes short so designers do not invent new ones.
For shape, pick one corner style for the whole system. Set Product suggests rounded corners by default, and square corners only for systems built on a square grid.
Anchor Position
Choose one anchor point and use it everywhere. A common choice is the top-right corner of the parent item. When people see the signal in the same place every time, they find it faster. Check the space too. A small badge should not run into the edge of the screen. A large badge needs room, so avoid placing it where it will collide with other content.
Variants That Map to Meaning
A variant is the same badge made for a different meaning. Keep the list short, and give each variant one clear job. A common set uses five meanings.
Info
Adds helpful but non-urgent information, such as a new feature someone may like to try.
Success
Shows that something finished well, such as a completed upload.
Warning
Asks for attention soon, such as a plan that is about to expire.
Error
Shows that something failed or needs fixing now.
Neutral
Shows a plain count or state with no good or bad meaning, such as unread mail.
Carbon warns that one shape should not switch between different colors inside the same experience. This means each meaning needs its own clear cue, not just a new color on the same shape.
Tip
Store each variant as a named role, such as a badge error background, that points to a color token. When the brand color changes, you update the token once and every badge follows. Do not copy color values into each badge by hand.
Worked Example: The Mail Icon Badge
Picture a mail app's bottom bar. Mail apps such as Gmail on a phone, and the iOS Mail icon, show a small red circle with a number that tells how many messages are unread. This is a familiar pattern. Our job is to turn it into a component the whole team can reuse. Follow these steps.
- 1
Name the anchor and the content
The anchor is the mail icon. The content is the unread total. Because the content is a number, this is a numeric count badge.
- 2
Add a dot variant
Define a second form of the same badge with no number, for a quieter case such as a folder that has new mail but where the exact total does not matter. Use the dot only when the surrounding item makes its meaning clear.
- 3
Set the cap
Show 12 when there are 12 unread messages. When the total goes above the cap, show 99+. Write the cap in the component rules so every mail screen follows it.
- 4
Place and size it
Anchor the badge to the top-right of the icon, in the size your rules allow for numbers. Keep the same position on every screen so people learn where to look.
- 5
Give it an accessible label
Attach the count to the mail icon's accessible name, so a screen reader says something like 12 unread messages. Without this, the number is visible to sighted users only, and a screen reader user hears just the word Mail.
- 6
Test it without color
View the badge in grayscale. If the number and the position still carry the message, the badge passes. If the meaning only shows through the red, add a second cue.
The result is one component with a count form, a dot form, a 99+ cap, variants for meaning, and a spoken label that changes with the number. Every mail screen uses the same rules, so designers and builders do not have to guess.
Using Badges Well
A badge is easy to add and easy to overuse. These four habits keep it useful for every reader.
Keep Labels Very Short
Use a short word or a number. If the meaning needs a full sentence, put that sentence on the page itself, near the item, and leave the badge short.
Never Rely on Color Alone
Carbon advises against using only color and status labels to tell content apart. Add a second cue, such as a shape, an icon, or a word. A red dot tells a sighted person something, but a screen reader hears nothing from it, and some people cannot tell red from green. Pair every variant with a cue. For example, an error badge can carry an error icon or the word Error next to the count.
Make Screen Readers Announce It
A screen reader reads the words attached to an element. Put the badge's meaning into the label of the element it sits on. MUI's guidance is to include the count in the item's name, so the inbox button is announced as Inbox, 4 unread messages rather than just Inbox. Keep the spoken words in step with the visible number, so a count that changes on screen also changes in the label.
Avoid Badge Overload
If every item has a badge, none of them stands out. Show a badge only when information changes and someone needs to act on it. If you cannot keep a count accurate, use a dot or remove the badge. When a status matters on its own, show it in the interface rather than relying on a small mark. Animated badges, such as a bounce or a count that flashes, should respect the person's reduced-motion setting.
Tip
Count the badges on one screen. If there are more than a few, ask which ones a person must act on today. Remove or quiet the rest.
Check Your Understanding
Try these short scenarios. Each one needs the rules from this lesson.
Quick check
Your app's bell icon must show 134 new alerts. A teammate proposes a green badge that reads 134 for updates, and a red badge for errors. The only difference between them is color. What should you change?
Quick check
The Downloads tab receives a new file every few minutes in the background. The person only needs to know that something is new, not how many files there are. Which badge fits best?
Quick check
A chat app shows 1,482 unread conversations on its chat icon. The team's cap is 99. What should the visible badge show?
Key Takeaways
Pick one type
Use a count when the number changes the choice, a dot when change matters more than amount, and a short text label for a state.
Define it once
Fix the sizes, the anchor position, the cap, and the meaning-based variants in one shared component, and build its colors from tokens.
Never lean on color or a dot alone
Pair meaning with a shape or words, and put the count into the label of the element the badge sits on.
Sources
- Material Design 3: Badge guidelines
- Material UI (MUI): React Badge component usage guidelines
- Carbon Design System: Status indicators pattern
- Carbon Design System: Status indicators pattern (version 10 archive)
- Carbon Design System: Status indicators pattern (version 11 archive)
- Carbon Design System: Status indicators (building blocks, core patterns)
- Set Product: Badge UI design and what a badge is, with status patterns
- Eleken: Badge UI design principles, types and real examples
Last updated on 17 November 2026
Related lessons
- Design systemsBadges: Small Status Marks That Show Counts, New Items, and States
- Design systemsDefining Design Tokens: Named Design Decisions Shared by Designers and Builders
- Design systemsInput Checkbox: One Shared Box for Choices, Partial Selections, and Clear States
- Design systemsTextarea: One Shared Multi-Line Text Box With Clear States and Rules
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.