Have you been keeping an eye on what’s coming in WordPress 7.0? Between real-time collaboration landing in Core, a built-in AI infrastructure layer, and a freshened-up admin experience, this is the most consequential release in years. Let’s dig right in.
WordPress 7.0 is scheduled to drop on April 9, 2026 — timed to coincide with WordCamp Asia — and it’s being positioned as the formal launch of Phase 3 of the Gutenberg project, which has always been about collaboration and workflows. Where earlier phases tackled the block editor and full-site editing, Phase 3 is about what happens when more than one person is working on a site at the same time.
Here’s everything that’s landing.
Real-Time Collaboration
This is the headliner. Multiple users can now edit the same post or page simultaneously, with live data syncing and block-level notes for leaving feedback mid-document. Think of it as Google Docs-style co-editing, but inside the block editor.
Under the hood, it uses an HTTP polling sync provider — WebRTC was evaluated and dropped in favor of universal hosting compatibility. Conflict resolution is handled via CRDT (Conflict-free Replicated Data Type), and sync state is stored persistently in post_meta on a dedicated internal post type: wp_sync_storage. The transport and storage layers are designed to be swappable, so hosts and plugin authors can drop in a WebSocket provider if they want lower latency.
Be mindful that the client-side Gutenberg code currently limits simultaneous collaborators to two by default, but that ceiling can be raised by hosts via a wp-config constant or a custom provider.
WP AI Client & Connectors
WordPress 7.0 introduces a new AI infrastructure layer called the WP AI Client, built around a shared php-ai-client package. This isn’t a built-in writing assistant — it’s an extensible foundation that allows plugins and themes to connect to and interact with AI models from any provider within the WordPress framework.
Managing those connections lives in a new admin page: Settings > Connectors. From there you can add, update, and remove external AI connections in one place. The UI is powered by @wordpress/components and @wordpress/admin-ui, and the underlying architecture is route-based, so plugins can hook into the page and extend it.
New Blocks & Block Enhancements
Quite a few editor additions are shipping in 7.0:
- Cover block now supports video embed backgrounds
- Grid block is now responsive by default
- Icon block — new
- Breadcrumbs block — new
- Heading block — new standalone block (split from the existing heading functionality)
- Navigation block — updated to make menu changes more reliable in fewer steps
The Font Library screen is now enabled for all themes, not just block themes. So regardless of what theme is active, editors can browse, install, and manage fonts from the admin.
Responsive Visibility Controls
You can now hide or show specific blocks based on screen size directly from the editor, without writing a line of CSS or reaching for a plugin. If a block should only appear on mobile, or only on desktop, there’s a toggle for that in the block settings sidebar.
Client-Side Media Processing
WordPress 7.0 moves image resizing and compression into the browser before upload, using the browser’s native capabilities rather than leaning on the server. This means faster media workflows, reduced server load, and support for more advanced image formats and compression techniques — for both new uploads and when processing existing content.
Admin UI Refresh & DataViews
The traditional WordPress list tables — Posts, Pages, Users, and so on — are being replaced by DataViews, a modern app-like interface that’s been landing incrementally in the Site Editor and is now rolling out more broadly across wp-admin.
7.0 also ships a new activity layout in DataViews, along with the foundation for registering third-party types in future releases.
Command Palette in the Omnibar
Logged-in editors now have a ⌘K / Ctrl+K shortcut visible directly in the top admin bar. Clicking it opens the command palette from anywhere in wp-admin — whether you’re editing content, browsing plugins, or deep in the Customizer. It’s a small thing that genuinely speeds up navigation once you get used to it.
PHP Requirement Bump
WordPress 7.0 raises the minimum PHP requirement to PHP 7.4, with PHP 8.3+ recommended for best performance. If you’re managing client sites still running PHP 7.x or earlier, now’s the time to get that sorted before the release.
What Developers Should Do Before April 9
There are a few areas worth auditing against on your themes and plugins:
- The new Web Client AI API and Client-Side Abilities API introduce new extension points — worth reviewing if you’re building anything that touches the editor
- PHP-only block registration has changes in 7.0 — check your
register_block_type()calls - Block Bindings pattern override behavior has been updated
I prefer to spin up a staging environment and run through the official testing guide before any major release touches production. Go ahead, I’ll wait…
WordPress 7.0 feels like the release the community has been building toward since the block editor shipped. Real-time collaboration alone changes how editorial teams work inside WordPress — and the AI infrastructure layer sets up what’s coming in 7.1 and beyond.
Are you testing 7.0 before launch? I would love to hear what you’re running into — or what features you’re most excited about. Let me know!