WordPress 7.0 “Armstrong” is here

What it means for your site

WordPress 7.0 landed on 20 May 2026, and it’s the biggest structural update to the platform since the block editor arrived back in 2018. Named after jazz legend Louis Armstrong and built by more than 750 contributors, this release is less a coat of paint and more a quiet rewiring of how WordPress connects, edits, and presents content.

If you run a WordPress site — whether it’s a brochure site, an online shop, or a content-heavy publication — here’s what’s actually changed, and why it matters that you don’t sit on the upgrade for too long.

The headline features

AI foundations, built into the core

For the first time, WordPress core ships with a standardised way to connect to external AI services. A new Connectors screen lives in your admin and acts as a single hub for managing integrations — including AI providers like OpenAI, Google Gemini, and Anthropic’s Claude.

The core itself stays AI-agnostic. WordPress doesn’t ship an AI model; it ships the plumbing. An optional companion plugin adds editor-level tools — generating titles and excerpts, creating and editing images, and suggesting alt text — and any third-party plugin can plug into the same connection system.

The practical upshot: AI features stop being a tangle of competing plugins each with their own API key fields, and start behaving like a managed part of the platform.

Visual revisions you can actually read

Revision history has always been there, but reviewing it was a chore. WordPress 7.0 introduces a timeline slider with block-by-block visual markers showing exactly what changed between versions. One click restores the version you want. For anyone working with editors, clients, or content teams, this turns “undo” into a proper editorial tool.

Patterns that behave like single blocks

Patterns — the pre-built layouts you drop into a page — used to expand into a forest of nested blocks the moment you placed them, making small tweaks unnecessarily fiddly. In 7.0, a dropped pattern behaves like a single block. Swap the text, change the image, adjust styles in the inspector. When you do need to dig deeper, one click on “edit pattern” gives you full access to everything underneath.

A dedicated canvas for navigation

Building a decent mobile or full-screen menu in WordPress has historically meant fighting the theme. The new navigation overlay gives you a proper canvas: add columns, scale up the font, align elements, start from a template or build it from scratch. It’s the kind of feature that should have existed years ago.

Responsive visibility for blocks

You can now choose which blocks appear at each screen size — desktop, tablet, mobile — directly from the block settings. No more duplicating sections with conditional CSS hacks just to hide a sidebar on mobile.

Font library across all themes

The font library, previously locked to block themes, now works everywhere. Browse, install, and manage fonts directly from the editor regardless of whether you’re on a block theme or a classic one.

Smaller wins worth noting

• A new Icon block with a built-in icon library, so you don’t need an extra plugin for something every site eventually needs.
• A refreshed admin experience — new default colour scheme, updated buttons and form inputs, and smoother page transitions. It’s subtle, but the admin feels considerably less dated.
• Performance improvements to image loading prioritisation, particularly around hidden images in overlays and interactive blocks that were previously stealing bandwidth from above-the-fold content.
• Continued accessibility work across media management, voice control, and colour contrast in the new admin scheme.

Why upgrading matters (and isn’t optional)

It’s tempting to leave a working site alone. Here’s why that’s a riskier strategy than it looks.

Security. WordPress powers a huge chunk of the web, which makes it an enormous target. Each major release rolls security improvements directly into core, and older versions stop receiving the same level of attention from the security team. Sites running outdated WordPress are the single most common entry point for compromises we see.

The PHP 7.4 floor. WordPress 7.0 raises the minimum PHP requirement from 5.6 to 7.4. If your hosting is still on an older PHP version, you’ll need to bump that up before upgrading — but you should be doing that anyway. PHP 5.6 hasn’t received security updates in years.

Plugin and theme compatibility. The plugin and theme ecosystem moves with core. Sit on an old version long enough and you’ll find new versions of the plugins you rely on quietly dropping support for it. The longer you wait, the bigger the eventual jump.

Editorial efficiency. The new revisions interface, the pattern editing improvements, and the AI Connectors aren’t just nice-to-haves — they’re real time savers for anyone editing content regularly. A faster editorial workflow compounds.

Future-proofing. WordPress 7.0 marks the start of Gutenberg Phase 3, the collaboration and workflow phase. Real-time collaboration is targeted for 7.1, and native multilingual support is on the roadmap for Phase 4. Staying current means you’ll actually benefit from those features when they ship, rather than facing a multi-version leap.

A word of caution before you click “update”

Major version upgrades are best done deliberately, not reactively. A few things we’d recommend:

1. Wait two to four weeks after the initial release if your site is business-critical. The early patch cycle catches the compatibility issues that real-world traffic surfaces but staging never does.
2. Back up everything — files and database — before upgrading, not after.
3. Test on staging first. Run the upgrade in a staging environment, click through the parts of the site that matter, and check that your page builder, e-commerce setup, and key plugins behave as expected.
4. Check page builder and plugin compatibility. For sites built with Breakdance, WooCommerce, or other heavyweight tools, confirm those vendors have validated the new version before you push to production.
5. Don’t upgrade on a Friday afternoon. You know why.

Need a hand?

Major WordPress upgrades are one of those jobs that looks simple until something breaks at 11pm. If you’d rather not gamble with it, we manage WordPress upgrades — including pre-flight checks, staging tests, and full backups — for sites of every shape and size.

Get in touch and we’ll get your site safely onto WordPress 7.0.