Webflow Just Killed CMS and Business Plans for "Premium." Here's the Real Pricing Math for a Designer Studio Running 8 Client Sites.
A studio-operator breakdown of Webflow's May 13, 2026 pricing migration. Maps the old Basic / CMS / Business / Ecommerce ladder to the new Basic / Premium / Ecommerce / Team layout, walks Webflow's three official scenarios (A: save $10,…
On May 13, 2026, Webflow collapsed CMS and Business into a single Premium plan, introduced a new Team bundle, and added AI credits to every Workspace. The headline reads simpler. Run the math across an 8-site studio and roughly a quarter of the sites get cheaper, a quarter get more expensive, and the rest stay flat with a silent bandwidth haircut underneath.
The May 13 changes in one paragraph
Premium replaces CMS and Business with one merged plan at $25/mo yearly or $39/mo monthly. A new Team plan slots in above it as the all-in-one bundle for studios that have outgrown self-serve seats. Every Workspace received AI credits the same day, but Webflow won't enforce the credit limits until June 29, 2026 – until then the AI usage dashboard is live in read-only mode. Existing sites auto-migrate at the next renewal or billable change after June 29, with one carve-out: Freelancer and Agency Workspace sites have until November 16, 2026 to flip. Webflow's own help center frames the migration through three scenarios – save $10, pay the same, pay $6 more – and the scenario you land in depends on bandwidth, not plan choice.
The new ladder vs the old ladder
The old Site plan ladder was four rungs: Basic at $14/mo yearly, CMS at $23, Business at $39, and Ecommerce at its own pricing. The new ladder is shorter: Basic at $15, Premium at $25, Ecommerce unchanged, and Team as a separate all-in-one bundle that mixes Workspace seats and Site plans into one line item.
The plan-price moves are the easy part. The hidden moves are inside the limits.
CMS items jump from 2,000 on the old CMS plan to 20,000 on Premium. CMS Collections go from 20 to 40. The CMS items add-on, which used to bill separately for content-heavy sites, is removed entirely on Premium. For any site that was paying that add-on monthly, this is a real reduction.
Bandwidth moves the other direction. The new Premium plan starts at 50 GB of monthly bandwidth. Old Business sites had 100 GB included. Bandwidth add-on tiers also got more expensive at the lower end.
So the ladder simplified from four rungs to three, but the cost composition inside each rung changed. Content-heavy sites win. Bandwidth-heavy sites lose. Plain landing pages pay a dollar more.
The three Webflow scenarios, decoded for studios
Webflow's help center lays out three scenarios. They're useful as anchor points, not as guidance.
Scenario A – Business monthly under 50 GB. $49/mo drops to $39/mo. Save $10. This is the scenario Webflow's marketing leads with, and it's real, but it only applies to sites that were on Business monthly billing and sit under the new 50 GB bandwidth ceiling. In an actual client portfolio, this is a minority of sites.
Scenario B – Business yearly at 500 GB. $199/mo total stays $199/mo total. The plan price drops from $39 to $25, but the bandwidth add-on rises by the same amount. Same bill, different line composition. The simplification is invisible at the total.
Scenario C – Business yearly at 150 GB. $59/mo becomes $65/mo. Pay $6 more. This is the one Webflow buries. Any site sitting between 50 GB and 100 GB of monthly bandwidth – exactly where most mid-traffic marketing sites live – gets a price increase because the bandwidth you used to get for free on Business is now an add-on, and the add-on tier is more expensive than it used to be.
The pattern across all three: the headline plan-price drop only helps you if you're under 50 GB. Between 50 GB and 100 GB you pay the same or more. Above 100 GB, the new add-on tiers eat the savings. The "simplified plans" framing is technically true at the plan level and misleading at the bill level.
My 8-site studio ledger, before and after
Here is the actual ledger across eight client and studio sites, with old monthly cost and post-migration monthly cost. This is the only way I know to talk about this change honestly – abstract scenarios don't reconcile a real bill.
Site 1 – agency landing page. Basic yearly. $14 → $15. Plus one dollar. The cost of doing business under the new ladder.
Site 2 – portfolio site on legacy CMS yearly, 1,200 CMS items. $23 → $25. Plus two dollars. CMS items were never the constraint here, so the 10x ceiling on Premium is wasted; the studio pays $2/mo more for headroom it won't use.
Site 3 – DTC brand on Business yearly, 40 GB average bandwidth. $39 → $25. Minus $14/mo. Scenario A in the wild. The site doesn't push enough traffic to need Business-tier bandwidth, and the auto-migration to Premium drops the bill cleanly.
Site 4 – content-heavy SaaS marketing site on Business yearly, 180 GB average bandwidth. $39 base plus $40 in bandwidth add-ons → $25 base plus $80 in bandwidth add-ons. Plus $26/mo. The plan price dropped $14, the bandwidth add-on rose $40, net $26 worse. This is the site that will surprise the studio's accounting in July.
Site 5 – Ecommerce Standard. No change. Ecommerce plans were left alone in this migration.
Site 6 – client microsite on Basic monthly. $25/mo. No change at the plan level. But because this site is on monthly billing, it has no legacy-pricing protection at the next renewal. We should switch this to yearly this week.
Site 7 – small SaaS on legacy CMS monthly, 4,500 CMS items. Was paying $23/mo for CMS plus a $15/mo CMS items add-on because the site sat above the old 2,000-item ceiling. New Premium plan: $39/mo monthly, no CMS items add-on. Net: $38 → $39, but the add-on disappears and the site stops triggering overage alerts.
Site 8 – agency presentation site on Business monthly, 60 GB average. $49/mo → $39/mo Premium plus $20/mo bandwidth add-on for the 50-to-100 GB tier. New $59/mo total. No headline change, but the composition shifted and the lock-in opportunity is real.
Monthly total before: $277. Monthly total after: $279.
On paper, the studio's Webflow bill barely moved. Underneath, two sites got materially cheaper, one got materially more expensive, and the rest absorbed small shifts. The migration didn't raise the total. It rebalanced who pays what.
The bandwidth trap inside the Business-to-Premium migration
The cleanest cost-shift trick in this migration is the 50 GB starting bandwidth on Premium versus 100 GB on legacy Business. Half the included bandwidth, same plan price.
Webflow's help center is explicit about how this gets enforced. At the next renewal after June 29, 2026, sites that exceeded the new 50 GB ceiling across the past two billing months will be auto-assigned a bandwidth add-on. Not a warning email or a manual upgrade prompt – an automatic add-on attached to the bill.
The add-on pricing got worse at lower volumes. So if a site was sitting at 70 GB on legacy Business, paying nothing extra, it now pays $25 base plus $40 bandwidth, total $65. The old bill was $39. The "simplified" outcome is $26/mo more.
The action item this week: open the Webflow Cloud bandwidth panel for every client site. Anything sitting between 51 GB and 100 GB on the trailing two-month average is a silent price increase waiting for the next renewal after June 29. You have two outs: switch the site to yearly billing before its renewal date to lock in legacy pricing, or talk to the client about the new bill line before it shows up.
If you bill Webflow back to clients without a retainer cushion, this is the conversation to have in June, not in August.
AI credits, the June 29 cliff, and what they actually pay for
Every Workspace plan now includes AI credits. They cover the AI site builder, AI assist features inside the Designer, and on-canvas AI actions across Workspaces. The credit dashboard is live now in read-only mode – Webflow is logging usage but not enforcing limits until June 29, 2026.
This is the part of the migration that needs instrumentation, not opinion. The honest answer to "how many credits does my workflow burn" is: open the dashboard, do your normal week of work, read the number. Anything else is guessing.
The AI site builder itself didn't change capabilities with this announcement. Enterprise access tiers exist for higher caps.
The honest read on the credit model: it replaces what was effectively a "use it freely while we figure it out" experience with a metered allowance. The dashboard is the only way to size the add-on before the cap kicks in. If you generate site drafts as part of every client kickoff, instrument now. If you only touch AI assist occasionally, the included allowance will probably cover you and you can ignore the dashboard until late June.
Either way, June 29 is the cliff. Read-only becomes enforced.
The lock-in move I made this week
Webflow lets you lock in your current Site plan for another 12 months if you switch from monthly to yearly billing before the changes take effect for your account. The clause is in the help center, not the marketing post, which is how you know to look for it.
For me that meant switching Site 6 (Basic monthly) and Site 8 (Business monthly at 60 GB) from monthly to yearly billing this week. Site 6 is a small move – locking in the $14/mo legacy Basic rate buys back the $1/mo Basic increase for another year. Roughly $12 saved.
Site 8 is the move that matters. By switching from Business monthly to Business yearly before the renewal triggers the auto-migration to Premium, the site keeps its 100 GB included bandwidth at the old $39/mo rate until May 2027. Avoiding the $20/mo bandwidth add-on for 12 months saves $240. Net of the yearly billing commitment, roughly $180/year preserved on a single site.
If you have any Webflow site on monthly billing that's currently on Business or legacy CMS, this is the one move to make this week, not next month. The lock-in window closes when your account's migration date arrives, and Webflow has been clear that the window is finite.
The $387/mo solopreneur stack
How I reconcile every bill line – Webflow, Cloudflare, Anthropic – into one operating ledger.
What this means if you build for clients on Webflow
For client-billed sites, June is the month to have two conversations. First, the AI-credit ceiling – if the client signed up expecting unlimited AI assist usage, set expectations before June 29. Second, the bandwidth add-on – if any of their sites sit between 50 GB and 100 GB, budget the add-on into the next retainer cycle now, not after the bill arrives.
For studios with five or more active client sites and more than two collaborators on the team, the new Team plan is worth 20 minutes of math. It bundles Workspace seats and Site plans into one line item, and depending on your mix it can collapse two separate bills into a single number. I haven't moved my own studio onto it yet because my site count fluctuates and the per-site math still wins for me, but the calculation isn't obvious – run it against your actual seat and site count before assuming.
webflow.com
Webflow pricing-change calculator
The official tool to model your specific site portfolio against the new plans.
The headline simplification doesn't simplify the bill. It just renames the lines. Designer studios running multiple client sites need to read the ledger, not the announcement post – the cross-site math is where the actual change lives.
Last Updated
May 14, 2026
Category
Design
