WordPress 7.0: What's Actually Coming and Why It Got Delayed

WordPress 7.0 was supposed to ship on April 9, 2026. It didn't. The core team pulled the plug a week before launch because the data storage layer behind real-time collaboration wasn't ready. A revised schedule should land by April 22, so we're probably looking at late April or early May.

That delay says a lot about the ambition here. This isn't a point release with tweaked margins and a new default theme. WordPress 7.0 is the official start of Phase 3 of the Gutenberg project — Collaboration — and it brings along an AI infrastructure layer, the beginnings of an admin redesign, a PHP version bump, and some meaningful editor improvements.

I've been in the Make WordPress Slack discussions and testing the release candidates. Here's what I know.

Real-Time Collaboration

For the first time in 23 years, WordPress is trying to become a multi-user editing tool. Two people open the same post, they see each other's cursors, changes sync in something close to real time.

The team built this on CRDTs (Conflict-free Replicated Data Types) instead of Operational Transform, which Google Docs uses. The sync runs on HTTP polling, not WebSockets. That second choice is practical — most shared hosting doesn't support persistent connections, and WordPress has always prioritized running everywhere.

What you get:

• Live cursors and presence indicators
• Block-level sync so edits in one block don't stomp on another
• Notes for leaving feedback inside the editor
• Offline editing that catches up when you reconnect
• Sync data stored via post meta on an internal wp_sync_storage post type

Compared to Google Docs or Notion, the experience feels rough. There's visible latency from the polling approach, and conflict resolution on complex nested blocks still has problems. The delay was specifically about the data model and cache invalidation — the storage layer wasn't handling real-world load patterns well enough.

Even so, it works for the common case: two or three editors on the same long-form post without stepping on each other. If you've been hacking together workflows with post locking and revision diffs, that's a real improvement.

The Abilities API and AI Client

WordPress 7.0 doesn't ship with an AI writer or a "generate post" button. It ships plumbing.

The Abilities API was introduced in 6.9 and lets plugins register what they can do in one central place. Those capabilities become discoverable through REST endpoints or the new MCP (Model Context Protocol) Adapter — same protocol Anthropic developed for connecting AI tools to external services.

The AI Client is a provider-agnostic PHP API. You configure your AI provider (OpenAI, Anthropic, Google, a self-hosted model) through a new Connectors screen in the admin. Plugins send prompts and get responses through a consistent interface. Auth, rate limiting, content sanitization, context management — the API handles it.

Right now every AI plugin for WordPress reinvents the wheel: separate settings pages, separate API key management, separate error handling. The Abilities API standardizes that. A content generation plugin, a layout assistant, an image alt-text writer, and an SEO tool can share the same AI connection configured once.

The privacy controls matter too. Admins can control which content types get sent to AI providers, set up data anonymization, and audit every request through logging. Most current AI plugins handle this poorly or skip it entirely.

Admin Refresh

The WordPress admin hasn't had a visual overhaul since 2013. It shows. The block editor looks modern, the settings pages look like 2013, and the plugin screens look like neither.

7.0 starts fixing this with DataViews, which replace WP List Tables. Inline filtering without full-page reloads. Visual language that matches the block editor. It's not a complete redesign — that'll take multiple releases — but it removes some bad friction points.

PHP 7.4 Minimum

7.0 raises the minimum from PHP 7.2 to 7.4. Sites on 7.2 or 7.3 won't get the update and stay on 6.9.

PHP 7.4 reached end of life in November 2022. WordPress requiring it in 2026 tells you everything about the project's relationship with backward compatibility. Recommended is PHP 8.2 or 8.3.

Check your hosting. A surprising number of managed WordPress hosts still default to PHP 8.0 or even 7.4. You won't be blocked from running 7.0, but you'll miss performance and security improvements.

Other Editor Changes

The collaboration system gets the headlines. Some smaller changes might matter more in daily use.

Responsive styling controls are better — you can set different padding, margin, and typography for desktop, tablet, and mobile directly in the editor. Possible through custom CSS before, but having it in the UI helps non-technical users.

Navigation block improvements address complaints about building complex menus. Not flashy, but if you've fought with the Navigation block on a site with deep menus, you'll notice.

