Filter chip
v4.1
Filter chips provide quick access to values that refine a list of content.
Filter chips have 2 options Default and Expressive.
A title is required for all filter chips. The title should represent the discrete value or succinctly summarize the values contained in a dropdown filter.
A lead accessory is optional and should be used sparingly. Lead accessories should be clear, obvious and directly related to the content within the chip. Default chips only use an icon and expressive chips use an image as it’s lead accessory. If images are used, they should all be visually similar - lifestyle images with full bleed backgrounds or transparent images with white backgrounds
Chips that represent a single discrete value will immediately filter content when selected. They can be unselected by interacting with the chip again. Discrete chips are the default and preferred version because they only require a single interaction.
Single select options within a menu apply a value immediately after an option is selected. The label is updated to represent the value selected.
Dropdown chips that represent multi-selection have checkboxes next to each value label within the menu. Selecting values appends a counter to the label representing how many values are being applied. The data set should asynchronously update as each value is selected within a menu. If asynchronous updates aren’t possible, an apply button needs to be present to submit the selection.
Filter chips are a smart choice when users need to quickly filter or refine content. They support multi selections, provide immediate visual feedback, and offer a clear hierarchy to a layout. To ensure clarity and usability, keep labels short, group related filters logically.
Expressive chips are intended for immersive browsing moments and intentionally guide users through rich categories of content. They update content within a section or layout to keep users engaged and not disrupt their flow.
Chips leverage our state layers for interactions.
Filter chips have a minimum width of 56px and a maximum width of 296px. Expressive chips have a minimum width of 72px and a maximum width of 296px.
A counter is appended to the label when multiple values are selected within multi-value dropdown filters.
Filter chips can be wrapped in a horizontally scrollable container to ensure all chips are accessible when wider than the screen.
Video description: An animation of the filter chip component and its specific micro-interactions. This example shows the interaction on the chip container scaling down and using a micro-interaction on the chevron moving and rotating 180 degrees. A bottom sheet is brought on and the user selects and confirms multiple filters. The chip then updates- having the chevron reverse back to its original position/rotation and the background of the chip fills in with an active color. The amount of filters selected are also represented inside parentheses within the chip, and this is animated on with a position / fade transition.
Filter chips clearly indicate the selected value(s) and there’s a clear way to adjust or reset them.
Filter chips work for a wide variety of filter values across screen sizes.
Filter chips surface the top filter values or filter groups without overwhelming users.
Do keep labels short and focused on a single value or summary of a filter group.
Don’t override the height of chip to allow label wrapping. Allow the label to be truncated if it cannot be reduced.
Do use a rounded image as the lead accessory in expressive chips.
Don’t use other lead accessories like icons or square images in expressive chips.
Do use filter chips to refine the current view.
Don’t use filter chips to navigate users to new experiences or views. Use tabs instead.
Do use filter chips when filtering content.
Don’t use filter chips for input.
Do use a single row of chips.
Don’t stack or wrap filter chips.
Do use expressive chips for discrete values.
Don’t add dropdown behavior to expressive chips. Use filter chips instead.
Do use expressive chip for immersive browsing moments
Don’t use expressive chips for utility and task-based filtering or flows, like data tables. Use filter chips instead.
