Webflow Freelancer & Agency Workspace Plans: Nov 16 Renewal

Webflow hasn't changed its Freelancer or Agency Workspace prices: per webflow.com/pricing in October 2026, the Freelancer plan is still $16 a month and the Agency plan $35 a month on yearly billing. What changes is the Site plan under each client site in those Workspaces, which moves to Webflow's new prices at its first renewal or billable change on or after November 16, 2026, as does any site on legacy pricing from 2022 or earlier. Monthly billing takes the brunt of it; in the ten-site book I model below, almost 90% of the increase comes from monthly-billed sites, and switching those to yearly before November 16 keeps today's yearly price for one more year.

Who the November 16 change applies to

The November 16 change is the last of three waves in Webflow's 2026 price increase, and the one aimed squarely at client sites in Freelancer and Agency Workspaces; Webflow's pricing FAQ sets out all three:

A billable change means one of two things: upgrading or downgrading the base Site plan, or switching between monthly and yearly billing. Make either on or after your date and the new price applies immediately.

Credit where it's due: Webflow gave freelancers and agencies four and a half extra months precisely to make room for those client conversations, and told the affected customers directly. It's a rolling change, too: monthly sites move within about a month of November 16, while a yearly site renewing in March 2027 keeps its price until then.

Two groups sit outside all this. Ecommerce plans weren't changed, and sites already living in a client's own Workspace (Webflow's free Starter Workspace, say) followed the June 29 timeline.

Sites on legacy pricing deserve a closer look. They may be paying less than the standard prices below, so their jump will be bigger; pull the actual invoice for each and talk to those clients first, as they're often your longest-serving ones.

What the Webflow Freelancer and Agency Workspace plans cost, and what does change

Webflow's Workspace plans aren't part of this change, so the Freelancer and Agency prices are the same either side of November 16:

Agency earns its extra $19 a month on yearly billing when you need more than 10 staging sites, more than one client seat per site, or the controls Freelancer leaves out: site-level roles and publishing permissions, plus password protection and 301 redirects on unhosted staging sites (every paid Site plan has those two anyway). With the Legacy Editor retired on August 4, 2026 and extra client seats not currently on sale, a client with two people editing is a concrete reason for Agency, or for a transfer. Teams that own their own sites use Webflow's separate in-house track (Starter, Core and Growth) instead.

The change lands on the Webflow Site plan, which every live client site carries separately (prices per month):

Premium replaces both the old Webflow CMS plan and Business, with 20,000 CMS items and 40 collections. Business sites that used more than 50 GB in the past two billing months get bandwidth add-ons automatically; taking a site to 100 GB costs an extra $20 a month on yearly billing or $30 on monthly.

The pattern:

• Yearly billing barely moves: +$1 a month for Basic and +$2 for CMS-to-Premium, so $12 to $24 a year per site.
• Monthly billing jumps: Basic +39%, CMS-to-Premium +34%.
• Business can go either way: cheaper under 50 GB ($39 to $25 on yearly billing), dearer above it once add-ons are counted; Option 1 has the details.

The full line-up is on webflow.com/pricing, and the Webflow pricing calculator gives the new number for any single site.

What a 10-site freelancer book costs before and after

For a typical small book, Site plans go from $204 to $258 a month once everything has renewed: +$54, about 26%, or $648 a year, and almost 90% of it comes from monthly billing. The illustrative book is ten small-business and nonprofit sites in a Freelancer Workspace, mostly brochure sites, on a mix of billing cycles because some clients baulked at paying a year upfront.

With the $16 Freelancer Workspace on both sides it's $220 against $274. Of the $54, $48 comes from the six monthly-billed sites, so for a book like this the increase is mostly a penalty for monthly billing. Here's what each choice does to those six sites:

The lock-in is worth $8 a month here, about $96 a year, and only for one year. The real money is in leaving monthly billing: $68 a month, or $816 a year, whichever side of November 16 you do it, so a client who can't approve a yearly payment by the deadline can still switch in December and keep most of the saving.

Then there's who absorbs the difference. If clients pay you a flat fee that includes hosting, the $54 comes out of your margin unless you talk to them. I'd stop carrying the hosting altogether: the client pays the platform directly, and you charge for your time. One of the top replies in an r/webflow thread on the new pricing says much the same: "Client pays for hosting direct to Webflow, pays me for creation and editing." Options 2 and 4 both get you there.

Option 1: Switch monthly sites to yearly before November 16

This is Webflow's own offer, and for most monthly sites it's the best deal going. Switch a monthly-billed site to yearly billing before the changes take effect for your account, and it stays on its current plan at today's yearly price for one more year, then renews at the new yearly price. The switch lives under Site settings > Plans for each site.

• Monthly sites only. A site already on yearly billing has nothing to switch.
• Decide what's going static first. Yearly plans aren't refundable (Webflow's FAQ says you can cancel but still pay for the rest of the term), so pick your Option 4 candidates before locking in, and lock in only sites staying on Webflow for at least a year.
• The window closes on November 16. From that date the switch is itself a billable change and puts the site on the new pricing, which is still worth doing: Basic costs $15 a month on yearly billing against $25 on monthly.
• Someone pays a year upfront. That's $1,224 for the six sites in the example. For a small charity, approving $168 in one go can be harder than $18 a month, even though it works out cheaper.
• Business sites depend on bandwidth. Under 50 GB, wait: switched to yearly on or after November 16, a monthly Business site lands on Premium at $25, which beats locking in Business at $39. On 50 to 100 GB, lock in: a monthly site on 60 GB would otherwise renew at $69 (Premium monthly at $39 plus the $30 add-on), or $45 if switched after the 16th, while locked in it stays on Business at $39 with 100 GB for a year. Over 100 GB, run the calculator; Webflow's own example has a yearly Business site on 150 GB going from $59 to $65.

Charity clients: Webflow's nonprofit discount is narrower than it sounds: 50% off one new Premium Site plan billed yearly, for 12 months, and one discount per Workspace per 12 months. It's for new plans only, so an existing client site on Basic or CMS probably won't qualify.

Option 2: Hand the bill or the site to the client

If you'd rather stop fronting the money, Webflow gives you two tidy ways to do it.

Webflow Client Payments

Client Payments lets the client pay Webflow directly for the Site plan and add-ons with their own card, while the site stays in your Workspace and you keep full design access. You pick "Charge to client" in the site's plan settings and enter their email (Webflow's Client Payments guide has the steps); they accept, sign in and add a card. There's no fee, no downtime and no effect on custom domains or indexing, and any time you'd already paid for comes back as a prorated credit towards future purchases in your Workspace.

It's the same price with a different payer, which means no more explaining a markup. The limits:

• One client per site, and at most ten pending payment requests per Workspace, so send invites in batches.
• Paying doesn't confer ownership. Webflow's help centre is clear that a site in your Workspace belongs to your Workspace, whoever manages the billing. If a client assumes otherwise, put it in writing or look at a transfer.
• The price still changes at renewal. Webflow ties the November 16 date to the Workspace a site sits in, and its published material says nothing about who pays.

Transferring a Webflow site to the client's Workspace

A transfer is the cleaner break. A site with an active Site plan moves into the client's own Workspace with its plan and custom domains intact and no downtime, and Webflow's free Starter Workspace can hold paid sites, so the client needs no paid Workspace plan. To keep working on it you join as a guest, and free guest access in client Workspaces comes with Freelancer and Agency, one reason that plan stays on your books whatever you decide.

The open question: sites in a client's own Workspace come under the June 29 rule, so would a site transferred before November 16 move to the new prices at its next renewal, even if that falls before the 16th? Webflow hasn't said anywhere I could find, so ask Webflow support, in writing, before you transfer anything.

Option 3: Stay put (often the right call)

None of this means rushing clients off Webflow. Staying is the sensible call when:

• The client is CMS-heavy. Premium's 20,000 items and 40 collections at $25 a month on yearly billing is good value.
• The client edits the site themselves through a client seat, which is much of what they're paying for.
• The site uses Ecommerce, Webflow Localization or site search, none of which survive a code export.
• The site is billed yearly and the increase is $12 to $24 a year, less than a migration would cost you in time.

For a bigger move, see my comparison of Webflow alternatives, Framer vs Webflow if a rebuild comes up, or Webflow vs WordPress for the CMS-heavy ones.

Option 4: Move small brochure sites to static hosting the client pays for

This one is for the smallest sites in the book: the five-page site for a local physio or community group, edited twice since launch and sitting on Basic. A good candidate has no CMS, changes rarely, has a contact form that can move to Formspree or Basin, and doesn't need Ecommerce, Localization or site search. Code export comes with your Workspace plan, and how to export code from Webflow covers the steps and what stays behind.

The arrangement that keeps everyone straight: the client opens their own account with a static host and owns it (and the bill, where there is one), and you charge for changes and maintenance. The trade-off is that the client loses visual editing, so every change comes back to you, which for a site edited twice a year makes a small and perfectly reasonable retainer. The simplest publishing routine I've seen work is a fresh export that you send over and the client drags in, with a screen-share the first time.

Two things to sort out before you cancel anything. Point the form at Formspree or Basin inside Webflow: in the form's Settings panel, remove the default Webflow and Email notifications destinations (a Custom action can't be combined with them), add a Custom action under Send to with the endpoint URL, and set the method to POST, so it carries through every fresh export; hand-edit the exported HTML instead and every re-export ships a broken contact form. And a site whose Site plan you cancel stays in your Workspace as an unhosted staging site, which counts against Freelancer's 10 staging sites (sites on a paid Site plan don't), so keeping several static clients' sites there for re-exports uses up those slots, and that's what can push a busy freelancer onto Agency.

