WordPress 7.0, code-named Armstrong, was released on May 20, 2026 — one of the biggest releases in years. Originally planned for April, it was delayed to protect stability given the scale of architectural changes. It also kicks off Phase 3 of the Gutenberg project, focused on collaboration and workflows.
Here’s what’s new, and how to update without breaking your site.
The Headline Features
AI infrastructure built into core
WordPress 7.0 ships the new AI Client and Abilities API — a standard way for plugins to connect AI features into the CMS. You won’t see a chatbot appear on your dashboard, but this foundation means AI-powered plugins (content generation, image editing, search) will now work in a consistent, safer way instead of each plugin reinventing the wheel.
Block visibility per device
Expanding on 6.9, you can now show or hide any block on mobile, tablet, or desktop — natively, without extra plugins or custom CSS. Huge for responsive design: build one page, tailor it per device.
Navigation overlays (finally out of experimental)
The Navigation block now supports fully customizable overlays, giving you real control over mobile menus. No more fighting the default hamburger menu behavior.
New Icon block
A native Icon block lets you insert SVG icons from a curated library, backed by a new server-side SVG Icon Registration API. One less reason to install an icon plugin.
Revisions for templates and patterns
The revisions panel now extends to templates, template parts, and patterns — you can finally track changes to your site’s design and roll back mistakes, not just for posts and pages.
What didn’t make it
Real-time collaboration (Google Docs–style co-editing) was postponed due to concerns about server load, race conditions, and memory usage. Expect it in a future release.
Should You Update Now?
Yes — but carefully. Major releases can conflict with themes and plugins that haven’t caught up yet. Our recommended process:
- Back up first. Full backup — files and database — stored off-server.
- Check compatibility. Confirm your theme and key plugins list support for 7.0. Look at plugin changelogs and support forums.
- Test on staging. Clone your site, update the clone, click through your key pages and checkout/contact flows.
- Update during low traffic. Then verify forms, menus, and any custom functionality.
- Watch for a week. Check error logs and site speed after updating.
If you’re several versions behind (6.5 or older), don’t jump straight to 7.0 — update incrementally and test between steps.
What This Means for Your Business Site
The direction is clear: WordPress is becoming a full site-building platform with AI hooks and design-system-grade tooling. Sites built on old page builders and abandoned themes will fall further behind in speed and compatibility with each release.
If your site hasn’t had a professional review in a couple of years, a 7.0 upgrade is the right moment for a health check: performance, security, and whether your theme is holding you back.
Frequently Asked Questions
Will WordPress 7.0 break my existing theme?
Not automatically — but themes and plugins that haven’t been updated for the new block visibility and navigation-overlay features may behave inconsistently until their next release. Always test on staging first.
Do I need to enable the new AI Client to update to 7.0?
No — the AI Client and Abilities API are infrastructure other plugins can use; they don’t add any AI features to your dashboard on their own or require configuration if you don’t use AI-powered plugins.
Is per-device block visibility a replacement for a responsive theme?
No — it’s a targeted tool for hiding or showing specific blocks (like a promo banner only on mobile), not a substitute for a theme that’s genuinely responsive across all breakpoints.
👉 HD Web Mobile handles WordPress upgrades end-to-end — staging tests, compatibility fixes, and rollback plans included. Ask us about a managed upgrade to WordPress 7.0.