Webflow Roles, Seats & Pricing Explained - 2026 Guide

If there's one thing that makes new Webflow users' eyes glaze over faster than you can say "workspace plan," it's the roles and pricing structure. We've had this conversation with clients more times than we can count, and honestly? Webflow doesn't make it easy on themselves. The documentation exists, but it's scattered, the terminology isn't always consistent, and by the time you've cross-referenced three help articles you've forgotten what you were trying to figure out in the first place.

So we wrote this. Consider it the guide we wish existed when we started.

Fair warning: this is a long one. Grab a coffee. We've structured it so you can jump to the section you need, but if you're new to Webflow or setting up a client workspace for the first time, we'd recommend reading the whole thing. It'll save you a headache later.

First, the thing that trips everyone up

Webflow has two completely separate billing layers, and confusing them is the number one source of "why am I being charged this?" emails we get from clients.

Workspace Plan — this controls who can access your workspace, how many staging sites you can have, and what collaboration features you get. Think of it as your studio. The monthly fee you pay here is about your team and your tools, not your website being live on the internet. Usually, a Free one is fine for small teams.

Site Plan — this controls hosting. Your custom domain, your bandwidth, your CMS item limits. This is billed per site, separately from your Workspace Plan. It's the rent on each individual property you manage.

A Workspace Plan alone does not put your site live on a custom domain. You need both. We can't tell you how many times a client has upgraded their workspace thinking it would fix their site not going live on their domain. It won't. You still need a Site Plan.

Right. Now that's out of the way, let's get into it properly.

The two types of roles (yes, two)

Every person you add to Webflow gets two roles simultaneously — one at the Workspace level and one at the Site level. They're related but separate, which is where a lot of confusion creeps in.

Your Workspace Role applies to the entire account. It determines what someone can do in the workspace itself — things like managing billing, inviting team members, and accessing workspace settings.

Your Site Role applies to a specific site. The same person can have a Designer role on one site and a Content Editor role on another. This is actually really useful once you know it's there.

When you assign someone a Workspace Role, Webflow automatically gives them a matching default Site Role. On Growth, Agency, and Enterprise plans, Admins and Site Managers can then override that Site Role per site. On lower plans, it's more rigid.

The seven workspace roles, explained like humans

Owner

The account holder. Full control of absolutely everything — design, billing, team management, the lot. There's only one Owner per workspace, and transferring ownership is possible but involves a bit of back-and-forth with Webflow. Use a proper business email when you create the account. Not your personal Gmail. We've seen this cause problems at handoff time and it's entirely avoidable.

Admin

Basically the Owner minus billing access. Can design, manage team members, and control site settings across the workspace. Your senior designer or project lead would typically sit here. If you're an agency and you want a client to have real control without handing over billing, Admin is a good fit.

Site Manager

Full design access, but scoped to only the sites they're assigned to. Can manage settings for those sites, can't touch anything workspace-wide or mess with billing. Good for a project lead or account manager who needs to be hands-on with specific sites but doesn't need the whole workspace.

Designer

Full design and dev access. Can build, publish (with a toggle on higher plans), add custom code, access backups. No workspace management. This is the standard role for anyone building in the Designer — developers, designers, the works. Milk Moon Studio sits here when we access client workspaces as a guest team.

Marketer

Can build using pre-approved components and edit content. Can't touch the design system, can't add custom code. Ideal for a marketing team member who needs to create landing pages or update content but you don't want near the underlying structure of the site. They can publish with the toggle enabled, which is either great or terrifying depending on your setup.

Content Editor

Text, images, links. That's it. No design changes, no structural changes, no publishing the full site (though they can publish individual CMS items). Perfect for the client's copywriter, their blog manager, or the person who's going to be updating products. This is the most common role we set up for clients themselves.

Reviewer

Comment-only. They can view the site in the Designer and leave feedback, but can't change anything. No account required if you share a comment link — which means the CEO who just needs to approve the homepage doesn't need to create a Webflow login. This is genuinely one of the most underused features in Webflow. Share a link, get feedback, done.

