WordPress 7.0: Release Date, Key Features, and How to Prepare Your Site

WordPress 7.0 is scheduled for release on April 9, 2026, coinciding with WordCamp Asia. It’s the most significant WordPress release in years, officially launching Phase 3 of the Gutenberg project with real-time collaboration, a foundational AI infrastructure layer, and a refreshed admin experience that developers have been requesting for a long time.

If you’re running a WordPress or WooCommerce site, this release affects you. Not in a “minor update you can ignore” kind of way. In a “this changes how teams work inside WordPress” kind of way.

This post walks you through everything: what’s actually shipping, what it means for your site, what the PHP requirements look like, and the exact steps you should take before April 9 to avoid a bad upgrade day.

What Is WordPress 7.0, and When Will It Be Released?

The release of WordPress 7.0 is a major change for WordPress after having experienced a difficult 2025, which included legal issues and lower-than-anticipated release schedules. WordPress is returning to its original schedule of three major releases per year, with an anticipated final release on April 9, 2026, and Beta 1 available since February 19, 2026.

In addition to introducing a few new blocks, WordPress 7.0 introduces & delivers Phase 3 of the Gutenberg project, which has been in development for the last several years – that phase is focused on collaboration, allowing WordPress to move from being a tool for single authors to being a platform allowing multiple teams to collaborate in real-time.

Why WordPress 7.0 Was Delayed

The delay for WordPress 7.0 was the result of the original roadmap that anticipated the release of 3 major updates in 2025, however, due to several governance issues, legal challenges involving key contributors, and a strategic shift to ensure that any release would be stable and functional, the timeline changed.

The release of WordPress 6.9 in December 2025 provided a stable foundation by releasing the Notes feature for asynchronous collaboration and establishing the framework for the AI integration that will be provided with 7.0. In essence, 6.9 created a bridge that has allowed the creation of 7.0.

The Official Release Timeline

Here’s where things stand as of March 2026:

• Beta 1: February 19, 2026 (released on schedule)
• RC1 (Release Candidate): March 19, 2026
• Final Release: April 9, 2026, at WordCamp Asia

After 7.0, the project plans to continue with WordPress 7.1 in August 2026 and WordPress 7.2 in December 2026, each anchored to a major WordPress event.

The Biggest WordPress 7.0 Features You Need to Know

Let’s get into what’s actually shipping. There’s a lot here, and some features are more production-ready than others. I’ll be clear about which is which.

Real-Time Collaboration (Phase 3 of Gutenberg)

This is the headline feature, and it’s genuinely a big deal. WordPress 7.0 lets multiple users edit the same post or page at the same time, with live data syncing to keep changes aligned across sessions. Think Google Docs, but inside your WordPress editor.

The sync engine handles offline editing too, so if a contributor temporarily loses their connection, their work isn’t lost when they come back online. Block-level notes get real-time syncing as well, which makes the in-editor review process much more practical than the async commenting approach that shipped in 6.9.

A few things worth noting:

• During the beta period, real-time collaboration is opt-in. To test it, navigate to Settings > Writing and toggle on “Enable real-time collaboration.”
• The feature requires a persistent server connection, which means budget shared hosting may not deliver the full experience. If you’re on managed WordPress hosting, you’re likely fine. If you’re on an entry-level shared hosting, it’s worth checking with your provider.
• A default HTTP polling sync provider ships in core, with options for plugins or hosting providers to add WebSocket support for lower-latency sync.

For editorial teams who’ve been juggling “I’m editing this post, please don’t touch it” workflows, this is a real quality-of-life improvement. It won’t apply to every site, but for teams publishing frequently, it changes the day-to-day experience.

The Abilities API and AI Integration

Here’s where it gets interesting from a developer perspective. WordPress 7.0 ships with a foundational AI infrastructure layer made up of three components working together:

