WordPress 7.0 Arrives in April—Here’s Why We’re Excited

WordPress 7.0 lands in April 2026, and the core team plans to ship it live during Contributor Day at WordCamp Asia in Mumbai, in front of thousands of attendees. This is the first time a major release is scheduled at a WordCamp. 

WordPress 7.0 brings real-time collaborative editing, a provider-agnostic AI integration layer, and a refreshed admin interface. Together, they mark the start of Phase 3 of the Gutenberg project, namely the collaboration phase, and represent the most architecturally significant release since the block editor arrived in 2018.

For enterprise teams, the WordPress 7.0 features open up entirely new workflows. It is worth understanding what you can build on top of it.

Real-time collaboration: Writing to publishing within WordPress

Drafts start in Google Docs, and feedback lives in comment threads. The final version gets pasted into the editor. 

WordPress 7.0 changes that by removing the need to hop across tools. Editors can now work on the same post simultaneously, with conflicts resolving automatically. The lock-wait-merge cycle slowing down breaking coverage or publishing velocity is eliminated. Imagine newsrooms running WordPress at scale and covering national elections or reporters in multiple regions filing updates into one evolving story.

The collaboration infrastructure is designed with WordPress’ hosting diversity in mind. The default sync uses HTTP polling, so it works everywhere, including shared hosting. Environments that support WebSockets can enable faster syncing, and developers can plug in custom transport layers via the sync.providers filter. At launch, simultaneous editing supports two collaborators per post, configurable through wp-config.

Editorial workflows that stay inside WordPress

The collaboration story extends beyond co-editing. WordPress 7.0 builds on the Notes system introduced in 6.9, adding multi-block notes, a suggestion mode, and @mentions that trigger email and dashboard notifications.

If your editorial team currently hops between Google Doc comments and your CMS, this is the feature that can bring the full feedback loop into one place.

Revisions get a visual overhaul too. Color-coded overlays show added blocks (green), removed blocks (red), and modified blocks (yellow) directly in the editor, with a timeline slider for scrubbing through versions in a read-only review mode. For compliance-heavy industries where content audit trails matter, this kind of built-in visibility is significant.

WordPress 7.0 AI integration: A foundation rather than a feature

This is the WordPress 7.0 capability we’ve been watching most closely.

Building on the Abilities API introduced in 6.9, WordPress 7.0 adds a provider-agnostic AI integration layer to core. No single vendor is baked in. Instead, any plugin or theme can connect to AI services through a standardized interface, and administrators get a single management screen at Settings → Connectors to control which providers are active and how they’re used.

OpenAI, Google AI, and Anthropic ship as default provider plugins. Additional providers can be registered via the connections-wp-admin-init hook.

Why this matters strategically

The AI layer in 7.0 is deliberately infrastructural. WordPress is shipping the plumbing that lets the entire ecosystem build AI features on a stable, governed foundation.

For technology leaders, it means AI capabilities can be introduced and governed through core infrastructure rather than through fragmented plugin-level integrations. You choose the provider, control the API keys, and decide which capabilities to activate and where.

For marketing and content teams, the advantage is immediate. Think about a brand managing an eCommerce catalog with 500 product pages. With the AI Connectors framework, plugins can connect to any supported AI provider through core infrastructure, opening the door to capabilities like generating SEO meta descriptions and alt text at scale directly inside WordPress.

This is early-stage infrastructure, and that’s precisely what makes it exciting. The roadmap it enables, that of personalized content delivery, intelligent editorial assistance, and automated accessibility improvements, is far bigger than any single release. 

We are all set to pursue AI-led digital experiences, building on the WordPress AI foundation we have been investing in across client engagements and capitalizing on 17 years of good work.

A refreshed admin experience

The wp-admin interface gets its first major visual update since WordPress 3.8 shipped in December 2013, which alone is notable.

Command Palette, everywhere

The Command Palette, previously confined to the block editor, now lives in the Omnibar across the entire admin. Press ⌘K (Ctrl+K on Windows) from any screen to jump to a draft, a settings page, or a specific post. No more clicking through nested menus.

