Agencies have until 16 November before Webflow's plan change reaches client sites

If you hold client sites in a Webflow Freelancer or Agency Workspace, you have a date and most people who have it do not know it. Webflow's plan changes reach those sites on 16 November 2026, which is two months from now, and they reach every other existing site on 29 June 2026, which has already passed. The gap was deliberate: Webflow says it built in more time because agencies often manage sites on behalf of clients and those conversations take longer.

So this is the short version of what lands, what it does to a bill, and the one lever that is still available before the date. The change itself is covered in full in Webflow's May 2026 plan changes; this is the part that is specific to holding somebody else's site.

The three dates

The CMS and Business plans are gone, merged into one Premium plan. For a client who was on CMS this is a large upgrade: 20,000 CMS items instead of 2,000, 40 collections instead of 20, 300 static pages instead of 150, and higher Webflow Cloud limits. For a client who was on Business it is mixed, and the two that go the wrong way are the ones to check before the renewal rather than after.

• Bandwidth drops from 100GB to 50GB. Webflow says that where a site has exceeded 50GB in the past two billing months it will add bandwidth add-ons to cover the usage. On a media-heavy client site that is a price rise arriving as an add-on, and it lands automatically.
• Webflow Cloud limits fall for a former Business site: web app requests from 10 million a month to 2 million, CPU from 120 to 30, with reductions across SQLite, the key-value store and object storage.
• CMS item add-ons have been removed. If a client was paying for one, that line disappears and the allowance it bought is now included, which is a reduction rather than a rise.

The lever, and it expires

Webflow states that switching a site from monthly to yearly billing before the changes take effect for that account locks in the current plan for one more year. For an agency that is the only control left, and it is per site rather than per workspace, so it is a list to work through rather than a single setting.

Whether it is worth using depends on which side of the change each client sits. Locking in a former CMS-plan site keeps it on the smaller allowance for another year, which is the wrong way round. Locking in a media-heavy former Business site keeps its 100GB of bandwidth for another year, which may be worth real money. So the answer is per site, and working that out is a two-column list rather than a policy.

A two-month checklist

• List every site in the Freelancer or Agency Workspace with its current plan and its billing cycle. That list is the whole job and most agencies do not have it written down anywhere.
• Mark the former Business sites and check their bandwidth over the last two billing months. Anything over 50GB will acquire an add-on automatically, and the client should hear that from you rather than from an invoice.
• Mark anything running on Webflow Cloud. The request and CPU reductions are the change most likely to break something rather than just cost something.
• Decide the billing-cycle switch per site, not as a blanket policy, and do it before 16 November. After that the lever is gone.
• Write the new figures into whatever document holds the client's stack. The old numbers are in every proposal and scoping note written before May, and they are wrong now.

One last thing worth doing in the same pass, because it costs nothing and it is the same list of sites. Check each one's redirect table while you are in Site settings. Redirects run in the order they were added and cannot be reordered, so an inherited table often has a broad wildcard near the top swallowing rules added later, which is set out in how Webflow 301 redirects actually behave.