WordPress 7.0: Everything You Need to Know About the 2026 Release

I have been tracking WordPress 7.0 since the delay announcement on March 31, 2026, refreshing the Make WordPress Core blog almost daily. This is the biggest WordPress release in roughly eight years — the milestone that officially closes Phase 3 of Gutenberg — and I wanted to know exactly what to expect before updating my own sites and client installs.

This guide is the short version of everything I have pieced together from wordpress.org/news, make.wordpress.org/core, and the Gutenberg GitHub repo. Last updated April 17, 2026. If you are new to WordPress in general, start with my pillar guide on how to make a WordPress website first.

TL;DR: WordPress 7.0 Key Dates and Features

• Original target date: April 9, 2026
• Status (April 17, 2026): delayed — revised schedule expected by April 22
• New ETA: mid-to-late May 2026 (release lead Matias Ventura described it as "weeks, not months")
• Headline features: real-time collaboration (opt-in), Abilities API for AI, DataViews in wp-admin, Pattern Overrides for custom blocks, Interactivity API maturity
• Minimum PHP: 7.4 — PHP 8.3+ strongly recommended
• Biggest risk: plugins using legacy metaboxes will disable the new real-time collaboration feature

WordPress 7.0 Release Date and Why It Was Delayed

WordPress 7.0 was originally scheduled for April 9, 2026, with Beta 1 on February 19 and Release Candidate 1 on March 19. Then on March 31, 2026, release lead Matias Ventura posted Extending the 7.0 Cycle on Make WordPress Core and confirmed the release would slip.

The reason is the new real-time collaboration feature. The original architecture stored sync data in post_meta on an internal wp_sync_storage post type, which disabled WordPress's persistent post caches whenever a user had the editor open. Matt Mullenweg pushed to revisit a dedicated collaboration database table before shipping.

"Matt has expressed a preference to revisit the custom table and ensure adequate time is given to come up with the best design possible from the start." — Matias Ventura, Make WordPress Core, March 31, 2026

Pre-release versions were paused through April 17, 2026, and a revised schedule will be published by April 22. Informal signals from the release squad point to a final release around mid-to-late May.

Confirmed Major Features in WordPress 7.0

1. Real-Time Collaboration (Opt-In)

This is the marquee feature and the reason for the delay. WordPress 7.0 brings Google-Docs-style co-editing into the block editor, backed by full inline commenting, Notes on specific blocks, and presence indicators.

Important caveats confirmed in the delay post:

• it ships as opt-in, not default-enabled
• it uses HTTP polling for maximum compatibility (no WebSocket infrastructure required)
• it is disabled when metabox-based plugins are active on the screen — plugin authors were given this cycle to migrate to modern Gutenberg APIs

2. The Abilities API for AI Integration

The Abilities API is a provider-agnostic framework in core for registering AI capabilities — text generation, summarization, translation, alt-text generation, code generation from prompts. A new Connectors screen lets admins configure LLM providers (OpenAI, Anthropic, local models) without installing a bespoke plugin per vendor.

If you are already exposing WordPress to AI agents, this stacks cleanly with the MCP approach I cover in my WordPress Claude AI MCP connector guide. The Abilities API is for capabilities WordPress itself exposes to models, while MCP is how external agents talk back to WordPress.

3. DataViews Replaces List Tables

The classic WP_List_Table admin screens (Posts, Pages, Media, Users) are being replaced by DataViews — a modern React-based interface with saved views, bulk actions, grid/list toggle, and filters. Plugin authors who extended WP_List_Table will need to migrate, though a compatibility shim keeps most screens working during the transition.

4. Pattern Overrides Expand to Custom Blocks

In WordPress 6.9, Pattern Overrides only worked on a hardcoded set of core blocks. In 7.0, any block attribute that supports Block Bindings also supports Pattern Overrides. Custom blocks opt in through the block_bindings_supported_attributes filter on the server side.

Two rendering paths are supported: dynamic blocks get bound values passed into render_callback(), and static blocks get attributes rewritten via the HTML API without needing custom code.

5. Interactivity API Maturity

Gutenberg 22.x hardened the Interactivity API during the 7.0 cycle. The notable additions:

• a new watch() function for side effects
• server-side state.url population (so you no longer need to rehydrate it on the client)
• state.navigation is now deprecated in favor of state.url
• the data-wp-each directive is production-ready for reactive lists

6. Performance and Admin Polish

Expected improvements include lazy-loading the block inserter, faster REST responses on posts queries, and a cleaner Command Palette in wp-admin. None of these are headline features, but cumulatively the admin feels noticeably faster.

What's Being Deprecated in WordPress 7.0

Developers, this is the section you care about. Based on current dev notes and deprecation warnings already shipping in Gutenberg 22.x:

