WordPress 7.0 Release Date and Features: Complete 2026 Roadmap (Updated)

WordPress 7.0 Armstrong was released on 20 May 2026. What shipped, what was pulled, every release since, 7.2 on 8 December, and how to upgrade safely.

WordPress 7.0 Armstrong released 20 May 2026, with 7.1 on 19 August, 7.1.4 current and 7.2 planned for 8 December

WordPress 7.0 “Armstrong” was released on 20 May 2026, after a delay from the original 9 April target. It shipped the first AI building blocks in core (an AI Client and a Connectors screen), a refreshed admin and a set of new blocks, but real-time collaboration was pulled from the release on 8 May. As of 15 November 2026 the current stable version is 7.1.4, and WordPress 7.2 is scheduled for 8 December 2026.

We checked every date and number below against the official WordPress.org release posts, the Make WordPress Core blog and the 7.0 Field Guide on 15 November 2026. This page started life in January as a roadmap guess, and almost none of that guess survived contact with reality, so we rewrote it from scratch around what actually happened.

When was WordPress 7.0 released?

WordPress 7.0 was published on 20 May 2026, according to the official 7.0 “Armstrong” announcement. The release is named after the jazz musician Louis Armstrong, and the announcement credits more than 875 contributors, including over 200 first-time contributors, with more than 420 enhancements and fixes.

It did not arrive on the date most people had in their calendars. The release was first planned for 9 April 2026. On 31 March, Search Engine Journal reported the delay, quoting the project’s call to “target extreme stability” because the real-time collaboration work had raised performance and database concerns. The core team’s own post, The Path Forward for WordPress 7.0 (2 April 2026), paused further pre-releases, closed trunk to 7.1 commits and promised a new schedule within weeks.

Date (2026)

What happened

Source

19 February

Beta 1 delayed (first schedule slip)

Make Core

31 March and 2 April

Release delayed, pre-releases paused

Make Core

9 April

Original planned release date

Search Engine Journal

8 May

Release Candidate 3, and real-time collaboration removed from 7.0

Make Core

14 May

Release Candidate 4 and the 7.0 Field Guide

Field Guide

20 May

WordPress 7.0 “Armstrong” released

WordPress.org

The lesson for planning is simple. WordPress still ships on a calendar most of the time, but a major release will slip when the project decides a headline feature is not ready. If your agency promises a client an upgrade on a fixed day, give yourself a buffer of a few weeks around any major version.

What shipped in WordPress 7.0?

The release centres on three things: the AI foundations, a modernised dashboard, and a larger toolbox for people who build themes and blocks. The 7.0 Field Guide lists every developer-facing change, and the headline items are below.

AI building blocks in core

The announcement describes 7.0 as laying the foundation for AI across WordPress. Four pieces make that real:

  • A provider-agnostic AI Client, so a plugin can call a generative model without hard-coding one vendor’s API.
  • A Settings, Connectors screen that manages connections to external services in one place, shipping with three presets and support for custom connections. The registry behind it is the new Connectors API.
  • A Client-Side Abilities API, the JavaScript counterpart to the Abilities API, with a command palette integration and query tools.
  • A separate AI plugin for generating and editing images, writing titles or excerpts and suggesting alt text. That one is optional and lives outside core.

If you build plugins, our guide to what plugin developers must get right with AI connectors covers the failure modes in more detail.

A refreshed admin

The dashboard gets a new “Modern” colour scheme with higher contrast, animated view transitions between admin screens (switched off when the visitor prefers reduced motion) and a Command Palette that opens with Ctrl+K or Cmd+K from an admin bar icon. There is also a dedicated Font Library page that works for block, hybrid and classic themes, and a visual way to scrub through two revisions of a post with a slider and colour markers showing where content changed.

Blocks and design tools

New blocks include Breadcrumbs, a Heading block with level variations, an Icons block and a Gallery block with a lightbox and optional slideshow. Existing blocks gained per-device visibility controls, customisable navigation overlays for mobile menus, per-block custom CSS, text indent support on paragraphs and expanded width and height supports in theme.json. Pattern editing also got broader support, including Pattern Overrides for custom blocks.

