How Does Webflow's May 13 2026 Plan Change Affect Your Site?

Webflow flipped its Site plan structure on May 13, 2026, and the change quietly reshapes how I price client retainers from my desk in Bengaluru. The old CMS and Business tiers are gone, folded into a single Premium plan. A new Team plan now sits next to Workspace. AI credits are bundled into every Workspace plan instead of sold separately. Base bandwidth on Premium drops from the legacy 100 GB ceiling to 50 GB, with paid add-ons available above. In this piece I will walk through what each change means for a real B2B SaaS site, which client archetypes from the 70+ projects shipped through Phoenix Studio come out ahead, and where the new bandwidth math forces a different conversation this quarter.

What changed in Webflow's plans on May 13, 2026?

On May 13, 2026, Webflow rebuilt its Site plans around two tiers, Basic and Premium, retiring the legacy CMS and Business plans. Workspaces now bundle AI credits, a separate Team plan slots in below Enterprise, base bandwidth on Premium drops to 50 GB with paid add-ons above, and Premium doubles CMS capacity to 20,000 items.

The structural moves matter more than any single price point. Webflow has tried for years to keep three site tiers, Basic, CMS, and Business, doing different jobs, and clients on every project I work on have struggled to choose the right one. Folding CMS and Business into one Premium plan removes the most common mid-build conversation I used to have with founders: do we need CMS now or wait for Business later. The answer is now just Premium, and the spec sheet adjusts in their favor on CMS items while quietly tightening on bandwidth. The Team plan additions and bundled AI credits sit at the Workspace layer, so they affect how the team logs in to build the site, not how the site itself is billed. The full breakdown lives in the Webflow Help Center plan FAQ.

How does the new Premium plan compare to the old CMS and Business plans?

Premium absorbs both the legacy CMS and Business tiers into a single mid-tier plan. CMS items double to 20,000, Collections rise to 40, base bandwidth lands at 50 GB, and the plan now includes 2 million Webflow Cloud web app requests per month. Sites previously on Business with low bandwidth use will see capability go up overall.

For a marketing team that was on CMS purely for the item limit, Premium is a clean win. The doubled item count means most B2B SaaS content libraries I have built, blog plus changelog plus customer stories plus a careers section, fit inside one plan with headroom for two more years of publishing. For a brand that was on Business mostly for the bandwidth, Premium needs a closer read. The 100 GB ceiling of the old Business plan has been replaced by a 50 GB starting point on Premium plus add-ons above. Most marketing sites I track on Phoenix Studio dashboards transfer well under 50 GB per month, but high-traffic content brands and any site running short-form video can blow past that within a quarter.

Why did Webflow cut base bandwidth from 100 GB to 50 GB?

Webflow did not publish a stated reason for the bandwidth drop. The most likely read is that the new add-on model lets bandwidth-heavy sites pay only for what they use, while the bulk of Premium customers, who never come close to 50 GB, no longer subsidize a 100 GB ceiling that almost nobody hits.

This pattern is familiar from other infrastructure pricing moves. Cloud platforms like Google BigQuery, Snowflake, and Amazon Redshift charge by consumed compute and storage rather than by ceiling. Webflow has, to my read, started edging in the same direction with site bandwidth and Webflow Cloud requests. The practical effect for clients is that the cost of a high-traffic site becomes more visible as a separate line item rather than buried inside a single plan price. For founders, that visibility is good. For agencies retaining clients, it adds one more conversation: this month your bandwidth crossed the threshold, here is what the add-on costs. I am rewriting two engagement scopes this week to make that conversation explicit upfront in the proposal.

How do the new AI credits work across Workspace plans?

Webflow bundled AI credits into every Workspace plan on May 13, 2026, ending the previous standalone purchase model. The credits cover Designer AI features such as image generation, alt-text suggestions, and content rewrites. The amount included scales with the Workspace tier, so paid plans have more headroom than the free Starter tier.

This is the change with the least visible impact and the highest potential to alter behavior over time. Until this week, I rarely saw founders use Webflow's in-Designer AI features at scale, because they were a separate paid add-on competing with whatever the team already paid for at OpenAI or Anthropic. With AI credits now sitting inside the seat fee, teams will at minimum try them. Whether they replace external tools depends on quality, not pricing, but the absence of a per-feature paywall removes the friction I used to see at handover. If you read my notes on monthly AI tooling cost reality, this is one of the few line items that actually got simpler this month.

What is the new Webflow Team plan and who is it for?

The Team Workspace plan sits between Freelancer and Enterprise. It supports multiple seats with role-based permissions, includes the Premium AI credit allocation, and gives a team a shared billing surface for several sites without requiring a formal Enterprise contract. It is aimed at in-house marketing teams of three to ten people running their own Webflow sites.