Enterprise note: Enterprise plans get up to 20 custom roles with granular permission toggles. Want a junior designer who can push to staging but needs approval before going live? That's a custom role. This replaces the old "Limited Designer" and "Designer (needs approval)" roles that used to exist.

Site roles and what they actually let you do

Here's the practical breakdown of what each role can and can't do on a given site. We've written this out instead of using a table because tables don't paste into Webflow rich text without turning into a mess.

Full design access (build freely in the Designer): Owner, Admin, Site Manager, Designer. Not available to Marketer, Content Editor, or Reviewer.

Build using components (use pre-approved components to create pages): Owner, Admin, Site Manager, Designer, and Marketer. Not Content Editor or Reviewer.

Edit content and copy (change text, swap images, update links): Everyone except Reviewer.

Publish the entire site: Owner, Admin, and Site Manager always can. Designer and Marketer can, but only if the "Can Publish" toggle is enabled for them on Growth and Agency plans. Content Editor and Reviewer cannot publish the full site.

Publish CMS items individually (update a blog post, add a product without doing a full publish): Owner, Admin, Site Manager, Designer, Marketer, and Content Editor. Not Reviewer.

Manage site settings, custom code, and backups: Owner, Admin, Site Manager, and Designer. No one else.

Manage billing: Owner only. Full stop.

Download form submissions: Everyone except Reviewer.

Worth knowing: Even if a Designer or Marketer doesn't have full publish permissions, they can still publish individual CMS items. So your content editor can keep the blog updated without accidentally pushing a broken homepage redesign live. That's the feature you actually want.

Seats — the bit that costs money

Every team member needs a seat to access your workspace. The seat type determines what roles they can be given and how much you pay. This is where a lot of people get surprised by their Webflow bill.

Full Seat — $39/month (annual)

Required for Owner, Admin, Site Manager, and Designer roles. Anyone who's actually building in the Designer needs one of these. You get one Full Seat included in your Workspace Plan price — so if you're a solo operator, you're not paying $39 on top of your plan fee for yourself. That's already included.

Limited Seat — $15/month (annual)

For Marketer and Content Editor roles. The right seat for your client's marketing manager or the person who'll be writing blog posts. They get meaningful access without getting near anything design-related, and it costs less than half a Full Seat.

Free Seat (Reviewer) — $0

Comment-only access. Free. Up to 100 Reviewer seats per workspace. If your client's CEO, legal team, and entire board of directors need to review the site, you can add all of them as Reviewers and it won't cost a cent. Again — massively underused.

Client Seat — $0

Site-specific content editing access. Free and included in your plan. The person with a Client Seat can only see and edit the specific site they're assigned to — they can't see other sites in your workspace, can't touch workspace settings, nothing. This is the cleanest way to give a client content editing access without creating any risk. More on this below.

Guest Seat — $0

This is how agencies like Milk Moon access client workspaces. We get invited as a guest team — free, doesn't count against your seat limits, and gives us Designer-level access to build your site. We can't see billing, can't manage your team, can't touch anything outside the sites we're working on. Most plans allow up to 2 guest teams (5 people per team). Enterprise bumps that to 10 guest teams.

One thing that catches people out: removing a team member doesn't automatically reduce your seat count. You need to go into workspace settings and manually remove the seat. Otherwise you'll keep paying for it.

Workspace plans — which one do you actually need?

Workspace Plans split into two tracks depending on whether you're an agency or an in-house team. Here's the honest breakdown.

For freelancers and agencies

Starter — Free
Two staging sites, one Full Seat, basic access. No code export. You can invite up to 2 guest teams, which is how your clients can give you access at no cost to them. Enough to get started and test things out. Most clients who just need a website live don't need anything more than this.

Freelancer — $16/month (annual)
Ten staging sites, code export, client workspaces, site transfers, and white-labeling. If you're working across multiple client projects and need to transfer sites when they're done, this is the minimum viable agency plan.