The developer toolbox

  • PHP-only block registration, so a simple block no longer needs a JavaScript build step.
  • A new watch function and a data-wp-watch directive in the Interactivity API, and a server-side state URL.
  • New Activity and Details layouts in DataViews, plus support for third-party field types in DataForm.
  • A plugins_list_status_text filter and custom status tabs for the plugin list.
  • Groundwork for extensible Site Editor pages, with route validation and a boot package.
  • Administrator and Editor roles removed from the default role dropdown on user registration, with a filter to change the exclusions.

Iframed editor and PHP changes

Two items deserve a plugin author’s attention. First, the post editor now runs in an iframe when every block in the post uses version 3 or higher of the Block API; if any block uses an older version, the iframe is removed to protect backward compatibility. Second, the minimum PHP version rose to 7.4, which means a site on PHP 7.2 or 7.3 will not be offered the 7.0 update at all.

What was delayed or left out of WordPress 7.0?

Real-time collaboration, the feature the whole 7.0 cycle had been built around, did not ship. On 8 May 2026 a Make Core post announced that it was being removed from the release. Matt Mullenweg was not confident that the current approach was solid enough for core, and the listed concerns were surface area, race conditions, server load, memory efficiency and recurring bugs found through fuzz testing. The post said the release schedule was unchanged and that a plan for wider testing would follow.

That plan arrived on 18 September 2026 in Moving to a server-aware approach for collaboration. In the new model, collaborators send updates to WordPress rather than to each other. The server records who changed what, checks permissions, merges changes and flags conflicts that cannot be merged. The team is comparing three candidate sync engines (a PHP implementation of Yjs, a three-way merge that syncs on save, and an operational-transform “intent log”) and says the work is not ready for core. The post names no target release, and the stated goal is to ship a preferred engine as a feature plugin first.

In practice that means two things for you today:

  • You cannot count on live multi-user editing in a stock WordPress install, in 7.0, 7.1 or the 7.2 beta.
  • If a client asks for it, plan for a plugin or an external workflow, and read our test list for real-time collaboration before choosing one.

A smaller set of 7.0 items was also described as groundwork rather than finished product. The Site Editor routing and boot package, for instance, prepare the ground for extensible admin pages, but the Field Guide presents them as foundations, not a finished user feature.

Which WordPress versions have come out since 7.0?

Quite a few. The 7.0 branch received four minor releases, then 7.1 arrived on 19 August 2026, and 7.1 has had four of its own. Most of them are security releases, which is the main reason to stay current. The list below comes from the WordPress.org releases archive, checked on 15 November 2026.

Version

Date (2026)

Type

What the release post says

7.0.1

9 July

Maintenance

31 bug fixes across Core and the Block Editor

7.0.2

17 July

Security

Two issues, one critical and one high, including a SQL injection chain; forced auto-updates enabled

7.0.3

6 August

Security

12 security fixes, among them a pre-auth reflected XSS on the login screen

7.0.4

12 August

Security

One security fix: remote code execution through a malicious upload for Author+ users on sites using Imagick and Ghostscript

7.1

19 August

Major

“Mary Lou”

7.1.1

17 September

Maintenance and security

17 Core and 19 Block Editor bug fixes, 11 security fixes

7.1.2

22 September

Release

Release post

7.1.3

6 October

Maintenance and security

4 bug fixes, 7 security fixes

7.1.4

28 October

Security

13 items in the security section, with backports to every branch still eligible for security fixes

Two details are worth reading carefully. The 7.0.2 and 7.0.4 posts both recommend updating immediately, and 7.0.2 enabled forced background updates for affected sites. And the 7.1.4 post says only the most recent version of WordPress is actively supported, even though backports roll out further back. If you are still on 7.0.x, you are on a branch that has already been superseded.

What did WordPress 7.1 add?

WordPress 7.1 “Mary Lou” shipped on 19 August 2026 and, per the release announcement, focuses on editing comfort and media handling:

  • Responsive styling, so blocks can be styled per screen size from Global Styles or block settings, and block themes can define their own mobile and tablet breakpoints in theme.json.
  • An admin bar that stays visible in all editors.
  • A single media editor modal that combines cropping, flipping, rotation and metadata editing.
  • Notes with rich text, links and @mentions, which can attach to specific text rather than a whole block.
  • Browser-based image processing: compression, resizing and thumbnail generation in the browser, plus native support for AVIF, HEIC and HDR gain maps.
  • New Playlist and Tabs blocks, custom icon collections for the Icon block and interactive button styles.
  • A post editor that is fully iframed for all themes, matching the Site Editor.

