Website management has changed dramatically over the past several years. Where content was once created by a single person working through a simple editor, modern publishing now involves cross-functional teams, distributed contributors, and workflows that demand speed and flexibility. WordPress, which powers a significant portion of the web, has been evolving steadily to match these demands.
WordPress 7.0 represents the next major chapter in that evolution. Scheduled for release on April 9, 2026, this version doubles down on collaborative editing, modern content management tools, and a stronger foundation for developers building the next generation of WordPress-powered experiences.
Whether you manage a personal blog, a content-heavy media site, or a large WooCommerce store, understanding what is arriving in WordPress 7.0, and how to prepare for it, will help you make the most of the update while avoiding disruptions.
Every major WordPress version follows a structured, publicly documented development cycle. This transparent process gives developers, theme authors, and hosting environments ample time to test for compatibility before the update reaches millions of live websites.
Work on WordPress 7.0 began during the alpha phase in November 2025. During this stage, core contributors focused on integrating the features and architectural changes outlined in the Gutenberg Phase 3 roadmap, which prioritizes collaborative editing, improved editorial workflows, and a more modern block-based development experience.
Once the major features were sufficiently stable, the update moved into public beta testing, allowing developers worldwide to check compatibility with their plugins, themes, and custom code.
February 19, 2026
Beta 1 — Public testing begins
Core features finalized; wider community testing starts.
February 26, 2026
Beta 2
Bug fixes and refinements based on Beta 1 feedback.
March 5, 2026
Beta 3
Stability improvements across the block editor and admin.
March 12, 2026
Beta 4
Final beta iteration; only critical bug fixes accepted.
March 19, 2026
Release Candidate 1 (RC1)
Feature-complete; critical-only patch window opens.
March 26, 2026
Release Candidate 2 (RC2)
April 2, 2026
Release Candidate 3 (RC3)
Final review before general availability.
April 9, 2026
Official Release
Available through the WordPress dashboard for all sites.
WordPress 7.0 ships with a focused set of improvements spanning the editing experience, content management, media handling, design tooling, and developer infrastructure. Here is a detailed look at each major feature.
Multiple authors edit the same content simultaneously with live cursor tracking.
A modern, filter-rich content management panel for large-volume sites.
Editorial comments and feedback directly inside the block editor.
Show or hide specific blocks by device type without custom CSS.
Breadcrumbs, video backgrounds, icons, and expanded layout controls.
Images optimized in the browser before upload for faster performance.
One of the most significant goals of the Gutenberg Phase 3 roadmap has always been enabling true real-time collaborative editing, the ability for two or more authors to work on the same post or page at the same time, directly inside the block editor.
WordPress 7.0 takes a meaningful step toward that goal. Instead of requiring complex WebSocket server infrastructure, the synchronization layer in this release uses HTTP polling. This design decision is intentional: it allows real-time cursor tracking and co-editing to function on standard shared hosting environments without any specialized server configuration, making the feature accessible to the vast majority of WordPress sites from day one.
Key benefits for teams include:
Managing hundreds or thousands of posts, pages, and custom post types through the traditional WordPress list view has always had limitations. WordPress 7.0 addresses this with DataViews, a redesigned content management interface built for efficiency at scale.
DataViews replaces the basic list with a flexible, filterable panel that gives editors more control over how they browse and manage their content library. Key improvements include:
Note: DataViews enhances the content management experience inside the WordPress admin, it does not replace the entire dashboard or remove any existing functionality.
Collaboration does not stop at simultaneous editing. Effective publishing workflows also require clear communication between writers, editors, and reviewers. WordPress 7.0 improves this aspect of the editorial process by introducing contextual commenting and inline notes directly inside the block editor.
Rather than relying on external tools or email threads to communicate feedback, team members can now leave notes tied to specific blocks or sections of content. This keeps editorial conversations organized, traceable, and visible to everyone involved in the workflow.
The practical benefits include:
Design flexibility has long been a challenge in the block editor. Previously, showing or hiding blocks based on the visitor’s device type typically required custom CSS or a third-party plugin. WordPress 7.0 brings this capability natively into the block controls, giving designers and site owners a simpler way to tailor layouts for different screen sizes.
With the new responsive visibility controls, you can:
WordPress continues expanding its built-in block library with each release. WordPress 7.0 adds a new collection of design-focused blocks and UI enhancements:
These additions reduce reliance on third-party page builder plugins for sites that need polished, professional designs built entirely within the native editor.
Image uploads have traditionally been processed on the server after the file is transferred. In WordPress 7.0, this process shifts partially to the client side: images are optimized directly in the browser before they are sent to the server.
This change delivers meaningful performance gains across the board:
Sites that publish large volumes of images, photography portfolios, news publishers, e-commerce catalogs, stand to benefit the most from this improvement.
Artificial intelligence is becoming an increasingly important part of content creation and web development workflows. Rather than leaving AI integration entirely to third-party plugins, WordPress 7.0 introduces two new core components that provide a standardized foundation for AI-powered features.
The WP AI Client is a core library that establishes a consistent communication layer between WordPress and Large Language Models (LLMs) such as OpenAI, Google Gemini, Anthropic Claude, and others.
The Abilities API provides a defined “handshake” protocol so that plugins and themes can interact with these AI models in a predictable, well-documented way, rather than each plugin rolling its own integration from scratch.
What this enables in practice:
Important: The AI features in WordPress 7.0 remain largely plugin-driven and require connecting to an external LLM provider. The WP AI Client and Abilities API provide the infrastructure, not a bundled AI model.
Beyond the user-facing features, WordPress 7.0 includes a significant set of improvements aimed squarely at developers. These updates modernize the development experience and give plugin and theme authors more powerful tools to work with.
The Block API receives meaningful updates in this release, making it easier to create and maintain custom blocks:
The WordPress REST API powers a wide range of headless, decoupled, and JavaScript-driven WordPress applications. Version 7.0 brings targeted performance improvements to the REST API, reducing response latency and improving throughput for high-traffic use cases.
The core editing framework, the engine that powers the block editor, receives architectural improvements in this release:
WordPress 7.0 continues aligning the core platform with modern JavaScript development conventions. This includes better compatibility with current build toolchains, improved TypeScript tooling support, and expanded documentation for the @wordpress/scripts package used widely in block development.
Heads up for developers: The shift toward an iframe-based editor architecture in 7.0 (with full enforcement in 7.1) may break plugins or themes that inject CSS or JavaScript directly into the editor context using legacy methods. Test your code thoroughly.
Each major WordPress release removes or deprecates outdated technologies that have reached end-of-life status. This is a healthy and necessary part of keeping the platform secure, performant, and maintainable. WordPress 7.0 follows this pattern with one particularly impactful change.
PHP 7.2 and PHP 7.3 have both been officially end-of-life for some time, meaning they no longer receive security patches from the PHP development team. Running WordPress on an unsupported PHP version exposes your site to unpatched vulnerabilities.
WordPress 7.0 formally removes support for these versions. Here is a clear breakdown of what this means for your hosting environment:
PHP 7.2 / 7.3 – No Longer Supported
PHP 7.4 – Minimum Required
PHP 8.3 / 8.5 – Strongly Recommended
WordPress 7.0 is also the first release to introduce Beta Support for PHP 8.5, which was released in early 2026. The core team strongly recommends PHP 8.5 for sites looking to maximize the speed benefits of the new DataViews admin interface and other performance-focused features.
Action required: Log in to your hosting control panel and verify which PHP version your server is running. If you are still on PHP 7.2 or 7.3, upgrade to PHP 8.1 or higher before installing WordPress 7.0. Many hosting providers allow you to switch PHP versions in one click.
The table below provides a concise comparison of key areas where WordPress 7.0 improves upon the 6.x series.
| Feature Area | WordPress 6.x | WordPress 7.0 |
|---|---|---|
| Editing Experience | Block editor with basic real-time hints | Full real-time multi-user co-editing NEW |
| Collaboration Tools | Limited to basic revision history | Inline editorial notes and contextual feedback NEW |
| Content Management | Traditional admin list views | DataViews: filterable, customizable content panels NEW |
| Responsive Design | Custom CSS or plugins required | Native block visibility controls per device NEW |
| Media Uploads | Server-side image processing | Client-side optimization before upload NEW |
| Creative Blocks | Core block library with basic controls | Breadcrumbs, video backgrounds, new icons NEW |
| AI Integration | Plugin-only, no core infrastructure | WP AI Client + Abilities API in core NEW |
| PHP Support | PHP 7.2+ supported | PHP 7.4 minimum; PHP 8.5 recommended CHANGED |
| Editor Architecture | Mixed legacy and block-based | Progressing to iframe-based architecture CHANGED |
| Developer Tools | Existing Block API and REST API | Improved Block API, REST API performance, JS tooling NEW |
Major WordPress releases can shift how plugins and themes interact with the core platform. WordPress 7.0 is no exception, with changes to the block editor architecture, PHP compatibility requirements, and the new AI infrastructure, developers should expect to review their products before the update lands.
If your plugin interacts with the block editor, especially if it injects styles or scripts into the editor environment, the progression toward an iframe-based architecture may affect how your code behaves. Specifically:
enqueue_block_editor_assets may no longer have access to the outer document when iframe enforcement arrives in WordPress 7.1.Theme compatibility in 7.0 centers primarily on three areas:
functions.php and any custom theme code for deprecated PHP patterns that no longer work in PHP 8.x.Best practice: Do not wait for the official release to test. Clone your production site to a staging environment, install the WordPress 7.0 Beta Tester plugin, and run a full compatibility check now. This gives you weeks to resolve any issues before your live site is at risk.
Upgrading to a major WordPress version is a straightforward process for most well-maintained websites. Taking a few deliberate preparation steps beforehand reduces the risk of unexpected issues and ensures your visitors experience zero disruption.
Once the official release is available on April 9, 2026, you can update directly from your WordPress dashboard. The process is simple:
Alternative installation: You can also download the WordPress 7.0 package manually from wordpress.org/download and install it via FTP or your hosting file manager, which is useful if your automatic update process is disabled.
WordPress 7.0 is not simply a maintenance release, it is a meaningful step forward in the platform’s long-term vision as a collaborative, modern, and extensible publishing system. The combination of real-time co-editing, DataViews, client-side media processing, and a new AI infrastructure makes this one of the more substantive releases in the 6.x-to-7.x transition.
For website owners, the most important immediate action is to verify your PHP version and make sure your plugins and themes are up to date before the April 9 release date. A few hours of preparation on a staging site today can prevent hours of troubleshooting after a live upgrade.
For developers, the progression toward an iframe-based editor architecture and the new Block API improvements signal where WordPress is heading. Getting ahead of these changes now, rather than reacting after the release, will put you in a stronger position as the platform continues to evolve through 7.1 and beyond.
Keep an eye on the official Make WordPress Core blog for the latest development updates, RC announcements, and any changes to the release schedule.

Hassan Tahir wrote this article, drawing on his experience to clarify WordPress concepts and enhance developer understanding. Through his work, he aims to help both beginners and professionals refine their skills and tackle WordPress projects with greater confidence.