Subscribe now for best practices, research reports, and more.
You are now subscribed.
In December 2024, we announced that we would be deprecating our legacy Editor. We know this change has been a long time coming, and we appreciate your patience as we finalized the details. Today, we’re sharing everything you need to know, including key dates, migration details, and resources to help you prepare with confidence.
Before we dive in, here are the most important pieces of information:
The legacy Editor will no longer be available starting August 4, 2026, giving you time to prepare before this change takes place.
Starting May 4, 2026, existing legacy Editor users will be given access to a free limited seat or client seat as part of the automatic migration.
As of today, client seats are available on Workspace plans for freelancers and agencies.
The short version
Skip ahead to the sections that matter most to you:
Here’s an overview of what to expect with the deprecation:
Deprecation overview
Starting Feb 2, 2026
Starting May 4, 2026
Starting Aug 4, 2026
Agency, Freelancer, or Starter* Workspace plans
Client seats now available; no change to legacy Editor invites
Automatic migration begins
Each existing legacy Editor user gets access to a free client seat
Legacy Editor still available, but new legacy Editor users can no longer be invited
Legacy Editor no longer available
Growth, Core, or Starter Workspace plans
No change to workflows or legacy Editor invites
Automatic migration begins
Each existing legacy Editor user gets access to a free limited seat
Legacy Editor still available, but new legacy Editor users can no longer be invited
Legacy Editor no longer available
Migration overview
Agency, Freelancer, or Starter* Workspace plans
Feb 2, 2026:Client seats now available; no change to legacy Editor invites
Starting May 4, 2026: Automatic migration begins. Each existing legacy Editor user gets access to a free client seat. Legacy Editor still available, but new legacy Editor users can no longer be invited.
Aug 4, 2026: Legacy Editor no longer available
Growth, Core, or Starter Workspace plans
Starting Feb 2, 2026: No change to workflows or legacy Editor invites
Starting May 4, 2026: Automatic migration begins. Each existing legacy Editor user gets access to a free limited seat. Legacy Editor still available, but new legacy Editor users can no longer be invited.
Starting Aug 4, 2026: Legacy Editor no longer available
*Starter Workspace plans who have been identified to belong to a service provider.
If you’re an Enterprise customer, reach out to your Customer Success Manager to discuss your migration details.
Prefer to watch instead of read? Check out this video.
Why we’re making this change
For years, the legacy Editor has helped teams and clients collaborate on simple content updates by establishing clear guardrails for what actions a user can and cannot take when editing a site. But as collaboration needs have evolved, Webflow saw an opportunity to reimagine how teams work together.
We built a more flexible and powerful way for teams to collaborate safely in Webflow through seats, roles, and permissions. This includes the introduction of limited seats and client seats, which give users access to three roles that can be assigned based on their specific needs. This includes the Content editor role, which combines the best of the legacy Editor capabilities plus so much more.
Seat
Role
Description
Client or limited seats
Marketer
Build and edit pages using components and templates
(formerly known as Build mode)
Content editor
Update text, images, and CMS content
(formerly known as Edit mode)
Reviewer
View and comment on sites
Note: Assigning the Reviewer role to a user on a limited seat moves them to a free seat, making the limited seat available to assign to someone else.
Seat → Role → Description
Client or limited seats
Marketer: Build and edit pages using components and templates (formerly known as Build mode)
Content editor: Update text, images, and CMS content (formerly known as Edit mode)
Reviewer: View and comment on sites. Note: Assigning the Reviewer role to a user on a limited seat moves them to a free seat, making the limited seat available to assign to someone else.
*As part of the automatic migration, your legacy Editor users will be assigned the Content Editor role by default. You can update their role to Marketer or Reviewer.
While the move away from the legacy Editor may require updates to your workflows, it unlocks more power and flexibility in how your teams and clients collaborate. This marks a shift from the old one-size-fits-all approach of the legacy Editor to a new experience that empowers each user to work with speed, confidence, and the proper guardrails to keep the site safe.
If you’re a freelancer or agency
For customers on an Agency, Freelancer, and Starter (for freelancers and agencies) Workspace plan, each of your existing legacy Editor users that haven’t already been assigned aclient seat by May 4, 2026will be given access to a free client seat as part of the automatic migration.Client seats allow your clients to contribute to a site without giving full design access and they can be assigned a Marketer, Content editor, or Reviewer role. Learn more about each role here.
Check out what your migration journey will look like in the table below. To learn what steps you and your clients should take at each milestone, refer to these migration guides:
Client seats now available; no change to legacy Editor invites
As part of the client seats rollout, you'll automatically receive free, unassigned client seats in your Workspace. The number of seats you receive will be based on the details of your Workspace plan.
You can assign these client seats to clients who don't have legacy Editor access. You can also assign any remaining client seats to existing legacy Editor users to give them early access to the new experience. Click here to see how.
You can continue inviting clients as legacy Editor users in new and existing Workspaces prior to May 4.
Automatic migration begins
Any existing legacy Editor users that you haven't already assigned to a client seat will automatically get access to one for free — no action needed. (These seats are in addition to any client seats assigned before May 4.) Clients will be migrated over the course of two weeks.
Migrated clients will be assigned the Content editor role by default. You can change this to the Marketer or Reviewer role if needed.
Migrated clients can keep using either the legacy Editor or their new role from their client seat prior to August 4.
You can no longer invite clients as legacy Editor users.
Legacy Editor no longer available
From this point on, your clients will need to use their new roles from their client seats to access and update sites.
Key milestones for freelancers or agencies
What's happening
Feb 2, 2026: Client seats now available; no change to legacy Editor invites
As part of the client seats rollout, you'll automatically receive free, unassigned client seats in your Workspace. The number of seats you receive will be based on the details of your Workspace plan.
You can assign these client seats to clients who don't have legacy Editor access. You can also assign any remaining client seats to existing legacy Editor users to give them early access to the new experience. Click here to see how.
You can continue inviting clients as legacy Editor users in new and existing Workspaces prior to May 4.
Starting May 4, 2026: Automatic migration begins
Any existing legacy Editor users that you haven't already assigned to a client seat will automatically get access to one for free — no action needed. (These seats are in addition to any client seats assigned before May 4.) Clients will be migrated over the course of two weeks.
Migrated clients will be assigned the Content editor role by default. You can change this to the Marketer or Reviewer role if needed.
Migrated clients can keep using either the legacy Editor or their new role from their client seat prior to August 4.
You can no longer invite clients as legacy Editor users.
Aug 4, 2026: Legacy Editor no longer available
From this point on, your clients will need to use their new roles from their client seats to access and update sites.
If you’re an in-house team
For customers on a Growth, Core, and Starter (for teams) Workspace plan, each of your existing legacy Editor users that haven’t already been assigned a Workspace seat by May 4, 2026 will be given access to afree limited seat as part of the automatic migration. Limited seats can be assigned a Marketer or Content editor role. Keep in mind that assigning the Reviewer role to a user on a limited seat moves that user to a free seat, making the limited seat available to assign to someone else. Learn more about each role here.
Note: Those on a Core or Starter Workspace plan do not have site-specific access, and anyone with a limited seat can access all sites in the Workspace. To enable site-specific access, you can upgrade to the Growth Workspace plan.
Check out what your migration journey will look like in the table below. To learn what steps you and your teams should take at each milestone, refer to these migration guides:
You can continue inviting team members as legacy Editor users in new and existing Workspaces prior to May 4.
Automatic migration begins
Any existing legacy Editor users that you haven't already assigned to a Workspace seat will automatically get access to a free limited seat — no action needed. Team members will be migrated over the course of two weeks.
Migrated team members will be assigned the Content editor role by default. You can change this to the Marketer or Reviewer role if needed. (Assigning the Reviewer role to a user on a limited seat moves them to a free seat, making the limited seat available to assign to someone else.)
Migrated team members can keep using either the legacy Editor or their new role from their limited seat prior to August 4.
You can no longer invite team members as legacy Editor users.
Legacy Editor no longer available
From this point on, your team members will need to use their new roles from their limited seats to access and update sites.
Key milestones for in-house teams
What's happening
Feb 2, 2026: No change to workflows or legacy Editor invites
Keep doing what you're doing.
You can continue inviting team members as legacy Editor users in new and existing Workspaces prior to May 4.
Starting May 4, 2026: Automatic migration begins
Any existing legacy Editor users that you haven't already assigned to a Workspace seat will automatically get access to a free limited seat — no action needed. Team members will be migrated over the course of two weeks.
Migrated team members will be assigned the Content editor role by default. You can change this to the Marketer or Reviewer role if needed. (Assigning the Reviewer role to a user on a limited seat moves them to a free seat, making the limited seat available to assign to someone else.)
Migrated team members can keep using either the legacy Editor or their new role from their limited seat prior to August 4.
You can no longer invite team members as legacy Editor users.
Aug 4, 2026: Legacy Editor no longer available
From this point on, your team members will need to use their new roles from their limited seats to access and update sites.
Resources and what’s next
Key resources to help make your migration as smooth as possible are available in the Legacy Editor Migration Hub, including the below:
Migration guides — outlines what you and your users need to do at each milestone
We know that the legacy Editor has supported countless teams and clients over the years, and we’re committed to making this transition as smooth and transparent as possible for everyone who still relies on it today. If you work with the legacy Editor, you’ll get an email outlining what this transition means for you. We’ll also send reminders and helpful resources to you, your team, and your clients ahead of each milestone to help you prepare with confidence. Legacy Editor users on whitelabeled sites will be excluded from deprecation communications.
While this marks the end of one chapter, this shift unlocks a more powerful, flexible, and secure way to collaborate in Webflow. Thank you for your patience and partnership as we complete this transition. We’re excited to see what you’ll build next.
Please note that scheduled dates are subject to change, and we’ll provide updates if any adjustments are made.
