WordPress 7.0 is the most significant release the platform has seen since the introduction of the Block Editor in WordPress 5.0. Launching on April 9, 2026 - strategically timed to coincide with WordCamp Asia - this release marks the definitive start of Phase 3 of the Gutenberg project, focused entirely on collaboration and workflows.
After a quiet 2025 shaped by legal shifts and a deliberate focus on stability with WordPress 6.9, the engine is humming again. Here's everything you need to know.
Release Schedule
WordPress 7.0 Beta 1 is available from February 19, giving developers and site maintainers roughly seven weeks to test before the final launch.
| Milestone | Date |
|---|---|
| Beta 1 | February 19, 2026 |
| Field Guide Published | March 19, 2026 |
| Final Release | April 9, 2026 |
Phase 3: Collaboration Takes Center Stage
For years, WordPress was great for writing, but managing a team of writers, editors, and designers required a stack of third-party tools. Version 7.0 aims to bring those collaborative interactions directly into the dashboard.
Enhanced Notes and Asynchronous Collaboration
The first major piece of Phase 3 is a robust commenting system within the editor. While a basic version appeared in WordPress 6.9, version 7.0 expands this into a full communication suite:
- Block-level Notes: Leave comments on specific blocks or even text fragments within a post
- @mentions: Tag teammates directly in the editor and trigger email or dashboard notifications
- Suggestions mode: Propose changes without directly modifying content
- Multi-block notes: Attach feedback that spans multiple blocks for broader layout discussions
This solves a massive pain point for agencies: no more taking screenshots of a layout to email feedback to a designer. The conversation happens exactly where the content lives.
Real-Time Co-Editing (Experimental)
The "holy grail" of Phase 3 is real-time co-editing - multiple users editing a post simultaneously with live cursor tracking. The team is working toward a stable, performant, Yjs-powered sync engine within Gutenberg.
However, there's an infrastructure challenge. Most performant transport layers rely on WebSocket servers, and many PHP hosting providers don't yet support this. WordPress 7.0 may ship real-time features as experimental or limited to specific environments. WordPress VIP has already open-sourced a WebSocket-based implementation proving the technology works, but universal accessibility across WordPress's diverse hosting landscape remains a work in progress.
The Modern Admin Redesign
The WordPress dashboard has largely looked the same for a decade. Version 7.0 introduces the most significant visual and structural change to the back-office in years, built on a system called DataViews.
Rather than a complete reset that would break older plugins, DataViews modernizes how you view and manage content:
- App-like interface: Post and Page lists are replaced with a fluid, modern interface
- No-refresh filtering: Filter, group, and sort content without page refreshes
- Multiple layouts: Switch between table, grid, or list views depending on your workflow
- Persistent views: The interface remembers your preferences between sessions
It feels fast, fluid, and much more like a modern SaaS application than a traditional database-driven admin screen.
The Abilities API and AI Integration
WordPress 7.0 isn't trying to be an AI writer. Instead, it's building the infrastructure that allows AI to work better within the CMS.
The new Abilities API provides a standardized way for AI services to understand what a specific WordPress site is capable of doing. Rather than hard-coding connections to specific AI models, WordPress is creating an AI Client within the core.
The Abilities API works with the Model Context Protocol (MCP), enabling AI assistants to:
- Discover what capabilities a WordPress site exposes
- Request permission to perform specific actions
- Execute tasks within defined boundaries
This means plugin developers can build AI features that are consistent across the entire platform - whether it's generating alt text for images, suggesting SEO improvements, or automating content workflows.
Technical Changes Under the Hood
PHP 7.4 Minimum
WordPress 7.0 raises the minimum supported PHP version to 7.4, dropping support for PHP 7.2 and 7.3. The core team recommends PHP 8.3 or higher for best performance and security.
This change is necessary to support the modern libraries required for collaboration features and AI APIs, and enables more consistent typing that makes the codebase easier for both developers and AI tools to understand.
Editor Isolation via Iframing
To ensure site styles don't leak into the editor, WordPress 7.0 moves toward full iframing of the editor canvas. This creates a sandboxed environment for content editing, making WYSIWYG significantly more accurate. Third-party plugin scripts won't accidentally break the editor layout, and theme styles render exactly as they will on the frontend.
No New Default Theme
WordPress 7.0 won't ship with a "Twenty Twenty-Six" theme. The project has moved away from the tradition of a new theme for every major version. Instead, the focus is on making existing block themes like Twenty Twenty-Five more powerful through the Site Editor and Phase 3 tools.
What This Means for Different Teams
For plugin developers: The Abilities API opens the door to building AI-powered features with a standardized interface. Plugins that modify the Posts, Pages, or Media list views are most likely to need updates for DataViews compatibility.
For theme developers: Invest in block theme patterns rather than building new themes from scratch. Test how your theme's editor styles render in the new iframed environment.
For agencies and site maintainers: The testing window between Beta 1 (February 19) and launch (April 9) is critical. Spin up a staging environment, upgrade to the beta, test your entire plugin and theme stack, and document any incompatibilities.
Preparing for April
Here's a practical checklist:
- Check your PHP version. Ensure you're on at least PHP 7.4 - though PHP 8.2 or 8.3 is highly recommended. Don't wait until April.
- Audit admin plugins. Any plugin that modifies the Posts or Pages list view might be affected by the DataViews migration.
- Experiment with Notes. Use a staging site to try out the collaboration features with your team.
- Watch the Field Guide. When published on March 19, read the Dev Notes for any deprecated functions.
- Test on staging. Always test against the beta in a staging environment before touching production.
Our Take
WordPress 7.0 is more than a collection of features - it's a signal that the platform is maturing. The focus on collaboration and infrastructure shows WordPress is ready to compete with modern content platforms while keeping the freedom of open source.
At Rockbell, we've been building on WordPress for years, and we're genuinely excited about what Phase 3 means for editorial teams. The measured approach to AI through the Abilities API, with clear boundaries and developer control, is exactly the right way to integrate these capabilities.
We'll be testing extensively during the beta period and covering any surprises as they come. If you're planning a WordPress project or need help preparing for the 7.0 upgrade, get in touch.
