What happened to the Webflow Editor?
Webflow replaced it, in Webflow's words, swapping "the one-size-fits-all approach of our legacy Editor" for "seats, roles, and permissions". The Editor, now called the legacy Editor, had let clients and content editors change text, images, and CMS items on the live site without opening the Webflow Designer, where the design and layout are built. Its shutdown ran in three steps.
| Date | What happened |
|---|---|
| February 2, 2026 | Webflow announced the deprecation; client seats became available on Workspace plans for freelancers and agencies |
| May 4, 2026 | Automatic migration began: existing legacy Editor users got a free limited seat or client seat, over about two weeks, and new legacy Editor invites stopped |
| August 4, 2026 | The legacy Editor and Editor whitelabeling stopped working |
Migrated Webflow Editor users were all assigned the Content editor role. People on freelancer and agency plans got a client seat for each legacy Editor user, and Team plans got a limited seat for each. Webflow's FAQ says there's no end date currently planned for these free seats and that it will give an update if that changes.
Whitelabeling, which let agencies brand the Webflow Editor, went with it. If your team still has old bookmarks with ?edit at the end, they belonged to the legacy Editor; the new shortcut is ?update.
How do you edit website content without the Webflow Editor?
You open the site in Webflow and edit website content on the canvas. From the Webflow Dashboard, hover over the site and click Open in Webflow, or add ?update to the site's URL. Then change copy, replace images, or update a URL directly on the page.
Content editing does more than the Webflow Editor did.
| Capability | Legacy Editor | Content editing now |
|---|---|---|
| Publish to the staging domain and the custom domain | No | Yes |
| Comments | No | Yes |
| Edit dynamic content (CMS items) on the canvas | No | Yes |
| Edit content inside interactive elements, such as tabs and sliders | No | Yes |
| See which pages teammates are working on | No | Yes |
| Edit localized content | No | Yes |
| Manage image alt text | No | Yes |
| Quick-edit shortcut | ?edit | ?update |
| Editor branding (whitelabeling) | Yes | No |
Five details help a marketing team work safely:
- Designers decide what's editable. Site managers and designers control which elements content editors can change, so the layout stays protected.
- CMS changes save as drafts. In the CMS panel, edits are automatically saved in draft state; on the canvas, the CMS status in the top bar gives options such as the slug and Publish now.
- Content editors can't change design. They can't make structural, style, or element settings changes, add custom code, change CMS settings, or create CMS Collections.
- Some page settings are editable. Content editors can manage a page's SEO settings, such as the SEO title and meta description, plus Open Graph settings and password protection, but they can't change page names, folders, or slugs.
- The last edit wins. Several people can work in Webflow at the same time, but if two people edit the same content, Webflow keeps the last edits, so agree who edits what.
In alternate locales, a globe icon above a selected text element applies or removes machine translation. Webflow's AI copy generation is available to designers and content editors once it's turned on in Workspace settings, and it uses Webflow AI credits.
Can content editors edit static and dynamic content?
Yes. Webflow says members with the Content editor role can edit static and dynamic site content. Static content is text and images placed on a page; dynamic content is bound to CMS data, such as the title and body of blog posts in a Collection. CMS content can be edited on the canvas or in the CMS panel, and content editors can publish individual Collection items without publishing the entire site.
Which roles and seats does a marketing team need?
Give each person the smallest role that does the job; most non-technical users need only the Content editor or Reviewer role. Webflow has five seat types: full, limited, client, free, and guest.
| Person | Webflow role | Seat | What they can do |
|---|---|---|---|
| Writer or content marketer | Content editor | Limited, or client on an agency's Workspace | Update text, replace images, manage CMS Collection items such as blog posts |
| Marketing manager who builds landing pages | Marketer | Limited, or client | Create and edit pages using components |
| Stakeholder who approves copy | Reviewer | Free | View and comment on sites |
| Web designer or developer | Designer or Site manager | Full | Design with all features in the Webflow Designer; Site managers also manage site settings |
| Workspace owner or admin | Owner or Admin | Full | Manage the Workspace, members, and billing settings |
| Agency or freelancer working on your site | Guest | Guest | Design a client's site from their own Workspace |
A few rules make this cheaper and safer:
- A limited seat is required for the Content editor role. Extra limited seats can be purchased.
- Reviewers don't need a paid seat. Webflow says that assigning the Reviewer role to someone on a limited seat moves them to a free seat.
- Roles can differ by site. The same person can be a Content editor on one site and a Reviewer on another; Webflow lets you change site role assignments on Growth, Agency, and Enterprise Workspace plans.
- Enterprise teams can go further. Workspace owners and admins on Enterprise can create up to 20 custom roles, with permissions such as publishing a single page to production, approving changes, and using Webflow AI.
Who can publish, and how do approvals work?
Only people you allow. Site managers can publish to the live site; Designers, Marketers, and Content editors can publish only when "Can publish" is turned on for them; Reviewers can't publish at all.
| Action | Site manager | Designer | Marketer | Content editor | Reviewer |
|---|---|---|---|---|---|
| Publish to the live site | Yes | If "Can publish" is on | If "Can publish" is on | If "Can publish" is on | No |
| Create, update, delete, and publish CMS items | Yes | Yes | Yes | Yes | No |
| Create and delete CMS Collections | Yes | Yes | No | No | No |
| Create page branches (plans with branching) | Yes | Yes | Yes | Yes | No |
| Merge page branches | Yes | Yes | No | No | No |
For publishing workflows with approvals, Webflow's newer tools are on higher plans:
- Page branching. Since July 2026, several people can edit the same page branch at once and review and approve changes before merge, on Enterprise. Webflow's May 2026 pricing update also lists page branching on its new Team plan.
- Single-page publishing. Marketers and designers can launch a page without publishing the entire site, on Enterprise and on the Team plan. People with page-specific access can publish only the pages they're allowed to edit, and admins can stop them from publishing the full site.
- Locale-specific access. On Enterprise, you can limit editors to the locales they manage.
On plans without branching, a simple rule works: publish to the webflow.io staging domain first, have a reviewer comment there, then publish to the live site. Our Webflow Enterprise guide covers custom roles, SSO, and audit logs in more depth.
What should you check when an agency hands over a Webflow site?
Ownership first, then access. Webflow says that if a site is in a freelancer's or agency's Workspace, that Workspace owns the site, and that a client managing billing doesn't get extra rights over ownership.
Use this handover checklist:
- Site ownership. Agree in writing who owns the site and whether you can transfer or duplicate it. Webflow says the client won't automatically have those rights unless it's explicitly agreed.
- Billing. With client payments, available on Freelancer and Agency Workspace plans, clients pay for their own site plans, bandwidth, and add-ons in Webflow, and a paid site can move to the client's Workspace. For what the November 16, 2026 plan change means for billing, see our post on the Webflow price increase.
- Workspace ownership. Only the Workspace owner can request a transfer of ownership, and the Workspace needs enough seats for it.
- Seats and roles. List every person, their role, and their seat, including anyone who had Editor access before the migration. Client seats can't go to someone who shares the business email domain of the agency's Workspace owner.
- Publishing rights. Decide who has "Can publish", and write it down.
- Guest access. If the agency works as a guest, decide when to remove its Workspace. Webflow says that once a guest Workspace is removed, all of its members lose access to your sites.
- Two-factor authentication. Each person sets up 2FA on their own account. Webflow shows eight backup codes only once, at setup, so store them safely.
- Backups. Webflow creates a restore point on every 50th auto-save, and only Site managers can access backups. Restoring a backup turns bot protection off, so turn it back on afterward.
- Domain and DNS. Confirm the domain registrar account is in your company's name and that your team can log in.
- Documentation. Ask for a list of editable elements, components, and CMS fields, and which pages marketers can build.
Our website maintenance checklist covers the access reviews to repeat every quarter after handover.
We build and support Webflow sites for B2B SaaS companies, so we have an interest in this topic. For how ongoing support works, see our ongoing website support page.
Questions about the Webflow Editor
Is the Webflow Editor still available?
No. Webflow says the legacy Editor and whitelabeling are no longer available starting August 4, 2026. Content editing now happens in Webflow's core platform, using roles such as Content editor.
What replaced the Webflow Editor?
Seats, roles, and permissions inside Webflow. Members with the Content editor role can edit site content and manage assets directly in Webflow, and the Marketer role can also create and edit pages using components.
Does a content editor need a paid seat?
A limited seat is required to assign the Content editor role. Legacy Editor users were migrated to a free limited seat or client seat with no end date currently planned, and additional limited seats can be purchased.
Can content editors publish a Webflow site?
Yes, if 'Can publish' is turned on for them. They can then publish to the webflow.io staging subdomain or to the production domain. Reviewers can view and comment but can't publish.
How do you open a Webflow site for editing?
From the Webflow Dashboard, hover over the site and click Open in Webflow, or add ?update to the site's URL. The old ?edit shortcut belonged to the legacy Editor.
Sources
- Webflow Updates: Legacy Editor deprecation Accessed October 23, 2026
- Webflow Blog: Legacy Editor deprecation Accessed October 23, 2026
- Webflow: Legacy Editor migration hub Accessed October 23, 2026
- Webflow Help Center: Legacy Editor deprecation FAQ Accessed October 23, 2026
- Webflow Help Center: What's the difference between the legacy Editor and content editing Accessed October 23, 2026
- Webflow Help Center: Feature sunsets Accessed October 23, 2026
- Webflow Help Center: Seats, roles, and permissions overview Accessed October 23, 2026
- Webflow Help Center: Site roles and permissions Accessed October 23, 2026
- Webflow Help Center: Create and manage custom roles Accessed October 23, 2026
- Webflow Help Center: Edit site content as a content editor Accessed October 23, 2026
- Webflow Help Center: Updated pricing and simplified plans for May 2026 Accessed October 23, 2026
- Webflow Updates: Real-time collaboration on branches Accessed October 23, 2026
- Webflow Updates: Single-page publishing Accessed October 23, 2026
- Webflow Updates: Single-page publishing access Accessed October 23, 2026
- Webflow Updates: Locale-specific access control Accessed October 23, 2026
- Webflow Help Center: Generate copy with AI Accessed October 23, 2026
- Webflow Help Center: Client payments Accessed October 23, 2026
- Webflow Help Center: Site ownership Accessed October 23, 2026
- Webflow Help Center: Transfer Workspace ownership Accessed October 23, 2026
- Webflow Help Center: Client seats Accessed October 23, 2026
- Webflow Help Center: Guests Accessed October 23, 2026
- Webflow Help Center: Two-factor authentication Accessed October 23, 2026
- Webflow Help Center: Site backups Accessed October 23, 2026
- BenorMedia: Webflow price increase: what to check before the November 16, 2026 change Accessed October 23, 2026
- BenorMedia: Webflow Enterprise: What to Check Accessed October 23, 2026































