Do I need a separate CMS site planning subscription for each of my 5 website projects in Webflow?
TL;DR
- Each Webflow project needs its own CMS Site Plan to access CMS features like Collections and dynamic content.
- CMS functionality cannot be shared between projects, so only purchase CMS Plans for the sites that require dynamic content.
If you want CMS features on all 5 Webflow projects, then yes, each project needs its own CMS Site Plan subscription.
1. Webflow Plans Are Per Site
- Webflow Site Plans (e.g., Basic, CMS, Business) are billed per site/project.
- CMS features like Collections, dynamic content, and the Webflow Editor are only available if a site has a CMS or higher Site Plan.
2. No Shared CMS Across Multiple Projects
- You cannot share CMS functionality across multiple sites.
- Each site must have its own CMS subscription if you need dynamic content (e.g., blogs, portfolios, directory listings) on that domain/project.
3. Workspace Plans vs. Site Plans
- A Workspace plan (e.g., Freelancer, Agency) allows management of multiple projects and team members but does not affect CMS features.
- Site Plans control hosting and functionality such as CMS or e-commerce—this is what you need for live CMS content per site.
4. Evaluate If All Sites Need CMS
- If a site is fully static (only static pages, no dynamic Collections), it could work with a Basic Site Plan instead.
- Identify which of the 5 sites actually require CMS features and only purchase CMS Plans for those.
Summary
Yes, if all 5 sites need CMS features, you must buy a separate CMS Site Plan for each one. Webflow does not allow CMS functionality to be shared across multiple projects.