WordPress 7.0 Shock: Real-Time Collaboration Feature Pulled Just Days Before Launch
A Sudden Shift in the WordPress 7.0 Roadmap
In a surprising move that has sent ripples through the web development community, Matt Mullenweg announced on May 8, 2026, that the highly anticipated Real-Time Collaboration (RTC) feature has been removed from the upcoming WordPress 7.0 release. The decision came a mere twelve days before the scheduled general release on May 20, leaving many editorial teams and agencies wondering about the future of concurrent editing in the world’s most popular CMS.
While WordPress 7.0 will still launch on schedule, it will no longer be the revolutionary “Google Docs-style” update that the community was expecting. Instead, the release has shifted from a marquee feature launch to a focus on stability, accessibility, and performance polish.
What Was the Real-Time Collaboration Feature?
Real-Time Collaboration was designed to fundamentally change how content is created in WordPress. For years, the platform has operated on a single-author model—if two people edit a post simultaneously, the last person to hit “Save” usually wins, potentially overwriting previous work.
RTC aimed to solve this by introducing:
- Concurrent Editing: Multiple users working in the same post or page at once.
- Presence Indicators: Visual cues (like colored cursors) showing exactly where other editors are located in the document.
- Conflict-Free Merging: A backend system to handle overlapping edits without data loss.
This would have been the most significant workflow evolution since the introduction of the Block Editor (Gutenberg), specifically targeting agencies and large editorial teams.
The Technical Breaking Points: Why It Was Pulled
According to the official announcement on make.wordpress.org, the decision to remove RTC wasn’t based on a lack of vision, but on critical technical instabilities. Five primary concerns were cited:
- Expanded Surface Area: RTC interacts with nearly every part of the editor, including every block and save path, creating a massive potential for bugs and security vulnerabilities.
- Race Conditions: Managing simultaneous edits is computationally complex. The team found that “race conditions” could lead to silent content corruption, where user data disappears without warning.
- Server Load: Unlike standard page loads, RTC requires persistent connections (WebSockets or polling). For users on smaller VPS hosting, this increased load could degrade site performance for all visitors.
- Memory Efficiency: Tracking the live state of multiple concurrent sessions consumes significant RAM and database resources, which could crash busy sites.
- Fuzz Testing Failures: The feature failed repeatedly during “fuzz testing” (where random, malformed data is thrown at the code). These failures suggested structural flaws rather than simple surface-level bugs.
What Now? The Future of RTC and WordPress 7.0
Is the dream of real-time editing dead? Not quite. The WordPress team has explicitly stated that RTC remains a priority. However, the path to implementation is changing. It is highly likely that the feature will move to the Gutenberg plugin first, serving as a testing ground for a smaller group of users before eventually migrating back into WordPress Core.
Realistic Timeline: While not officially confirmed, industry experts suggest that 7.1 (August 2026) and 7.2 (December 2026) are unlikely candidates for the feature’s return. A potential re-introduction in version 7.3 in 2027 is more plausible, provided the structural rework is successful.
As for the current 7.0 release, users can expect a highly stable version with refinements to the Site Editor and improved general performance.
Alternative Solutions for Collaboration Today
Since native real-time collaboration is delayed, teams requiring these features today have three primary options:
- Multicollab: Currently the most robust plugin for adding suggestions, comments, and live presence to the block editor.
- External Drafting: Many teams continue to use Notion or Google Docs for the drafting phase, migrating the final text to WordPress only for publishing.
- Gutenberg Beta: Keep a close eye on the Gutenberg plugin, as this is where the rebuilt RTC will likely appear first for early adopters.