Use a filter input to allow users to limit the number of visible items in a list. For example, the experiment overview tab filters to the substring that matches the experiment name and description.

Filter on the experiments overview tab.

Best Practices

Filter inputs should include placeholder text that indicates which strings are being matched (name; description; type; etc.). For example, "Filter by name". The list being filtered should update instantly as a user types.

Filtering vs. Searching

Filtering differs from searching in two ways: first, no data outside of the current set of items is available when filtering; and second, filtering is reductive, meaning it only ever makes the current set show fewer items. Searching would show an unknown number of new items, presumably from sources not readily visible.


Filter inputs can optionally provide a dropdown for selecting the scope of the current filter, such as just "Active" or "Archived" experiments. Changing the scope limits the items in the list to only those that match the selected type. For instance, in the screenshot above only "Active" campaigns are being filtered.