• The Abilities API gives WordPress a standardized way for plugins and themes to register what they can do in a machine-readable format. Instead of every plugin exposing features in its own custom way, they all follow the same pattern. This makes functionality discoverable, reusable, and permission-controlled by default. The API was introduced experimentally in 6.9 and is now part of the core in 7.0.
• The MCP Adapter sits on top of the Abilities API. It translates those registered abilities into the Model Context Protocol, which is an open standard for connecting AI systems to external tools. In practical terms, this means AI tools can connect directly to your WordPress installation, discover what it can do, and take actions on your behalf. No custom integrations. No bespoke plugins. Standardized access.
• The WP AI Client provides a provider-agnostic API, so plugins and themes can call AI models through a consistent interface. No AI provider is bundled by default, and no AI calls are made unless you configure them.

This is important: WordPress is building infrastructure, not making AI decisions for you.

Put it all together, and you have something WordPress has never had before. A site where an AI agent can securely discover what your plugins can do, read relevant data, and execute tasks, all through a standardized protocol.

For WooCommerce stores specifically, this opens the door to practical AI-assisted store management workflows that don’t require custom API work to set up.

Admin Interface Refresh with DataViews

The WordPress admin has looked much the same since 2008. WordPress 7.0 doesn’t do a complete redesign, but it brings a meaningful visual refresh that makes the interface feel modern and consistent.

DataViews components expand to more admin screens, replacing traditional list tables with a cleaner, more app-like interface. Typography gets harmonized across the dashboard. Spacing and iconography are more consistent. View transitions smooth out the movement between screens as you navigate.

This won’t blow anyone away visually. But it does make daily use more pleasant, and it signals that the admin UI is finally being treated as something that should evolve alongside the rest of the platform.

New Blocks, Visual Revisions, and Editor Improvements

Beyond collaboration and AI, WordPress 7.0 adds several practical editor improvements:

• New blocks: The Icons block and the Breadcrumbs block are now part of the core, along with a new Heading block. These reduce the need for third-party plugins for features that most sites need anyway.
• Responsive Grid block: The Grid block now supports responsive visibility controls, which makes the layout management in the editor more practical for real-world sites.
• Video backgrounds in Cover block: The Cover block gains support for video embed backgrounds, expanding design options without requiring custom code.
• Visual Revisions: Users can now do a visual comparison between page versions before reverting. This is one of those features that sounds small until the first time a client asks you to “put it back the way it was yesterday.”

Working with patterns has been simplified, making layout updates and content changes more intuitive than the previous workflow.

What WordPress 7.0 Means for WooCommerce Store Owners

If you run a WooCommerce store, WordPress 7.0 is relevant beyond the editor features. The AI infrastructure layer has direct WooCommerce implications.

The WooCommerce MCP integration is currently in developer preview, and it uses the same Abilities API and MCP Adapter architecture coming to WordPress core. What this means in practice: AI agents can eventually access your store’s orders, products, customer data, and operations through standardized, permission-controlled abilities, without you having to build custom integrations.

For agencies managing WooCommerce stores, this opens up genuinely useful automation possibilities, from AI-assisted order management to autonomous support flows that don’t require bespoke development work. It’s early days for the WooCommerce MCP integration specifically, so treat it as something to watch and test rather than deploy to production immediately.

The editor improvements also matter for store owners. The new Grid block with responsive controls, simplified pattern editing, and visual revisions all make it easier to maintain product pages and landing pages without developer involvement.

One thing to be aware of: plugin compatibility. Before updating any production WooCommerce store to WordPress 7.0, verify that your active plugins, particularly anything touching the block editor or admin screens, have been tested against 7.0.

At DevDiggers, we keep all our WooCommerce extensions updated for compatibility with the latest WordPress and WooCommerce releases, so you won’t face broken functionality when you upgrade. That’s the kind of thing worth confirming with any plugin you rely on for revenue-critical features.

For a deeper look at what’s possible with WooCommerce plugin development under this new architecture, our guide to WooCommerce plugin development covers the fundamentals worth understanding before building on top of the Abilities API.

Technical Requirements: What Changes Under the Hood

This is where you need to pay attention before the April 9 release, especially if you’re managing older hosting environments.

PHP Version Requirements

WordPress 7.0 drops support for PHP 7.2 and 7.3. The new minimum is PHP 7.4, and the core team recommends PHP 8.3 or higher for best performance and security.

If your site is running PHP 7.2 or 7.3, you need to upgrade before updating to WordPress 7.0. Most modern managed hosts default to PHP 8.1 or higher, so check your hosting control panel now rather than finding this out the hard way on update day.

