I’ve been running WordPress sites long enough to watch major releases land with a thud, along with a handful of editor tweaks that nobody outside the core contributor community cares about. WordPress 7.0 feels different, and the feature list backs that up.
This is the first major release of 2026. It ships real-time collaboration, a native AI layer, new blocks, responsive editing controls, and a refreshed admin. These are not checkbox features. Several of them have been in progress for years, and they are finally ready.
Here is what is coming, what it means in practice, and what I think you need to know before it drops on April 9, 2026.
Real-Time Collaboration Is Finally Here
This is the headline feature, and it has earned considerable attention during the beta period.
WordPress 7.0 lets multiple users edit the same post or page simultaneously. Changes sync in real time. Notes stabilize and sync across users, too. A default HTTP polling sync provider ships out of the box, with plugin or host-level WebSocket support available for lower-latency setups.
For teams managing a site together, this is a genuine shift in workflow. The “who has the page open” conversation can largely become a thing of the past. So, can you discover that you overwrote someone else’s edits? I have had that conversation more times than I want to count, and I am glad to retire it.
During the beta period, real-time collaboration is opt-in. That gives the core team room to gather feedback before it becomes the default.
What this means for your team:
- Content editors can work on the same post simultaneously without creating conflicts.
- Review and editing cycles get faster and less painful.
- Notes sync in real time, so feedback does not disappear.
- WebSocket support is available through plugins or hosting providers for teams that need faster sync.
The Admin Got a Visual Refresh
The WordPress dashboard is getting a new default color scheme and a cleaner interface. It is not a ground-up redesign. It is more like the admin finally got the update it should have gotten a few years ago.
Two functional changes matter more than the aesthetic ones.
Visual Revisions: You can now compare page versions side by side inside the editor. Green outlines flag added blocks, red marks removed blocks, and yellow marks modified settings. Text additions appear in green and underlined; removals appear in red with a strikethrough. This is the kind of thing content teams will quietly thank someone for.
View Transitions: Navigating between admin screens is now smooth instead of jarring. Not glamorous. Just better.
New Blocks and Design Tools
WordPress 7.0 ships several new blocks and a meaningful round of improvements to existing ones.
New blocks:
- Breadcrumbs Block: Adds navigation context to posts and pages without a plugin.
- Icons Block: Native icon support, built directly into the core.
- Heading Block Variations: Heading levels are now available as block variations for better layout control.
Block improvements:
- Cover Block: Video embeds can now serve as cover backgrounds.
- Grid Block: Responsive support is now built in. No more custom CSS workarounds for basic grid layouts.
- Gallery Block: Lightbox support lets users click through images with back and next navigation.
- Navigation Block: Menu editing got smarter with improved overlays, mobile-specific breakpoints, and customizable overlay template parts.
- Font Library: Font management is now available for all themes, not just block themes.
Responsive editing controls:
Block visibility can now be set by screen size. Hiding a block on mobile or showing it only on desktop has been a real pain point for years. I manage a large number of client sites, and the number of times I have patched this with CSS is embarrassing. The native solution is overdue.
A Native AI Layer Built Into Core
This is a meaningful architectural shift in 7.0 and one of the features with the longest potential tail.
WordPress 7.0 introduces a WP AI Client that lives inside Core and acts as a shared interface for connecting to generative AI models. Providers are external. Three are already available in the plugin directory: OpenAI, Google, and Anthropic. You manage them from the WP-Admin under Settings > Connectors.
The design is practical. Plugins and themes write against the shared interface once, and users choose their preferred AI provider through settings. Switching providers does not require touching anything in your plugins or themes.
The Client Side Abilities API works alongside this, providing a standardized way to register and run capabilities in the browser. That includes command palette improvements, ability filtering, and support for more complex multi-tool workflows.
What this means in practice:
- AI-powered plugin features can work across providers without requiring separate integrations.
- Site owners manage AI connections from one central place.
- Developers have a stable API to build against, rather than rolling their own AI plumbing.
- Future releases have a solid foundation for more capable AI-assisted editing tools.
If you are building for clients who want AI features in their WordPress sites, understanding the Connectors architecture before committing to any third-party AI plugin is worth the time. The approach for AI-assisted WordPress development is likely to look quite different once 7.0 ships.
Browser-Based Media Processing
This one is underrated and will matter to many site owners who haven’t realized it yet.
WordPress 7.0 moves image resizing and compression into the browser before the file ever reaches the server. Uploads are faster. Server load drops. Modern image format support improves.
For sites running on constrained hosting infrastructure, this is a real quality-of-life gain. Work that previously required server resources now happens on the client side before the upload even begins. I have clients on managed hosting plans where server-side processing is a constant source of friction, and this change will quietly improve their lives.
If your site relies on server-side image optimization plugins, test how they interact with client-side media handling in 7.0 before you update.
Developer Updates Worth Knowing
If you build plugins, themes, or custom WordPress sites, here is what deserves attention.
- PHP-Only Block Registration: Blocks can now be registered entirely in PHP with auto-generated inspector controls. No JavaScript required for simple blocks.
- Block Bindings Updates: Pattern overrides now extend to custom dynamic blocks.
- DataForm and DataViews: New layout options, new controls including combobox and adaptiveSelect, and validation support across all layouts.
- CodeMirror Update: Updated to a newer version for better extensibility. Confirm the exact version number in the official WordPress 7.0 dev notes before referencing it in documentation.
- WP-CLI wp block Commands: New read-only block entity commands are in development with pattern and template export support.
- wp-env Playground Runtime: phpMyAdmin support added, reaching feature parity with Docker.
One important note: the always-iframed post editor was originally planned for 7.0 and got pushed to 7.1. The Gutenberg plugin will still iframe the post editor, but Core will not enforce it until the next release.
When Does WordPress 7.0 Ship?
WordPress 7.0 is scheduled for April 9, 2026, during WordCamp Asia 2026 Contributor Day.
Beta 3 is available now. The Release Candidate is scheduled for March 19, 2026.
Ways to test before release:
- Install the WordPress Beta Tester plugin, select “Bleeding edge,” and choose the “Beta/RC Only” stream.
- Download the beta zip directly from wordpress.org.
- Run
wp core update --version=7.0-beta3via WP-CLI. - Test in your browser with no setup using WordPress Playground.
Do not test on a production site. Use a staging environment or a local install. I say this every release cycle, and someone always ignores it.
What to Do Before April 9
You do not need to act today. But a few things are worth doing before the release lands.
Test your plugins and themes against the beta. The block API updates, the AI Connectors screen, and changes around the iframed editor are the areas most likely to surface compatibility issues.
Review your navigation menus. The Navigation block has been meaningfully updated. If you use it heavily, confirm everything still behaves correctly.
Think through your AI integrations. The native AI Client changes the approach for anyone building AI-assisted features for clients. Understanding the Connectors architecture before committing to a third-party AI plugin will save headaches later.
Plan for the media processing change. If you rely on server-side image optimization, test the interaction with client-side handling in 7.0 before it goes live.
The Bottom Line
WordPress 7.0 is shaping up to be one of the more substantive releases in recent memory.
Real-time collaboration alone would make it notable. Add native AI infrastructure, a refreshed admin, new blocks, responsive editing controls, and browser-based media processing, and this release meaningfully expands what WordPress can do out of the box.
April 9, 2026, is worth putting on your calendar.
