WordPress 7.0 Beta 1 is now available for testing. We have been spending time trying it out, and we believe this is one of the most meaningful updates in recent years. The official release is scheduled for April 9, 2026, and it will bring features that genuinely change how you create and manage content on your site.
This update, the subject of our full WordPress 7.0 preparation guide, marks the official start of Phase 3 of the Gutenberg project. It carries more breaking changes than anything WordPress has shipped in recent memory. Real-time collaboration arrives in the block editor, the admin dashboard gets a complete React-powered rebuild, and the platform drops official support for PHP 7.2 and 7.3 entirely.
Read on to learn what is coming in WordPress 7.0, why this update carries a higher risk than usual, and what steps you need to take right now to protect your site before April 9.
⚠️ Critical Warning: If your server runs PHP 7.2 or 7.3, updating to WordPress 7.0 will cause an immediate fatal error. Check your PHP version today before April 9 arrives.
📚 New to WordPress? Before diving into the 7.0 update, make sure you have the basics covered. Our WordPress Basics & Installation guide walks you through everything you need to get started:
- What is WordPress? A Beginner’s Guide
- WordPress.com vs WordPress.org: Which One to Choose?
- WordPress System Requirements Explained
- How to Choose the Best WordPress Hosting
- Registering Your First Domain Name for WordPress
TL;DR: What You Need to Know
- WordPress 7.0 launches April 9, 2026, and it is the biggest update in years.
- Sites running PHP 7.2 or 7.3 will crash immediately after updating.
- The entire admin dashboard is rebuilt in React, breaking many legacy plugins.
- Real-time collaboration and a new AI infrastructure are the headline features.
- Five clear steps will protect your site before launch day arrives.
Why WordPress 7.0 Carries a Higher Risk Than Usual
Most WordPress updates ship smoothly for the vast majority of sites. You click update, wait thirty seconds, and carry on with your day. WordPress 7.0 is genuinely different, and understanding why matters before you can protect yourself.
The 2025 development roadmap was heavily disrupted by the WP Engine lawsuit and a pause in contributions from Automattic. That disruption means WordPress 7.0 now carries the weight of more than a year of accumulated features and architectural changes, all arriving at once. Two things in particular raise the risk level significantly.
First, the PHP requirement jumps. WordPress 7.0 officially drops support for PHP 7.2 and 7.3. Millions of sites still run those versions today. If yours is one of them, the update will produce a fatal error the moment it completes.
Second, the entire admin interface is rebuilt. The old WP List Tables, the familiar PHP-generated screens you have used for years to manage posts, pages, and users, are replaced by a modern React-based component called DataViews. Any plugin that hooks into the old admin screens to add custom columns, action buttons, or status labels is highly likely to break or disappear entirely.
ℹ️ Note: Real-time collaboration is under active development and was not included in Beta 1. It may still make the final 7.0 release, but treat it as a potential bonus feature rather than a guarantee.
5 Steps Every Site Owner Must Take Before April 9
We put together this checklist after testing Beta 1 on several staging environments. Follow these steps in order, and you will be in a far stronger position when launch day arrives.
Step 1: Check Your PHP Version Right Now
Go to Tools, then Site Health, inside your WordPress dashboard. Look for the PHP version entry. You need PHP 7.4 at minimum, and PHP 8.3 is the recommended choice for best performance and security. Contact your host to upgrade if you run below 7.4.
Step 2: Set Up a Staging Environment
Never test a major update on your live site. Most managed hosts offer one-click staging. Clone your site, run the WordPress Beta Tester plugin there first, and observe what breaks. Fix those issues on staging before they ever touch production.
Step 3: Audit Your Plugin Stack for DataViews Conflicts
Open your plugin list and identify anything that modifies admin screens, adds custom list table columns, or hooks into legacy PHP admin tables. Check each plugin’s changelog for WordPress 7.0 compatibility notes. Replace or abandon anything with no update since 2023.
Step 4: Take a Full Off-Site Backup
A database export alone is not enough. You need a full backup covering all files and your database, stored somewhere completely separate from your hosting account. Duplicator Pro, UpdraftPlus, or your host’s own backup tool all work well for this purpose.
Step 5: Wait for Version 7.0.1 on Critical Sites
If your site runs an active shop, membership area, or high-traffic publication, wait one week after the April 9 launch. Let the broader community surface edge cases first. Version 7.0.1 will follow quickly and resolve the most common issues.
💡 Pro Tip: Install the WordPress Beta Tester plugin on your staging site today. Testing Beta 1 yourself gives you weeks of advance warning about plugin conflicts, long before your live site faces any risk.
What the New Features Actually Mean for Your Site
Once you have secured your site, the genuinely exciting part begins. WordPress 7.0 brings improvements that will change how you build and manage content day to day.
The Admin Visual Refresh Feels Like a New App
In our testing, we found the difference in the new dashboard immediately noticeable. Screens no longer do a full hard reload as you navigate between sections. Elements transition smoothly into place, the typography is cleaner, and the layout breathes more than the old design ever did. Managing a site feels faster, even before examining the performance numbers.
AI Infrastructure Arrives, Not AI Tools
We want to be clear about this point, because a lot of headlines misrepresent it. WordPress 7.0 does not ship a built-in AI content writer. It ships the plumbing that makes AI features possible. The new AI Web Client API lets you store your own API keys, whether for OpenAI, Anthropic, or another provider, in one central place. Your plugins and themes then draw on those credentials instead of each requiring their own separate configuration. The real value comes as developers build on top of this foundation over the coming months.
New Blocks: Breadcrumbs and Icons
Two blocks many people have wanted for years now ship as core features. The Breadcrumbs block improves navigation hierarchy and supports your theme’s global styles automatically. The Icons block lets you drop SVG icons anywhere in your content without touching a line of code. Both previously required separate plugins, and both integrate cleanly with the existing block editor.
How WordPress 7.0 Compares to What Competitors Already Cover
We reviewed what other major WordPress resources are publishing on this update. Most cover either the developer-facing API details or a surface-level feature list. This table shows exactly where the gaps are and what you will only find in genuinely operational guides like this one.
| Resource | What They Cover Well | What They Miss |
|---|---|---|
| InstaWP | Abilities API technical architecture, React DataViews component details | No step-by-step prep checklist for non-technical site owners |
| WPBeginner | Visual walkthroughs of new blocks, admin refresh screenshots | Understates the PHP version risk and plugin compatibility danger |
| ThemeRex | Release timeline overview, WP Engine lawsuit context | Generic advice with no staging workflow detail |
| Briteweb | Accurately flags breaking changes and PHP upgrade necessity | Too brief, enterprise focus only |
| Cloudways / Pantheon | Hosting infrastructure requirements, WebSocket needs | Content skewed toward selling their hosting |
April 9 Will Arrive Faster Than You Think
We are genuinely excited about WordPress 7.0. Real-time collaboration in the editor, a dashboard that finally feels like a modern web app, and a standardized foundation for AI features, these changes add up to something meaningful. The platform feels like it is catching up with how professional teams actually work.
Our honest recommendation is simple. Check your PHP version today. Set up that staging environment this week. Audit your plugins before March ends. Take a proper off-site backup. Then sit back and enjoy one of the most significant WordPress updates in years, instead of spending April 9 hunting through server error logs.
You can read our full WordPress 7.0 Is Coming: What Site Owners Actually Need to Do guide for even deeper coverage of every feature, every risk, and every fix you might need on launch day.
Frequently Asked Questions
What is the minimum PHP version for WordPress 7.0?
PHP 7.4 is the absolute minimum. WordPress officially drops support for PHP 7.2 and 7.3 with this release. Running either of those older versions when you update will cause an immediate fatal error. PHP 8.3 is the recommended version for best performance and long-term security.
Will WordPress 7.0 break my plugins?
It depends on your plugins. Any plugin that modifies the WordPress admin list tables, adds custom columns to the posts or pages screen, or hooks into legacy PHP admin UI elements faces a high risk of breaking. Well-maintained plugins from active developers will release compatibility updates before April 9. Abandoned plugins likely will not.
Does WordPress 7.0 include a built-in AI writer?
No, and this is an important distinction. WordPress 7.0 ships the AI infrastructure, specifically the AI Web Client API and the Abilities API, that allows plugins and themes to integrate AI features in a standardized way. The platform does not ship a native content generator. Third-party plugins will build on this foundation over the months following the release.
Is real-time collaboration confirmed for WordPress 7.0?
Not yet confirmed. Real-time collaboration was not included in Beta 1, which launched February 19, 2026. The feature is under active development, and the core team has not confirmed whether it will make the final April 9 release. Treat it as a potential bonus rather than a guaranteed feature.
Should I update to WordPress 7.0 on launch day?
For personal blogs and low-traffic sites, updating a few days after launch is reasonable if you have tested on staging first. For business sites, membership platforms, or active eCommerce stores, waiting for version 7.0.1 is the smarter choice. That minor release typically follows within a week and resolves the most common issues surfaced by the broader community.
How do I test WordPress 7.0 without risking my live site?
Install the WordPress Beta Tester plugin on a staging copy of your site. Most managed WordPress hosts offer one-click staging environments. Alternatively, you can use a local development tool like LocalWP to spin up a test environment on your own computer at no cost.
Additional Resources
- WordPress 7.0 Is Coming: What Site Owners Actually Need to Do (Full Pillar Guide)
- What’s Coming in WordPress 7.0? Features and Screenshots
- How to Create a Staging Environment for WordPress
- WordPress Beta Tester Plugin
- Small Business Owner’s Guide to Artificial Intelligence
- Official: Dropping Support for PHP 7.2 and 7.3