Agency — $35/month (annual)
Unlimited staging sites, everything in Freelancer plus site-specific access controls, site-level role overrides, publishing permission toggles per Designer, Shared Libraries, and 3 client seats per site. If you're running a proper agency operation, this is where you want to be. The jump from Freelancer to Agency for $19/month more is very much worth it once you're dealing with multiple clients and want that granular control.

Enterprise — Custom pricing
Custom roles, SSO, SCIM provisioning, audit logs, SLAs, dedicated support. If you need to ask what this costs, you probably don't need it yet.

For in-house teams

Starter — Free
Same as above — two staging sites, basic access. Fine for a small team just getting started.

Core — $19/month (annual)
Ten staging sites, code export, custom code, password-protected pages, and basic guest access. The right plan for a small internal team managing one or two sites.

Growth — $49/month (annual)
Unlimited staging, site-specific access, site-level role overrides, publishing permissions, Shared Libraries. The equivalent of Agency for in-house teams. If your company has a proper marketing team managing Webflow, this is where you'll end up.

Enterprise — Custom pricing
Everything, plus advanced security and governance features.

Which track do you use? If you're building sites for clients and transferring them when done, use Freelancer/Agency. If a company is managing its own Webflow site with an internal team, they use Core/Growth. The features are very similar — the tracks exist mostly because the billing model and handoff workflows are different.

Site plans — what your client actually pays for hosting

These are billed per site, separate from your Workspace Plan. You need one for every site that goes live on a custom domain.

Starter — Free
Two static pages, 50 CMS items, 1GB bandwidth. Webflow subdomain only (yoursitename.webflow.io). Useful for staging and internal previews. Not for live client sites.

Basic — $14/month (annual)
150 pages, no CMS, 10GB bandwidth, custom domain. For static sites — landing pages, portfolios, brochure sites with no dynamic content. If there's no blog and the content doesn't change often, this is all you need.

CMS — $23/month (annual)
150 pages, 2,000 CMS items, 50GB bandwidth. The most common plan we set clients up on. Blog, case studies, team pages, service listings — if any of it is CMS-powered, this is your minimum.

Business — $39/month (annual)
300 pages, 10,000 CMS items, 100GB bandwidth. For high-traffic sites or anything with a lot of content. You'd typically only need this if you're hitting CMS or bandwidth limits on the CMS plan.

Enterprise — Custom
Everything, plus SLAs, enterprise security, and support. For large organisations with specific compliance or uptime requirements.

Ecommerce site plans

Standard — $29/month (annual)
500 products, 2% transaction fee. For small shops just getting going.

Plus — $74/month (annual)
5,000 products, no transaction fee. The right plan once you're past early-stage and moving real volume.

Advanced — $212/month (annual)
15,000 products, no transaction fee. Large established stores with high SKU counts.

Annual vs. monthly: Annual billing is roughly 20–25% cheaper across the board. A CMS plan is $29/month on monthly billing and $23/month on annual — that's $72 saved per year, per site. If a client is committing to more than a few months, always push them toward annual.

How to give clients access without giving them the keys

This is the question we get asked most often in one form or another: "How do I let my client update their own content without breaking everything?"

Here are your options, from simplest to most involved.

Client Seat (our default recommendation)

Free. Site-specific. The client can only see and edit the one site they're assigned to. They can update text, swap images, manage CMS items. They cannot publish the full site (they can publish individual CMS items), they cannot see other sites in your workspace, and they cannot touch anything structural. This is included in your Workspace Plan — 1 per site on Starter and Freelancer, 3 per site on Agency. For most clients, this is all they need.

Reviewer link

Share a staging link and anyone with it can leave comments on the site without creating a Webflow account. Great for approval rounds, great for getting feedback from stakeholders who don't need ongoing access. Zero cost, zero friction.

Limited Seat — $15/month

For a client-side marketing person who needs to do more than just edit content — someone who's going to be building landing pages using pre-approved components, or who needs access across multiple sites in their workspace. This gives them Marketer or Content Editor role workspace-wide.

