Do I need search if users can just use filters?

Not always—but in most products, filters and search solve different problems, so the best answer is usually “it depends on the size, variety, and user intent.”

Use filters alone if:

• Your dataset is small and well-structured
• Users already know the category they want
• The number of options is limited enough to browse quickly
• The main task is narrowing a list, not finding something specific

Example: a simple job board with filters like location, role type, and salary.

Add search if:

• Users may know a name, keyword, SKU, title, or phrase
• The dataset is large
• Content is messy, varied, or frequently changing
• Users often want to jump directly to a known item
• Filters would require too many steps or guesswork

Example: an ecommerce catalog where users might type “black running shoes” or search for a brand name.

Why search still matters even with filters:

Filters are good for exploration. Search is good for precision.
A lot of users don’t want to browse through all the filter combinations just to find one thing.

Best practice:

If you can, provide both:

• Search for direct lookup
• Filters for narrowing and discovery

A common pattern is:

• search bar at the top
• filters as refinements below or beside results

Rule of thumb:

If users ever say things like:

• “I know what I’m looking for”
• “Can I just type it?”
• “There are too many results”

…then you probably need search.

If you want, I can help you decide for your specific product by looking at:

• what users are searching for,
• how many items you have,
• and what your filters currently are.