Earlier this year webflow annouced the migration towards the more robust client seat with designer editing capabilities (especially for client who need to edit content with localization). However I still can’t see any changes yet and my client is still paying double: one for the hosting of the website and a second time for just having a freelancer account to be able to access the designer just to add and localize CMS items
My question is: when will the legacy editor be migrated to client seat ?
Short answer: sometime this summer (mid‑2025). The Webflow team hasn’t released a specific date, only that it’s coming in the first half of 2025 .
Community members have asked for clarity (“anybody got a more specific date?”), but the response remains that Webflow “rarely publishes feature release dates in advance”
It’s September. Still wondering the same question. It’s akward to onboard new clients - should we train them on editor in the meantime or use a work around such as asking them to hold the website in their own account?
Got an answer: I can (already) use the client seats when my clients use the payment system. Thing is, I don’t want to use that. I pay for the clients and clients pay me. So hopefully this isn’t mandatory..
From support: “Although the launch of Client Seats has been delayed, we’re aiming to have it ready before the end of the year. We don’t have an exact date just yet, but our team is working hard to make it happen.”
What worries me is the word ‘aiming’…
Also came here to post about the lack of communication surrounding this change.
It’s going to have a pretty substantial impact on how agencies work with clients and editors, so we were hoping it would be treated as a higher priority.
Seeing the conference agenda filled mostly with AI talks and demos really highlighted where the focus has been over the last 6-12 months.
Over the past few years, it has felt like there’s a wider focus issue with Webflow’s product direction, leading to prolonged delays and features that feel half-baked.
From an agency perspective, this makes it challenging to plan and scope projects, as well as communicate platform changes to clients, which ultimately benefits no one.
Right now, the communication pattern seems to go:
Initial announcement
Significant period of silence
A forum thread like this one
A vague update via support
Another long silence
Release
It would be hugely helpful to bridge that middle section with regular progress updates and revised timelines, even if the news isn’t great.
A simple suggestion: have the product team post or email regular updates on upcoming changes and features to fill that communication gap. Alternatively, consider bringing back the public roadmap and keeping it up to date.
Hey everyone, I’m Sef from Webflow’s Support team.
Thank you for your question and patience regarding the release of Client seats. The team is actively working on the product and supporting resources to ensure a smooth transition. While we don’t have a timing update to share, you can rest assured that you will still have a 6-month transition period from the launch of Client seats to the deprecation of the legacy Editor, giving you and your clients ample time to adjust. In the meantime, you can continue onboarding clients through the legacy Editor or with limited seats. We can also ensure you’re included in the Client seats beta when it becomes available.
Thank you for your reply, but the criticism in this forum concerns the lack of proactive, general communication from Webflow on a crucial topic: the transition of the Content Editor to the new Edit Mode. This is a crucial point that must be immediately prioritized over secondary updates.
The Impact on Webflow Users and Our Customers:
Customer Credibility: In late 2024/early 2025, Webflow announced that the unstable Content Editor would be discontinued at the end of 2025 and that Edit Mode would become the alternative. We, as Webflow users (designers/agencies), communicated this directly with our customers. They experience the limitations of the current Editor daily. It’s now almost October 2025, and I can’t tell my customers what the promised replacement looks like or when it will actually be available. This undermines our credibility and makes it difficult to retain customers.
Confusing policy changes: After a long search, you come across the message that customers whose hosting subscriptions are through the designer will be automatically migrated and that the number of users (previously 3 Editors) will be reduced to a single Client Seat.
This is a significant change in functionality and pricing that directly affects everyone and cannot be swept under the rug on a support page.
What exactly does this “Client Seat” entail? What does the workflow look like? What is the pricing model for additional seats? This uncertainty is untenable.
Call to action:
We, as existing Webflow users, are partly responsible for the growth and success of Webflow and depend on your stable and reliable product and communication. Good communication is the foundation of any successful business model.
Therefore, our urgent request:
Publish an official, easily accessible update now with a definitive roadmap, clear dates, and detailed information about the functionality and pricing of Edit Mode and the Client Seat.
Provide clarity about the transition for existing customers who are already paying for the current Editor.
Please bring transparency to this situation as soon as possible.
Appreciate the candid feedback, we hear you and would like to provide a bit more clarity.
The launch of client seats and the subsequent deprecation of the legacy Editor are now postponed to next year. We’ll share a more detailed timeline as soon as it’s ready, and you can rest assured that you’ll still have at least six months’ notice before the legacy Editor is no longer available. We’ll also be providing comprehensive resources to guide you through the migration, including new educational content, migration guides and enablement materials.
In the meantime, you can continue to use your legacy Editor users or limited seats without interruption.
We know change brings questions, and we’re committed to making this transition as smooth as possible. Thank you again for your patience and for sharing your feedback.
Added note. I can live with the postponement (not like I have a choice), but offering clients localization that they themselves can’t edit in the legacy editor is very, very silly.
Same here, broken promise to my client that he’ll be able to edit the translations for his website by end of 2025 and additional cost for me to host the whole setup for him. How can a native feature that critical be postponed 1 year over ?
Hey everyone, thanks again for the open conversation. I’ve shared all of this feedback directly with our team. Totally understand how important clear timelines and updates are, especially when you’re planning work with clients. While it’s delayed, we want to reassure you that our team is actively working on client seats and the deprecation of the legacy Editor. Our goal is to ensure the new experience meets your needs and the migration process is as smooth as possible.
We hear your feedback on the communication also and will take it into account for future launches!
Hi @sef-webflow - Thanks for the update. It was surprising to read that the launch has been postponed to 2026 via a forum thread and not an official Webflow release? Even the official Webflow site still states 2025.
I agree with the other comments - the transition is a significant amount of work that requires re-training editors, re-writing internal user guides/documentation etc. so would be great to hear some official updates and timelines from Webflow.
AI 
Hey everyone, I’m Sef from Webflow’s Support team.