Guest team access

If another agency or developer needs to work on the site alongside you, this is the way. Free, up to 5 people per guest team, up to 2 guest teams on most plans. They get Designer-level access on the sites you grant them, nothing else.

Real-time collaboration — it's live now

As of late 2025, Webflow's multiplayer collaboration is out of beta and enabled on all sites by default. It works like Figma — multiple people in the Designer simultaneously, on the same or different pages, seeing each other's changes in real time. Colour-coded avatars, element highlights, the works.

Everything auto-saves. No more manual saving, no more "I published over your work." If two people edit the same element at the same time, last-write-wins — whichever change hit Webflow's servers last is the one that sticks. Webflow will notify you if there's a conflict.

You can also edit CMS content directly in the Designer context now, without needing to switch to the legacy Editor. That's a genuine quality-of-life improvement.

A few gotchas worth knowing:

• Real-time collaboration is not compatible with legacy interactions (the old IX system). If your site uses classic interactions, you'll need to keep that in mind.
• Page branches, approval workflows, and the legacy Editor still exist on real-time enabled sites, but they're single-user only — they won't play nicely with multiplayer sessions.
• On slower connections (yes, we're looking at you, rural South Africa), syncing can lag, which increases the chance of a conflict. Work on a stable connection when you're collaborating live.
• If you restore from backup while someone else is in the Designer, the site locks for everyone until the restore is done. You'll get a confirmation email when it's finished.

What does it actually cost? A quick reference

Let's make it concrete. All prices are annual billing.

• Host one site with CMS: CMS Site Plan — $23/month per site
• Host one static site: Basic Site Plan — $14/month per site
• Run an agency operation: Agency Workspace — $35/month
• Add a second designer: +1 Full Seat — $39/month
• Add a content editor or marketer: +1 Limited Seat — $15/month
• Give a client content editing access: Client Seat — free (included in your plan)
• Let a stakeholder review and comment: Reviewer Seat — free
• Invite another agency to collaborate: Guest team — free (up to 2 teams)

A real-world example: what Milk Moon Studio's setup looks like

• Agency Workspace plan — $35/month (covers unlimited staging, Shared Libraries, site-level role controls)
• One Full Seat included in that $35 — that's the first person sorted
• Any additional designers — $39/month per Full Seat
• Client content editing — 3 free Client Seats per site, no extra cost
• Stakeholder approvals — share a Reviewer link, free, no account needed
• Client pays for their own hosting — we use Webflow's Client Billing feature so they add their card directly and Webflow invoices them for the Site Plan. We never touch their card details.

A real-world example: a client with an in-house marketing team

• Growth Workspace plan — $49/month (site-specific access, publishing permissions)
• Senior developer/designer — 1 Full Seat at $39/month
• Marketing manager building pages and updating content — 1 Limited Seat at $15/month
• CEO reviewing designs — free Reviewer seat, shares comment links, never logs in
• Site hosted on CMS plan — $23/month

In reality a very small team might only need a Site Hosting Plan if they just need access for one user. We have a free agency guest seat, the client has the free Workspace seat and everyone is happy for $23/mo with the above being an example for larger teams.

The most common mistake we see

Clients buying a paid Workspace Plan thinking it means their site is live.

It doesn't. A Workspace Plan is about your team and your tools. You still need a Site Plan to go live on a custom domain. They are completely independent. Always have been, always will be.

The second most common mistake: buying a Full Seat for someone who only needs to update blog posts. That's a $39/month seat where a $15/month Limited Seat would do the job just fine. Over a year, per person, that's $288 unnecessarily spent. Not the end of the world, but also entirely avoidable.

That's the whole picture. Roles, seats, plans, pricing, collaboration — all of it. Bookmark this one, you'll probably refer back to it.

If you've got questions about how any of this applies to your specific setup, drop us a message. We set up Webflow workspaces for clients regularly and we're happy to help you figure out the right configuration without buying more than you need.