WordPress 7.0: The Biggest Update in Years?

WordPress 7.0 "Armstrong" was released on 20 May 2026 (release announcement on wordpress.org). For the first time, the release put an interface to AI models into core, along with a refreshed admin design, new blocks and several developer tools. This post sums up what actually shipped, based on the release announcement and the core team's WordPress 7.0 Field Guide.

Last reviewed: 7 October 2026. WordPress 7.1 has since been released (19 August 2026, announcement); the current version is WordPress 7.1.3. If you are still on 7.0.x, plan the update.

AI in core: the AI Client and Connectors

The biggest change is the WP AI Client, a central interface that lets plugins talk to generative AI models without being tied to a specific provider. You manage the connections under Settings > Connectors. Three providers are preset there: Anthropic, Google and OpenAI, and you can add others. You enter the API key once, and plugins then use that connection.

On top of that comes a JavaScript counterpart to the Abilities API. The Abilities API itself has been in WordPress since 6.9. It describes a site's functions in a machine-readable way so that automations and AI tools can call them in a targeted way.

For context: WordPress 7.0 ships the infrastructure, not finished AI features. Image generation, title and excerpt suggestions or automatic alt text come from the separate AI plugin by WordPress.org or from third-party plugins. Without a plugin and an API key, the AI Client changes nothing on your site.

Admin and editor

• New "Modern" admin colour scheme and smooth transitions between admin screens.
• Command Palette via ⌘K or Ctrl+K, now with its own icon in the admin bar.
• Font management on a dedicated admin page, including for classic and hybrid themes.
• Visual revisions: compare two versions of a post directly and restore one.
• Iframed editor: the post editor runs in an iframe as soon as all blocks used in the post use block API version 3 or higher. If an older block is in the post, the editor loads without the iframe so that block keeps working. Details are in the developer note on the iframe changes.

New blocks and design tools

• New and revised blocks: Breadcrumbs, Icons, a new Heading block and a Gallery block with a lightbox slideshow.
• Show or hide blocks per device without affecting other screen sizes.
• Mobile menu overlay that you can design freely with blocks and patterns.
• Custom CSS per block, right in the post or page.

What changed for developers

• PHP-only block registration: blocks and patterns can be registered on the server without a JavaScript build.
• A more extensible Site Editor with routing and the new wordpress/boot package, which lets plugins build their own Site Editor pages.
• Iterations on the Interactivity API, DataViews and DataForms and the Block Bindings API.
• For AI features: the using_model_preference() function and the WP_AI_Client_Prompt_Builder class in the AI Client, plus the new Connectors API.

The full list with all developer notes is in the Field Guide.

What site owners should keep in mind

Before every major update, check whether your theme and plugins keep up, ideally on a staging copy. With 7.0 this mainly concerned custom or older blocks: WordPress is gradually moving the post editor into the iframe, and the core team advises block developers to move to block API version 3. How quickly an update can take a site down was shown by the next release: after WordPress 7.1, WP Rocket caused a fatal error.

For the AI features, decide deliberately which plugins get access to the configured connectors. The API key also means costs with the AI provider and the question of which content is sent to it.

If you'd rather not handle major core updates yourself: as part of my WordPress support, I test every new version on a staging copy of your site first and only roll it out once your theme and plugins demonstrably keep up.