Chips
Overview
Chips are compact label elements used to display status, categorize content, or represent attributes such as the classes assigned to a group or the tags on a record. They are visually similar to badges but are larger, more prominent, and may be interactive.
Unlike badges, chips can function as links when rendered using an anchor tag, providing hover and focus states. Chips should be used intentionally and sparingly, as they carry more visual weight than badges.
A chip has two independent axes: a context sets the color (chip-primary, chip-success, …) and a treatment sets how that color is applied (tonal, chip-solid, chip-outline). Any context works in any treatment.
Prefer the Vue components
EnChip renders all of this and picks the right root element for you, and EnChipGroup builds a row from an array and owns the removal plumbing. Reach for the raw classes only outside a Vue context.
Guidelines
Dos
- Use chips to display status, categories, or lightweight attributes.
- Use chips when the label needs more visual emphasis than a badge.
- Use interactive chips (
<a>or<button>) when the chip navigates to, or acts on, the thing it names. - Group multiple chips using a
chip-containerto ensure consistent spacing and alignment. - Keep chip text short and scannable (one or two words).
- Stay on the tonal treatment unless there is a reason not to — see below.
Don’ts
- Don’t use chips for primary actions or workflows.
- Don’t use chips interchangeably with buttons.
- Don’t overload interfaces with large numbers of chips.
- Don’t use chips when a badge or plain text would be sufficient.
- Don’t introduce custom chip colors outside approved variants.
- Don’t use
chip-pillon anything that isn’t a chip. Chips are the one deliberate exception to the system’s 6px radius.
Variants
| Variant | Description | Example Use |
|---|---|---|
| Default | Neutral chip for general labeling | Metadata, labels |
| Primary | Brand-emphasized chip | Highlighted category |
| Success | Positive or completed status | Active, Enabled |
| Danger | Error or blocked status | Error, Disabled |
| Info | Informational or descriptive status | Info, Details |
| Warning | Cautionary or pending status | Pending, Needs Review |
Treatments
The treatment is a second class alongside the context, so chip-solid chip-success is a solid green chip. Tonal is the default and needs no class of its own.
| Treatment | Class | Looks like | Reach for it when |
|---|---|---|---|
| Tonal (default) | — | Light tint fill, darker ink | A row of tags. It labels content rather than competing with it. |
| Solid | chip-solid | Saturated fill, white ink | A status that has to carry across a dense table. |
| Outline | chip-outline | No fill, 1px border in the ink color | The quietest token, or a chip that is a control (Add, +N more). |
Warning chips use a different yellow
Chip text is 12px at weight 400, so every pairing needs 4.5:1 — and the semantic $warning-color doesn’t reach it (white on it measures about 1.7:1). Warning chips therefore use the palette’s yellow.dark tone, giving 5.54:1 tonal and 5.90:1 solid, in line with the other four contexts. Don’t override a warning chip’s colors to “match” a warning label elsewhere — label-warning still has the original contrast problem.
Modifiers
Chip container
When displaying multiple chips together, wrap them in a chip-container.
- Ensures consistent spacing and alignment.
- Wraps to a second line, so a row grows with the number of chips assigned.
- Required when multiple chips appear inline.
Pill
chip-pill renders the chip fully rounded, and works with any context and treatment.
Chips
Solid
A saturated fill with white ink, for a status that has to carry across a dense table.
Outline
No fill, a 1px border in the ink color — the quietest of the three.
Pill
Interactive chips
Render the chip as an <a> when it navigates to the thing it names, and a <button> when pressing it acts on that thing. Hover shifts the fill by one step rather than switching treatment, so the chip stays recognizable while reading as clickable. Both get a focus ring, and both support disabled.
Removable chips
chip-action is the trailing × that removes the chip. It sits inside a static .chip — an anchor or button root cannot contain another control. Always give the × an aria-label naming what it removes, or a screen reader hears a row of identical “Remove” buttons.
Two hit areas
Add chip-label when the name is clickable as well as the ×: click the name to open or edit the thing, click the × to remove it. It cannot be one control, so the name gets its own button inside the static chip.
Related Components
- EnChip — the single chip, with the root element inferred from the props.
- EnChipGroup — a row of chips built from an array, with removal and overflow handled.
- Employee chips — the same vocabulary in the employee theme, drawn differently and without the removable variant.