The last item is the one that bites. A custom block that relied on the old non-iframed editor, or on editor styles that leaked into the canvas, can look wrong after 7.1. Our 7.1 developer testing checklist walks through what to test.

What is coming in WordPress 7.2?

WordPress 7.2 is scheduled for final release on 8 December 2026, according to the 7.2 Beta 5 post from 10 November 2026. Beta 1 landed on 20 October, and Beta 5 is described as a refinement round rather than a feature drop. All of it is beta software, and the official posts say plainly not to run it on production or mission-critical sites.

The Beta 1 announcement lists the planned changes:

Area

Planned for 7.2

Editing

Responsive controls for more blocks, a “Customized” filter in Global Styles, text shadow controls, navigation link management in the sidebar, Notes with emoji reactions, client-side image resizing and conversion

Admin

An “On This Day” dashboard widget, WordPress icon library in the admin bar and sidebar, faster admin loading through per-asset loading and prefetching

Developers

A Secrets API for credentials such as API keys, an expanded Abilities API, Interactivity API updates, HTML API and block supports improvements

Beta 5 adds a few concrete items: email notifications when application passwords are created, better keyboard navigation in the admin toolbar, accessibility refinements to Visual History and stronger permissions for Notes reactions. It also states that all known compatibility issues with PHP 8.6 are resolved in core, and PHP 8.6 itself is planned for 19 November 2026. For the developer side, see our guides to the Secrets API and to what plugin authors should check before 7.2.

WordPress 7.0, 7.1 and 7.2 compared

7.0 “Armstrong”

7.1 “Mary Lou”

7.2 (planned)

Date

20 May 2026

19 August 2026

8 December 2026

Headline

AI Client, Connectors screen, Modern admin, command palette

Responsive styling, media editor, rich Notes, iframed post editor

Secrets API, On This Day widget, more responsive controls

Real-time collaboration

Removed on 8 May

Not included

Not included, no target release named

New blocks

Breadcrumbs, Heading, Icons, Gallery lightbox

Playlist, Tabs

Not listed as a headline

Status on 15 Nov

Superseded

Current (7.1.4)

In beta (Beta 5)

Should I upgrade to WordPress 7.0, 7.1 or wait for 7.2?

Move to the latest 7.1.x release, not to 7.0. The 7.0 branch has already collected several security releases and has been replaced, and the 7.1.4 post says only the newest version is actively supported. Wait for 7.2 only if there is a feature you need; a final release on 8 December is close, but a first release after a beta is a poor moment to be an early adopter on a client’s live store.

A sensible order of work, in the way we run it for our own sites:

  1. Take a full backup (files and database) and confirm you can restore it.
  2. Check the host’s PHP version. WordPress.org currently recommends PHP 8.3 or greater, MariaDB 10.11 or greater or MySQL 8.4 or greater, and HTTPS, per its requirements page. The hard minimum for 7.0 is PHP 7.4.
  3. Update plugins and themes first, so they carry their own 7.x compatibility fixes.
  4. Clone the site to staging and run through logins, checkout, forms, search and any custom blocks.
  5. Update core on production in a quiet hour, then clear every cache layer and log in again.

The commands below do the first checks over SSH. They are standard WP-CLI, checked on 15 November 2026.

# Which WordPress and PHP are we on?
wp core version
wp eval 'echo PHP_VERSION . PHP_EOL;'

# Is a core update available, and which plugins need updates first?
wp core check-update
wp plugin list --update=available

# After updating, confirm core files match the official checksums
wp core verify-checksums

If a plugin you rely on has not been updated in a year or more, treat that as a finding. Either find a maintained alternative or test it on staging with debugging on before the core update.

Common mistakes people report after upgrading to WordPress 7.0

