What are the limitations of Webflow in terms of the number of pages and CMS fields, and what alternatives or workarounds can I use to overcome these limitations?

Webflow has specific page count and CMS field limits depending on your hosting and plan type. These can impact content-heavy or complex database-driven sites. Here’s a breakdown of those limits and how you can work around them.

​

1. Page and CMS Limits in Webflow

​

• Static Pages Limit: Maximum of 100 static (hard-coded) pages per Webflow project, regardless of plan.
• CMS Collection Items Limit:
• 10,000 items with a CMS or Business Site Plan.
• Lower limits on Starter or lower-tier plans.
• CMS Fields per Collection: Up to 60 fields per CMS collection.
• Reference Limits:
• Max of 5 Reference or Multi-reference fields per collection.
• Nested Collection List Limit: One-level nesting only.
• Total CMS Content Size: CMS storage is subject to overall account constraints, but typical usage rarely hits space limits before field or item limits.

​

2. Workarounds for the 100 Static Pages Limit

​

• Use CMS Collections for Pages:
• Convert static pages (like team profiles, products, or blog posts) to dynamic CMS collection pages.
• Design one CMS Template page, then generate pages via the CMS.
• Link to External Content:
• Host resource-heavy or archive content on an external platform (e.g., Notion, WordPress) and link to it.
• Duplicate Projects for Overflow:
• Maintain separate Webflow sites for sub-sections (e.g., blog.domain.com), though managing multiple sites increases overhead.

​

3. Workarounds for CMS Item or Field Limits

​

• Split Content Across Multiple Collections:
• Use multiple CMS collections to organize content types and spread item or field load.
• Use Reference Fields Carefully:
• Replace some multi-reference needs with manual relationships (e.g., using tags, IDs, or filters in templates).
• Use Third-Party Integrations:
• Tools like Airtable, Jetboost, or Whalesync can enhance Webflow’s CMS flexibility by syncing external data.
• Host Heavy CMS Content Elsewhere:
• Fetch dynamic content from platforms like Firebase, Airtable, or Sanity, and inject it via custom JavaScript and APIs.

​

4. Alternatives to Webflow for Heavier Use Cases

​

• WordPress + Elementor:
• No hard limit on static pages or CMS fields; great for content-heavy or multi-author websites.
• Framer:
• More flexible static page counts and built-in headless CMS (but fewer customization options than Webflow currently).
• Sanity + Next.js (or similar headless CMS + custom frontend):
• Fully scalable CMS; use when you need deep customization, complex data structures, or don’t want Webflow's visual editor.

​

Summary

​

Webflow limits you to 100 static pages, 10,000 CMS items, and 60 fields per collection, which impacts large or data-rich sites. Workarounds include using CMS collections for dynamic pages, syncing data from external sources, and splitting data structures. Alternative platforms like WordPress, headless CMSs, or Framer can offer more scalability when Webflow’s limits are reached.