Chips: Guidelines
Chips help people enter information, make selections, filter content, or trigger actions

Usage
Chips help people enter information, make selections, filter content, or trigger actions. They're best used to help people accomplish their current task faster and easier.

Chips aren’t buttons
Chips and buttons are similar. They both provide visual cues to prompt people to take actions and make selections.
While buttons appear consistently and with familiar calls to action, chips are dynamic to the situation, and appear as a group of interactive elements.
Use chips to enhance a person's current journey and encourage action. Use buttons to progress them through the product and for significant actions.


Chips should dynamically offer various actions depending on the current task, whereas a button should be a persistent fixture of a layout.
Chips represent forking paths for a current task, while buttons represent linear steps.


Multiple chips should appear together in a set, whereas there should be no more than 3 buttons in a single arrangement.
Chip sets can be scrolled horizontally.


Variants
Choose the chip variant based on its purpose and author.
Does the chip represent an action (assist chip) or filter results (filter chip)?
Is its content generated by the product (suggestion chip), or by the person using the product (input chip)?

There are four chip variants:
- Assist
- Filter
- Input
- Suggestion
| Purpose | Chip variant | Rationale | Example |
|---|---|---|---|
| Action | Assist chip | Assist chips represent smart or automated actions that can span multiple apps | Add to calendar action |
| Filter | Filter chip | Filter chips represent filters for a collection | Platform selector on material.io/components |
| Information, user-authored | Input chip | Input chips represent discrete pieces of information entered by a person | Gmail contact in the To field |
| Information, product-authored | Suggestion chip | Suggestion chips help narrow a person’s intent by presenting dynamically-generated suggestions | Suggested chat response |
Anatomy

- Container
- Label text
- Leading icon or image (optional)
- Trailing icon (required for input chips, optional for filter chips)
Container
All chips are slightly rounded with an 8dp corner.

Shadows & elevation
Chip containers can be elevated if placed on top of an image or dynamic background.





Label text
Chip label text should be 20 characters or fewer, and have the same typography style as buttons.
Chip labels should remain brief for the limited space available. Skip conventional grammar rules, such as articles (take "a" walk), to save space.


Leading icon or image (optional)
Chips can contain a leading icon, logo, or circular image. Use a system icon to help identify a chip's category.

The leading icon color for unselected chips can be customized through theming. While the default color role is primary, the on surface variant color role is a good alternative when the icon style requires less emphasis.

Leading circular images are sized larger than leading icons to provide more space for detail. Icons are designed to be legible at small sizes.
See the Specs tab for precise measurement values.

Trailing icon (optional, input and filter chips only)
The trailing icon is present for input and filter chips.
On input chips, it's required and must be used to remove the chip. On filter chips, it's optional, and can be used to open a menu or remove the chip.
Secondary actions (such as a trailing icon button for Remove) must have a 48x48dp interaction target that doesn’t interfere with the chip's primary action (such as Edit or Drag). To achieve this, apply a minimum width of 88dp to the chip, or 42dp to the label text.

Assist chips
Assist chips represent smart or automated actions that can span multiple apps, such as opening a calendar event from the home screen. Assist chips function as though the person asked an assistant to complete the action. They should appear dynamically and contextually in a UI.
An alternative to assist chips are buttons, which should appear persistently and consistently.



Assist chips can trigger an action or show progress and confirmation.
Write assist chips like buttons: start with a verb. Adjust text dynamically if the state changes, like Save to Saved.
Assist chips are displayed after primary content, such as below a card or persistently at the bottom of a screen.

Filter chips
Filter chips use tags or descriptive words to filter content. They can be a good alternative to segmented buttons or checkboxes when viewing a list or search results.
Tapping on a filter chip activates it and appends a leading checkmark icon to the starting edge of the chip label.
Write filter chips with nouns that describe the category to include in the results. Avoid negative phrases like Exclude images.



Tap a chip to select it. Multiple chips can be selected or unselected.


Alternatively, a single chip can be selected. This offers an alternative to segmented buttons, radio buttons, or single select menus.
However, avoid mixing chip set behaviors. All chip sets on a page should be either single-select or multi-select.
In medium and expanded breakpoints, filter chips may contain a trailing icon to directly remove the chip or open a menu of options.
In compact windows, the trailing icon's target area is too small to be accessible on its own. However, if the whole chip can be selected to accomplish the action, the chip is likely still accessible.


When combined with a menu, the filter chip opens a list of selectable options.
Filter chips can be used with other components, such as search fields and sheets.





Input chips
Input chips represent discrete pieces of information entered by a person, such as Gmail contacts or filter options within a search field.
They enable user input and verify that input by converting text into chips.

Input chips can support editing to change their contents, such as correcting an email address. In edit mode, the chip reverts back to a text string. Editing can be triggered by interacting with the chip, either by selecting it or by a second interaction after selection.
A single field can contain multiple input chips. These chips can be reordered or moved into other fields.


Input chips can expand to show more information or options. A container transform transition pattern is used to reveal additional content.
Placement
Input chips can be integrated with other components.
They can appear:
- Inline with the cursor in a text field
- In a stacked list
- In a list that can be horizontally scrolled

Icons & images
The leading icon of input chips can be an icon, logo, or circular image.

The trailing icon is always aligned to the end side of the container. It’s placed:
- On the right for left-to-right (LTR) languages, such as English
- On the left for right-to-left (RTL) languages, such as Farsi


Suggestion chips
Suggestion chips help narrow a user’s intent by presenting dynamically generated suggestions, such as possible responses or search filters.
Write suggestion chips as nouns or short phrases, depending on context. Avoid exceeding 20 characters when possible.



Placement
When displaying multiple chips together, place them inline as a row of options, not listed vertically. Overflowing chips should break to the next line.
If the field is only one row high, chip sets can scroll horizontally instead.
Keep an 8dp minimum space between chips. Chips must also have a minimum 48dp target size, regardless of placement or density. If required, the target can extend beyond the visible container of the chip.
Text labels for chips should be concise. Chip labels will truncate when in a wrapped layout, and when they are wider than the full width of the window.

- Margins between chips
- Margin between each line