WordPress 7.0 Armstrong

When 7.0 shipped

WordPress 7.0 was released on 20 May 2026. The name is Armstrong. Matias Ventura wrote the WordPress.org announcement. The name comes from the jazz trumpeter Louis Armstrong. Each major release uses a musician’s name. 6.8 was Cecil, 6.9 was Gene Harris, and 7.0 is Armstrong.

This is not a maintenance release. It is a new major branch. The WordPress.org download archive, at the time of this article, lists 7.0 as the latest recorded major release. The versions page lists 7.1 for 19 August 2026 and 7.2 for 10 December 2026 as planned dates. The archive has no 7.1 row. Update a live site from the version you downloaded, not from a planned date.

7.0 dropped PHP 7.2 and 7.3. It needs PHP 7.4 or newer. The recommended floor is 8.3. The PHP calendar is in a separate article.

How AI entered core

7.0 did not add a button that writes the site for you. It put an AI Client in core. That client is a shared way for WordPress to talk to generative models. Connections are managed from one Connectors screen. The announcement describes three presets and a way to add your own connection. You choose the provider. Nothing calls a model until you connect one.

The Abilities API is how plugins declare work on that connection. There is a browser-side counterpart, Client-Side Abilities, with its own interface and a command palette. An optional AI plugin is installed separately. The announcement lists generating and editing images, writing titles or excerpts, and suggesting alt text. Those buttons do not appear until the plugin is installed.

On a shop or a company site, write two things down before you turn this on. Is generated text read before it is published? Does the image sit under a license you hold? Core does not answer those questions for you. The connection hub only opens the path.

What changed in the editor

The announcement counts four new blocks. Galleries can open a lightbox slideshow. The Heading block sets heading markup from the editor. The Breadcrumbs block prints the page path. The Icons block picks from a built-in set. An older theme may not show all of them the same day. If the theme does not carry block-theme styles, the look needs a separate check.

Blocks can be hidden or shown by screen size. A section closed on mobile can stay on desktop. That is not two copies of the same content side by side. One block is not painted in the view you turned off. The menu overlay is its own canvas. Columns, type size, and alignment can sit next to the link list. You can start from a template.

Patterns behave like one block. Dropping one on the page ends the hunt through nested blocks. Text and images change, and style is set from the sidebar. Deeper work stays behind “edit pattern”. Post revisions are visual. A timeline slider marks what changed, block by block. The version you want comes back in one click. That does not replace a backup. A revision is post content. The database, plugins, and uploads are a different job.

Fonts and the admin

The Font Library used to depend on block themes. In 7.0 it also opens on classic themes. You pick and install a font from the editor. Hand-written CSS in the theme file is no longer the only path. You do not have to convert a classic theme into a block theme for that reason alone.

The admin changed too. There is a new default color scheme, and buttons and inputs were refreshed. Pages fade between each other instead of jumping. The announcement also names accessibility work on media management, voice control, and color contrast. The new color scheme was reviewed for contrast.

Speed, and what did not ship

7.0 aims to stop hidden images from hurting the load of critical resources. Images inside a navigation overlay or an interactive block move back in the priority order. On-demand block stylesheets in classic themes are more consistent. Scripts can depend on script modules. The aim is fewer files that block the first paint.

Real-time co-editing did not ship. Justin Tadlock’s developer note of 12 May 2026 says so. The reasons are surface area, race conditions, server load, and memory. Repeated bugs showed up in testing. The feature was left for a later release. Do not plan 7.0 as “two people write the same post at once”.

Before you update

A major release touches plugins and the theme the same day. Take a backup first. Then open 7.0 on staging. Click checkout, forms, login, and the cache plugin. If a template breaks, do not move it to production. The security maintenance list is in the 6.8 security article. For the shop plugin, read the WooCommerce 11.2 article.

The OwnHost WordPress hosting page has two cards. Personal is $0.79 a month, or $8.99 when billed yearly. The card lists one site, 15 GB NVMe, one-click WordPress install, free SSL, Nginx, and a weekly backup. Pro is $3.29 a month, or $26.99 when billed yearly. It lists ten sites, staging, a daily backup, and 4096 MB of RAM. The staging line for a major-release test is on the Pro card. The Personal card has no staging line. The PHP version is not printed on these cards. Read it in the panel. Do not assume it from this article.

After you install 7.0, confirm the version number on Dashboard, Updates. The name “Armstrong” is in the announcement. The line in the panel should read 7.0. If a plugin updated itself before you were ready for 7.0, read the plugin author’s note first. Rolling core back is not always safe once a database update has run. That is why the test copy comes before the live site.