Client-side media handling changes how images and videos get processed in the browser before upload. Less server load, better experience on limited hosting.

What Comes After 7.0

Three major releases planned for 2026: 7.0, 7.1 (mid-year), 7.2 (late year).

7.1 will refine collaboration. Better conflict handling, notification systems, support for content types beyond posts and pages. More admin refresh. The "sand the rough edges" release.

7.2 gets more interesting. The roadmap mentions early Phase 4 work: Multilingual. Native multilingual support has been one of the most requested WordPress features for years. Today you need WPML or Polylang, and they add complexity that breaks things in unexpected ways. Even a partial core implementation would reshape the plugin landscape.

Block Bindings also go deeper in 7.2, with more native data source connections. WordPress trying to compete with headless CMS platforms by making structured data easier to pull into block layouts.

Where AI in WordPress Is Heading

The Abilities API is foundation. What gets built on it depends more on the plugin ecosystem than on core development. But some directions seem clear based on what's happening in the broader CMS and AI space:

Contextual content help. Not "write me a blog post" but: better headline suggestions based on your existing content, internal linking recommendations, readability adjustments for your audience. The API lets tools understand your site holistically instead of one post at a time.

Layout generation. Describe what you need — "landing page with hero, three feature cards, testimonial slider" — and the AI builds it from your block patterns and design tokens. Tools like 10Web already do this, but a standard API means you're not locked into one vendor.

Accessibility scanning. AI checks pages for missing alt text, poor contrast, broken heading hierarchy. Fixes the simple stuff automatically, flags the rest. The permission model means the AI can access your full site structure to be thorough about it.

Translation. With Phase 4 multilingual work starting, AI translation at the CMS level becomes practical. Not for high-stakes content where you'd hire a translator, but for docs, support articles, content where speed outweighs perfection.

SEO that goes beyond keywords. Tools that understand search intent, analyze competing content, suggest structural changes. Plugins do this now, each with separate AI connections and separate site understanding. Shared infrastructure means better results, less setup.

The MCP Adapter is the piece I keep thinking about. External AI agents can interact with your site programmatically — discover what it can do, request permissions, take actions. Tell an assistant "update the product descriptions to mention the spring sale" and it does it through a structured API instead of screen scraping. That's where this is going.

What to Watch Out For

Server load from collaboration. HTTP polling means regular requests even when nothing's changing. Busy sites with many editors could feel this. Some hosting providers will need to adjust infrastructure.

Plugin breakage. Any release that changes editor architecture this much will break things. The team has been running compatibility tests, but there will be surprises. Test in staging first.

AI privacy gaps. The Abilities API has good controls on paper. Plugin developers will implement them with varying care. Someone needs to actually read the audit logs and understand what data goes where.

Collaboration hitting its limits. Google has refined real-time editing for 20 years. WordPress is starting from zero with the constraint of supporting every host on the planet. It'll work for simple cases. Complex ones will take time.

Preparing Your Sites

1. Check PHP version. 7.4 minimum, 8.2+ recommended.
2. Test 7.0 in staging when it ships. No auto-updating production day one.
3. Watch for plugin compatibility statements in the first week after launch.
4. If you run multisite, be extra careful. Multisite gets the least beta testing, always.
5. Think about which AI tasks would actually help your workflow. The infrastructure makes experimentation cheaper, but you still need to know what problem you're solving.

So What Does This Mean

WordPress powers roughly 40% of the web. When it adds collaboration and AI infrastructure, the ripple effect is enormous. The collaboration features, even in early form, lower the barrier for small teams that can't justify separate Google Workspace or Notion subscriptions. The AI layer, if the plugin ecosystem builds on it well, could bring sophisticated content tools to site owners who can't afford enterprise CMS platforms.

The delay before April 9 suggests the team would rather ship late than ship broken. Good. Broken real-time collaboration would be worse than no real-time collaboration.

I'll update my maintenance clients once the release stabilizes and the first compatibility reports come in. If you're managing WordPress sites, give it a couple weeks after launch before pulling the trigger on production.

Need help preparing your WordPress sites for the 7.0 upgrade? I offer WordPress Maintenance plans that include update testing, compatibility checks, and safe deployment. Book a free consultation to discuss your setup.