Webflow legacy Editor: what’s changing on August 4

If you or your clients edit a Webflow site using the old Editor, mark your calendar. Webflow is retiring the legacy Editor on August 4, 2026. After that date, anyone who still relies on it loses access completely, and they’ll need a new seat and role to keep making updates. This isn’t a minor UI tweak. It changes who can edit what, and it changes the workflow your team or your clients use every day.

The timeline you need to know

Webflow announced this change back in December 2024, and the company published the full legacy Editor deprecation timeline on its blog this year. Here’s how it breaks down. Client seats became available on February 2, 2026, giving agencies and freelancers early access to the replacement system. Automatic migration started on May 4, 2026, and rolled out over about two weeks. Every existing legacy Editor user who hadn’t already been moved to a new seat got one for free, either a client seat or a limited seat depending on the Workspace plan. Then on August 4, 2026, the legacy Editor shuts off for good, along with Editor branding (whitelabeling) for agencies that used it.

What replaces the legacy Editor

Webflow built the replacement around seats and roles instead of one blanket Editor experience. Freelancers and agencies get client seats, which live at the site level. In-house teams get limited seats, which apply across the whole Workspace. Both seat types support three roles. Marketer can build pages with components and templates plus edit content. Content editor updates text, images, and CMS content, which is the closest match to what the legacy Editor used to do. Reviewer can only view and comment. If your account was migrated automatically, Webflow assigned you the Content editor role by default, and you (or your Workspace admin) can change that later.

The upgrade isn’t just a rename. The Content editor role can do things the legacy Editor never could: edit dynamic content directly on canvas, create CMS collection pages from the Designer, upload and organize assets, manage alt text, publish to staging and production, and log in with SSO. If your team has been stuck fighting the legacy Editor’s limits, this is a real upgrade, not just a forced migration.

What this means if clients edit your Webflow site

Agency and freelancer Workspace plans come with a set number of client seats per site. Starter and Freelancer plans get one seat per site, and Agency plans get three. If you have more legacy Editor users than seats when the automatic migration runs, Webflow adds extra client seats to cover them, so nobody gets locked out. Migrated clients can still use the legacy Editor alongside their new role until August 4, then the legacy Editor disappears and they’re on their new role only.

One practical detail: the quick-edit shortcut changes too. Instead of adding ?edit to a live page URL, you’ll use ?update. If your team or clients have that shortcut saved anywhere, update it now so nobody hits a dead link after August 4.

How to prepare before August 4

You don’t have to do anything for the migration itself. Webflow handles it automatically for anyone still on the legacy Editor. But a few steps now save you a scramble later. Check who on your team or client list still has legacy Editor access and confirm each person has a unique email address, since duplicate emails can affect seat assignment. If you want more control over roles, you can proactively move legacy Editor users to client seats ahead of time instead of waiting for the automatic rollout. If your site’s build itself needs attention before you hand off editing access, check whether your website’s underlying build is holding back your local search ranking, since a clean structure makes any editor experience easier to use.

This shift fits a broader pattern this year. Platforms keep pushing toward giving non-technical users more editing power without full design access, similar to Canva’s move into free AI website building and the changes in the WordPress 7.1 update. It’s also worth checking whether the pages your team edits are structured in a way search engines and AI tools can read, something we covered in our look at Google’s Lighthouse tool grading agent-ready websites.

Frequently Asked Questions

Do I lose my Webflow site content when the legacy Editor retires?

No. Your site content stays exactly as it is. Only the editing interface changes. Once you’re moved to a client seat or limited seat, you access the same pages and CMS content through the Content editor or Marketer role instead of the old Editor screen.

What happens if I don’t do anything before August 4, 2026?

If you were still using the legacy Editor and hadn’t already been assigned a seat, Webflow automatically gave you a free client seat or limited seat during the May 4 migration window. As long as you had an active legacy Editor account before that date, you should already have a new seat waiting. Log in and check your role if you’re unsure.

Can agencies still remove Webflow branding from the client editing experience?

No. Editor branding, also called whitelabeling, was exclusive to the legacy Editor and retires along with it on August 4, 2026. Agencies that relied on whitelabeling will need to plan around its removal.

Getting ahead of the Webflow legacy Editor deadline

The Webflow legacy Editor deadline is close enough now that waiting isn’t a strategy. Most accounts have already been migrated automatically, so the real work left is checking that every person who edits your site, whether that’s your own team or a client, knows their new role and has tested it before the old system disappears on August 4. Do that now, and the switch will be a non-event. Skip it, and you risk a scramble the week the legacy Editor goes dark.