I'm working on an application where it requires filtering and sorting. Typically, these two functionalities, albeit similar, are always separated.

However, I came across this article today where they are combined - https://medium.com/@reddexperience/ux-design-patterns-6-search-sort-and-filter-sorted-913a3ce1e160

It's understandable in the sense that both functionalities are aiming to achieve one outcome - to display relevant results. But changing "Filter" to a different label makes the most sense.

enter image description here

With all that said, should filtering and sorting functionality still remain separate?

  • Important topic. You wrote, "...these two functionalities [sorting and filtering], albeit similar..." — Let's elaborate. What is similar about sorting and filtering? Feb 16, 2023 at 0:11
  • I elaborated in the post in case you missed it - Similar in the sense that the user's goal is to display results relevant to them.
    – J Bo
    Feb 16, 2023 at 3:13
  • "...display relevant results." I see, similar in purpose. I was thinking similar in functionality, in which, of course, they're distinctly different. Feb 16, 2023 at 9:09

2 Answers 2


...where [filtering and sorting] are combined...

For clarification, combined here means both functionalities are presented on the same page and linked under a single button labeled "Filters".

With that presumption in mind...

...both...achieve one outcome - to display relevant results.

...should filtering and sorting functionality still remain separate?

Since they serve the same purpose they cognitively work well presented together, as in the example provided. (Some reasons to put each on separate pages or modals might be due complexity of one or the other, or user testing demonstrating UX improvement doing so.)

Does "Filters" describe sorting and filtering?

Asked another way, does "Filters" cognitively prepare people for filtering and sorting functionality?

It does. Here's why...

The linked article describes filtering as determining if an item is included or excluded from the list—essentially removing items from the list. And describes sorting as altering the sequence of the list.

Keep in mind, all lists are sequenced...sorted. The default sequence may or may not be explicit. If not purposely sorted by designers or programmers the list is likely sorted by entry into the storage mechanism...a database, a text file. Or, due to the underlying retrieval mechanism or protocol, a random sequence.

What this means is "Sorting" is a means to alter the sequence of the list. And "Filtering" is a means to reduce the number of items in list.

  • Filtered lists are sorted.

  • Sorted lists are not filtered.

Because sequence is inherent to lists people are not surprised or confused to see a sorting operation on a list filtering page.

As a side note, not mentioned in the question, but mentioned in the article, searching also serves the same purpose—display relevant results—AND the same functionality as filtering—reduce list results, so, generally, grouping searching, filtering, and sorting functions together on a separate page, modal, or "tool" can be an effective way to simplify a list interface.


As they say: testing, testing and more testing. This is a great example of when exactly the user will be able to tell which option is more convenient for him to use. You need to create different scenarios for his path and see how he copes with it.й

Just answer: this is better in such cases and this in others, this will be a tricky answer, since both types have the right to life and only the user will be able to answer you

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.