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 limits on static pages, CMS items, and CMS fields that can affect larger or more complex projects. Here's how to understand and work around them.

1. Webflow Page Limitations

• Static pages are capped at 100 pages per project (includes published and unpublished pages).
• This does not include CMS-generated pages; those are governed by CMS collection limits.
• No current workaround to bypass the static page cap within a single project.

Workarounds:

• Use CMS Collections for repeatable content like blog posts, product pages, or team profiles. Each CMS item generates a dynamic page.
• Split your site into multiple projects and link them under the same domain via subdirectories (using reverse proxy) or subdomains (blog.yoursite.com).
• Use embeds for content to avoid creating new static pages (use tabs, modals, or expandable sections on a single long-form page).

2. CMS Item and Field Limitations

• CMS Items Limit: Up to 10,000 CMS items on the Business plan (max allowed per site).
• CMS Collections: Max 40 collections per project.
• Fields per collection: Max 60 fields, though some field types (like Option and Multi-Reference) consume more internal “slots,” effectively reducing usable field count.

Workarounds:

• Merge fields wherever possible: Use Rich Text fields to consolidate multiple text or media sections.
• Use reference fields to relate collections and reduce field usage.
• For items over 10,000: Use external databases via APIs or third-party tools like Airtable + Whalesync, PowerImporter, or custom APIs.
• Break content into multiple Webflow projects and serve them under the same brand infrastructure.

3. Hosting & Site Plan Limitations

• Business sites limited to 250,000 monthly visits and 400 GB Site bandwidth.
• CMS features only available on CMS and Business site plans—not on the Basic plan.

Workarounds:

• Use reverse proxies or Cloudflare Workers to load external pages or content.
• For massive scaling, consider headless CMS models where Webflow is primarily the frontend, and CMS/data served from systems like Sanity, Contentful, or Firebase.

Summary

Webflow limits you to 100 static pages, 10,000 CMS items, and 60 fields per collection, which can be a bottleneck for large or complex sites. Use CMS pages, reference fields, and external content sources to bypass these limits or split your content into multiple Webflow projects connected through custom configurations.