WordPress 7.0 was supposed to ship on April 9, 2026. It didn’t. On April 22, the WordPress release squad (the contributor team responsible for shepherding each major version through to General Availability) announced a new date: May 20, 2026.
The reason given by release lead Amy Kamala on the Make WordPress Core blog was straightforward. The team needed more time for “necessary architectural improvements” to deliver a release that’s “the most stable and most performant it can be” while still keeping the cornerstone features the community had been promised.
Here’s what that means for your site, what’s still in 7.0, and what to do between now and the new release date.
The new release schedule
The release squad published a revised timeline on April 22. The full sequence to General Availability is:
- RC3 (testing as a “new Beta 1”) on May 8, 2026
- RC4 (testing as a “new RC1”) on May 14, 2026
- Dry run and 24-hour code freeze on May 19, 2026
- General Release on May 20, 2026
The unusual labelling matters. Even though RC3 (the third Release Candidate, normally a near-final build) carries the “release candidate” name, the squad is treating it as a beta in practice. That signals real changes still landing in the codebase, not just bug polish. RC4 is where the release returns to true RC behaviour.
For site owners and agency operators, the practical takeaway is: do not put 7.0 anywhere near production until May 20, and test compatibility on staging during the RC3 and RC4 windows.
Why was WordPress 7.0 delayed?
The official wording is “necessary architectural improvements”. The release squad has not published a detailed list of what changed under the hood, but the timing tells a story.
RC2 shipped on March 26, 2026 with an April 9 GA target. That’s a normal two-week gap. Then nothing public until the April 22 announcement of a six-week slip. Six weeks is significant. It suggests the team found problems during the host testing window that couldn’t be patched at the surface level and required deeper rework.
The good news in that decision: the squad chose stability over schedule. A version that ships on time but breaks plugin ecosystems or hosting compatibility creates years of cleanup. A version that ships six weeks late with the architecture done properly is the cheaper outcome for everyone running WordPress in production.
What’s still in WordPress 7.0
The cornerstone features the team committed to in February have not been pulled. They’re still landing in the May 20 release.
Real-time collaboration
Multiple users editing the same post or page simultaneously, with live cursors showing who’s working where. When one person finishes editing a block, changes sync to everyone else. The Notes feature introduced in 6.9 expands into inline block-level comments with threading and resolution.
What this means for you: editorial teams, marketing managers, and agencies reviewing client content can work inside WordPress instead of round-tripping through Google Docs and Slack. Fewer tools, fewer version conflicts, faster publishing.
AI infrastructure (Abilities API and AI Client)
WordPress 7.0 doesn’t ship an AI writing tool. It ships the plumbing. A standardised interface lets plugins and themes connect to any AI provider (OpenAI, Anthropic, Google, self-hosted models) through one API. A new Connectors page in the admin (Settings then Connectors) gives site owners a central place to manage AI connections. A separate AI Experiments screen lets you opt into specific capabilities like alt text generation or content summarisation.
What this means for you: this is the foundation. Over the next twelve months, plugin developers will build on this API to deliver AI features that work consistently across the WordPress ecosystem instead of every plugin reinventing its own integration.
Admin interface refresh
The wp-admin dashboard gets a visual overhaul. Traditional list tables are being replaced by DataViews, a more modern app-like interface for managing posts, pages, and media. View transitions between admin screens make the whole experience feel faster.
Pattern Overrides for custom blocks
Pattern Overrides, introduced in 6.6, expand to support custom blocks in 7.0. Agency teams building reusable layouts for clients can now lock structural patterns while letting clients override specific content fields, without the lockdown breaking when custom blocks are involved.
PHP 7.4 minimum requirement
WordPress 7.0 raises the minimum PHP version to 7.4. Sites still running PHP 7.2 or 7.3 will not receive the update and will stay on 6.9. The core team recommends PHP 8.2 or 8.3 for best performance and security.
Smaller improvements worth knowing
New Icon and Breadcrumbs blocks in core. Lightbox support in the Gallery block. The Grid block becomes responsive. Cover blocks can use video embed backgrounds. Viewport-based block visibility lets you show or hide blocks based on screen size without custom CSS. The editor canvas moves toward full iframing, which creates a sandboxed environment where what you see in the editor matches what visitors see on the front end.
For developers and theme authors, block-aware revision comparison is the upgrade to watch. You can now compare page versions at the block level rather than wading through raw HTML diffs.
What HostLogic is doing between now and May 20
We’ve been testing 7.0 betas on staging since Beta 1 dropped in February. The delay gives us a longer compatibility window, not a shorter one, which is good for clients.
We’re not a reseller. We leverage WP Cloud for the best optimised stack for WordPress sites. That means when 7.0 lands, the underlying infrastructure has already been tuned for it at the platform level, not patched in afterwards.
Here’s what’s running on our side:
- PHP 8.2 or higher across all client sites on the platform. No action needed from you.
- Plugin and theme regression tests against RC3 and RC4 as they ship. If a plugin breaks, we flag it and discuss alternatives before May 20.
- Phased rollout after GA. We don’t apply major core updates on day one. Low-risk sites first, monitor, then scale across the portfolio once we’re confident.
- Pre-update backups on every site. If something unexpected happens, we roll back immediately.
The short version for HostLogic clients: you don’t need to do anything. When 7.0 is ready for your site, we’ll handle the update. If something needs your input, we’ll tell you before we touch anything.
What to do if you self-host
If you manage your own WordPress site, here’s the practical checklist for the next two weeks:
- Confirm your PHP version. Run phpinfo() or check your hosting control panel. If you’re below 7.4, upgrade now. If you’re below 8.2, upgrade soon.
- Check plugin compatibility on staging during the RC4 window (May 14-19). The “Tested up to” version in plugin readmes should read 7.0 by RC4. If your critical plugins haven’t been updated, contact the plugin author or look for alternatives.
- Take a full backup before May 20. Database and files. Test the restore.
- Wait at least a week after GA before updating production. Let the early issues surface in other people’s sites first.
What’s next after WordPress 7.0?
The release squad has not yet published a revised schedule for 7.1 and 7.2. Before the delay, 7.1 was tentatively planned for August and 7.2 for December, returning WordPress to three major releases per year. That cadence is likely to slip with 7.0 landing six weeks later than planned.
For agency operators and businesses running WordPress at scale, the practical implication is clear: 2026 is going to involve more compatibility testing than 2025 did. Having a team that handles this proactively, instead of reacting to broken sites after a botched update, is the difference between WordPress as an asset and WordPress as a liability.
If you have questions about how 7.0 affects your specific stack, get in touch.
Related reading
- WordPress Care Plan: What It Is and Why You Need One
- Master Guide to WordPress Management
- View HostLogic Plans
Frequently Asked Questions About WordPress 7.0
When is WordPress 7.0 being released?
WordPress 7.0 is now scheduled for May 20, 2026. The original April 9, 2026 release date was missed, and the release squad announced the new May 20 date on April 22, 2026.
Why was WordPress 7.0 delayed?
The release squad cited “necessary architectural improvements” needed to ensure stability and performance. The team chose to push the date back six weeks rather than ship a release with unresolved compatibility issues that would affect plugins, themes, and hosting platforms.
Will WordPress 7.0 break my website?
Most well-maintained sites will handle the update without issues. If you’re running outdated themes or plugins that haven’t been updated for 7.0 compatibility, there could be conflicts. The safest approach is to test on staging before applying to production. HostLogic tests all major updates in staging before deploying to client sites.
Do I need to update to WordPress 7.0 immediately?
You don’t need to update on day one. It’s generally sensible to wait a week or two for any initial bugs to be patched. Don’t wait too long either, because outdated WordPress versions create security vulnerabilities. If you’re on a HostLogic Care plan, we handle the timing and testing for you.
What are the main changes in WordPress 7.0?
Real-time collaboration in the block editor, an Abilities API for AI integration, a refreshed admin interface using DataViews, expanded Pattern Overrides for custom blocks, and a new minimum PHP requirement of 7.4. The focus is on collaboration, AI infrastructure, and architectural improvements.
Should I update my plugins before or after WordPress 7.0?
Update your plugins first. Make sure all plugins are on their latest versions before updating core. Plugin developers typically release compatibility updates ahead of major WordPress releases. Check that your critical plugins confirm 7.0 compatibility before proceeding.
How does HostLogic handle WordPress 7.0 updates?
HostLogic manages 7.0 updates for all Care plan clients. We test on staging, verify plugin compatibility, check for visual regressions, and only deploy to production once everything is confirmed working. Premium plan clients get same-day updates with staging testing. Starter plan clients receive the update within the first scheduled maintenance cycle after release.