Webflow CMS limits, and what to do when you hit them

Webflow's CMS is pleasant to use until the content grows. Then the limits start shaping decisions that should be editorial: how many posts you publish, how you tag them, whether you build that integrations directory at all.

Exact numbers change with Webflow's plans, so check the current pricing page. The kinds of limits stay the same.

The limits teams run into

• Item caps per site, set by plan. Blogs, changelogs, and directories hit them first.
• Collection caps. Each new content type uses one, so teams squeeze different things into one collection.
• Reference fields. You can link collections, but deep or many-to-many relationships get awkward to model and to display.
• Nested collection lists. Showing related items inside related items has limits.
• Localization. It's a paid add-on, and every locale multiplies the content you manage.
• Editorial workflow. Roles and review steps are limited on lower plans.

Workarounds and their cost

Teams get creative. They archive old posts to stay under the cap, store data in rich text instead of fields, or pull content from an external source with scripts. Each of these works for a while. Each also makes the site harder to change, and none of them shows up on an invoice, so the cost stays hidden.

Your options

1. 01Upgrade the plan. Simple and right if one tier up solves it for the next couple of years.
2. 02Clean up. Merge thin posts and delete unused items. Often worth doing anyway.
3. 03Move only the heavy part. Put the blog or resource center on a headless CMS on a subfolder, and keep Webflow for the rest.
4. 04Migrate fully. Move to Next.js or Astro with a headless CMS when limits, cost, and workflow problems add up.

There's no right answer for everyone. We look at how fast your content is growing and what the next two years of plans would cost, then compare.