WordPress 7.0 Release Date: Delayed New Timeline for April 2026

If you are searching for the WordPress 7.0 release date today, the first thing to know is that the original April 9 launch is no longer current. WordPress core has delayed the release and is reworking the final stretch of the cycle after testing feedback, especially around real-time collaboration.

What is WordPress 7.0? 

WordPress 7.0 is the first major WordPress release planned for 2026. While the final release is delayed, the 7.0 cycle is now well-defined. A major part of the work centers on real-time collaboration, AI infrastructure, admin-side interface changes, navigation overlays, editor compatibility updates, and the PHP 7.4 minimum requirement.

Why Has WordPress 7.0 Been Delayed?

On March 31, 2026, the WordPress core team announced that WordPress 7.0 would not ship on its planned April 9 date. The decision came out of the Making WordPress Slack workspace, where Matt Mullenweg and the release squad agreed the milestone needed more time in the Release Candidate phase to stabilize the data storage layer behind the new real-time collaboration feature.

The delay was driven by testing feedback and unresolved architectural details around real-time collaboration, especially the data model and cache invalidation approach. WordPress core also noted that reverting to beta-style version numbering after RC would create technical problems, so the project is continuing through pre-release builds without going back to traditional beta labels.

Release Candidates 1 and 2 had already shipped in March before pre-release versions were paused to address the outstanding real-time collaboration issues.

What’s new in WordPress 7.0?

Feature	WordPress 6.9	WordPress 7	Breaking?
Minimum PHP version	7.2	7.4	Yes. Sites on 7.2/7.3 stay on the 6.9 branch
AI Client in core (php-ai-client)	Not bundled	Bundled as external library	New API surface
DataViews in admin	Limited to specific screens	Expanded across the admin refresh	UI change
Command Palette in admin bar	Not present	⌘K / Ctrl+K shortcut	New UI
Iframed post editor	Opt-in	Default for Block API v3+	Breaking for v1/v2 blocks
Icon registration API (/wp/v2/icons)	Not present	New REST endpoint	New API
Client-side media processing	Server-side by default	Client-side by default	Behavior change

1. Real-time collaboration in the block editor

Real-time collaboration is the headline feature in the WordPress 7.0 cycle. Multiple users will be able to edit the same post or page simultaneously, with live cursors, presence indicators, and synced block content. The experience is closer to Google Docs than anything WordPress has shipped before.

A few practical details worth knowing:

• The default sync mechanism is HTTP polling, not WebSockets. The WordPress team chose HTTP polling so the feature works across the full hosting landscape, including shared hosting that does not support persistent connections. Hosts and plugin authors can swap in a WebSocket provider for lower latency.
• Sync data is stored using a CRDT (Conflict-free Replicated Data Type) approach, persisted via post meta on a dedicated internal post type called wp_sync_storage.
• The default client-side limit is two simultaneous collaborators per post, configurable by hosts and developers.
• Collaboration will be opt-in in 7.0 through Writing settings.

2. WP AI Client and the Connectors page

WordPress 7.0 introduces a provider-agnostic AI infrastructure built on the php-ai-client library. The core team deliberately did not bundle an AI service or pick a preferred vendor.

• A new Settings → Connectors screen in wp-admin where site owners connect AI providers like OpenAI, Anthropic, and Google Gemini using API keys.
• A registry that lets plugins add additional providers dynamically.
• A standardized client interface plugin that authors can build against, so AI features like content suggestions, image generation, alt-text automation, or translation can target a single API rather than three vendor SDKs.

3. Admin Refresh and DataViews

The WordPress admin is getting its first meaningful visual refresh in years. The team has positioned this as a “coat of paint” rather than a full redesign.

• Work in the 7.0 cycle includes ongoing DataViews and DataForm iterations.
• A new activity layout is available in DataViews.
• Admin styling is being aligned more closely with the WordPress Design System to reduce inconsistencies between legacy screens and newer block-based interfaces.

If your client sites have plugins that hook deeply into the wp-admin screens, this is one area worth auditing on staging before updating.

4. Command Palette in the Admin Bar

Logged-in editors will see a new trigger in the upper admin bar with a ⌘K (or Ctrl+K) shortcut. Clicking it opens the Command Palette from anywhere in the admin. You can jump straight to editing, designing, or browsing plugins without navigating through menus.

5. Notes: Richer Commenting Workflows