For the WP AI Client and MCP Adapter features specifically, PHP 8.2 or higher is recommended, and you’ll need WebSocket or Server-Sent Events support depending on your setup.

Other under-the-hood changes in 7.0:

• React 19 upgrade for the block editor, bringing performance improvements and enabling new block capabilities.
• Enforced iframed editor: The editor runs in an iframe by default, improving style isolation and reducing conflicts between theme styles and editor styles.
• Block validation improvements that significantly reduce those frustrating “this block is broken” recovery prompts.

These changes are largely invisible to end users but matter a lot for custom block developers. If you’ve built custom blocks or editor extensions, test them against 7.0 beta before the final release.

If you want to understand how to create a WooCommerce plugin that works cleanly within the Abilities API pattern, the underlying concepts are worth reviewing now rather than after 7.0 ships.

Hosting Considerations for Real-Time Features

Real-time collaboration is the one feature with a hard dependency on your hosting environment. It needs persistent server connections to function well. Budget shared hosting may only deliver a degraded experience or not support the feature at full capacity at all.

If real-time collaboration is a priority for your team, managed WordPress hosting is the safer choice. Providers that support WebSocket connections will deliver the best experience. The default HTTP polling sync provider in core will work on more environments, but with higher latency than a WebSocket connection.

How to Prepare for the WordPress 7.0 Update (Without Breaking Your Site)

Don’t update production on April 9 without doing these steps first.

1. Check your PHP version: Log in to your hosting control panel and confirm you’re on PHP 7.4 minimum, ideally PHP 8.1 or higher. If you’re not, contact your host and get that sorted before the release.
2. Set up a staging environment: Any major WordPress release deserves a staging test before it touches your live site. Most managed hosts offer one-click staging. Use it.
3. Install the WordPress Beta Tester plugin: This lets you switch a staging environment to the beta channel and test 7.0 right now. The more time you spend with the beta, the fewer surprises you’ll get on release day.
4. Test your critical plugins: Focus on plugins that touch the block editor, admin screens, or any WooCommerce functionality. Run through your most important user flows: checkout, forms, membership access, and publishing.
5. Test custom blocks and editor extensions: If you’ve built anything custom for the editor, the React 19 upgrade and enforced iframed editor can surface conflicts. Find them now.
6. Review your patterns and templates: The pattern editing improvements in 7.0 are welcome, but they can shift behavior. Verify your existing patterns render as expected in the new editor.
7. Back up before updating: This should go without saying, but do a fresh backup immediately before running the update on your live site.

For WooCommerce stores specifically, also check the DevDiggers WooCommerce plugins you rely on. We ensure our plugins are tested and compatible with major WordPress releases so your store keeps running smoothly through updates.

Is Real-Time Collaboration a Game-Changer for WordPress Teams?

Most previews of WordPress 7.0 describe real-time collaboration as a “game-changer” and move on. Let’s be a bit more honest about it.

For certain teams, it genuinely is. If you manage an editorial operation where multiple writers and editors work on the same content simultaneously, or where the “who’s editing this?” lock has caused lost work before, this feature removes a real friction point. The ability to add inline notes that other collaborators see live is also more useful than async commenting for fast-moving publishing workflows.

For solo operators and small sites, it’s irrelevant. This feature doesn’t make your site faster or your content better if you’re the only one editing it.

The hosting dependency is also a real constraint. Getting true real-time sync to work well across the full spectrum of WordPress hosting environments, from shared hosts to managed cloud infrastructure, is a different challenge from building the feature itself. The beta period for this feature exists precisely to shake out those
issues. Treat it as opt-in during beta for good reason.

Here’s the thing, though: even if you don’t use real-time collaboration on day one, it sets a foundation that the WordPress ecosystem can build on. The patterns it establishes for concurrent editing, data syncing, and conflict resolution will inform how the platform handles collaborative workflows for years. In that sense, it matters even for people who won’t touch the feature immediately.

The underlying question for most teams isn’t “will real-time collaboration work?” It’s “Does your hosting environment support it, and do your workflows need it?” Answer those two questions, and you’ll know whether to enable it on day one or wait.

Frequently Asked Questions About WordPress 7.0