WordPress 7.0 Preparation Guide: What Site Administrators Need to Know
Prepare for WordPress 7.0 with this actionable 90-day timeline. Covers PHP requirements, plugin audits, staging setup, and backup verification for site administrators.
WordPress 7.0 is targeting an April 9, 2026 release, coinciding with WordCamp Asia. For site administrators managing production environments, now is the time to start preparing, not waiting until release day.
With Beta 1 arriving on February 19, 2026, you have roughly three months to assess your current setup, audit your plugins and themes, and establish a testing environment. This guide provides a practical preparation checklist and timeline so you can approach this major version upgrade with confidence rather than concern.
By the end of this article, you will have a clear action plan covering server requirements, plugin compatibility, staging setup, and backup verification.
Release Timeline
WordPress 7.0 follows a predictable release cycle. Here are the key dates for your planning:
| Milestone | Date | What It Means for You |
|---|---|---|
| WordPress 6.9 Released | December 2, 2025 | Current stable version; upgrade now if you have not already |
| WordPress 7.0 Beta 1 | February 19, 2026 | First public testing opportunity |
| WordPress 7.0 RC1 | March 19, 2026 | Feature freeze; final testing phase |
| WordPress 7.0 Final | April 9, 2026 | Production-ready release |
These dates matter because they define your preparation windows. Beta 1 is your first chance to test compatibility in a staging environment, while RC1 signals that features are locked and you can begin final validation.
Note that 2026 marks WordPress’s return to a three-release cadence, meaning more frequent updates throughout the year.
What Is Changing in WordPress 7.0
Several changes in WordPress 7.0 will affect site administrators, even those who do not write custom code.
Block Editor Enhancements
The post editor will fully run inside an iframe in WordPress 7.0. For administrators, this means any custom blocks or plugins using older Block API versions may need updates. Block developers are strongly encouraged to migrate to Block API v3 for full compatibility.
Potential PHP Version Requirements
As of December 2025, WordPress 6.9 requires PHP 7.2.24 or higher, with PHP 8.3 recommended. WordPress 7.0 is expected to bump the minimum to PHP 7.4, though this decision is still under discussion. Regardless of the official minimum, running PHP 8.2 or higher is advisable for performance and security.
New Blocks
WordPress 7.0 introduces new native blocks including Tabs and Breadcrumbs, expanding layout options without requiring third-party plugins.
Real-Time Collaboration
Phase 3 of the Gutenberg project brings real-time collaborative editing features. While still in development, this represents a significant shift in how teams may work within WordPress.
Preparation Checklist
Server Requirements
Start by checking your current PHP version. You can find this in your hosting control panel or by navigating to Tools > Site Health > Info > Server in your WordPress dashboard.
If you are running PHP 7.2 or 7.3, plan to upgrade to PHP 8.2 or higher before April 2026. Contact your hosting provider to confirm upgrade availability and any associated costs. Some shared hosting plans may require a plan change to access newer PHP versions.
Additionally, verify your MySQL version is at least 5.5.5. This requirement is not expected to change for WordPress 7.0, but confirming your database version is good practice before any major upgrade.
Plugin and Theme Audit
Review every active plugin and theme for maintenance status:
- Check the “Last Updated” date in the WordPress plugin repository. Plugins not updated within the past year may be abandoned.
- Look for compatibility notes from developers regarding WordPress 7.0 or Block API v3.
- Identify plugins that modify the block editor, as these are most likely to require updates.
- Note any premium plugins and check their support documentation for WordPress 7.0 roadmaps.
Create a list of potentially problematic plugins now. This gives you time to find alternatives or contact developers before the release.
Staging Environment
If you do not have a staging environment, set one up before February 2026. Your staging site should mirror your production environment as closely as possible, including the same PHP version, plugins, themes, and content.
Many hosting providers offer one-click staging. Alternatively, you can use a local development tool or a separate subdomain.
Your staging environment is where you will install WordPress 7.0 Beta 1 on February 19 to test compatibility before the changes affect your live site.
Backup Strategy
Before any major version upgrade, confirm your backup solution is working correctly:
- Verify that full-site backups (files and database) are running on schedule.
- Test your restore process. A backup you cannot restore is not a backup.
- Ensure you have off-site backup copies, not just backups stored on the same server.
Always backup your site before major version upgrades. This is your safety net if something goes wrong during the update process.
90-Day Preparation Timeline
January 2026: Assessment Phase
- Upgrade to WordPress 6.9 if you have not already done so.
- Check your current PHP version and plan upgrades if below 8.2.
- Begin plugin and theme audit; document any unmaintained items.
- Set up or verify your staging environment.
- Confirm backup procedures and test a restore.
February 2026: Beta Testing Phase
- Install WordPress 7.0 Beta 1 on your staging site on February 19.
- Test core site functionality: forms, e-commerce, membership features.
- Document any issues and report them to plugin developers or WordPress Trac.
- Monitor plugin update announcements for compatibility releases.
- Do not install beta versions on production sites.
March-April 2026: Final Preparation Phase
- Install RC1 on staging on March 19 for final testing.
- Apply any plugin updates released for WordPress 7.0 compatibility.
- Schedule your production update window for after April 9.
- Plan for post-update verification: test critical workflows immediately after upgrading.
Consider waiting one to two weeks after the final release to allow plugin developers to address any last-minute issues. Sites with custom functionality or many plugins may benefit from a cautious approach.
Conclusion
WordPress 7.0 represents a significant update with Block API changes, potential PHP requirements, and new collaborative features. By starting your preparation now, you can test thoroughly during the beta period and upgrade with confidence.
Focus on three priorities: verify your PHP version meets current recommendations, audit your plugins for compatibility concerns, and ensure your backup strategy is tested and reliable.