Notes shipped in WordPress 6.9 as block-level comments. In the WordPress 7.0 cycle, the team is continuing that work with planned improvements around partial selection inside rich text fields, richer comments, multi-block notes, and more notification options, such as mentions.

For now, it is safer to describe this as an active area of iteration rather than a fully finalized checklist of shipped behavior. 

6. Iframed Post Editor

The post editor in WordPress 7.0 is moving further toward iframe compatibility, but it is not fully iframed across the board. In 7.0, WordPress changes the logic so the post editor can be iframed when the blocks used in a post are Block API version 3 or higher. The team has delayed the enforcement of full iframe in favor of a more gradual rollout.

The practical takeaway is still the same: older blocks and editor extensions may need updates. If you maintain custom blocks, start migrating to Block API version 3 and review the iframed editor dev note before updating production sites.

7. Client-side Media Processing

Client-side media processing was introduced during the 7.0 cycle as a way to move image resizing, compression, and format conversion into the browser. It promises smoother upload workflows, lower server demand, and support for formats such as AVIF, but this is one area to check against the latest release-candidate notes because Beta 6 temporarily reverted the feature.

8. New Blocks and Editor Improvements

A few additions worth flagging:

• Icon block: A new block for adding SVG icons from a built-in library, backed by a server-side SVG Icon Registration API and a /wp/v2/icons REST endpoint. Third-party icon registration is planned for a future release.
• Navigation block overlays: Customizable mobile menus that are no longer marked experimental.
• Patterns default to Content-Only editing: Reduces design clutter for content creators while keeping structural editing available via “Detach pattern.”
• Gallery block lightbox: Now supports back/next navigation and arrow key controls.

The Tabs block was considered for 7.0 but deferred.

WordPress 7.0 Raises the Minimum Supported PHP Version

WordPress 7.0 drops support for PHP 7.2 and 7.3. The new minimum supported version becomes PHP 7.4.0, while the minimum recommended version remains 8.3. Sites still on PHP 7.2 or 7.3 will stay on the 6.9 branch once 7.0 is released. If you manage multiple sites, this should be one of the first checks in your prep process.

Should You Install WordPress 7.0 on Production Sites?

Not yet.

Until WordPress 7.0 is released and you have tested it against your own stack, production sites should stay on the latest stable maintained release. Right now, that means WordPress 6.9.4. 

When 7.0 does ship, the right move for most agencies will still be staged testing first, especially on sites with custom plugins, heavy editorial workflows, membership setups, WooCommerce, or older admin customizations.

WordPress 7.0 Upgrading Checklist For Agencies & Developers

The delay gives agencies and developers a few extra weeks of runway. Use it. Here’s a practical checklist for the period between now and the new release date:

• Check PHP versions first. Any site still running PHP 7.2 or 7.3 already has a compatibility problem for WordPress 7.0 and needs a hosting-side review before the core update.
• Review editorial workflows. If a site depends on metabox-heavy plugins or custom publishing interfaces, collaborative editing may not behave the way it does on a clean block-editor install.
• Audit plugin compatibility. Pay extra attention to plugins that extend the editor, inject admin UI, or rely on older publishing workflows.
• Test custom blocks and theme behavior on staging. This is critical if you maintain custom blocks, editor styles, or older plugin code that assumes legacy editor behavior.
• Take a fresh backup before testing. Make sure you have a recent restore point before the upgrade.
• Verify critical site functions after updating. Check key templates, forms, login flows, e-commerce flows, and any client-specific functionality before moving toward production.
• Decide whether you need the WP AI Client immediately. If yes, plan how API keys will be stored. Use environment variables or PHP constants in production rather than the Connectors UI.

How to Contribute to WordPress 7.0?

WordPress 7.0 is still coming, just not on April 9. The combination of real-time collaboration’s architectural work and the PHP 7.4 requirement means agencies have extra runway to audit client sites, upgrade PHP versions where needed, and test plugin compatibility before the official release ships.

Watch make.wordpress.org/core for the revised schedule (expected by April 22) and keep an eye on the official release notes when the new beta drops. Until then, WordPress 6.9.4 remains the stable version for production sites.

Running client sites at scale? WP Umbrella runs visual regression tests on every update automatically, so your first WordPress 7.0 update on 50 or 500 sites is the same workflow as a routine patch release. Start your free trial — no credit card required.

Want to help shape 7.0? Feature contributions have closed, but testing, bug reports, and documentation are still open. Browse 7.0 tickets on WordPress Trac or join the weekly #core meetings on the Making WordPress Slack (Wednesdays at 15:00 UTC).