Badges: Small Status Marks That Show Counts, New Items, and States
Learn the three main badge types, how to place and color them, how to cap long numbers, and how to keep badges clear for everyone.
In short
A badge is a small status mark that shows a count, a new item or a state, and it comes in three main types that need clear placement, color and caps.
12 min readFree
What you will learn
A badge is a small mark that sits on or beside another item. It tells the user something about that item, such as how many new messages are waiting or whether a feature is new. Badges look simple, but a design system makes them even more useful. The team defines each badge once, with set styles, sizes, and colors, so the same signal means the same thing on every screen.
In this lesson you will learn the three main badge types, the rules for placing and coloring them, how to handle long numbers, and the accessibility checks that keep badges useful for everyone. You will also walk through one example step by step.
Key words
- Badge
- A small label or shape attached to another element to show a count, a status, or that something is new.
- Parent element
- The icon, button, or tab that a badge belongs to. The badge gives extra information about it.
- Count
- A number, such as 4 unread messages.
- Dot indicator
- A small plain circle with no text. It says something is new, but not how much.
- Status
- The current condition of something, such as done, waiting, or failed.
- Variant
- A set version of one part, such as a small badge or a large badge. The system defines each variant once.
- Cap
- The highest number a badge will show, such as 99+. Above the cap, the badge shows the cap with a plus sign.
- Screen reader
- Software that reads the screen aloud for people who cannot see it well.
- Accessible name
- The words a screen reader says when it reaches an item, such as Inbox, 4 unread messages.
What is a badge?
A badge always belongs to something else. On its own, a small red dot means very little. A red dot on a mail icon, however, tells the user that mail is waiting. That link to a parent element is the heart of the idea.
Badges usually appear on navigation items, icons, and tabs, which are the places where people move between parts of an app. Material Design describes badges as a way to show notifications, counts, or status for these items, and it says a badge can hold a label or a number.
In a design system, the badge is a shared part. The team sets its variants, sizes, and color roles once. Product teams then reuse it. This matters because a user who sees a red count in one area of an app should understand the same kind of signal in another area without guessing.
What are the three main badge types?
Most systems use three main types of badge. Each one answers a different question for the user.
Numeric count
Use this when the user needs to know how many items are waiting, such as unread emails. The number tells the user how much attention is needed.
Dot indicator
Use this when something is new or has changed, but the exact number does not matter. It is a plain circle with no text.
Text label or status badge
Use this for a short word, such as New, Paid, or Beta, attached to an item. It names a state or category rather than a quantity.
Each type has its own place. The sub-topics below explain when to choose each one.
When does a number help?
A count is useful when the user can act on the quantity. Unread messages are a good case. The number should match the real number of items the user has not yet seen. When the count is zero, most libraries hide the badge.
When is a dot enough?
A dot works when the surrounding screen makes its meaning clear. Material UI advises using dot badges only when the layout already explains the state, such as Online or Unread. Carbon, the design system from IBM, says a dot without a number is more subtle than a numbered badge, yet it still draws attention to an icon button. It fits best when the exact count is unknown or unimportant.
Text labels and status badges
A text badge names a state. Shopify’s Polaris system, built for store admin screens, uses short badges to show things such as the status of an order. Its label guidance favors a single word where possible. Use a text badge to describe a fact about the item, not to act as a button.
Tip
Give each badge one job. A badge that shows a count and a word at the same time is harder to read at a glance. Pick one, then keep it consistent across the product.
Placement, size, and spacing
Placement should be fixed. Material Design’s guidance says badge positions should not be moved arbitrarily, and it warns against placing a badge over the icon itself. Users learn where to look. If the badge jumps from screen to screen, scanning becomes slow.
Placement
Attach the badge to the top corner of its parent, in the same spot every time. Do not cover the icon, because a covered icon becomes hard to recognize.
Size
Keep the badge small. It is an extra signal, not the main content. Angular Material offers small, medium, and large sizes, and its small badges leave out the label text.
Padding and spacing
Padding is the empty space between the text and the edge of the badge. The system should set it once, so every badge has the same comfortable shape and the number is not pressed against the edge.
The rule is simple: the badge should draw the eye, but it should never hide or crowd the item it belongs to.
Color meaning and text contrast
Color carries meaning. Each status also has an icon. Shopify’s team proposed a red badge for critical messages, so that red means urgent everywhere in the admin. The lesson for a designer is to choose a small set of colors, give each color one job, and write that job down.
Red
Use for urgent or critical states. The Shopify team suggested the same job for red.
Green
Use for success, such as a task that finished as expected. Carbon uses green with a check icon for this.
Blue
Use for information that is useful but not urgent. Carbon uses blue for informational notices.
Yellow
Use for warnings, such as a state that may have unexpected results. Carbon uses yellow with a warning icon.
Text contrast matters too. The words inside a badge must stand out clearly from the badge background. Check this in every mode your product supports, such as light and dark themes. Do not rely on color alone. The number or word should carry the meaning as well.
Tip
Color is for meaning, not decoration. If a new feature needs a badge, ask which existing meaning it matches before you pick a new color.
What should you do with long numbers?
Long numbers need a limit. A count of 1,250 would make the badge grow wide and push into nearby items. So systems set a cap, which is the highest value the badge will show. Carbon limits its numbered badge to three digits, with the last character as a plus sign.
Other rules are stricter. Material also notes that four- and five-digit numbers on navigation items can be cut off at the edge of the container. Polaris web components cut long badge text with an ellipsis instead of wrapping it onto a second line.
Tip
Choose one cap for your whole system and write it in the guidelines. If one app shows 99+ and another shows 999+ for the same thing, users who move between them will be confused.
Worked example: an unread count on a mail app
This example follows the published badge rules for a mail app’s inbox icon in a bottom navigation bar. That is the row of main destinations at the bottom of a phone screen. We did not inspect a live mail screen; the steps show how the rules combine into one finished element.
- 1
Name the parent
The inbox icon is the parent element. Its job is to take the user to their mail. The badge must add information to that job, not replace it.
- 2
Decide the meaning
The badge will show how many mail items are unread. The user can act on that number, so a numeric count fits better than a dot.
- 3
Pick the variant
Use the system’s large count badge, which holds text. Keep the small dot variant for destinations where only the word new matters.
- 4
Choose the color
Use the system’s color for counts. Do not add a second color for Calendar or Chat in the same bar, because the bar would then carry several meanings at once.
- 5
Place it
Set the badge at its fixed corner on the inbox icon. Keep it there on every screen, and do not let it cover the icon.
- 6
Cap the number
With 4 unread mail items, the badge shows 4. With 1,250 unread items, the badge shows the system’s cap, such as 999+ under Material’s rule or 99+ under Carbon’s three-digit rule.
- 7
Label it for screen readers
The inbox button should be named Inbox, 4 unread messages. A screen reader user then hears the count together with the name, not only the word Inbox.
- 8
Clear it
When the user opens the inbox and reads the mail, the count should update.
Quick check: choosing a badge type
Quick check
A news app adds a privacy page to its Settings tab this week. Nobody needs a number, and the team only wants users to notice that something is new. Which badge fits best?
Accessibility and usage rules
A badge is easy to miss. Some users cannot see color well, and some use screen readers that will skip a small dot unless it is labeled. Good badge design gives every user the same information. These rules help.
Never the only signal
A badge should not be the only way to show a meaning. If a status matters on its own, show it in the screen as well. Material UI says this directly: if the status is important alone, show it in the interface rather than relying only on the badge.
Give it screen-reader text
The badge’s meaning should become part of the name of the item it belongs to. Material UI gives the example of a label that reads Inbox, 4 unread messages, rather than only Inbox.
Use badges sparingly
This is a design judgment, not a fixed rule. When every item has a badge, none of them stands out. Keep badges for things that truly need attention, so the few that appear keep their impact.
Keep them apart from buttons
A badge is information, not a control. If a user must tap it, pair it with a button instead.
Screen-reader text in practice
Screen-reader text is the hidden words that a screen reader speaks. Sighted users see only the badge and the icon, so the spoken words must add the context they get visually. A count with no label is unclear when heard alone. Pair the count with the item’s name, as in Inbox, 4 unread messages. Angular Material follows the same idea by requiring a meaningful description for each badge.
Tip
Read the badge label aloud. If it sounds like a bare number with no subject, add the item name and the meaning.
Quick check: caps and color rules
Quick check
Your team’s badge rule allows at most three characters, including the plus sign. An inbox has 1,250 unread messages. What should the badge show?
Quick check
Your mail app’s inbox icon shows a red count badge. A teammate wants a green badge on the Calendar icon, a blue badge on the Chat icon, and a yellow badge on the Tasks icon. Each is for a different new feature. What principle is at risk, and what would you suggest?
Key takeaways
Pick the right type
Use a count for quantities the user can act on, a dot for something new, and a text label for a state or category.
Define it once
Set the placement, size, padding, cap, and color meanings in the system, so every badge looks and behaves the same way.
Design for everyone
Never let a badge be the only signal, label it for screen readers, use it sparingly, and keep it clearly separate from buttons.
Next, try the idea on a real screen. Pick one icon in an app you use and ask three questions: what is the parent, what does the badge add, and what would a screen reader say?
Sources
- Material Design 3: Badge guidelines
- Material Design 3: Tabs guidelines
- Material UI: React Badge component
- Angular Material: Badge overview
- Carbon Design System: Status indicators pattern
- Carbon Design System: Status indicators (building blocks)
- Carbon Design System: Notifications pattern
- Shopify Polaris: Badge web component reference
- Shopify: Migrate Badge from Polaris React
- Shopify Polaris React issue 1969: proposal for badge guidelines
- Polaris Vue: Badge guidance (community port)
Last updated on 17 November 2026
Related lessons
- Design systemsBadge: Defining One Shared Status Mark for Counts, Dots, and States
- Design systemsButtons: How Action Buttons Show Priority, States, and Clear Labels
- Design systemsCarousel: Rotating Slides That Show Related Items One at a Time
- Design systemsWhat Is a Design System? A Plain-Language Guide for New Designers
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.