WordPress 7.0 “Armstrong” has been available since May 20, 2026, named after the jazz trumpeter Louis Armstrong and built by more than 875 contributors, with over 420 enhancements and fixes. If you maintain one site or fifty, the practical question is whether to upgrade now, and how to do it without breaking anything. That is THE question this checklist answers. Let’s go through it together, calmly.
Is WordPress 7.0 a big upgrade or a quiet one?
From the announcement, 7.0 looks large. It brings a modernized dashboard, a Command Palette reachable with Ctrl+K or Cmd+K, dedicated font management, new design blocks, and the first piece of AI infrastructure to live in WordPress core. Read the detail, though, and most of these are additive and optional. The AI Client, in particular, is a developer interface rather than a content generator that switches on by itself, a point we unpack in our piece on what the AI Client actually changes.
For day-to-day editing, the result feels like a polished 6.x rather than a rebuild. For most sites, 7.0 is an evolution you can adopt on your own schedule, not a release that forces your hand. If you want the full tour of what is new before deciding, our guide to the WordPress 7.0 features walks through each one; here we stay on the upgrade decision itself.
Two features that did not ship, and why that reassures
Some previewed features were pulled before release, which matters when you weigh the risk. Real-time collaboration, long demonstrated in the block editor, did not make 7.0. The decision to remove it cited surface area, race conditions, server load, memory efficiency, and recurring bugs found through fuzz testing, and the work now targets 7.1.
The second deferral is more technical but more relevant to your plugins. The planned jump to React 19 was reverted in Gutenberg after many plugins built for React 18 began crashing, so 7.0 ships on React 18, with the upgrade deferred to a later cycle. Both deferrals mean 7.0 carries less new surface area than the previews implied, which is good news if your priority is a stable site.
Should you upgrade now, or wait?
Upgrade soon if your stack is mostly core plus well-maintained plugins, your host runs a recent PHP version, and you can test on a staging copy first. Hold off if you depend on a custom theme that relies on HTML5 script support, on blocks pinned to an old Block API version, or on a plugin that has not yet declared 7.0 compatibility. When a critical plugin has not confirmed 7.0 support, waiting a couple of weeks costs nothing and avoids a live incident.
Point releases also help. The first 7.0.x updates iron out the early edges, so delaying two or three weeks rarely costs anything and often spares you a surprise. Nobody is grading you on upgrading on day one.
A cautious upgrade procedure, step by step
When you do move, the order matters more than the speed. Back up, clone to staging, test every theme and plugin, then switch: that sequence is the whole method. Here is how it breaks down.
- Back up your files and database, and confirm you can actually restore the backup before you touch anything.
- Check your PHP version. THE first thing to check is the host: WordPress 7.0 raises the minimum to PHP 7.4, so an older host has to move up before you upgrade.
- Clone the site to a staging environment and upgrade there first, never on production.
- Test themes and plugins on staging, with extra care for custom blocks (the iframed editor is now enforced for Block API version 3 and above), themes that lean on the removed HTML5 script support, and anything bundling its own React.
- Walk your key flows by hand: the editor, checkout, contact forms, and any custom fields your content depends on.
- Only once staging is clean, schedule the production switch for a low-traffic window, with the backup within reach.
Our take
WordPress 7.0 is a confident but deliberately conservative release. The AI groundwork matters for what comes next, yet the everyday value today is the polish and the 420 fixes, not a feature that rewrites your workflow. The two deferrals tell you the team chose stability over spectacle, and that should shape how you upgrade: methodically, not in a hurry.
So here is a calm way to decide. If you run a simple site on managed hosting with mainstream plugins, upgrade after a quick staging pass. If you maintain client sites or custom code, budget an afternoon for staging tests before any production switch. And if a key plugin or your PHP version is not ready, wait for a point release rather than forcing it. Whichever case is yours, keep the backup, test in staging, and read what is actually new in our WordPress 7.0 features guide before you commit. Enjoy the upgrade, on your own terms.