For a site editor managing thousands of posts, this is a material time-saver. For developers working across environments, it’s the kind of keyboard-driven navigation that makes wp-admin feel modern.

DataViews replace legacy list tables

The DataViews component progressively replaces WP List Tables for Posts, Pages, and Media. The result is filterable, sortable, app-like content browsing.

This is a significant DX change. Plugins that hook into legacy list views, particularly for Posts, Pages, or Media will need testing. The groupByField string has been replaced by a groupBy object supporting field, direction, and showLabel properties.

New blocks and editor improvements worth knowing about

WordPress 7.0 ships several other editor enhancements:

Breadcrumbs and Icons blocks

The Breadcrumbs block auto-generates navigation paths with PHP filters (block_core_breadcrumbs_items and block_core_breadcrumbs_post_type_settings) for customization. The Icons block provides a REST-accessible icon library at /wp/v2/icons.

Viewport-based block visibility

Blocks can now be shown or hidden by device type. This is now stable after several releases of experimental development. For eCommerce teams, this means device-specific calls-to-action without maintaining separate templates or relying on third-party plugins.

Per-instance custom CSS

Individual block instances can receive custom CSS through an Advanced panel. The Cover block gains video embed backgrounds, the Grid block becomes responsive, the Gallery block gets lightbox navigation, and the Navigation block supports customizable overlays with mobile-specific breakpoints.

Client-side media processing

Image resizing and compression now happen in the browser before upload, supporting AVIF, WebP, and MozJPEG output. For a photojournalism team uploading 50 high-resolution images daily, files are optimized before they hit the server, cutting upload times and reducing infrastructure load.

What your engineering team needs to prepare for

PHP 7.4 is the new floor

Support for PHP 7.2 and 7.3 is dropped after combined usage fell below the project’s 4% threshold. PHP 8.3+ is recommended. Sites on older versions stay on the 6.9 branch and will not receive the 7.0 update.

DataViews API breaking change

The groupByField to groupBy object migration requires testing for any plugin that modifies Posts, Pages, or Media list views.

Interactivity API gains watch()

A new primitive for subscribing to reactive state changes at the store level, independent of the DOM. It will be useful for analytics and side-effect tracking on client-side navigations.

Block API v3 is becoming the reference model

Blocks relying on global document queries or .wp-admin selectors should plan for migration. The iframed editor is expected to be enforced in WordPress 7.1.

Classic meta boxes and collaboration

Real-time collaboration is disabled when classic meta boxes are present on a post. Plugins relying on them will need to migrate to registered post meta with show_in_rest before collaboration can be enabled.

Three releases in 2026, each tied to a flagship event

WordPress returns to a three-release cadence in 2026, after shipping two releases in 2025. Each major version is anchored to a key community event:

• 7.0 — April 9, WordCamp Asia (Mumbai)
• 7.1 — August, WordCamp US
• 7.2 — December, State of the Word

WordPress 7.0 is led by Matias Ventura, Gutenberg’s chief architect. The cadence itself tells a story: the collaboration phase is a year-long arc, and 7.0 is the opening chapter.

Looking ahead: the enterprise roadmap this enables

Step back from the individual features, and the big picture becomes clear. WordPress 7.0 is building the infrastructure layer for a platform that can serve as the operating system for enterprise digital experiences.

• Collaboration makes WordPress the authoring environment, not just the publishing endpoint.
• AI integration gives organizations a governed, extensible foundation for intelligent content workflows.
• The refreshed admin and DataViews bring the management interface closer to the modern application standards that enterprise teams expect.

These are foundations rather than finished products, and that’s what makes them strategically important. Organizations building on this foundation now will have a meaningful head start.

Ready to plan your WordPress 7.0 roadmap?

Before applying the update, check your PHP version (7.4 minimum), audit any plugins using classic meta boxes or WP List Tables, and assess whether your editorial team is ready to adopt real-time collaboration.

If your team is evaluating what WordPress 7.0 means for your technology stack, we’ve written about how WordPress fits into enterprise ecosystems. And if you’re ready to build on what’s coming, our WordPress DXP services are designed for exactly this kind of platform transition.