For a five-page site, Cloudflare Pages and Netlify both cost the client $0 a month within their free plans' limits, and both take an uploaded folder without git. One difference a business should know about: Netlify's credit-based free plan pauses every project on the account once the month's credits run out, with no overage option, which a five-page site rarely gets near, while Cloudflare Pages has no such cap on static traffic. I'd skip Vercel, whose Hobby tier is for personal, non-commercial use (a business needs Pro at $20 a month per seat plus usage, which saves little or nothing over Webflow Basic), and GitHub Pages, which expects a git workflow. The Webflow hosting alternatives guide compares the wider field.

Hostsmith is the other option (this is its blog, so weigh that accordingly). A client site on its own domain needs Hostsmith Pro, at $15 a month billed yearly or $21 monthly, as Hostsmith's Starter plan doesn't take custom domains. That matches Webflow Basic on yearly billing, so it saves nothing there and Cloudflare Pages costs less still; and, having called Webflow's monthly prices a penalty, I should say Hostsmith charges more for monthly billing too, though $21 is still $4 under Basic monthly. Where I reckon it earns its place is with three kinds of client:

• A client who wants a dashboard they can find their way round. Cloudflare's is a full DNS and security console, which is a lot to hand a physio, while Hostsmith's is built around sites and domains and publishing a re-export means dragging the folder or ZIP in. In my experience a client who's comfortable in their own dashboard is one who actually does the publishing, and that's what the extra money buys over Cloudflare's $0.
• A client who wants to compare the exported copy with the still-live Webflow site before you cancel the Site plan. Private Sites can password-protect that preview or limit it to an email whitelist on its hostsmith.link address, in the client's own account.
• A charity with a main site plus a few campaign microsites, which fit Pro's 5 sites and 5 custom domains.

