Webflow's Agency Workspace plan costs $35 a month billed yearly, or $42 billed monthly, and its most useful line is easy to miss: three free client seats on every site, staged or paid, according to Webflow's pricing page as of 28 October 2026. That line matters more than it did a year ago, because Webflow fully retired the legacy Editor on 5 October 2026. Every client who edits a Webflow site now needs a seat somewhere.
Below: what the plan includes, the five kinds of seat, the three ways a finished site reaches a client, and what changes when a white-label partner builds. Every price and rule comes from Webflow's own pricing page and help centre, read on the date above; they are vendor documents and change often.
What the Agency Workspace plan includes in 2026
Webflow splits billing in two. A Site plan pays for hosting one site on a custom domain: Basic is $15 a month and Premium, which adds the CMS, is $25, both billed yearly. A Workspace plan pays for the place where sites are staged and where people collaborate. Agencies and freelancers get their own family of Workspace plans, separate from the Core and Growth plans sold to in-house teams.
| Feature | Starter | Freelancer | Agency |
|---|---|---|---|
| Price, billed yearly | Free | $16 a month | $35 a month |
| Price, billed monthly | Free | $24 a month | $42 a month |
| Staging sites on webflow.io | 2 | 10 | Unlimited |
| Pages per staged site | 2 | 300 | 300 |
| Free client seats | 1 per paid site | 1 per site, staged or paid | 3 per site, staged or paid |
| Client payments | No | Yes | Yes |
| Guest access in client Workspaces | No | Yes | Yes |
| Shared Libraries | None | 1 | Unlimited |
| Site-level roles and publishing permissions | No | No | Yes |
| Password protection, 301 redirects, badge removal on staged sites | No | No | Yes |
| AI credits a month | 200 | 300 | 400 |
Source: Webflow pricing page and "Choose a Workspace plan" help article, read 2026-10-28
Published sites do not count against the staging limit, so the Freelancer plan's ten staging sites cap work in progress, not clients. The other reason to pay the extra $19 a month is control: only the Agency plan lets you decide who can publish which site.
The five kinds of seat, and who should sit in each
Webflow separated people from Workspace plans in December 2024. Since then, the plan decides features and the seats decide people. Each person fills one seat, and the seat limits which roles they can hold.
| Seat | Price | Roles available | Typical person |
|---|---|---|---|
| Full seat | 1 included; extra $39 a month yearly, $45 monthly | Admin, Site manager, Designer | Your developers and designers |
| Limited seat | $15 a month yearly, $19 monthly | Marketer, Content editor | An account manager who builds campaign pages |
| Free seat | $0, up to 100 | Reviewer | Stakeholders who only comment |
| Client seat | Free, 3 per site on Agency; cannot be bought | Marketer, Content editor, Reviewer | The client's marketing lead |
| Agency or freelancer guest | Free; needs a Freelancer or Agency plan | Site manager down to Reviewer, as the host allows | A partner studio or contractor team |
Source: Webflow pricing page; "Seats, roles, and permissions overview" and "Manage client seats", Webflow Help Center, 2026
Client seats are per site. Filling one on site A does nothing to site B. If five people at a client want to edit, three fit in client seats and the rest need paid limited seats, or the site moves to the client's own Workspace.
The email domain rule. You cannot put someone in a client seat, or invite them as a guest, if they share the Workspace owner's business email domain. That includes a contractor using your agency's email address.
Marketer or Content editor. A Marketer can build new pages from your components and publish when allowed; a Content editor changes existing content and CMS items only. For most B2B clients, Marketer is the role that stops "can you add a landing page" tickets, provided the component kit is good. Our guide to building a website the marketing team can actually edit covers how to design that kit.
The Editor is gone: what that changed for agencies
Until this year, clients edited content through the legacy Editor, which needed no seat and no proper Webflow account. Webflow's deprecation FAQ sets out the timeline: client seats arrived for freelancer and agency Workspaces on 2 February 2026, an automatic migration started on 4 May 2026, the Editor stopped being available on 4 August, and editing through the ?edit link was switched off on 5 October 2026.
The automatic migration gave each eligible Editor user one client seat for each site they could access, with the Content editor role. Anyone who had been invited but never created an account was not migrated, so those people now need a fresh invitation. If a client says they "cannot get into the Editor", the fix is an invite from Site settings, Site access, Clients, not a password reset.
Three ways a finished site reaches the client
Once a site is built, an agency has three options, which differ in who pays, who controls the site, and whether you can still work on it.
| Transfer to the client | Client payments | Client hosts, agency as guest | |
|---|---|---|---|
| Where the site lives | Client's Workspace | Agency's Workspace | Client's Workspace |
| Who pays the Site plan | Client | Client, by card on file | Client |
| Who controls the site | Client | Agency | Client, with agency access |
| Can the agency keep editing | Only if re-invited as a guest | Yes | Yes, within allowed roles |
| Plan needed on the agency side | Freelancer or Agency | Freelancer or Agency | Freelancer or Agency |
| Downtime | None, unless Enterprise is involved | None | None |
| Fits | Clients who want to own the asset | Managed-site retainers | Long retainers with an owner-minded client |
Source: "How do I transfer a site or plan to another workspace?", "Client payments" and "Agency or Freelancer guest role overview", Webflow Help Center, 2026
Transfer. From a Freelancer or Agency Workspace, a site moves to the client's Workspace with its paid Site plan and connected domains, with no downtime once the client accepts by email. If you were paying, you get a prorated credit for unused time. The exception is Enterprise: if the destination is an Enterprise Workspace, or the source is Core, Growth or Enterprise, the site must be downgraded to Starter first, which takes a published site offline until it is upgraded and republished.
Client payments. The site stays with you and the client's card pays for the Site plan and add-ons. One client per site; they get the Content editor role by default. You can transfer the site outright later.
Guest access. The client owns the Workspace and invites your team as a guest. Guests see only the shared sites, never Team, Plans or Billing. A self-serve host can admit two guest teams of up to five people each for free.
Our white-label Webflow development guide explains how these choices fit the wider handover; the short version is that transfer suits most B2B clients and client payments suits agencies that sell the site as a managed service.
What resets when a site changes Workspace
A transfer moves the build intact: styles, static and CMS pages, assets, backups, Collections, custom code, fonts, form submissions and 301 redirects. Webflow resets anything tied to an account or an email address.
| Moves with the site | Reset or removed on transfer |
|---|---|
| Classes, global styles, pages and CMS content | Form notification settings |
| Assets, custom fonts, custom code | reCAPTCHA keys (reCAPTCHA stays enabled) |
| Site backups and form submissions | Adobe Fonts API key |
| 301 redirects and site settings | Billing and email-specific details |
| Ecommerce products and order history | Comments |
| Shared Library components, copied to the site | The Library link itself, and third-party app authorisations |
Source: "How do I transfer a site or plan to another workspace?", Webflow Help Center, updated 2026-08-01
Three consequences follow. Form notifications must be set again by the client. Library components become plain site components, so later kit updates will not reach that site. And a site listed on Made in Webflow must be removed, with Creator Credits cleared, before the transfer works. Our Webflow client handover kit turns these into a checklist.
What changes when a white-label partner builds for you
A partner does not need one of your paid seats. Webflow's guest role is built for this: its help centre lists "an agency inviting a contractor" as one of the expected host types. The partner must hold its own Freelancer or Agency plan, then joins your Workspace as a team and adds up to five of its people.
There are three workable set-ups, each with a different white-label exposure.
Partner as a guest in your Workspace. The partner builds on your staging sites; you transfer or bill the client from your Workspace. The client never sees the partner, and on an Agency plan you can switch off the guest team's publishing so nothing goes live without your say.
Partner builds in its own Workspace, then transfers to you. The partner hands the finished site to your Workspace, and you hand it to the client. It adds a second transfer and a second round of resets, so form notifications and app logins are checked twice.
Partner as a guest in the client's Workspace. This only works when the client knows a partner exists. Guest teams appear in the client's team settings under a display name the partner sets when joining, so the client can see that a second studio has access. If the arrangement is meant to be silent, avoid this route.
Whichever you choose, write it into the agreement. Our post on what to put in a white-label agency contract covers the clauses; add one line saying whose Workspace the build lives in and when the partner's access ends. On a white-label build, we would normally ask to join the agency's own Workspace as a guest and leave it on handover, though the agency decides.
A worked cost example. Take a three-person agency shipping a dozen sites a year with a partner doing the builds. At list prices: the Agency plan is $420 a year, two extra full seats are $936, and one limited seat for an account manager is $180, so $1,536 a year before any Site plans. The partner's guest team adds nothing to that, and with client payments or a transfer, Site plans sit on the clients' cards. The figures are Webflow's October 2026 yearly prices, before tax.
What this means for an agency choosing a Workspace plan
If you run fewer than ten builds at once, edit only through your own team and never need to stop someone publishing, the Freelancer plan at $16 does the job. Move to Agency when any of three things is true: clients need more than one editor per site, you work with partners or contractors whose publishing you want to control, or your staging list keeps hitting ten.
Set it up before the first partner build. Decide which Workspace owns staging, which roles the partner's guest team may hold, whether the client gets a transfer or a payment request, and who audits client seats after launch. Our white-label service page explains how we scope builds for agencies.
