Filter menu

Filter menus open from a filter chip and allow users to adjust parameters before applying.

Anatomy

A menu diagram with 5 elements numbered: 1. Container, 2. Menu item, 3. Lead icon/control, 4. Menu item label, 5. Menu item description
  1. Container
  2. Menu item
  3. Leading selection control
  4. Menu item label
  5. Menu item description

Properties

Container

The filter menu container groups all options related to the trigger element. Web uses the popover container by default. Native apps use native menus where appropriate.

On web, popover menus commonly use List rows for the menu item layout.

Menu listing Replace, Generate with AI, Edit, Remove, each paired with minimal icons.

Labels

Required. The label names the filter option the user can select. Use short and distinct labels to name the filters so users can compare them at a glance.

  • Use sentence case
  • No ending punctuation
  • Use noun or noun phrases
  • Aim for 1–3 words
Menu listing labels: Research, Store, Performance, Payments, Help, Settings.

Descriptions

Optional. A description provides clarity or context when the label alone isn't enough. Don't restate the label.

  • Use sentence case
  • No ending punctuation
  • Use parallel structure
  • Max 1 sentence

Descriptions are only supported on web, not Android or iOS. If a description is necessary, use a context sheet on Android or iOS.

Menu with icons and brief descriptions: Move to folder, Share via app, Change delivery option, Report.

Density

A filter menu’s density is determined by the height of the individual menu items. By default, menu items are 48px tall on web, 44px tall on iOS, and 48dp tall on Android devices. These defaults maintain a comfortable tap target size.

Smaller menu items save room but are more prone to accidental taps.

Two menu density examples side by side listing Research, Store, Performance, Payments, Help, Settings; right menu uses tighter spacing.

Grouping

Content can also include optional dividers, with or without group titles.

Menu grouping example; left uses section headers Buying and Selling; right uses a divider to separate sections.

Submenus

Submenus let users drill down into specific categories, and can be expanded and collapsed.

Accordion submenus: Women expanded with Tops & shirts, Pants, Outerwear; Men and Kids collapsed with chevrons.

Behavior

Filter chips can open a filter menu for users to adjust multiple parameters. The view updates immediately upon selection, or after the user selects the "Apply" button in the footer.

Color filter dropdown with multi-select checkboxes; Blue and White selected, Green, Yellow, and Red unselected.

When a form field opens a filter menu, selections behave like input values. The selected values are held until the form is submitted or confirmed.

Form dropdowns: multiselect checklist with Bookmarks and Trading cards checked; single‑select radio with Weekly chosen.

Checkboxes let users select one or more options from a list.

Form dropdowns: multiselect checklist with Bookmarks and Trading cards checked; single‑select radio with Weekly chosen.

Radio buttons let users select one option from a list.

Form dropdowns: multiselect checklist with Bookmarks and Trading cards checked; single‑select radio with Weekly chosen.

Menu items include selected, unselected, and disabled states to clearly indicate the current selection.

Selected state examples for list items: trailing checkmark, leading icon with checkmark, checked checkbox, and selected radio for Item 1.

Positioning

The filter menu should appear in the most logical and convenient place for users. The default placement is below the trigger element. If the trigger element is near the screen’s edge, the menu repositions to remain visible.

Add to folder field with selected chips; multiselect dropdown checklist with Bookmarks and Trading cards checked; Sell these, My Idols, Sci‑Fi unchecked.

Height

The height of the filter menu container can flex with its contents. By default, the container flexes to show up to 9 options plus half of the tenth option.

For example, if the rows are 48px tall, then 24px of the tenth option is visible from the bottom of the container.

Menu height guidance showing options 1–10 and a pink indicator for bottom padding equal to row height × 0.5.

Scrolling

Filter menus scroll when the content extends beyond the height of the menu. A scroll bar appears when scrolling to indicate the length of the list.

Menu list with many options and a vertical scrollbar, indicating content extends beyond the visible area.

Width

Filter menus triggered by a text field should match the field width. Filter menus triggered by filter chips default to a width of 160px.

Menu width comparison: wide multiselect dropdown under Add to folder and a narrower Actions menu with Add to list, Remove from list, Add note, Report.

Dismissing

Filter menus are dismissed when:


  • Selecting a single-select value
  • Interacting with a submit button
  • Interacting with another element on the page
  • Pressing the Escape button on a keyboard
  • Pressing the hardware back button on an Android device
Menu interaction showing tap ripple on Remove from list and a second tap outside the menu to dismiss.

Text overflow

Menu item labels and descriptions wrap to a new line when extending beyond the width of the menu container.

Menu with multi‑line labels demonstrating text overflow; “Price: Lowest to highest” selected; includes price and duration sort options.

Native sheets

Native apps can use a context sheet if the list is long or includes layouts that aren’t supported by the native menu components.

If an interaction asks the user to slow down, scan a list, compare options, or make a more considered choice, a sheet should be used.

Create event screen with a bottom sheet overlay listing categories: Art prints, Bags, Collectibles, Electronics, Furniture, Luxury, Sneakers.

Platforms

Android

Menus on Android use the Evo popover menu. Form and filter selections can use a context sheet for longer lists.

Two Android mobile screens: eBay item page with overflow popover menu of actions; and search results showing a Condition bottom sheet with checkboxes and a Show 290,000+ results button.

iOS

iOS devices use a native menu for actions. Form and filter selections can use a context sheet for longer lists.

Two iOS mobile screens: eBay item page with overflow popover menu of actions; and search results showing a Condition bottom sheet with checkboxes and a Show 290,000+ results button.

Web

Web uses the popover menu across screen sizes.

Web layout showing a menu anchored to the top‑right; actions include Unwatch this item, Sell one like this, Share, and Help & Report

Best practices

Keep labels short

Do use clear, short, action-oriented labels.

Filter menu with radio options: Add to list, Remove from list, Add note, Report; none selected.

Don’t use unnecessarily long or vague labels.

Menu with longer labels: Replace the selected item, Generate new content with AI, Edit this item, Remove this item.

Native app menus

Do use a bottom sheet if the list includes interactive items that aren’t supported by the native menu components like checkboxes.

Bottom sheet on search with checkboxes: New with box and New without box selected; New with defects and Pre-Owned unselected; blue button “Show 290,000+ results”.

Don’t include interactive items in a popover menu on native platforms.

Popover anchored to filter on search: New with box and New without box selected; New with defects and Pre-Owned unselected; menu overlays results grid.

Web menus

Do present menu items in a popover menu across screen sizes.

Category menu listing Art prints, Bags, Collectibles (selected), Electronics, Furniture, Luxury, Sneakers, Toys, Vintage watches; Update button beneath.

Don’t use a modal element for menus on web, even on smaller screens.

Category selection modal under field; items include Art prints, Bags, Collectibles (checked), Electronics, Furniture, Luxury, Sneakers, Toys, Vintage watches.

Leading selection control types

Do use radio buttons when the user should only select one option from a set.

Two dropdowns: Add to folder multiselect with checkboxes (Bookmarks and Trading cards selected; Sell these, My Idols, Sci‑Fi unselected) and Frequency radios with Weekly selected.

Don’t use radio buttons when the user can select multiple options from a set. Instead use checkboxes.

Add to folder dropdown with checkboxes; Bookmarks and Sci‑Fi selected; divider above footer actions View all folders and Help.

Specs

Menu spacing diagram showing 16px margins and padding; list with leading icons and trailing checkmark on Item 1.