When Should You Split a Webflow CMS Collection in Two?

When Should You Split a Webflow CMS Collection in Two?

When the items in it need different fields, different templates or different URLs. Not when it simply has a lot of items. Size is the reason teams give, but shape is the reason that actually matters, and the two get confused constantly.

We inherit a lot of Webflow sites, and the CMS is where the structural mistakes live. A collection called Resources holding blog posts, case studies, webinars and whitepapers is the single most common thing we find, and it is usually the reason the site is hard to change.

Here is how we decide, and how we do the split without breaking the live site.

What Problem Is Splitting Actually Solving?

Ambiguity. A collection is a contract that says every item in here is the same kind of thing. When that stops being true, every part of the system gets harder: the fields, the template, the filters, the URLs and the person entering content.

You can see the symptom in the editing experience first. If half the fields are blank on half the items, the collection is describing two kinds of thing. The blanks are not a data quality problem, they are a modelling problem showing through.

The cost lands on whoever maintains it later. Our guide to content modelling for a CMS covers the general principle. This piece is the Webflow-specific version of the same decision.

What Are the Signs a Collection Is Doing Two Jobs?

Four signs, and any one of them is enough to start the conversation. Fields that only apply to some items. A template full of conditional visibility rules. An Option field that quietly acts as a type selector. And a URL structure that reads awkwardly for at least one kind of item.

The Option field one is the clearest tell. Webflow documents Option as a field where you create predefined choices with unique IDs and pass the option's ID as a string when writing. If your Option field is named something like Content Type, it is not describing a property of the thing. It is naming what the thing is.

Conditional visibility is the second tell, and it is sneaky because it works. A template with a dozen conditions renders fine and is almost impossible to reason about. Every future change has to be checked against every branch.

The rule we use is simple. A property varies between items of the same kind. A type decides which kind an item is. Properties belong in fields. Types belong in collections.

Does Item Count Alone Justify a Split?

Rarely, and usually not for the reason people think. A large collection of genuinely identical items is fine and splitting it by an arbitrary boundary such as year or region creates duplicate templates you now have to keep in sync.

Where size does start to matter is in how you read the data. Webflow's API for listing collection items uses offset-based pagination with a documented maximum limit of 100 records per request. A collection of five thousand items is fifty requests, every time something needs the whole set.

Those requests sit against a rate limit. Webflow documents 60 requests per minute for Starter and Basic sites and 120 for CMS, eCommerce and Business sites, with Enterprise custom. Fifty requests is a meaningful share of a minute's budget, so a large collection changes how any integration around it has to be built.

That is an argument for better filtering and caching, not for splitting. Only split on size if the items were different kinds anyway. Our piece on managing large Webflow CMS collections covers the size problem on its own terms.

How Do Reference Fields Change the Answer?

They are what makes splitting cheap rather than destructive. Webflow documents a Reference field as holding a single item ID as a string, and a Multi-Reference field as holding an array of item ID strings, both linking items across collections.

That means a split does not have to lose relationships. If your Resources collection currently uses a plain text field for Author, splitting is the moment to make Author a real collection and reference it. The same applies to Topic, Industry, Product and anything else that repeats.

Webflow's documentation does not state a limit on how many items a Multi-Reference field can hold, so we would not design around an assumed ceiling in either direction. Test the shape you actually need rather than trusting a number someone repeated in a forum.

The practical point is that the choice is not one collection versus many isolated ones. It is one overloaded collection versus several focused ones joined by references. Our guide to Webflow reference fields covers the mechanics.

What Do the API Limits Tell You About Structure?

More than you would expect, because they reveal what Webflow expects a collection to be. Listing items supports up to 10 filter terms and 2 text-search terms per request, with filters combined using AND logic and operators including eq, ne, gt, gte, lt, lte, in, nin, contains, ncontains and exists.

Sorting is similarly bounded. Basic sorting uses sortBy across createdOn, lastPublished, lastUpdated, name and slug, with an ascending or descending order. Custom field sorting supports up to three fields and only applies to PlainText, Email, Phone, Number, DateTime and Switch field types.

Read that list against your own collection. If the thing you most need to sort by is a Rich Text or Reference field, sorting is not available to you, and no amount of splitting fixes that. The fix is adding a sortable field that encodes the order you need.

Ten filter terms is generous for a focused collection and tight for an overloaded one, because an overloaded collection spends filter budget just isolating the type before it can filter on anything useful. That is the API telling you the same thing the blank fields were.

When Should You Merge Instead?

When two collections have nearly identical fields and identical templates. Over-splitting is a real failure mode, and it is more annoying to live with than over-merging because content editors have to remember which collection a thing belongs in.

The test is whether a reader would perceive a difference. If Case Studies and Success Stories render the same way, carry the same fields and sit in the same navigation, they are one collection with an Option field, which is exactly the correct use of an Option field.

A related smell is a collection with fewer than about five items that never grows. That is usually static content wearing a CMS costume. Our piece on Webflow CMS versus a static page covers when not to use the CMS at all.

How Do You Actually Split One Safely?

In a fixed order, with the old collection untouched until the end. Create the new collection with only the fields that kind of item needs. Build its template page. Then copy items across rather than moving them, so the original stays intact as a fallback.

Copying by hand is fine for tens of items and a bad idea for hundreds. For the larger case, read from the source through the API, transform the fields, and write into the new collection, remembering the 100 record page size on reads and the per-minute request budget on writes.

Do this against staged items first. Webflow's CMS has a staged and live dual state, which means you can create and populate a new collection without publishing anything. Use that gap to check the whole structure before any visitor sees it.

Only once the new template renders correctly from real data do you switch navigation, collection lists and links over. Then leave the old collection unpublished but present for a couple of weeks before deleting anything.

What Breaks on the Front End?

Every collection list bound to the old collection, and every filter built on it. A Webflow collection list is bound to one collection, so a split means auditing every list on the site, not just the obvious archive page.

The ones that get missed are in shared components: a related items section in a footer, a sidebar on a template page, a featured strip on the homepage. Search the site for every place the old collection appears before you assume you have found them all.

Image and file fields need a check too. Webflow documents a maximum file size of 4MB per image, and requires images and files uploaded through the API to be hosted on a publicly accessible URL. A scripted migration that re-uploads assets will meet both rules whether or not you planned for them.

What About SEO and URLs?

Splitting usually changes URLs, and changed URLs need redirects. A collection's slug forms part of the site URL structure, so moving an item from one collection to another changes its address even if the item slug stays the same.

Map every old URL to its new one before you publish, and put the redirects in place in the same change. Doing it afterwards means a window where every link and every indexed URL returns a 404, and that window is exactly when a crawler tends to visit.

Take the opportunity to improve the paths while you are there. A split is the rare moment when changing URL structure is justified, because you are paying the redirect cost once regardless.

How Do You Get the Model Right the First Time?

Write down what each kind of item is before you create any fields. One sentence each. If two sentences are nearly identical, you have one collection. If they differ in what the thing fundamentally is, you have two.

Then check the fields against the sentence. Any field that would be blank for a meaningful share of items is a question about whether the model is right, and it is much cheaper to answer that question before there are nine hundred items in the collection.

If you want a second opinion on a CMS structure, or help splitting a collection on a live site without breaking it, we are happy to walk through it. You can find us at phoenix.studio.