WordPress 7.0 RC1 has been delayed to March 24, 2026, after three critical issues surfaced: real-time collaboration performance problems, client-side media optimization concerns, and package size bloat. The delay represents a rare stumble for WordPress’s most ambitious release since the block editor arrived in 2018 — and the first to add a core database table in 11 years.
The Performance Problem
Real-time collaboration was supposed to be the star feature of WordPress 7.0, allowing multiple editors to work on the same post simultaneously. However, it became the primary reason for the delay. Release coordinator Amy Kamala cited performance issues that sparked heated debate among contributors.
The solution? WordPress 7.0 will ship with real-time collaboration disabled by default, requiring users to opt-in at Settings > Writing. Nevertheless, this unprecedented caution signals that performance at scale remains unsolved.
The controversy ran deep enough that Matt Mullenweg approved something that hasn’t happened since 2015: a new core database table. The last time WordPress added a core table was wp_termmeta in version 4.4. Therefore, this architectural change underscores both the ambition and complexity of real-time collaboration.
Why HTTP Polling, Not WebRTC
WordPress chose HTTP polling as the default sync provider instead of WebRTC, trading performance for universal compatibility. The system polls once per second for solo users and four times per second with multiple collaborators — more aggressive than WordPress’s Heartbeat API, which fires once every 10 seconds.
The trade-off makes sense: HTTP polling works on any hosting environment, including shared hosting with strict resource limits. In contrast, WebRTC would require a centralized signaling server, excluding millions of WordPress sites.
What’s Actually in WordPress 7.0
Beyond the troubled real-time collaboration, WordPress 7.0 introduces two other major features marking the beginning of Phase 3 (Collaboration) of the Gutenberg project.
AI Infrastructure
WordPress 7.0 ships with built-in AI infrastructure — but not an AI writing tool. Instead, it provides developer infrastructure through a provider-agnostic design that supports OpenAI, Anthropic, Google, or self-hosted models. Additionally, developers manage AI connections centrally at Settings > Connectors, and plugins can leverage AI capabilities without building their own infrastructure.
When API keys are configured, WordPress enables auto-alt text generation, content summarization, and translation assistance. Ultimately, it’s a smart, open approach that avoids vendor lock-in.
Command Palette
The Command Palette brings modern UX patterns from VS Code and Figma into WordPress. Press ⌘K or Ctrl+K from anywhere in the admin for instant access to all actions. Beta 5 introduced the feature, making keyboard-first workflows finally possible in WordPress.
Client-Side Media: Pulled from Release
Meanwhile, WordPress also pulled client-side media optimization from the 7.0 release. The feature would have processed images in browsers instead of on servers, potentially reducing server CPU usage by more than 80%. However, the team decided it needed more development time.
The removal highlights a broader issue: WordPress 7.0 tried to tackle too many architectural changes at once. Specifically, adding AI infrastructure, real-time collaboration, and client-side media processing simultaneously proved too ambitious.
WordCamp Asia: High-Stakes Release
Despite the RC1 delay, WordPress 7.0 still targets an April 9, 2026 release at WordCamp Asia’s Contributor Day in Mumbai. This represents a historic first: no major WordPress release has ever happened live at a WordCamp. More than 3,000 attendees are expected.
Furthermore, the delay from March 19 to March 24 cuts an already tight testing window even shorter, raising the pressure on what will be the most watched WordPress release in years.
Developer Impact
For developers, WordPress 7.0 brings both opportunities and complications. The AI infrastructure enables new plugin possibilities. Additionally, the Command Palette modernizes admin workflows. But the new database table affects backup and migration tools, and real-time collaboration shipping disabled by default means limited initial adoption.
Importantly, the delay underscores a fundamental tension: balancing modern feature expectations against the reality that WordPress must work well on constrained hosting. Google Docs and Notion set user expectations for real-time collaboration, but they don’t need to run on budget shared hosting with strict resource limits.
The Timeline
Here’s where things stand:
- March 17: Beta 5 released with 101+ updates
- March 24: RC1 (delayed from March 19)
- April 9: Final release at WordCamp Asia
WordPress 7.0 represents the most architecturally significant release since 2018. The delay shows WordPress grappling with the complexity of modern web expectations while maintaining its commitment to work everywhere. Ultimately, the April 9 release will reveal whether the team’s ambition exceeded its execution.
