WordPress 7.0 is the first major WordPress release of 2026 and it’s a big one. The official schedule currently targets release on 9 April 2026.
If you run a business site, an e-commerce store, or manage client sites, this post will help you:
- Understand what’s changing,
- Spot the biggest risks (there’s a key PHP requirement change),
- Update safely without surprises.
Quick WordPress 7.0 Coming April 2026
When is WordPress 7.0 due? Scheduled for 9 April 2026.
What’s the biggest “gotcha”? WordPress 7.0 raises the minimum PHP version to 7.4, so sites on PHP 7.2/7.3 won’t get 7.0 until PHP is upgraded. Find out more here.
What should you do now? Make a staging copy, test your theme/plugins, and plan PHP upgrades early.
WordPress 7.0 Release Timeline
Here are the key milestone dates from the official 7.0 schedule:
- Beta 1: 19 Feb 2026
- Beta 2: 26 Feb 2026
- Beta 3: 5 Mar 2026
- Beta 4: 12 Mar 2026
- Release Candidate 1: 19 Mar 2026
- Release Candidate 2: 26 Mar 2026
- Release Candidate 3: 2 Apr 2026
- Code freeze / dry run: 8 Apr 2026
- Target release: 9 Apr 2026
(Like all software releases, dates can move – the schedule page is the source of truth.)
What’s New In WordPress 7.0
Based on the official “Help Test WordPress 7.0” guidance, these are some of the headline areas landing in 7.0:
1. Real-Time Collaboration In The Editor
WordPress 7.0 introduces a first iteration of real-time collaboration (RTC) in core. It’s focused on editing content in the block editor and site editor.
Key practical notes:
- It doesn’t apply across all wp-admin screens – it’s editor-focused.
- Many plugins still rely on “classic” meta boxes that don’t sync in real time, so collaborative editing may feel inconsistent depending on your plugin stack.
2. A Visual Refresh Of WP-Admin
WordPress 7.0 includes admin UI polish aimed at modernising wp-admin styling and consistency (without major functional changes). This is exactly the kind of change that can surface plugin UI quirks, contrast issues, spacing problems, etc.
3. Visual Revisions Inside The Editor
Revisions become more visual inside the editor, with clearer highlights of what changed and a new “Revisions” view (instead of kicking you to a separate screen).
4. Font Library Support Expands Beyond Block Themes
The Font Library is expanding to better support classic themes, not just block themes.
5. Responsive Editing Mode
A responsive editing mode adds more control to preview and tailor content for device sizes, including the ability to hide blocks per screen type (desktop/tablet/mobile).
6. New Blocks + Block Updates
WordPress 7.0 adds Icon, Breadcrumbs, and Tabs blocks, and also ships updates like:
- Gallery: lightbox switching
- Cover: external video support
- Grid: new controls
7. Client-Side Media Processing
WordPress 7.0 introduces client-side media processing in the browser for tasks like image resizing/compression, reducing server demand and improving media workflows.
The Biggest Breaking-Change Risk
This is the one you should check today.
WordPress 7.0 raises the minimum supported PHP version to 7.4. Sites still on PHP 7.2 or 7.3 won’t receive WordPress 7.0 and will remain on the 6.9 branch until PHP is upgraded.
WordPress core continues to recommend newer PHP versions (the dev note calls out PHP 8.3 as the recommended minimum).
How To Prepare
1. Check Your PHP Version First
- If you’re on 7.2 / 7.3 → plan a PHP upgrade with your host before you think about WordPress 7.0.
- If you’re on 7.4+ → you can move to testing normally (still: staging first).
2. Clone To Staging
The official testing guidance is clear: use a staging site and keep your live site safe.
3. Update Your Plugin + Theme Stack On Staging
Before testing 7.0, make sure your staging site is fully updated on:
- Theme
- Plugins (especially page builders, WooCommerce, security, caching)
- Custom functionality / MU plugins
4. Test Your Critical Journeys
On staging with a 7.0 beta/RC, test what actually makes money / generates leads:
- Contact forms (and CRM delivery)
- Checkout, payment, order emails
- Login/register/reset password flows
- Any membership portals / client areas
- Site editor / templates (if you use blocks)
5. Decide your update strategy
For brochure sites with simple plugins: updating closer to release day can be fine.
For WooCommerce / membership / high-traffic sites: plan for a staged rollout (and often waiting for early point releases can reduce drama).
Want Us To Handle The WordPress 7.0 Update Safely?
If you’d like us to:
- check PHP readiness,
- clone to staging,
- test your exact plugin stack,
- fix compatibility issues,
- and push to live with minimal downtime,
Get in touch and we’ll run it as a managed update.