The Team plan fills a real gap. Until this week, an in-house team of five marketers either lived on a single Freelancer Workspace, sharing one login in ways that violated their own security policies, or they jumped straight to Enterprise and paid for capability they did not yet need. Team is the cleanest answer for the mid-size marketing org that has graduated past one person but is not ready to write an Enterprise check. Three of my recent clients fit that shape exactly, and I will be repricing their seats this quarter based on the new tier. For solo Webflow Partners like me, Team is also useful as a billing structure for the agency itself rather than for any one client.

Does the Webflow Cloud quota change affect existing sites?

Premium now includes 2 million Webflow Cloud web app requests per month as part of the base plan. Sites running custom server-rendered logic on Webflow Cloud will see the included quota go up, with overages billed as add-ons. Static marketing sites that do not use Webflow Cloud functions are not affected by this part of the change at all.

Webflow Cloud is the part of the platform that runs custom JavaScript and server logic alongside the visual site. Most of the marketing sites I have built do not use it, but the SaaS clients with gated content, custom forms, or interactive product configurators do. A 2 million request quota covers a fairly busy marketing site, but a programmatic SEO site generating thousands of dynamic pages can spend it quickly. If you are on a programmatic build, audit your Cloud request log before you celebrate the new Premium plan. If you are on a standard marketing site, this number is irrelevant and you can skip it entirely. Knowing which side of that line your site sits on is the actual work this week.

Should you switch billing cycles before your plan migrates?

For most sites already on an annual cycle, the migration to the new structure happens at renewal with no immediate change. Sites on monthly billing pay slightly more under the new plan structure, so switching to annual before the migration locks in a lower effective price. The exact migration date depends on your current plan and billing cycle position.

Webflow's Help Center documents the migration path in detail. The summary is that current Workspace and Site plans continue to bill at their existing rate until the next renewal, at which point they convert to the closest equivalent in the new structure. There is no forced mid-cycle switch. If your client is on a monthly Business plan, switching to annual before renewal saves real money, and the conversation is worth having this week. If they are already on annual, do nothing and revisit at renewal. The piece I wrote about how I reprice client retainers without churn explains the conversation script I use when a vendor change like this lands mid-engagement.

How do CMS item add-ons get absorbed into Premium?

Existing CMS item add-ons purchased on top of legacy plans get folded into the Premium baseline at migration. Sites that previously paid for 5,000 extra items on top of a Business plan now have those items included in Premium's 20,000 ceiling, removing a separate line item from the bill and simplifying the renewal conversation considerably.

This is one of the cleanest pieces of the migration for active clients. Two of my recent B2B SaaS marketing teams had been paying for extra CMS items as bolt-ons because their content library outgrew the Business plan ceiling mid-year. Both teams now sit comfortably inside Premium's 20,000 item limit without the add-on, which removes a recurring invoice line. The follow-up question I get is whether the saved add-on cost should pass through to the client as a credit. My answer is yes by default. Transparency on platform pricing is the cheapest trust I can build with a B2B SaaS marketing lead, and the retainer-pricing lessons from Bengaluru I wrote up earlier this year all point in the same direction.

Will your client retainers need re-pricing because of this?

Most retainers will not need re-pricing for the plan change itself. The reset point is at renewal, when the new Premium baseline removes some add-ons but the tightened bandwidth ceiling may introduce new ones for high-traffic sites. Retainers covering ongoing platform costs should be audited within the next two weeks against the new structure carefully.

The retainer audit is mostly mechanical. For each active client, list the current plan, current bandwidth use, current CMS item count, and any active add-ons. Map them to the new Premium baseline. Two outcomes are common: the client saves money because absorbed add-ons disappear, or the client crosses the new 50 GB bandwidth ceiling and needs an add-on that did not exist before. In the first case, decide whether to pass the savings through. In the second case, build the conversation about the new line item upfront. The agencies who get caught flat-footed are the ones who treat the May 13 change as a Webflow internal event rather than a billing conversation with their own clients.

When will your specific Workspace migrate to the new plan?

Most Workspaces migrate to the new plan structure at their next renewal date. Webflow has stated that no immediate mid-cycle changes will be forced on existing plans. Check the Plans section of your Workspace settings for the exact migration date listed against your subscription, and the Webflow Updates feed for any rollout adjustments through May and June.

The cleanest source of truth for your own Workspace is the Plans section inside Workspace settings. Webflow surfaces the migration date there for each plan currently in force. For agencies running multiple Workspaces, treat this like a vendor migration project: list each Workspace, capture each migration date, schedule a 30-minute review of bandwidth and CMS use against the new Premium baseline a week before each date. For solo Partners with one Workspace, set a single calendar reminder a week before your renewal and run the same review at smaller scale. The Webflow Updates feed is also worth subscribing to for any rollout adjustments through the rest of May.

If you are running a Webflow practice and want to talk through the migration math for a specific client or your own Workspace, drop me a line and tell me what the current plan and bandwidth pattern look like. I will tell you what the new Premium baseline does to the math and whether the retainer needs a conversation this week. Let's chat.