WebAnts

Framer CMS · Troubleshooting Guide · 12 min read

Framer CMS not filtering or sorting correctly: five common mistakes.

Broken Framer CMS filters and wrong sort orders almost always trace back to five root causes: a field type that cannot be filtered reliably, a missing Collection List binding, pagination that only works on Framer's own hosting, the wrong field type for dates and numbers, and variable scope set at the wrong level. This guide covers all five with exact fixes.

By WebAntsPublished November 2026WebAnts is a Framer development agency in London. 4.9★ on Google & Clutch.
WebAnts is a London web design and development agency specialising in Framer website development. This article covers Framer CMS filtering and sorting issues commonly encountered by designers and developers building with Framer in 2026.

1. Why Framer CMS filtering and sorting breaks

WebAnts is a London-based Framer website development agency. We use Framer CMS on client projects — portfolios, directories, resource libraries, and marketing sites where the team wants to publish and filter content without developer involvement. We have encountered every Framer CMS filtering and sorting problem in this guide at least once, usually handed to us after another designer or developer set up the CMS and left.

Framer CMS is well-designed for its intended use case: structured content that a non-technical editor can manage, displayed through Collection List components, with basic filtering and sorting in the Framer canvas. Its limits are not hidden — they are architectural. Filtering in Framer CMS works correctly only when the data model and the variable binding chain are set up in a specific way. Miss one of the five steps below and either nothing works, or it works in the preview but not in production.

The problems in this guide are not random bugs. Each one has a specific cause rooted in how Framer CMS handles field types, variable scope, and the difference between dynamic hosting and static export. Understanding the architecture makes the fixes obvious. The five mistakes below, in order of how often we encounter them in projects handed to us for review.

2. Five mistakes — and their fixes

Each mistake below includes what causes it, why it is easy to miss, and the specific steps required to fix it. The fixes are ordered by impact — mistakes 1 and 2 together account for approximately 80% of broken Framer CMS filter setups in projects we inherit.

01

Using a plain text field instead of a Reference field for categories and tags

The wrong field type makes filtering unreliable by design — not by accident.

Framer CMS has a "Link" field type (also called a Reference field) specifically designed to connect items across collections. When you want to filter blog posts by category, the correct architecture is: a separate Categories collection with a Name field, and a Link field in Blog Posts that points to that collection. What most users do instead is create a plain text field called "Category" and type values like "Design", "Development", "Marketing" directly into it.

This works visually — the category text appears on cards. But Framer's Collection List filter performs an exact string match, and plain text fields introduce two failure modes: inconsistent capitalisation ("design" vs "Design") and multi-value entries ("Design, Development" that can never match a single filter value). The filter control reads the linked collection's item IDs, not strings — a text field comparison will either never match or match incorrectly.

The fix is to rename the existing text field, create a dedicated Categories (or Tags) collection, and replace it with a Link field. For items that belong to multiple categories simultaneously, use a Multi-link field rather than a Link field — Multi-link allows one blog post to be associated with several category items at once, and Framer's filter handles this correctly.

The fix

Create a separate CMS collection for each taxonomy (Categories, Tags, Industries). Use "Link" for single-value and "Multi-link" for multi-value associations. Never store filterable values as comma-separated text in a single field.

02

Setting the filter variable on the button — but not binding it on the Collection List

The variable chain has three links. Users consistently forget the third one.

Framer's filtering system is built on a three-component chain: a filter control sets a variable, and a Collection List reads that variable to determine which items to display. All three must be explicitly connected. The step that is skipped almost universally is connecting the Collection List to the variable.

Here is what the setup looks like in Framer's right panel. You add a Collection List and connect it to your CMS collection. You add filter buttons or a Segmented Control component. You create a string Variable to hold the active filter value. You bind the filter buttons so that clicking them sets the variable. Then — and this is the missed step — you open the Collection List's properties, find the Filter section, and bind it to read the variable.

Without that final binding, the Collection List has no idea the variable exists. It renders all items unconditionally. The buttons fire, the variable changes, nothing happens on screen.

The quickest diagnostic in Framer's Preview mode: open the Variables panel (or add a text layer bound to the variable value). Click a filter button and confirm the variable value changes in the panel. If it does, the problem is on the Collection List side — go to the list's settings and check the Filter binding. If the variable is not changing, the button binding is missing.

The fix

After binding filter buttons to set the variable, open the Collection List component settings → Filter → bind to the same variable. Without this step, the Collection List ignores all variable changes.

03

Expecting pagination to work on a static HTML export

Framer CMS pagination is a server feature. Static files have no server.

Framer gives you two ways to publish a site: use Framer's hosting (the default, publishing to framer.app or a custom domain via Framer), or export the project as static HTML and deploy it yourself elsewhere — Netlify, Vercel, GitHub Pages, or any file server.

