Real-time collaboration was the marquee feature of WordPress 7.0. On May 8, 2026, twelve days before the scheduled May 20 release, Matt Mullenweg pulled the feature from the release, citing concerns around surface area, race conditions, server load, memory efficiency, and recurring bugs surfaced through fuzz testing.
WordPress 7.0 still ships May 20. It just won’t be the release everyone expected.
What Was Real-Time Collaboration Supposed to Do?
Real-time collaboration (RTC) would have let multiple editors work in the same WordPress post or page simultaneously, the way Google Docs handles concurrent editing. Two cursors in the same paragraph, presence indicators showing who’s online, conflict-free merging of overlapping edits.
For agencies, editorial teams, and any site with more than one writer, this would have been the biggest workflow shift since the block editor. WordPress’s editing model has always assumed one author at a time. RTC was the rewrite of that assumption.
The feature had been in development for several release cycles, with parts of the underlying infrastructure (block notes in 6.9, presence APIs, the broader Gutenberg collaboration roadmap) shipping incrementally. 7.0 was supposed to be the version where it all came together.
Why It Was Pulled
The May 8 announcement on make.wordpress.org lists five specific concerns:
- Surface area. RTC touches almost every editor surface. Every block, every editor view, every save path. That’s a large attack and bug surface to ship into Core in one release.
- Race conditions. Concurrent editing is hard. When two people type in the same paragraph at the same time, the system has to decide which edit wins, in what order, and how to merge them without losing work. Race conditions in this layer can corrupt content silently.
- Server load. Persistent connections (websockets or polling) for active editing sessions add real cost. On a small VPS hosting a multi-author site, this can degrade performance for everyone, not just the editors.
- Memory efficiency. Storing the live state of every concurrent editing session in memory or in the database adds up fast on busy sites.
- Recurring bugs through fuzz testing. Fuzz testing throws random or malformed input at code to find crashes. RTC kept failing fuzz tests in ways that suggested deeper structural issues, not surface bugs.
Matt’s quote from the announcement: “not confident the current approach is robust enough to include in Core at this time.” That reads less like “this needs another month” and more like “the current implementation needs structural rework.”
Is RTC Shelved Permanently?
No. The May 8 post is explicit on this: “Real-time collaboration remains an important and exciting feature for WordPress.” The team is preparing a plan for broader testing and continued iteration toward a future release.
What’s not announced: the target version, or whether RTC will land as a Core feature or a feature plugin first. The Gutenberg plugin has historically been the testing ground for ambitious features (Full Site Editing, Block Patterns, Site Editor) before Core inclusion. A “real-time collaboration” feature plugin in Gutenberg, with extended community testing, is the most likely path forward.
Realistic timeline: not 7.1 (August 2026), probably not 7.2 (December 2026). 7.3 in 2027 is plausible if the structural rework moves quickly.
What Does WordPress 7.0 Actually Ship With Now?
With RTC out, 7.0 becomes a stability and polish release. The current release-candidate notes don’t position any other feature as a marquee headline; instead, the focus is on the editor performance, accessibility, and Site Editor refinements that were already part of the cycle.
The release-party schedule (RC4 on May 14, general release May 20) is unchanged. RC3 was the last release candidate that included RTC code paths; RC4 ships with those paths removed.
For most WordPress users, the practical effect of 7.0 is small. If you weren’t planning to use RTC, nothing in your workflow changes. If you were, you keep using a third-party plugin (Multicollab, Frase, etc.) for now.
What This Means for the Roadmap
This isn’t the first time a marquee feature has slipped late in a WordPress cycle. The Site Editor moved between Core and Gutenberg several times before stabilizing. Block-based widgets shipped, broke a lot of sites, and got the “Classic Widgets” plugin escape hatch. The pattern is consistent: Core is conservative on stability, even when it costs a release’s headline narrative.
The case for pulling RTC is strong on its merits. Concurrent editing systems that ship buggy lose user trust fast, and “I lost my draft because two editors saved at the same time” is the kind of bug that gets a CMS forked. Better to delay than to break.
The case against is mostly narrative. WordPress 7.0 was positioned as the version that would close the perceived feature gap with Notion, Google Docs, and other modern editing tools. Without RTC, it ships as a polish release in a year where ambitious-feature releases are arguably more important than ever to the platform’s positioning.
If You Need Real-Time Collaboration Today
Three options that work on current WordPress:
- Multicollab. The most mature WordPress collaboration plugin. Adds Google Docs-style suggestions, comments, and presence to the block editor. Works on 6.x today.
- Edit your content elsewhere, then paste. Many editorial teams draft in Google Docs or Notion (where multi-user editing is solved), then paste the final version into WordPress for publishing. Less integrated, but reliable.
- Wait for the feature plugin. If 7.0’s announcement triggers a Gutenberg feature plugin for RTC (likely, given the team’s stated next steps), early access via the plugin will probably arrive before the next Core inclusion attempt.
Frequently Asked Questions
Is WordPress 7.0 still releasing on May 20?
Yes. The May 8 announcement explicitly confirmed the release schedule remains unchanged. RC4 lands May 14 with RTC code paths removed, and 7.0 ships on May 20.
Will real-time collaboration ever ship in WordPress Core?
The team’s official position is yes. RTC remains on the roadmap. The structural concerns Matt raised on May 8 are about the current implementation, not the goal. Expect a feature-plugin testing phase first, then a Core merge attempt in a future release. No version target has been announced.
Why was RTC pulled so close to release?
The release cycle had already been extended once, with RC1 through RC3 acting as effective betas to surface stability issues. By May 8, the recurring fuzz-test failures and concerns about race conditions and server load made it clear that another month or two of patching wouldn’t be enough. The call to pull was made when “ship a stable 7.0” became incompatible with “ship 7.0 with RTC.”
What WordPress plugins offer real-time collaboration today?
Multicollab is the most established option. It adds Google Docs-style commenting, suggestions, and live presence to the Gutenberg editor. Other options include Frase and various editorial-workflow plugins. None are a true peer-to-peer real-time editor; most use a comment-and-suggestion model rather than concurrent typing.
Does this affect WordPress 7.1 or 7.2?
The 7.1 (August 2026) and 7.2 (December 2026) timelines were planned independently of RTC. They probably hold, although the team may use a future release to land the rebuilt RTC implementation, which could shift other features around it.
What does fuzz testing mean in this context?
Fuzz testing throws random or malformed input at a system to find crashes, hangs, or unexpected behavior. For RTC, that meant simulating chaotic editor activity (rapid concurrent edits, malformed sync messages, dropped connections at unusual times) to see how the implementation held up. Recurring fuzz failures usually indicate that the structural design has gaps that no amount of patching will close.
Wrapping Up
The decision to pull RTC from 7.0 is the right call from a stability perspective and a difficult call from a release-narrative perspective. WordPress shipping a stable, conservative 7.0 is better for the millions of sites running it than shipping an ambitious-but-broken one. But it does leave 7.0 without a marquee feature, and pushes the platform’s biggest editorial workflow shift in years to a date that hasn’t been announced yet.
If you’re tracking WordPress major releases, the full version history has the 7.0 entry updated to reflect this change, plus context on every major release back to 0.7.
