Nobody leaves Webflow because the site looks bad. The site usually looks great.
They leave because marketing asked for something ordinary. A second product line in the resource center. A German version. A pricing calculator that reads live data. A contractor who needs to publish one landing page without touching anything else. And the answer came back as a plan upgrade, or as a quote from the one designer who understands how the site is wired.
That pattern is worth taking apart, because Webflow’s limits don’t feel like limits when you hit them. They feel like pricing decisions. Each one is reasonable on its own. Stack five of them and you have a platform that runs your brand beautifully while your content sits on rented ground.
What the platform gets right
Start with the honest part. Webflow is the best tool on the market for turning a designer’s intent into a live page without a developer in between. The canvas writes production CSS. The interactions engine is serious. Hosting is managed, there are no plugins to patch, and nothing breaks on a Tuesday because a third-party extension shipped an update.
It has also been moving quickly. In May 2026 Webflow merged its old CMS and Business plans into a single Premium plan at $25 a month, and raised the CMS limit to 20,000 items, up from roughly 2,000 on the old CMS plan. 1 Source 1 Webflow, Pricing, webflow.com/pricing, accessed September 30, 2026. Premium: 20,000 CMS items, 40 Collections, $25 a month billed yearly. Webflow merged its former CMS and Business site plans into Premium on May 13, 2026; the old CMS plan carried roughly 2,000 items. It added app hosting and an MCP server for AI agents. Anyone who evaluated Webflow in 2024 should look again.
For a 40-page brand site run by one designer, it is hard to beat. The ceilings below only matter if your site is going to become something more than that. Most B2B sites eventually do.
The content model starts bending to the plan
Premium caps you at 20,000 CMS items and 40 Collections. Every Collection tops out at 60 fields, and reference fields, the ones that connect a case study to an industry or an author to their articles, are capped at 10 per Collection below Enterprise. 2 Source 2 Webflow Help Center, Reference Collection field. Collections support 60 fields, with reference and multi-reference fields counted toward the cap; non-Enterprise plans allow up to 10 reference fields per Collection.
Twenty thousand sounds like plenty. Then you count what an item actually is. Every blog post, yes, but also every author, every tag, every glossary term, every office location, every integration page, every localized variant your team stores as its own record. A programmatic section, say one page per integration or per city, can burn through thousands on its own.
The item cap is not the expensive part. The workarounds are.
Teams near a limit stop creating structured records. Tags collapse into a text field. Three related content types get merged into one Collection with a dropdown to tell them apart. Product specs move into rich text, because rich text is one field no matter how much you pour into it. Nobody decides to degrade the content model. 3 Definition 3 Content model: the set of content types a business publishes, the fields each one carries, and how they reference each other. It decides what a site can answer, filter, and reuse. It just happens, one sensible compromise at a time.
What you lose is structure, and structure is what everything downstream runs on: filtering, personalization, answer engines that want a clean fact, an agent that needs to know which records are case studies. Content stored as blobs can be displayed. It can’t be reasoned over. That’s the argument we make at length in What Is a Headless CMS?, and it applies to any platform that meters structure.
The price curve has a cliff in it
What happens when you outgrow Premium? The answer used to be a gentle step to Business. Since May 2026 it’s a jump.
Premium is $25 a month. The next published tier, Team, is $2,500 a month on an annual contract, $30,000 a year. It includes 20,000 CMS items (more cost extra), 100 Collections, 600 API requests per minute, two locales, and ten seats. Enterprise is priced by conversation. 4 Source 4 Webflow, Pricing, accessed September 30, 2026. Team: $2,500 a month, annual contract required; 20,000 CMS items with more sold separately, 100 Collections, 600 API requests per minute, 2 locales, 5 full and 5 limited seats included. Enterprise: custom pricing. Vendr’s buyer data, collected before the change, put the median negotiated Webflow contract at $37,900 a year across 132 purchases. 5 Source 5 Vendr, Webflow Software Pricing & Plans 2026, last updated February 2026. Median annual contract value $37,900 across 132 purchases; range $10,000 to $82,148.
Seats sit on top of all of it. A full seat, the kind that can design pages, costs $39 a month billed yearly. A limited seat for content editors is $15.
A 100x step in list price isn’t unusual in SaaS. What makes this one awkward in a budget meeting is what triggers it. You don’t cross into Team because traffic tripled. You cross because you needed more than 20,000 records, a second language at scale, single sign-on for security review, or the ability to publish one page without publishing the whole site. The site the customer sees barely changes. The invoice does.
For a CFO, that’s the worst shape of cost: a step function tied to capabilities nobody on the finance side can see.
The export is a photograph of the site
Webflow does let you export code, on a paid Workspace plan. Read its own description closely: “Dynamic content (CMS items/pages) can’t be exported.” 6 Source 6 Webflow, Pricing (Workspace plan comparison), code export description. Webflow Help Center, How do I export my Webflow site code?: CMS, user accounts, ecommerce, code components, and localized content are excluded; site search and forms do not work on exported sites.
What you get is the HTML, CSS, JavaScript, and images for your static pages. What stays behind is everything that makes the site work: the CMS content and its templates, forms, site search, localized versions, gated pages. The content comes out separately, one CSV per Collection, one locale at a time, with image links that still point at Webflow’s servers. 7 Source 7 Webflow, Export CMS content as a CSV. Export runs one Collection at a time and includes only the locale currently in view. Migration specialists note that image URLs in the export point to Webflow’s CDN and must be re-hosted.
Webflow’s limits don’t feel like limits when you hit them. They feel like pricing decisions.
So you own the look. The working parts are rented.
That changes your position at every renewal. A vendor whose customers can walk away with a running site prices differently from one whose customers would have to rebuild the content layer from spreadsheets. It’s a quieter version of the switching-cost lock we describe in The Five Locks. Nobody at Webflow says you can’t leave. The export just makes leaving a project.
Server-side logic lives next door
This is the ceiling that changed most in the past year, so precision matters.
Webflow now hosts server-side apps through Webflow Cloud, with their own databases and file storage, and publishes an MCP server so AI agents can work with a site through its API. 8 Editor's note 8 Credit where it is due. Webflow Cloud and Webflow’s MCP server are real, recent, and useful. The argument here is not that server-side work is impossible on Webflow. It is that it runs in a second system, on terms Webflow sets. Two years ago, the honest summary was that anything server-side waited on Webflow’s roadmap. Today it’s more accurate to say it runs on their terms.
Those terms are specific. Cloud apps run on an edge runtime with 30 seconds of CPU and 128 MB of memory per request, partial Node.js support, and caching rules the platform overrides. 9 Source 9 Webflow Developers, Webflow Cloud Limits and About the Webflow Cloud edge environment, accessed September 30, 2026. Custom Cache-Control headers are replaced by the platform. The app is a separate project, deployed from its own repository and mounted beside the site. When it needs to change content, it goes through the same API as everyone else: 120 requests per minute on Premium, and one site publish per minute on any plan. 10 Source 10 Webflow Developers, Data API Rate Limits, accessed September 30, 2026: one successful site publish per minute. Webflow’s pricing page lists 120 requests per minute for Premium and 600 for Team.
Put that together and the architecture is two systems. One is a design tool with a CMS inside it. The other is an application platform bolted alongside, which talks to the first over a metered connection. A pricing calculator, a partner portal, a product configurator, or an agent that rewrites 300 pages after a positioning change all live on the second system, and all of them inherit the content model limits of the first.
The business cost isn’t technical. It’s ownership. Every integration becomes a project with two owners, the Webflow designer and whoever writes the app, and every capability you want next depends on what Webflow decides to expose.
Who actually controls a Webflow site in year three?
The original promise was marketing autonomy: no developer tickets, marketers ship pages. On day one that’s true.
It holds as long as the components cover the need. Limited seats can “edit content or build pages with components,” which means working inside what a full-seat designer has built. The first time marketing needs a layout that doesn’t exist, the ticket goes back to the designer, who is now the developer the platform was supposed to replace.
The governance tools that make a larger team safe are tiered upward. Publishing a single static page without publishing everything else in the site starts at Team. So do page branching and publishing workflows. Custom roles, permissions down to individual pages and Collections, design approvals, and single sign-on are Enterprise only. 11 Source 11 Webflow, Pricing (Platform plan comparison), accessed September 30, 2026. Single-page publishing, page branching, and publishing workflows start at Team. Custom roles, granular access controls, design approvals, and single sign-on are Enterprise only. On Premium, a contractor fixing a typo on a landing page publishes every staged change on the site along with it.
By year three, a mature Webflow site tends to run through one person who understands the class structure and which interactions are load-bearing. That person is usually excellent. They are also a single point of failure that no org chart shows.
What changes when the content is files you own
None of this argues for giving up the design. The design is usually the best thing about a Webflow site, and it moves intact. What changes is where the content lives and who shapes it.
When content is stored as structured files in your own repository, the content model is designed around the business instead of around a plan. Case studies can reference industries and products without anyone counting fields. A new content type is a decision, not a purchase. There’s no item meter, so programmatic pages stop being a budget question.
Cost starts to track traffic instead of headcount and features. Adding an editor doesn’t add a seat fee. Single sign-on and version history come with the tooling most engineering teams already run.
Server-side logic sits in the same codebase as the content, so the pricing calculator reads the same product records the product pages do. An agent that updates 300 pages works on the same files your team edits, and every change it makes is reviewable and reversible. The underlying argument is in Your CMS Is a SaaS Product Too: the CMS is the easiest SaaS product to replace, and the one whose replacement pays back fastest.
And the exit problem disappears, because there’s nothing to export. The site is already yours.
Not sure which ceiling you’re closest to? The Free AI Website Assessment scores your site in 60 seconds.
If you’re on Webflow today, you don’t need to move tomorrow. Pull three numbers: your CMS item count against 20,000, your full-seat count, and the date of your next renewal. Then ask marketing which request they stopped making because the answer was always a workaround. That last one is usually the real ceiling, and it has been costing you longer than any of the others.
The research is free. So is the diagnosis. 60 seconds →