Labels are read-only indicators used to communicate a category, metadata, or process's current state.

Anatomy

  1. Container: The component's container provides the background color, border, and border radius.
  2. Status indicator: The indicator is a colored dot meant to help better indicate the Label is used to describe a status.
  3. Text: Strong Label text helps provide contextual meaning with the background color. Bold by default.

Guidelines

Label vs Badge

Labels and Badges both convey information in visually similar ways but are not interchangeable:

  • Labels emphasize status or categorize an item with words, such as "Active" or "Draft."
  • Badges display the quantity of an item with a numeric value, such as showing how many notifications a user has.

Label vs Tag

Labels and Tags share visual similarities that may be easily misconstrued. Be sure to understand the fundamental difference between them as they are not interchangeable:

  • Labels are read-only indicators set by the system or application. Users have no direct control over their creation.
  • Tags may be user-generated and interactive. Users create them for categorization and filtering and can edit or remove them as needed.

Best practices

Color use

Color can be helpful for conveying meaning to users when used with descriptive text. Labels include a range of colors available for use. When using color, be consistent with their usage across the app. Avoid using color purely for decoration to fit a particular color scheme.

For more information regarding color and accessibility, see Color and Meaning.

SuccessWarningDangerInfoNeutral
Do: Use consistent colors to represent the same or similar status across the application.
InfoWarningDangerNeutralSuccessActive
Don't: Use colors to fit a theme or use multiple colors for the same status.

Status indicators

Status indicators are small dots added before the Label's text to visually emphasize a process's current status.

Labels can only become status indicators using the following common status colors:

  • Red: Critical, destructive, not functioning
  • Yellow: Warning or caution
  • Green: Success, confirmation, or functional
  • Blue: Info
  • Grey: Neutral
RunningScheduledStoppedOpenedDraft
Do: Use status indicators to communicate system or process states.

Appearance

Variants

When deciding what Label variant to use, consider what versus where. Each available variant solves a particular use case.

  • Base Labels have no status indicator dot. They're intended to be used for categorical attributes, that is, an attribute that describes what something is. Stables properties such as types, tiers, roles, tags, etc. fall into this category.
  • Status Labels include the status indicator dot. They're intended to be used for operational status. An operational status describes where something is in its lifecycle and represents a live, mutable state. "Online/offline," "running/scheduled/stopped," and "active/draft" are all examples that fall into this category.
Category
Base

Default Labels are used for categorization and metadata to describe what something is.

Delivered
Status

Status Labels include a colored dot to communicate process states like success, failure, warning, or neutral to describe where something is in its lifecycle.

Colors

Labels are available in a range of colors. The default is grey.

RedRaspberryClementineYellowGreenTealBluePlumPurpleGreyOutline
Colors

Use the best Label color for a given status or semantic use case.

Font weight

Label text is bold by default for readability and emphasis. Use a lighter font weight for cases where the Label should be less visually prominent. Light text is not compatible with status indicators.

Bold label
Bold

Bold text provides the strongest visual emphasis and is the default for most use cases.

Light label
Light

Light text is less prominent and is used when emphasis isn't required.

Content

It's important to accurately and concisely describe the category or status using the Label. Use sentence case, but avoid full sentences and verbs. One to two words without punctuation is preferred.

ActiveDraft
Do: Use text that accurately describes status.
This item is currently activeSaved as a draft
Don't: Use long phrases or full sentences.
In progress
Do: Use sentence case.