Last updated: May 2026 · By the Wpbloghost editorial team · 10+ years building blogs on WordPress.
WordPress 7.0 officially launched today, May 20, 2026, after a six-week delay from its original April release date. Codenamed “Armstrong,” it is the biggest core update since the Block Editor arrived in 2018, and bloggers will feel the impact whether they want to or not.
We tested every new feature in the release candidate over the past three weeks on a staging copy of our own blog. This guide covers what shipped, what got cut at the last minute, what bloggers actually need to care about, and which hosts handle the WordPress 7.0 update without breaking a sweat.
If you publish on WordPress, read this before clicking that update button. There are a few gotchas, especially around PHP versions and plugin compatibility.
WordPress 7.0 at a glance
| Release date | May 20, 2026 (delayed from April 9) |
| Codename | Armstrong |
| Headline feature | Native AI integration (Connectors + Abilities API) |
| What got cut | Real-time collaboration (delayed to 7.1 or later) |
| Minimum PHP | 7.4 (8.2 or 8.3 recommended) |
| Should you update now? | Yes, but test in staging first |
WordPress 7.0 release date and why it was delayed
The final version of WordPress 7.0 was originally targeted for April 9, 2026, to coincide with WordCamp Asia in Mumbai. The core team pushed the date back to May 20 after discovering a serious architectural issue.
The real-time collaboration feature was saving sync data through post meta and accidentally disabled sitewide WordPress query caches whenever the block editor was opened. Fixing it required building a new database table, which is why the schedule slipped.
The good news for bloggers: extra weeks of stabilisation mean a cleaner release. The bad news: the headline collaboration feature was eventually pulled from the final WordPress 7.0 build on May 8, and pushed to a future version.
Native AI integration in WordPress 7.0
The defining feature of WordPress 7.0 is native AI infrastructure built directly into core. For the first time, WordPress treats AI as a first-class part of the CMS instead of leaving it to third-party plugins.
Four pieces make this work together: the Connectors API, the Connectors admin screen, the Abilities API, and the MCP Adapter. As bloggers, you mostly interact with the screen. As plugin developers, the APIs are where the real changes happen.
The new Connectors screen
Go to Settings › Connectors in your dashboard and you will find a fresh interface for managing AI providers. It works a bit like a plugin directory but is dedicated to AI services.
You can connect OpenAI, Anthropic Claude, or Google Gemini with an API key, then choose which provider powers each AI feature on your site. Switching providers no longer means uninstalling a plugin and starting over.
What AI features ship out of the box
Open Settings › AI Experiments and you can opt in to four built-in features that come bundled with WordPress 7.0:
- Auto-generated post excerpts
- Image alt text suggestions for accessibility
- Content summarisation for long posts
- AI-assisted image generation
None of these features are turned on by default. The team made the entire AI layer opt-in, which is the right call for bloggers who care about transparency with readers and search engines.
Why the Abilities API matters for bloggers
The Abilities API lets plugins describe what they can do in a standard way that AI agents can read. Search Engine Journal called it the biggest architectural change for WordPress in a decade.
In practice, that means tools like Claude Desktop, Cursor, or other AI assistants can soon take real actions inside your blog: drafting a post, scheduling content, or checking SEO scores via the MCP Adapter. The plumbing is in WordPress 7.0 today; the workflows will follow over the next year.
What happened to real-time collaboration?
Real-time collaboration was the marketed flagship feature of WordPress 7.0 for almost a year. It got pulled twelve days before launch.
The core team made the call on May 8 after concerns about race conditions, server load, and memory efficiency on shared hosting. Co-editing a Google Docs-style post with two cursors is not in this release.
What remains is the Block-level Notes system, which arrived in WordPress 6.9 and gets expanded in 7.0. You can leave comments on individual blocks, tag teammates, and resolve threads, all inside the editor. For a solo blogger or a tiny editorial team, Notes covers 80% of what people actually wanted from collaboration.
True real-time editing is still in active development through the Gutenberg plugin and is expected to land in WordPress 7.1 (targeted for August 19, 2026) or 7.2.
Block Notes, visual revisions, and editing tools
Beyond the AI headlines, WordPress 7.0 ships several quality-of-life improvements that bloggers will notice within minutes of opening the editor.
Visual revisions screen. The new revisions interface gives you a color-coded preview of what changed between two versions of a post. Added text shows green, deleted text shows red. No more squinting at side-by-side text dumps.
Block Notes expansion. Add a note to any block, mention an editor or VA, and resolve the thread when the change is done. Useful if you outsource proofreading.
Pattern editing focus. Editing a reusable pattern now opens a content-first view with fewer distractions. If you reuse a “newsletter sign-up” block across posts, this is a real upgrade.
Navigation overlays. Mobile menus get customisable overlays so you can style the open-menu state separately from the closed one.
Refreshed admin and new blocks in WordPress 7.0
The wp-admin area got its biggest visual refresh in years. The cluttered grey-on-grey look is gone, replaced by more whitespace, cleaner typography, and React-based DataViews instead of static admin tables.
What that means in practice: posts, pages, comments, and media now load in dynamic lists with built-in filtering and sorting. No page reloads when you change a filter. It feels closer to a modern SaaS dashboard than the old WordPress admin.
New blocks shipping in WordPress 7.0 include:
- Icons block – native SVG icon library, no plugin needed
- Breadcrumbs block – finally native, instead of relying on Yoast or RankMath
- Native gallery lightboxes – tap any gallery image to open a lightbox without a plugin
- PHP-only blocks – simple dynamic blocks can now skip the JavaScript layer
For bloggers, the breadcrumbs block alone removes one common plugin from a typical site, which is a small win for site speed.
System requirements for WordPress 7.0
Before you update, check that your host meets the new minimum bar:
- PHP: 7.4 minimum, 8.2 or 8.3 recommended. PHP 7.2 and 7.3 are no longer supported.
- MySQL: 5.7+ or MariaDB 10.4+
- HTTPS: still required for AI features (the Connectors API will not authenticate over HTTP)
- Memory limit: 256 MB or higher recommended for the new editor
Confirm your PHP version under Tools › Site Health. If you are still on 7.3 or older, you cannot install WordPress 7.0 at all – the update will be blocked.
You can verify the full list at the official WordPress requirements page.
Best hosting for WordPress 7.0 (tested)
Not every host handles a major version upgrade smoothly. Some auto-update within hours, others wait weeks, and a few break themes the moment you click “Update Now.” Here are the hosts we tested with WordPress 7.0 during the RC phase.
Best managed pick: WP Engine
WP Engine pushed WordPress 7.0 to its staging environments the day RC1 dropped. The team also published a compatibility report listing the plugins they have already pre-validated. For bloggers running a serious content business, that level of preparation is worth the premium.
Read our WP Engine review for the full breakdown of speed tests and pricing, or jump to:
Best premium pick: Kinsta
Kinsta runs on Google Cloud Platform and updated all its container images to PHP 8.3 well before the WordPress 7.0 release. The Connectors API works flawlessly on Kinsta’s infrastructure because outbound HTTPS to OpenAI, Anthropic, and Gemini is unrestricted by default. See our Kinsta review for our speed tests.
Best budget pick: Hostinger
If you are a new blogger and the $25+ per month managed hosts feel too rich, Hostinger handled WordPress 7.0 smoothly in our tests at $3 per month. PHP 8.3 is the default, and the LiteSpeed cache plays nicely with the new editor. Full breakdown in our Hostinger review.
For a deeper comparison of all three tiers, see our guide to the best managed WordPress hosting.
How to safely update to WordPress 7.0
Even with the extra stabilisation, a major version is not something to update on a Friday afternoon. Follow this order:
- Back up everything. Files and database. Use UpdraftPlus, your host’s built-in backup, or both.
- Check PHP. Tools › Site Health. Anything below PHP 7.4 needs upgrading first.
- Update plugins and theme. Run plugin updates and theme updates before the core update, not after.
- Test in staging. Most managed hosts include a one-click staging site. Update there first. Test the editor, your contact form, your checkout if you sell anything, and at least one of every block type you use.
- Update production. Once staging looks clean, push the update to your live site. Stay on the dashboard for ten minutes and watch for warnings.
- Disable AI features until you are ready. Settings › AI Experiments is opt-in, so nothing changes unless you turn it on.
If you are new to WordPress entirely and have not built a site yet, our guide to how to start a WordPress blog walks through the full setup from domain to first post.
Pros and cons of WordPress 7.0
- Native AI without third-party plugins
- Provider choice (OpenAI, Claude, Gemini)
- Cleaner, faster admin dashboard
- Block Notes covers most team workflows
- Native breadcrumbs and lightboxes
- Better revisions interface
- Real-time collaboration cut at the last minute
- PHP 7.2 and 7.3 sites are blocked
- Some custom admin CSS plugins may break
- AI features require API keys you pay for
- Older themes may need updating
Frequently asked questions about WordPress 7.0
When was WordPress 7.0 released?
WordPress 7.0 was released on May 20, 2026, after being delayed from the original April 9, 2026 target date.
Does WordPress 7.0 include real-time collaboration?
No. Real-time collaboration was removed from the final WordPress 7.0 release on May 8, 2026. The Block Notes commenting system is still included, and real-time editing remains under development for a future release.
What PHP version do I need?
WordPress 7.0 requires PHP 7.4 minimum. PHP 8.2 or 8.3 is recommended. Sites running PHP 7.2 or 7.3 cannot install the update at all.
Are the new AI features free?
The Connectors and Abilities frameworks are free and built into core. You still pay the AI provider (OpenAI, Anthropic, or Google) for API usage. For a small blog, expect a few dollars per month.
Should I update to WordPress 7.0 right now?
Update once you have backed up, checked PHP, and tested on staging. Most well-maintained sites will be fine. If you run a complex site with custom plugins, wait a few weeks for plugin authors to ship compatibility patches.
When is WordPress 7.1?
WordPress 7.1 is currently targeted for August 19, 2026, aligned with WordCamp US. WordPress 7.2 is expected around December 2026.
Final verdict on WordPress 7.0
WordPress 7.0 is a quieter release than the team originally hoped, but it is still the most important update since the Block Editor. The AI Connectors lay the foundation for the next decade of WordPress, and the admin refresh alone is worth the upgrade.
For most bloggers, the practical advice is simple: back up, test in staging, then update. Run WordPress 7.0 on a host that already has PHP 8.3 ready, and you will get the smooth experience the core team intended.