These are patterns from public WordPress.org support threads and the 7.0 Field Guide, paraphrased. They are individual reports, not statistics, and we checked each page on 15 November 2026.

  1. Updating core before plugins and themes. The pinned moderator guide, Read this first, tells people whose site looks broken after a major release to update plugins and themes, clear browser cache and cookies and log in again before troubleshooting anything else. Most “7.0 broke my site” reports start there.
  2. Running a plugin that does not handle cached option values. In a thread on a critical error (WordPress 7.0, PHP 8.4), one of two similar sites crashed in Enhanced Autoload Manager because a persistent object cache returned an array where the plugin expected a string. The author shipped version 1.6.5 and the reporter confirmed the fix. The lesson: two sites with the same plugins can behave differently when only one uses an object cache.
  3. Assuming a page builder is compatible because it is current. A user reported in this SiteOrigin thread that after moving from 6.8.5 to 7.0, Custom HTML widgets on Page Builder pages output raw shortcode and markup. Support found no known conflict, could not reproduce it with a default theme and no other plugins, and suggested exporting layouts and trying a staged rollback through 6.9. Test builder-heavy pages on staging before the live update.
  4. Expecting the editor to behave like it did before the admin redesign. In a June 2026 thread a user complained of a cramped editor and a dark mode plugin that stopped working. WordPress has no built-in dark mode, and support pointed to the plugin developer. If a plugin restyles the admin, check that it declares 7.0 compatibility.
  5. Blaming core for a commercial plugin’s own bug. In a July 2026 thread a user said features of Advanced Ads broke after 7.0 and a plugin update. The moderator pointed to the vendor’s own support channel because the forums do not cover paid products. If you pay for the plugin, open the vendor ticket first and include your WordPress, PHP and plugin versions.
  6. Running an old PHP and waiting for the update to appear. The Field Guide states the minimum is now PHP 7.4, and WordPress does not offer an update to a site that fails the requirement. On PHP 7.2 or 7.3 that looks like “updates are broken” to a site owner. Ask the host to move you to a supported PHP first.

One honest caveat: forums skew toward problems, so these threads say little about how common any one issue is. Ours is a short list of what to rule out before you open a support ticket.

Is WordPress 7.0 still supported?

Not in any way you should rely on. The 7.1.4 release post states that only the most recent version of WordPress is actively supported, and the project continues to backport security fixes where it can. Treat 7.0.x as end of the road, and plan the move to 7.1.x now, then 7.2 once it has had a few weeks in the wild.

Frequently asked questions

What is the WordPress 7.0 release date?

20 May 2026. It was first planned for 9 April and delayed so the team could stabilise the collaboration work, which was then removed from the release on 8 May.

What is the latest WordPress version?

WordPress 7.1.4, a security release published on 28 October 2026, was the current stable version when we checked on 15 November 2026.

When is WordPress 7.2 released?

8 December 2026 per the 7.2 Beta 5 post of 10 November 2026. It is in beta now and should not run on production sites.

Does WordPress 7.0 include real-time collaboration?

No. It was pulled on 8 May 2026. A September 2026 Make Core post says the team is exploring a server-aware design and testing three sync engines, with no release named.

Does WordPress 7.0 need PHP 8?

The minimum is PHP 7.4. WordPress.org recommends PHP 8.3 or greater for new installs and upgrades, so the practical answer is yes: run a current PHP.

Is the AI in WordPress 7.0 switched on by default?

Core ships an AI Client and a Connectors screen, but the announcement describes generating images, titles and alt text as a separate AI plugin. A model is only called once you configure a connector and use a plugin or feature that needs it.

Which should I install, 7.0.4 or 7.1.4?

7.1.4. The 7.0 branch has been superseded, and the project supports only the latest version actively.

Sources checked on 15 November 2026: the WordPress.org releases archive and each release post linked above, the 7.0 Field Guide (14 May 2026), the Make Core posts of 2 April, 8 May and 18 September 2026, and the WordPress.org requirements page.

Varun Dubey

Written by

Varun Dubey

Varun Dubey runs Wbcom Designs, the WordPress studio he founded in India in 2009. He has spent sixteen years building on WordPress and BuddyPress, shipping client work and products such as Reign, BuddyX, Jetonomy and MediaVerse, and has been putting Claude and OpenAI workflows into production since 2023. He writes up what the studio learns along the way.

More about Varun

No comments yet