It’s funny because it’s true…
But from joke to seriousness, @sef-webflow If you can’t share any dates for when it will be released, could you share some information about what the transition experience will be like for clients? Will they still be able to use “/?edit” to access the editor login? It would help a lot to know what we should prepare our clients for.
Appreciate the continued feedback and questions here. @craigb we’ve since updated our materials to reflect 2026 as our new timeline. Can you please confirm where you’re seeing 2025 so I can pass it along to our team to update?
While we don’t have an exact timeline to share yet, you’ll have at least six months’ notice before the legacy Editor is no longer available and we’ll be providing comprehensive resources to guide you and your clients through the migration to make the process as smooth as possible.
Thanks again for your patience and for sharing your perspective, we’ll keep you updated as we get closer.
Thanks @sef-webflow - The What’s the difference between the legacy Editor and edit mode? page still carries the 2025 date (as at 22 Oct 2025), I’m not sure about other official Webflow pages though.
Users won’t mind waiting longer for the update if it ensures the rollout goes smoothly - would just be nice to get some progress updates from Webflow along the way. Thanks again for the response.
Hi @sef-webflow, thanks for the update - but as an agency owner handling 150 sites I think one KEY element is missing from all this.
The legacy editor is almost useless for sites utilizing newer Webflow features like components, component variations and such. A lot of small things break in the editor - e.g. suddenly a hidden button within a component is visible, just because a text-change was made in the legacy editor.
To be honest the past 3-4 months our work load from all this has increased quite a bit, because either a) can’t do things properly in the legacy editor or b) something breaks and sometimes it takes days before anyone from us or our client finds out.
How are we supposed to work around this and keep clients convinced that Webflow is the right platform?
I also echo this sentiment, especially as it currently forces Webflow agencies to make difficult and costly choices that could be avoided during builds.
At the moment, we’re faced with two ways to approach Webflow builds:
It would be good to see this area of Webflow given higher priority to speed up the release. Perhaps this feedback could also be shared with the WF Partners team to highlight the issue further and gain more traction internally.
I created a seperate account that has access to a few websites form trusted clients. They can, for a period of time’ log in to that account to make component changes if they need to. Rest they form their own legacy editor account. Certainly not ideal and I’m paying for the extra account, but since my promise to my clients was made about the new editor, this is what I’m forced to do. And no, I can’t hand over the specific Webflow accounts to my clients: they don’t want that and I don’t want it as well. Hopefully some speed is set to the transition of the editor.
I would also like to share some feedback from an agency’s perspective. We currently have 25 websites running on Webflow, and we started using Components a lot last winter since it saves a lot of time. However, clients using the legacy editor are unable to access the features of Components. In reality, they call us almost every time they want to make a change, because they have learned: Almost every time they try to make a change to their website, there’s a problem with the editor (unable to add/remove/move components, unable to publish changes, unable to control order of CMS lists, etc.), so they call us directly, and now we even make small changes like simple text corrections for clients because they don’t want to face the limitations of the Editor all the time.
We also have to deal with a critical bug in the legacy editor that Webflow has not yet addressed: When you edit an element that is a component, you cannot publish the change in the legacy editor. You can only publish the site after editing an element that is not a component. I informed Webflow about this months ago, and they said that they probably wouldn’t address it since the new editor would ‘come very soon’.
I’d like to encourage Webflow to prioritise the release of the new editor, as the current situation creates unnecessary work and costs for us and our clients.
I agree, i am doing exactly the same - very lame way (if not dangerous) to allow clients to manage their website with advanced features like localisation. I can’t even comprehen how a feature like localisation could be released without allowing customer to CMS access their translation.
@sef-webflow I am really missing a reply here. Just now I got an email from a client asking “Why is it not possible for me to edit the english version of the site?”. It is pretty difficult to provide a good customer experience when my response is “Should have been here 4 months ago, then before year-end and now im waiting for Webflow to tell when in 2026 it will be possible. (also their reply after this was “Please keep me posted about when I can do it myself” - and honestly I don’t know what to say)
For context this client is using Webflow Localization and english is the secondary locale.
Not a coincidence.. I had 2 clients literally asking me this today and found myself ‘explaining’ why they are still waiting. And worse: I can’t handover a time path. Sucks.
So I stumble across this thread - and discover the changes to the Editor is now 2026 - ZERO public communication from Webflow - again.
I manage 100’s of sites, and the DNS changes they’ve forced upon us have been a farce - I was given 2.5 weeks to ‘cat-herd’ all my clients who have their own registrar accounts. (I know other Webflow Wordspaces have had far, far longer) It’s a total nightmare, and I fully expect many, if not the majority, to have not updated by the 15th December deadline.
I’m absolutely dreading the 2026 Editor Changes. And don’t get me started on the utter cluster***k that is Workspaces, Seats, etc. How mch more complicated can they make things?
’Some’body’ please get a grip, and get the basics right - and stop making it so hard for us troops on the ground - who are your bread and butter.
When I started with Webflow I opted for a few things:
Delivering clean code
CMS
Reliable hosting without myself doing any updating or backups
Offer my clients a comprehensible content editing experience
While competing with cheaper hosting and builders, I managed to get the clients I want on board on the platform I love. Took some convincing sometimes to use Webflow, but once on board…
Now, while adapting to evolving circumstances, I would like to have a platform that is:
delivering on the starting points above
make sure the platform stays relevant
Staying relevant has a lot of challenges, I imagine. All additions (and deleted stuff..) of the last couple of years: fine. Localization was a very welcome step. A much more comprehensive editor is also very needed. It’s what I consider as a key component to build a successful website. Webflow has very much fallen behind at this moment in that category. Not being able to give (limited) freedom to clients in terms of building or maintaining pages set up with components or Localization is crazy and certainly not an experience for this day and age. Reforming the editor and implementing it should have been on top of the list since delivering components and Localization. Please Webflow, get your priorities straight. I like all new cool small features, but for the near future we need just one basic feature: a new editor which enables clients to do cool content stuff.
Just adding a new mail today, a client that regularly makes changes to their site but way to often they cannot publish them and asks us to do it - so ineffective and actually embarrasing for us as an agency. (Screenshot in danish)
@Dan_Lam I’ve got the same problem with my clients. It seems to be a bug in the Legacy editor that clients can’t make changes to a Component and publish the changes. However, the changes is registered in the Designer, so i need to log into the designer and publish the site for our client.
“The Ycode site builder moves to Next.js + Supabase in 2026 and goes open source"
Looks like things are moving in the no-code world. Shape up, Webflow! Please don’t take your existing customer base for granted, fix existing problems before adding more upsell features!!
Hi @sef-webflow and @webflow in general I think we need to talk.
I have just realised that when I share my workspace with my client (which had to buy an additional freelancer plan just to access the localization within the designer), eventhough I just shared one specific website of my workspace to the workspace of the client, my client can still see ALL folders in my workspace (but can’t see the websites in it) BUT CAN ALSO DELETE all the folders if he wanted to ! If so, all the contents of those carefully created and organized folder would go into the All sites folder.
This is not acceptable, why would webflow allow people to see and delete things they were explicitly not allowed to do ? There is a real UX issue in the way that features has been design.
May I please get clarification ?
Thank you.
Not acceptable! Even workarounds seem seriously flawed! @webflow: please fix this! And while we’re at it: what is the status of the roll out for the new editor?
We are increasingly working with components and are running into more and more issues in the Legacy Editor. This sometimes puts us in a difficult position when explaining things to our clients.
Recently, we had (and still have) the issue that when defining headings (H1, H2, H3, etc.), clients suddenly could no longer edit the text in the Legacy Editor. Unless I’m completely mistaken, clients also can’t even manage alt tags for images. This is an absolute no-go.
Forget all the AI features — the fundamentals need to work perfectly first. It honestly feels like Webflow has taken a step backwards over the past months, despite all the supposed innovations. That realization really hurts, especially considering that the pricing is not insignificant either. Just 50 GB of bandwidth on the CMS plan… wasn’t that 200 GB before?
But back to the point: PLEASE focus on the Editor and make sure our clients are actually able to maintain their websites.
And yes — please do this without a price increase… not even a hidden one.
2 weeks ago got admitted to the beta, now apparently it’s live: Introducing client seats: A flexible collaboration experience for your clients | Webflow Updates
Luckily I was already updating client instructions 
Happy days.
I think it may still be in BETA based on my initial testing 
Related thread: Migrating from Legacy Editor to Client Seats (+ issue list & suggestions)