• Legacy metabox patterns that rely on add_meta_box() without Gutenberg integration disable real-time collaboration on the screen
• state.navigation in the Interactivity API — use state.url instead
• WP_List_Table extensions — still functional via shim, but flagged for future removal in 7.2 or later
• PHP 7.3 and below — WordPress 7.0 requires PHP 7.4 minimum; PHP 8.3 or newer is the recommended baseline
• Older block.json schemas missing the apiVersion: 3 declaration — still work but throw console warnings

Preparation Checklist: What to Do Before Updating

I always run this exact checklist on staging before pushing any major WordPress update to production. For 7.0 specifically:

1. Full backup. Files plus database. Store off-server. If you are on WP Engine, Kinsta, or Cloudways, use their one-click backup before anything else. Affiliate note: these are managed hosts I use on client sites because they automate this step.
2. Clone to staging. Every managed host listed above offers one-click staging. Never test 7.0 on a live site first.
3. Check PHP version. Confirm you are on PHP 8.1 or newer. PHP 8.3+ is the sweet spot for 7.0 performance.
4. Audit plugins. Log into staging, update all plugins, then watch the WordPress admin for "deprecation" or "compatibility" notices. Any plugin still using raw metaboxes is a red flag.
5. Test your theme. Classic themes still work, but block themes get the full benefit of 7.0. If you use a custom theme, confirm block.json is at apiVersion 3.
6. Run the upgrade on staging. Update to 7.0 on staging, walk through every critical user flow (checkout, contact form, login, the block editor itself).
7. Check site speed. Before and after. My guide on improving WordPress SEO covers the Core Web Vitals side of this.
8. Decide on real-time collaboration. It is opt-in, so you can skip it at first. I recommend leaving it off until after your first successful 7.0 deploy.
9. Schedule the production update. Low-traffic window. Tell clients. Have a rollback plan.

What WordPress 7.0 Means for AI Agents and MCP

The Abilities API is a quiet game-changer for the AI-plus-WordPress ecosystem. Until now, every AI plugin shipped its own provider integration. With the Abilities API, core exposes a single registry of "what this site can do" — and AI agents discover those abilities through a consistent interface.

If you are already connecting external agents via Model Context Protocol, follow my WordPress Claude AI MCP connector guide — the MCP server layer sits nicely on top of the new Abilities registry in 7.0. I expect MCP-aware AI plugins to start exposing their abilities through the core API within the first few weeks after release.

Should You Update Immediately?

My rule of thumb is simple:

• Hobby site or personal blog: update within the first week. The feature wins outweigh the risk.
• Small business site: wait for 7.0.1 (usually 2 to 3 weeks after the main release). Point releases clean up the inevitable edge cases.
• Revenue-critical site (WooCommerce, membership, booking): wait 4 to 6 weeks. Let plugin authors ship their compatibility updates. Test on staging first, always.
• Agency or multisite: wait for 7.0.2 and confirm every critical plugin has a 7.0-compatible release.

Frequently Asked Questions

When is WordPress 7.0 releasing?

It was originally scheduled for April 9, 2026. After the March 31 delay announcement, the revised ETA is mid-to-late May 2026. The core team will publish the exact new date by April 22, 2026.

Will WordPress 7.0 break my site?

Probably not, if you are already on WordPress 6.8 or 6.9 with PHP 8.1 or newer. The biggest compatibility risk is with plugins that still use legacy metaboxes — these will disable the new real-time collaboration feature but will not crash your site. Always test on staging first.

What's new in WordPress 7.0?

The headline features are real-time collaboration in the block editor, the Abilities API for AI integration, DataViews replacing the classic admin list tables, Pattern Overrides for custom blocks, and a matured Interactivity API. It is the largest release since Gutenberg Phase 1.

Should I update to WordPress 7.0 immediately?

If it is a hobby site, yes, within the first week. For business or e-commerce sites, wait at least 2 to 4 weeks until 7.0.1 ships. Major WordPress releases always have a small number of edge-case fixes in the first point release.

Do I need to change my PHP version for WordPress 7.0?

The minimum is PHP 7.4, but PHP 8.3 or newer is strongly recommended for performance. If you are still on PHP 8.0 or below, upgrade your PHP version before upgrading WordPress.

Will my plugins work with WordPress 7.0?

Most well-maintained plugins will. Plugins relying on WP_List_Table extensions still work through a compatibility shim, but you should check plugin changelogs for "WordPress 7.0 compatible" notes. Plugins with legacy metaboxes are the main risk and will prevent real-time collaboration from activating on affected screens.

Does WordPress 7.0 require a new theme?

No. Classic themes still function. Block themes benefit most from the new features (DataViews, Pattern Overrides, Interactivity API improvements), so if you are planning a redesign, now is a good moment to move to a block theme.

Primary Sources

• Make WordPress Core: WordPress 7.0 release page
• Make WordPress Core: Extending the 7.0 Cycle (delay announcement)
• Make WordPress Core: Pattern Overrides in WP 7.0 — support for custom blocks
• Make WordPress Core: WordPress 7.0 Release Party Schedule
• WordPress Developer Blog: What's new for developers (April 2026)
• WordPress.org Roadmap