Lina Irawan
In a major shift for the WordPress development roadmap, project leadership has officially confirmed that the highly anticipated Real-Time Collaboration (RTC) feature will not be included in the upcoming WordPress 7.0 release. The decision, announced by co-founder Matt Mullenweg, marks a significant pivot for the platform, which had positioned RTC as the cornerstone of "Phase 3"—the third stage of a four-part evolution aimed at transforming how content is created and managed within the CMS.
For a platform that powers over 40% of the web, the decision to pull a flagship feature mere weeks before a major release is rare. However, the move has been met with a surprising wave of relief from the developer community, who had grown increasingly concerned about the technical maturity of the RTC implementation.
The Core of the Conflict: Technical Hurdles
The announcement, delivered via the official WordPress Make Slack workspace, was direct. Mullenweg cited a lack of confidence in the current iteration of the RTC codebase, noting that it failed to meet the rigorous performance standards required for inclusion in WordPress Core.
"I’m not confident with RTC being in core at this point," Mullenweg stated. "I’m fine taking the heat for pulling it out, but the surface area, race conditions, server load, memory efficiency, and the bugs that keep popping up in fuzz tests don’t give me a lot of confidence on our current approach being the robust one we want to support."
Beyond the raw technical metrics, Mullenweg also acknowledged the compounding pressure of ongoing legal challenges—specifically the "lawfare" involving WP Engine—which have diverted the attention of key contributors and core developers. "There’s also the added burden right now of the WP Engine lawfare and depositions being a time DoS [Denial of Service] for critical people," he noted. "Perhaps without that in the background we could have gotten to a better place by now, but I don’t think with the current deposition schedule… we’re able to support this feature."
Chronology: The Evolution of Phase 3
To understand the weight of this decision, one must look at the ambitious trajectory of WordPress’s "Gutenberg" era.
- Phase 1 (2018): Introduced the block editor, fundamentally changing the content creation experience.
- Phase 2 (2019–2022): Focused on Site Editing, shifting the focus from static pages to full-site control.
- Phase 3 (The Current Era): Dedicated to Collaboration. The goal was to eliminate the archaic "post-locking" mechanism, where only one user can edit a document at a time, replacing it with a fluid, multi-user environment similar to Google Docs or Notion.
- April 2026: Matt Mullenweg teased the potential for AI integration, suggesting that RTC would serve as the bridge for AI agents to interact with content in real-time.
- May 8, 2026: Official announcement confirming the removal of RTC from the WordPress 7.0 release cycle, originally scheduled for May 20, 2026.
Understanding Real-Time Collaboration
The objective of RTC was to modernize the editorial workflow. Currently, WordPress utilizes a "post-locking" system that prevents two users from editing the same post simultaneously. This prevents data overwrites but creates significant bottlenecks for newsrooms, marketing teams, and collaborative agencies.
By enabling multiple users to edit a post or page simultaneously, with changes appearing instantly across all active sessions, WordPress aimed to streamline editorial efficiency. While the feature has been successfully deployed in a controlled, premium environment on WordPress.com for VIP and Enterprise users since late 2025, moving it into the open-source "Core" software is a different challenge entirely. Open-source WordPress must run on a vast, fragmented array of server configurations, hosting environments, and PHP versions, making performance and memory efficiency much harder to guarantee than in a managed cloud environment.
Official Responses and Internal Documentation
The official documentation regarding the removal of the feature highlights the procedural steps now underway. According to the release team, the priority is maintaining the stability of the 7.0 release.
"This is a difficult decision, especially given the amount of work that has gone into the feature," the official statement read. "It is being made in service of shipping a stable and reliable WordPress 7.0 release for our users. Work to remove the feature from the release is being organized in #65205 and in the #feature-realtime-collaboration."
The project remains committed to the idea of collaboration, but the timeline has effectively been reset. The community has been advised that while the release schedule for 7.0 remains intact, the "unwinding" of the feature will be the primary focus for the final days leading up to launch.
The Community Sentiment: A Sigh of Relief
While delays in major software projects are often met with frustration, the reaction to the RTC delay has been overwhelmingly positive. The WordPress community, often vocal about feature bloat, expressed concerns that RTC was being rushed into Core before it was ready for the diverse "wild west" of self-hosted WordPress sites.
Developer Perspectives
Kento, a prominent contributor, voiced a common sentiment on the WordPress.org forums: "I honestly welcome this decision. Besides the fact that this needs further work to confidently get into core, it will also give extension developers more time to prepare, experiment, and provide feedback."
This perspective highlights a critical aspect of the WordPress ecosystem: the plugin economy. If RTC had been forced into Core in a buggy state, thousands of third-party plugin developers would have been forced to scramble to ensure their own tools didn’t break.
Industry Leadership and Expert Analysis
On X (formerly Twitter), industry analysts interpreted the move as a sign of maturity rather than failure. Katie Keith, a well-known WordPress entrepreneur, categorized the move as a "delay rather than an actual change of direction."
However, others were more critical of the initial concept. Justin Ferriman, an advocate for lean software, tweeted, "That feature always came across as a bit tone deaf. This was the right decision." Mark Wesguard echoed this, noting, "Good move. I never understood why this should be in core."
The prevailing argument among these critics is that RTC is a "heavy" feature that serves a specific subset of high-end enterprise users, and therefore might have been better suited as an optional plugin rather than a mandatory piece of the WordPress Core architecture.
Implications for the Future
The removal of RTC from WordPress 7.0 has several profound implications for the platform’s future.
1. The "Plugin vs. Core" Debate
This incident has reignited the conversation regarding what constitutes "Core" functionality. As WordPress continues to expand its feature set, the risk of technical debt grows. The decision to pull RTC suggests that the leadership is willing to sacrifice "feature parity" for the sake of long-term stability—a shift that many long-time developers find encouraging.
2. The AI Integration Roadmap
Matt Mullenweg’s earlier comments regarding AI agents editing in real-time suggest that RTC is not dead, but merely deferred. The future of the WordPress editor likely depends on this technology. If WordPress is to remain competitive against headless CMS solutions and AI-driven site builders, it must eventually solve the real-time synchronization problem. The question remains: will it be a native feature, or will WordPress provide the APIs necessary for plugin developers to build it better?
3. Stability Over Speed
The backdrop of the "WP Engine lawfare" provides context for the current climate within the project. With legal and administrative resources stretched thin, the project’s ability to maintain high-quality engineering standards is under the microscope. By pulling back on RTC, the leadership has signaled that they are prioritizing the reliability of the core software over the pressure to hit marketing-driven release milestones.
Conclusion
The decision to remove Real-Time Collaboration from WordPress 7.0 is, in many ways, a testament to the growth of the project. It demonstrates a willingness to pivot, listen to community feedback, and acknowledge the limitations of current resources.
For the average user, WordPress 7.0 will now ship as a leaner, more stable release. For the developer community, it provides a much-needed breathing room to innovate. While the dream of native, real-time multi-user editing in WordPress remains, it is clear that the project is not yet willing to compromise on quality to get there. As the industry watches, the focus now shifts to how the WordPress team will handle the eventual re-introduction of these collaborative tools—and whether they will learn from the "race conditions" and "memory efficiency" challenges that stalled them this time around.
Ammar Sabilarrohman
Ali Ikhwan