The difference matters for CMS pagination. When hosted on Framer's infrastructure, collection pages are rendered server-side: the "Next page" button triggers an API call to Framer's servers, which returns the next batch of CMS items. The page updates without a full reload, and your visitors never wait for all items to load at once.

When you export as static HTML, Framer generates a flat set of HTML files. Those files do not include the client-side code that calls Framer's pagination API, because there is no Framer server to call. What you get is the first page of items — typically 10, whatever your "Items per page" setting is — and pagination controls that either do nothing or throw a network error when clicked.

This is not a bug. It is a documented architectural constraint. Framer's static export is designed for sites where all content can be rendered at build time. CMS pagination is a dynamic feature that requires a runtime.

The three options: (1) use Framer's native hosting; (2) on static export, increase "Items per page" to a number larger than your total item count so everything renders on one page, and remove the pagination UI; (3) replace Framer's native pagination with a custom Code Component that loads all items upfront and handles pagination entirely in component state.

The fix

If you are exporting to a non-Framer host, do not use Framer's built-in pagination. Set "Items per page" above your total item count, or implement pagination as a Code Component that slices a client-side array.

04

Storing dates and numbers as text fields, then sorting by them

Framer sorts text alphabetically. Text fields do not know what a date or number is.

Framer CMS supports dedicated Date and Number field types. Sorting on these fields uses the actual timestamp or numeric value respectively. Text fields sort alphabetically — which means the sort order depends entirely on how the text happens to be formatted, not on its semantic meaning.

The date case is the most common and most confusing. If you have a "Published" text field containing values like "2026-11-15", "2026-02-01", "2026-08-20", sorting descending by this text field will give you the right answer purely by coincidence — ISO dates in YYYY-MM-DD format sort identically alphabetically and chronologically. But if you switch to "November 2026", "February 2026", "August 2026" for display reasons — which is a common aesthetic preference — alphabetical sorting gives you: August, February, November. That is not chronological order and it will never be fixed by adjusting the sort direction, only by changing the field type.

The same issue affects number sequences. If you create a "Sort order" text field with values "1", "2", "3", "10", "11", text sort gives you: 1, 10, 11, 2, 3. The leading zero workaround ("01", "02", "03", "10", "11") works up to 99 items but fails at 100. Use a Number field.

The migration path is not automatic. Framer will not convert the values in an existing text field when you change its type — you will need to re-enter or paste the values after creating a new Date or Number field.

The fix

Use the "Date" field type for any field you intend to sort chronologically. Use "Number" for any numeric sequence. Do not use text fields as proxies for typed data — the sort behaviour is alphabetical regardless of content.

05

Scoping filter variables at page level when they should be component-level

A page-level variable is shared across everything. That causes two distinct failure modes.

When you create a variable in Framer, its default scope is the page — meaning every component on that page can read and write it. For simple setups with one Collection List and one set of filter buttons, this works. For more complex layouts, page-level variable scope introduces two specific problems.

The first problem is cross-contamination. If you have two Collection Lists on the same page — say, a Blog Posts list and a Case Studies list — and both are bound to the same page-level filter variable, clicking "Design" in the blog filter also applies "Design" to the case studies list. The two lists share the variable and cannot have independent filter states.

The second problem is state loss on navigation. In Framer's SPA routing, navigating from a page and returning causes the page component to re-mount. Page-level variables re-initialise to their default value on mount — so the filter state the user set before clicking into a CMS detail page is gone when they return via the back button. This is frustrating for browsing-heavy sites like portfolios, blogs, or directories.

Both problems have the same fix: scope the variable to the component, not the page. In Framer, this means creating the variable inside the Collection List component itself (a "component variable" rather than a "page variable"). Each Collection List then has its own isolated filter state that does not interact with others on the page.

For filter state that should persist across navigation — a directory with complex multi-faceted filtering, for example — the correct approach is to store the active filters in the URL query string using Framer's URL variable support. The URL is preserved on back-navigation, so the filter state is restored when the page re-mounts and reads from the URL.

The fix

Create filter variables at component scope, not page scope, to isolate filter state per Collection List. For filter state persistence across page navigation, bind filters to URL variables rather than in-memory state.

3. Diagnosing your specific issue in under 5 minutes

If you are unsure which mistake applies to your project, this four-question sequence isolates the cause in almost every case.

Do filter buttons appear to respond but the list does not change?

This is Mistake 2. The variable is being set, but the Collection List is not bound to it. Open the Collection List → Properties → Filter, and bind it to the variable your buttons are setting. Confirm the binding by watching the Variables panel in Framer Preview — the variable value should change on click.

Do filters work in Framer Preview but not on the published/exported site?

Two possibilities: if you are using static export, pagination is the cause (Mistake 3) — the first page renders, the rest do not. If you are using Framer hosting and published the site, check whether the variable is a page-level variable that is resetting on page mount (Mistake 5). Open the site, set a filter, reload the page — if the filter resets, it is scope related.

