Enable Tabs Filtering for CMS Without Requiring Relational Collections
R
Ryan K
Currently, the Tabs filtering feature for CMS content only works when relational collections are enabled. This creates an unnecessary barrier for simpler use cases, especially for portfolio-style sites that don’t require full relational CMS structures.
In my case, I needed to display categorized content from a CMS list, but without relational collections, the Tabs filtering wasn’t usable. The workaround involved creating multiple variants to simulate filtering, which significantly increases complexity, maintenance overhead, and build time.
This effectively forces users into upgrading to higher-tier plans or relying on third-party tools just to achieve what feels like a basic filtering interaction. For smaller projects or single-page portfolios, this pricing and structural dependency feels disproportionate to the feature being used.
Suggested improvement:
Allow Tabs filtering to work with non-relational CMS collections, or introduce a limited version of the feature that supports simpler datasets. Alternatively, increasing the number of collections allowed per page on lower-tier plans would make this functionality more accessible without requiring a full upgrade.
This would reduce friction for smaller clients and independent creators, while still preserving the value of advanced CMS capabilities for larger-scale use cases.
Log In
Autopilot
Merged in a post:
Tabs (Dynamic Filter) in CMS for basic plans
P
Piyush Kumar
Currently, implementing tab-based filtering with CMS content becomes difficult or not feasible on paid plan (basic) due to collection limitations. This is confusing because the free plan allows more flexibility with multiple collections, which makes tabs easier to implement.
From a UX perspective, tabs provide clear visibility of all options upfront, while dropdowns hide options and add friction. This limitation forces a compromise on user experience rather than just design preference.
Upgrading to a paid plan should ideally unlock more flexibility, not restrict core use cases like this. It would be helpful to either remove this limitation or provide a better way to implement tab-based filtering with CMS content.
R
Rhys Merritt
I did just figure out a pretty simple workaround for this. It still requires the creation of at least ONE categories collection though, so I think your request is still very valid.
The workaround for my case was to have all categories as part of the one mega category collection, and I can just add a 'sub-category' filter, and when using the referenced collection to create the tab filters on a list of CMS items, I filter the tab filter by sub-category.
R
Rhys Merritt
Wholeheartedly agree with this. I'm working on a clients site right now that has 3 collections which need to be filtered. To allow a decent experience filtering those collections on their respective pages I need to create 6 collections - this would put them over the 10 collection limit for a Pro plan and significantly increase their monthly cost to a point they are not comfortable with.
It seems very silly that the ability to have usable, tab format filtering on collections is pushing people to higher payment tiers.