Current prices are on hostsmith.net/pricing.

What to tell your clients before November 16

For a typical book, the job this week is short: list the monthly Basic and CMS sites, pick the two or three that are going static, and get yearly approval for the rest, since that's where most of the increase sits.

Then write to clients early. A good few years of my Java stint went on invoicing code for a utility company, and the lesson that outlived the codebase is that customers forgive a price rise far more readily than a surprise on the bill, which is why I'd send these emails in October while there's still a cheaper option to offer.

A verdict for each kind of site:

For the most common case, a monthly Basic site, something like this works:

Hi name, Webflow is updating its prices, and your website's plan moves to the new price at its first renewal on or after November 16, going from $18 to $25 a month on monthly billing. If we switch to yearly billing before November 16, you keep today's yearly rate of $14 a month for another twelve months, which is $168 paid upfront and non-refundable, and after that it renews at $15 a month. Shall I make the switch, or would you like a quick call about the options first?

And a rough timetable:

• This week: list every site with its plan, billing cycle, renewal date and, for Business sites, recent bandwidth; pull the actual invoice for anything on legacy pricing.
• Before locking anything in: pick the sites going static, since a yearly plan can't be refunded.
• By the end of October: decide per site and send the emails, giving clients a fortnight to approve a yearly payment.
• Before November 16: switch approved monthly Basic and CMS sites, and monthly Business sites on 50 to 100 GB, to yearly; send any Client Payments invites.
• On or after November 16: move monthly Business sites under 50 GB to yearly, landing them on Premium at $25.
• Before each site's next renewal: move the brochure sites you're taking static.

Frequently asked questions

How much does Webflow cost for a freelancer or agency?

The Webflow Freelancer plan costs $16 a month billed yearly or $24 monthly, and the Agency plan $35 yearly or $42 monthly, per webflow.com/pricing in October 2026; neither changed in the 2026 update. On top of that you pay one Site plan per live client site: $220 a month in total for the ten-site example today, and $274 after renewal if nobody touches the billing.

What is the difference between a Webflow Site plan and a Workspace plan?

The Workspace plan covers you and your team: seats, staging sites, code export, client seats and Client Payments. A Site plan covers one published site's custom domain, bandwidth, pages and CMS, and it's the part that changes on November 16.

Can I keep my old Webflow pricing?

For one more yearly term at most. A monthly-billed site switched to yearly billing before November 16 keeps today's yearly price for one more year, and a yearly site that renews before November 16 renews at today's price for another full year; beyond that there's no grandfathering. Webflow's nonprofit discount won't help most existing charity sites either, as it only applies to a new Premium plan billed yearly (see Option 1).

Is Webflow still worth it for agencies?

For CMS-driven sites, client-edited sites and Ecommerce, I reckon it is; Premium at $25 a month on yearly billing is a fair price for 20,000 CMS items, and Client Payments and clean transfers make the client side tidier than it's ever been. The small static brochure site on monthly billing is harder to justify, and that's exactly where the November increase bites hardest.