Most merchants asking this question assume the answer is a workaround. It is not. Shopify's native filtering is free, it is properly built, and for a large number of stores it is genuinely enough. The reason merchants end up paying is rarely that free filtering could not do the job. It is that nobody set it up properly.
So before you compare pricing pages, set up what you already have. It costs nothing but your time, and it will tell you far more about whether you need to pay than any app listing will.
What you actually get for free
Shopify's filtering lives in the Search & Discovery app, which is free to install from the Shopify App Store. Everything below is included at no cost on any plan.
The six standard filters
Every store can use filters for Availability, Category, Price, Product type, Tags, and Vendor. These require no setup beyond having clean product data. If your products have accurate types and vendors, several useful filters are one click away.
Custom filters from your own product data
This is where the real capability sits. You can build filters from:
- Product options, such as the Size or Colour options already on your variants
- Product metafields, which apply across all products in the store
- Category metafields, which apply to specific product categories
- Variant metafields, for attributes that differ between variants of the same product Metafield filters support single line text, text lists, decimals, integers, true/false values, and metaobject references. That covers almost any product attribute a merchant would want to filter on — fabric, wattage, scent, dietary flag, compatibility, room type, whatever your catalogue needs.
You can create up to 25 filters in total, combining standard and custom ones. Each source can only be used once, so if Price is already active, it cannot be selected again for a second filter.
Colour swatches and image filters
Visual swatches used to be one of the clearest reasons to buy a filter app. They are now free. Using a metaobject reference with a colour field or an image field, you can render actual colour swatches and pattern images in your filter dropdowns, provided your theme supports the filter value API.
There is also automatic grouping for standard product attributes. If your Colour filter contains Light red, Burgundy and Ruby, Shopify can group them under a single Red value without you configuring anything.
How to set up free filters properly
Check your theme first
Filters only display if your theme supports storefront filtering. Any current Online Store 2.0 theme does. If yours does not, you can still create filters in the app, but customers will never see them — which is exactly the kind of silent failure that convinces a merchant the free tools are broken when they are not.
You can check by going to Content, then Menus in your admin. If your theme does not support filtering, a message appears in the Collection and search filters section.
Fix your product data before you touch the app
This is the step almost everyone skips, and it is the one that decides whether your filters are any good.
Filters are generated from the data on your products. A filter value only exists if at least one product in that collection carries it. So if half your products have the material recorded and half do not, your material filter will quietly hide products from customers who use it. A shopper filtering for cotton will never see the cotton shirt where nobody filled in the field.
Before creating a single filter, audit:
- Which attributes are actually populated across your catalogue, and how consistently
- Whether option names match exactly across products, since "Color" and "Color:" are treated as different things
- Whether the same value is spelled multiple ways, since Oak and oak become two separate filter options The Bulk Editor is free and is the fastest way to fix this at scale. The same underlying data drives your search results, so it is worth working through how to improve your store's search results at the same time rather than treating the two as separate jobs.
[YOUR STORY: a short, specific example of a catalogue you cleaned up before filtering — what state the data was in, what you changed, and what improved. Two or three sentences is plenty.]
Choose metafields over tags
If you take one thing from this post, take this. Tags are the intuitive choice and the wrong one for most filtering.
Tags are case sensitive, have no enforced data type, accumulate inconsistencies as your team adds them, and are often already being used for other jobs like collection conditions and admin filtering. Turn tags into a customer-facing filter and every internal label you ever created leaks onto your storefront.
Tags also break in multiple languages. Shopify's documentation is explicit that the product tag filter only displays to customers shopping in your store's default language, and tag values cannot be translated. If you sell internationally, a tag-based filter is invisible to most of your customers.
Metafields have strict types, stay consistent, translate properly, and let you expose only the values you want shown. Shopify itself recommends using a single line text or list metafield instead of the tag filter when you need control over displayed values.
Tags are fine for temporary merchandising labels like Sale or New. For anything structural, use metafields.
Create and refine the filters
In the Search & Discovery app, go to Filters, click Add filter, and select your source. Then do the parts most merchants ignore:
- Rename the filter to language your customers use, not your internal field name
- Group similar values so shoppers see Black rather than Onyx, Ebony and Midnight as three options
- Set the sort order, since manual sorting matters for anything that is not alphabetical
- Handle empty values, either hiding them or pushing them to the bottom, so shoppers stop clicking options that return nothing
- Choose the logic for tag and list filters, where you can switch values from OR to AND Then drag the filters into priority order. With a cap of 25, and shopper attention far lower than that, the ordering is a merchandising decision.
The free technique most merchants never use
Applied filters are reflected in the URL, and those URLs are stable and linkable. That means you can create pre-filtered landing pages for free, without creating a single extra collection.
The structure is straightforward:
/collections/all?filter.p.product_type=shoes/collections/all?filter.v.option.color=red/collections/all?filter.p.m.custom.made_in=canadafilter.v.price.lte=50for a price ceiling You can combine them, and you can pass multiple values to one filter with commas.
Put these URLs directly in your navigation menu. A "Shop by" menu with entries like Under £50, Waterproof, or Made in Canada now behaves like a curated category without you building and maintaining dozens of collections. For a merchant with no budget, this is the highest-leverage free move available, and it takes minutes.
One caution: be deliberate about which of these you link to and whether you want them indexed. Filtered URLs multiply fast, and an unmanaged sprawl of near-duplicate filtered pages is a genuine SEO problem. Link the handful that map to real customer intent. Leave the rest to the filter widget.
What free filtering actually costs
Free filters are free in money, not in effort. The cost is data work, and it is front-loaded.
Defining metafields, assigning values across a catalogue, standardising spelling, grouping values and testing on mobile is real work. On a small catalogue it is an afternoon. On several thousand SKUs with inconsistent history, it is considerably more.
This is worth saying plainly because it changes the comparison. The honest question is not free versus paid. It is your time versus a monthly fee. Some merchants should absolutely spend the afternoon. Others have a more valuable use for that afternoon, and paying is the rational choice even when native filtering could technically do the job.
Either way, you cannot skip the data work. No paid app fixes a catalogue where nobody recorded the material.
Where free filtering stops working
These are the specific ceilings. They are documented, not opinion, and they are the honest answer to when free stops being enough.
Collections over 5,000 products do not display filters at all. Not degraded — absent. Shopify's own recommended fix is splitting large collections into smaller ones, which for some catalogues is sensible structure and for others is an unworkable amount of maintenance.
A single filter displays a maximum of 100 values on your storefront. Beyond that, values are simply not shown. If you sell auto parts and have 400 compatible models, shoppers cannot see most of them, and nothing on the page tells them so. This is the failure mode I would watch for most closely, because it is invisible from the admin.
Search results over 100,000 products do not display filters.
Tags cap at 5,000 unique values, and product options and attributes at 1,000.
Re-indexing is not instant. When you add new metafield values, Shopify's own troubleshooting advice is to wait 24 to 48 hours for automatic re-indexing, or force it by making a trivial edit to the product, such as adding a space to the title and saving. That is the official guidance, and it tells you something about where this tool sits. If your catalogue changes daily, or you run frequent bulk updates, that lag becomes an operational problem rather than a curiosity.
The price filter does not display in any currency other than your store's default. If you sell into multiple markets, a large share of your customers lose price filtering entirely.
There are no filter analytics. You cannot see which filters shoppers use, which combinations return nothing, or where they abandon. You are merchandising without instrumentation, which is workable on a small catalogue and increasingly costly on a large one.
[YOUR STORY: a merchant who hit one of these specific walls. Which limit, how it showed up in their store, and how they found out. The 100-value cap or the 5,000-product collection limit make the strongest examples because both fail silently.]
My honest opinion on when to pay
We build a paid filtering app, Hyper Search & Filter, so treat this section with appropriate scepticism and judge it on the reasoning rather than the source.
My view is that most stores asking this question should not pay yet. If your catalogue is under a few thousand products, sits in reasonably sized collections, sells in one currency, and has attributes that fit comfortably under 100 values, native filtering set up properly will serve your customers well. Paying for an app on top of that adds cost and a dependency without solving a problem you have.
The point to reconsider is not a catalogue size or a revenue number. It is when you can name a specific thing filtering is failing to do, and you have already ruled out the data being the cause. Concretely: your collections exceed the product ceiling, or a filter needs more values than the storefront will display, or you need to see how customers are actually using filters, or your merchandising team needs control the native tool does not offer, or the indexing lag is costing you sales during bulk updates.
If none of those describe you, stay native. There is nothing embarrassing about a store running well on free tools, and a lean app stack is an asset rather than a compromise.
If one or more of those do describe you, then you are no longer shopping for features, you are solving a defined problem — and you can compare what Hyper Search & Filter does against that specific gap rather than against a feature list.
[YOUR OPINION: one or two sentences of your own here, in your voice — a position you hold about filtering, apps, or merchant spending that you would defend if challenged. This is the part readers will remember.]
Common questions
Do I need to pay for Shopify filters?
No. Shopify's Search & Discovery app is free and provides standard filters, custom filters from product options and metafields, colour swatches, value grouping and sorting. Most stores can build a strong filtering experience without spending anything.
Can I filter by colour swatches for free?
Yes. Visual swatches are available at no cost using a metaobject reference with a colour or image field, as long as your theme supports the filter value API.
Why are my filters not showing up?
The most common causes are a theme that does not support storefront filtering, a collection containing more than 5,000 products, filtering switched off in the collection template settings, or product data that has not been re-indexed yet.
Should I use tags or metafields for filtering?
Metafields, for anything structural. Tags are case sensitive, untyped, do not translate, and only display to customers shopping in your store's default language. Keep tags for temporary merchandising labels.
How many filters can I have?
Up to 25 in total across standard and custom filters, and each filter source can only be used once.
Start free, and let the data tell you when to move
Set up native filtering properly. Fix the product data, use metafields rather than tags, group your values, and add a few pre-filtered URLs to your navigation. Then watch what customers do.
If shoppers are finding products and your collections sit inside the documented limits, you have your answer and it cost you nothing. If you hit a specific ceiling, you will know exactly which one, and you will be evaluating apps against a defined problem rather than a feature list.
That is the right order. The mistake is not paying for filtering. It is paying before you know what you needed.
