- Published
- Updated
- 9 min read

TL;DR: Webflow switched off its legacy Editor on August 4, 2026 and fully shut it down on October 5. The sites kept running. What changed was editing: each editor now needs a Webflow account and a seat with a role that a Workspace owner assigns and can change. Know who holds that power on your site.
Updated October 31, 2026: we first published this in July, before the cutoff; it now covers what happened since and drops claims we could not source.
When Webflow retired the legacy Editor, no website went dark. Pages loaded, hosting ran, forms kept sending. What ended was the simple login that let a non-designer click on a page, fix a typo and hit publish. For many small businesses that login was the only part of the website they ever touched.
I want to walk through what the legacy Editor change actually did, because the lesson reaches past one platform. A website has two kinds of ownership: owning the pages, and owning the right to change them. This deprecation separated the two in plain view.
What happened to the Webflow legacy Editor?
Webflow announced in December 2024 that it would deprecate the legacy Editor, then published the full timeline on February 2, 2026. In its own words: "The legacy Editor will no longer be available starting August 4, 2026." (Webflow blog (opens in a new tab)) The same post says that 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."
The legacy Editor timeline, step by step
- December 2024: Webflow announces the legacy Editor will be deprecated.
- February 2, 2026: client seats become available on Workspace plans for freelancers and agencies. (Webflow updates (opens in a new tab))
- May 4, 2026: automatic migration begins. Webflow says clients "will be migrated over the course of two weeks," and from then on nobody new can be invited as a legacy Editor user. (Webflow blog (opens in a new tab))
- August 4, 2026: the legacy Editor, and Editor whitelabeling with it, is no longer available.
- October 5, 2026: Webflow's help center says the legacy Editor is fully deprecated and editing through the old ?edit link no longer works. (Webflow Help Center (opens in a new tab))
Between May 4 and August 4 there was an overlap: migrated people "can keep using either the legacy Editor or their new role" until the cutoff. (Webflow blog (opens in a new tab)) That is a long runway and a free migration. By the standards of software deprecations, Webflow handled the legacy Editor change openly.
Why the legacy Editor login did not carry over
The old access was not converted into the new one automatically. Webflow's help center says people who did not make the switch "will lose their ability to edit content until they accept their seat invitation" and sign in to a Webflow account. (Webflow Help Center (opens in a new tab)) The blog states the same thing from the other side: after August 4, clients "will need to use their new roles from their client seats to access and update sites." (Webflow blog (opens in a new tab))
So a person who ignored the invitation email did not lose the website. They lost the ability to change it, until someone with the right permissions sorted out their seat.
What replaced the legacy Editor?
Seats and roles. Webflow describes three roles that can sit on a client seat or a limited seat (Webflow blog (opens in a new tab)):
- Content editor: "Update text, images, and CMS content (formerly known as Edit mode)." This is the closest match to the legacy Editor.
- Marketer: builds pages from components and templates, plus content updates (formerly Build mode).
- Reviewer: "View and comment on sites." No editing.
Migrated users "will be assigned the Content Editor role by default," and the Workspace can "update their role to Marketer or Reviewer." (Webflow blog (opens in a new tab)) Read that as an owner. The right to edit is now a setting on someone else's account screen. It can be granted, narrowed or moved.
Is the new setup better than the legacy Editor?
In many ways, yes, and I would rather say so plainly. Webflow's reasoning is that the legacy Editor was a "one-size-fits-all approach," and that seats, roles and permissions give each user "the proper guardrails to keep the site safe." (Webflow blog (opens in a new tab)) Role-based access is a sound security idea. A reviewer who can only comment cannot break a page by accident.
The trap is that "more capable" and "more conditional" arrived in the same box. Nobody argues with a better tool, so the change in terms is easy to miss. The toolbar improved. The terms of access moved to whoever administers the Workspace.
Who was most exposed when the legacy Editor ended?
Clients of whitelabeled sites. Some agencies removed Webflow's branding from the Editor so their clients never saw the platform underneath. Webflow's blog says: "Legacy Editor users on whitelabeled sites will be excluded from deprecation communications." (Webflow blog (opens in a new tab))
That makes sense from the platform's side, since it was asked not to show its name to those clients. It also means the people editing those sites heard nothing from Webflow about the legacy Editor going away. If the agency did not tell them, the first notice was a login that stopped working.
That is the clearest version of the point. The person who pays for the website and the person who controls who may edit it can be two different parties, and the owner may not know which party holds which key.
The questions to ask whoever built your site
- Which account owns the Workspace or hosting account, and is it in the business's name?
- Who can add, remove or change editors, and is at least one of those people on your payroll?
- If the person who built the site disappeared tomorrow, how would you get admin access back?
- Is two-step sign-in turned on for every account that can publish? CISA puts it simply: "Users who enable MFA are significantly less likely to get hacked." (CISA (opens in a new tab))
We cover the ownership side of those questions in our knowledge base article on who owns the website and the login. Brian also keeps an offboarding checklist for IT access (opens in a new tab), which applies the day an editor or a contractor leaves.
Does a seat cost money now?
Some do. On Webflow's current pricing page, team plans include a set number of limited seats, described as "Edit content or build pages with components. Add more seats for a separate fee." Free seats let stakeholders "review and comment on work without edit access." (Webflow pricing (opens in a new tab)) Agency and freelancer plans include free client seats per site: the Agency plan lists "3 free client seats per site." (Webflow pricing (opens in a new tab))
The cost shape is the thing to know. Reviewing is free. Editing uses a seat. Beyond the included seats, editing costs extra. A common, avoidable mistake is giving someone who only writes blog posts a full seat meant for designers. Before you add seats, list who actually edits, what they edit and how often.
We wrote about another way platform pricing shifted this year in Webflow's move to AI credits on every plan.
Was the legacy Editor change really about Webflow?
No. Webflow is just the platform where it was visible this year. On any closed platform, the vendor decides not only whether your site runs but how editing works, who may edit and what each editor costs. This was simply the moment those terms got rewritten in public. The same pattern shows up when a website builder makes it easy to launch and expensive to leave.
The useful question was answered on the day the site was built: is your content something you can pick up and walk away with? The deadline only made the answer visible. It is the same question as vendor lock-in anywhere else in your stack.
What can you take with you from Webflow?
More than nothing, less than everything. Webflow's pricing page says you "can export your site and host it anywhere you like with any of our paid Workspace plans," with a note: "Dynamic content must be exported on a collection-by-collection basis and forms will stop working." (Webflow pricing (opens in a new tab)) That is a fair answer, and it tells you where the work is if you ever move: the CMS collections and the forms.
What does owning the edit button look like?
It looks boring, which is the point. Your words live in files or a database you can export without asking anyone. For example, an open source CMS like WordPress includes an export screen that, in its own documentation, creates "an XML file" with "your posts, pages, custom post types, comments, custom fields, categories, tags, custom taxonomies, and users," which another WordPress site can import. (WordPress.org documentation (opens in a new tab)) A site built from plain Markdown files is even simpler: the files are the content.
Owning it does not mean running your own servers. For most small businesses the honest middle ground is managed hosting on open foundations, where someone else does the patching and the backups and the content stays portable. The choice of system matters less than three facts you can check:
- The admin account is in the business's name, not a freelancer's personal login.
- You can export the content today, without a support ticket.
- At least two people inside the business can sign in and grant access.
If your site runs on a hosted builder you like, keep it. Just know, before the next change like this one, which access rights you own and which you hold by permission. Our note on headless and traditional CMS choices covers the trade-offs if you are planning a rebuild.
What should you do now if your site was on the legacy Editor?
If your site used the legacy Editor, the migration is over and the old ?edit link is gone. A short check is still worth an hour:
- List every person who used to edit the site and confirm each one accepted a seat and can sign in.
- Check each role. Content editor for people who update text and images, Reviewer for people who only comment.
- Confirm who owns the Workspace, and that the business, not a past contractor, can reach that account.
- Turn on two-step sign-in for every account that can publish.
- Export your CMS collections once, so you know it works and have a copy.
If a step fails, that is your real finding. It means someone outside the business decides who edits your website, and now is a calm time to change that.
Frequently asked questions
When did the Webflow legacy Editor stop working?
Webflow made the legacy Editor unavailable on August 4, 2026. Its help center says it was fully deprecated on October 5, 2026, when editing through the ?edit link stopped working.
Did Webflow sites go offline when the legacy Editor ended?
No. Published sites kept running. What changed was editing: each editor needs a Webflow account and an accepted seat with a role.
What replaced the legacy Editor?
Client seats and limited seats with three roles: Content editor, Marketer and Reviewer. Migrated users got the Content editor role by default, and the Workspace can change it.
Why did some editors get no warning?
Webflow excluded legacy Editor users on whitelabeled sites from its deprecation emails. Those editors depended on their agency to tell them.
Do Webflow editing seats cost money?
Plans include some seats. Webflow's pricing page says extra limited seats are a separate fee, free seats can review and comment without edit access, and agency plans include free client seats per site.
Can I move my content off Webflow?
On paid Workspace plans you can export the site. Webflow notes that CMS content exports one collection at a time and forms stop working after export.
Where we fit
This story is about who controls a website after launch. That is the part our managed website operations work covers: one studio runs your whole website, from hosting and design to writing, publishing, search and security. Your website should not be a second job, and you never log into a server.
When a site needs to do more than a template, our custom web applications are yours: the code and the data belong to you, we host and run it on dedicated infrastructure, and you can take it with you if you ever leave. Our managed technology services start by taking inventory of every system, account and dependency, which is exactly where a forgotten editor login shows up. Some of our client relationships go back more than 13 years.
First conversation is free. No commitment.