Do items sort into the wrong order even when the sort direction is correct?

This is Mistake 4. Check the field type in Framer CMS. If the field you are sorting by is a "Text" type, Framer is sorting alphabetically regardless of the values it contains. Create a new "Date" or "Number" field, re-enter the values, and sort on the new field.

Do filters work for single-value selections but break for multi-value or combined filters?

This is Mistake 1. Your category or tag field is likely a plain text or single Link field rather than a Multi-link field connected to a separate collection. Text-based multi-value filtering is not reliable in Framer CMS. Restructure the data model to use a Multi-link reference field.

If the above questions do not identify your issue, the problem is likely in the CMS collection structure itself — field names do not match the bindings in Framer canvas, or a collection was duplicated without updating the references. The fastest way to confirm: in Framer canvas, select the Collection List component and check the Property panel. Every CMS field binding shown there should reference an existing field in the connected collection. Any binding that shows a warning icon or is blank is a broken reference.

4. When native Framer CMS filtering is not enough

Framer's native filtering handles a well-defined set of requirements: filter a single Collection List by one field, sort by one field in one direction, paginate with simple previous/next controls. For requirements beyond this, the native system reaches its limits and a Code Component is the right architectural choice.

Multi-faceted filtering (filter by two or more fields simultaneously)

Framer's Collection List filter binds to one variable at a time. If you need to filter by Category AND Industry AND Date range simultaneously — with each filter narrowing the results — you need a Code Component that accepts the full item list from a CMS variable and applies compound filter logic in React state. This is a significant build, but it is the only reliable architecture for complex directory or search-and-filter interfaces on Framer.

Full-text search across CMS fields

Framer does not have a native free-text search component that queries CMS fields. If your site needs a search input that finds items by keyword across title, description, and tag fields simultaneously, the options are: a Code Component implementing client-side fuzzy search (Fuse.js is a common choice) over the full collection fetched upfront, or an external search service (Algolia, Typesense) with a custom Code Component as the UI layer. Neither is a Framer CMS feature — both require code.

Collections with more than a few hundred items

Framer CMS fetches items in pages. For small collections this is invisible. For large collections — job boards, property listings, product catalogues — fetching all items for client-side filtering is inefficient, and Framer's native pagination is the only server-side option. If your content volume makes client-side filtering slow and server-side filtering is unavailable on your chosen host, Framer CMS is likely the wrong CMS choice for that use case. A headless CMS (Contentful, Sanity) with a custom Next.js front end handles large-collection filtering with server-side queries significantly better.

For filtering requirements that go beyond Framer's native system, our Framer development service includes Code Component builds for custom search, multi-faceted filtering, and complex CMS architectures. We also advise on whether Framer CMS is the right tool for a given content model — sometimes the honest answer is that Webflow or a headless architecture serves the brief better.

5. Frequently asked questions

Common questions about Framer CMS filtering, sorting, and pagination.

Why is my Framer CMS filter not working?+

The most common cause is a missing Collection List binding. The variable your filter buttons are setting must also be bound to the Collection List's Filter property. Open the Collection List component settings and confirm the Filter is wired to the same variable. If the Filter is unbound, the list ignores all variable changes.

Why is Framer CMS sorting in the wrong order?+

Framer sorts text fields alphabetically. If your sort field is a Text type containing dates like "November 2026" or numbers stored as strings, the alphabetical sort will not match chronological or numeric order. Change the field type to Date (for dates) or Number (for numeric sequences) — then sorting uses the actual value.

Why does Framer CMS pagination break on static export?+

Framer's built-in pagination makes server-side API calls to Framer's hosting infrastructure. Static HTML exports do not include this — there is no server to call. On a third-party host, the first page of items renders correctly and pagination controls stop working. Use Framer's native hosting for pagination, or implement client-side pagination in a Code Component.

How do I set up multi-reference filtering in Framer CMS?+

Create a separate collection for your taxonomy (Categories, Tags). In your main collection, add a Multi-link field that references the taxonomy collection. In Framer canvas, bind filter buttons to taxonomy collection items and bind the Collection List filter to the same variable. Using plain text fields for filterable categories is the most common mistake.

How do I fix Framer CMS filter state resetting on navigation?+

Page-level variables re-initialise when the page component re-mounts. To fix: scope filter variables to the Collection List component (component-level variable), or bind the filter to a URL variable so the active filter is stored in the URL query string and survives navigation.

WebAnts · London Framer Agency

Framer CMS problems you cannot fix yourself? We can.

WebAnts builds and repairs Framer sites in London — custom CMS architecture, Code Components for complex filtering, and fixes for broken setups inherited from other developers. Free 30-min call, flat written quote, no deposit.