frameworkExperience & interface

Badge, Chip, and Tag

Badges show compact counts or status, chips represent compact interactive choices or entities, and tags label or categorize content.

Download Markdown (.md)

01What it means

A badge is a small indicator attached to or near another element, often showing a count or status. A chip is a compact component that can represent an input, filter, choice, or action. A tag is primarily a label for classification or recognition and may optionally support navigation or removal. Design-system terminology varies, so behavior must be specified alongside the name.[1][2]

02Why it matters

These elements look similar but imply different interaction, hierarchy, and accessibility expectations. Separating indicator, interactive token, and descriptive label roles prevents decorative pills from becoming ambiguous controls.

03When to use it

Use a badge for concise supplemental status, a chip for a compact selectable or removable entity, and a tag for classification. Use ordinary text when the information is essential or lengthy, and a full button, checkbox, or link when its familiar affordance would be clearer.

04How it works

  1. Identify whether the element communicates status, represents data, or accepts an action.
  2. Choose a variant with only the interactions the task requires, such as select, remove, or navigate.
  3. Write a short label and expose count, state, and removal purpose in an accessible name.
  4. Provide distinct focus, selected, disabled, overflow, and error behavior where relevant.
  5. Test wrapping, truncation, repeated items, color independence, keyboard order, and touch targets.

05A practical example

Example

An issue tracker shows a numeric badge on Inbox, removable chips for active assignee filters, and non-interactive tags for issue categories. Removing an assignee chip updates results and announces the change; the category tag does not look focusable because it has no action.

06Where it breaks

Terminology is inconsistent across systems, compact shapes leave little room for explanation, and large sets become cluttered. Color-only status and tiny removal targets create accessibility problems.

Common mistakes

  • Using badge, chip, and tag names interchangeably without defining behavior.
  • Making a non-interactive label look like a clickable control.
  • Putting critical status only in a color or unexplained count.
  • Allowing removable chips to wrap or truncate in ways that obscure which item will be removed.

07Sources

  1. ChipsMaterial Design · Institutional design systemChips
  2. ComponentsAtlassian Design System · Institutional design systemComponents
View saved topics

Start typing to search titles, definitions, categories, and frameworks.