WordPress 7.0 “Armstrong” was released on 2026-05-20, and it carried the largest admin redesign since 2013 plus the first AI layer ever shipped in WordPress core. If you own a site rather than build them for a living, four of those changes will actually affect you: the Posts and Media screens look different, there is a keyboard shortcut that now does most of your navigation, there is a new Settings screen for AI credentials, and the minimum PHP version moved. Everything else in the release notes is either invisible from where you sit or aimed at developers.
Version and verification. This guide is written against WordPress 7.0.2, released 2026-07-17, which is the current stable release. WordPress 7.0 shipped 2026-05-20, 7.0.1 on 2026-07-09, and 7.1 is scheduled for 2026-08-19. Last verified 2026-07-30 against wordpress.org.
The short version: four things you will actually notice
- The Posts, Pages and Media screens changed shape. The old list tables were replaced by a filterable, sortable view. Nothing was removed. It looks like an app now instead of a spreadsheet.
- There is a command palette. Press Ctrl+K on Windows or Cmd+K on Mac from anywhere in the admin and type what you want. There is a matching icon in the top admin bar.
- There is an AI credentials screen. Settings > Connectors stores an AI provider key once so that compatible plugins can use it, instead of each plugin asking you for its own.
- PHP 7.4 is now the floor. Support for PHP 7.2 and 7.3 ended with 7.0. If your host had you on one of those, the update either refused or something broke.
If you want the tour of the redesigned admin rather than the summary, the task-based walkthrough of the new admin covers the twelve everyday jobs that changed the most.
The version numbers, and which one you should be on
There are more version numbers in circulation right now than usual, and several pages still on page one of search results were written when 7.0.1 was the newest release. As of the verification date above:
| Version | Released | What it is |
|---|---|---|
| 7.0 | 2026-05-20 | The major release. Admin redesign, AI Client, new blocks. |
| 7.0.1 | 2026-07-09 | Maintenance release. |
| 7.0.2 | 2026-07-17 | Maintenance release. Current stable. |
| 7.1 | 2026-08-19 | The next major release. Not out yet. |
The honest recommendation is the boring one: be on the latest release in the 7.0 series. WordPress.org’s own release archive is explicit that only the most recent release in a series is actively maintained, which means older 7.0.x installs stop receiving security fixes.
Minor releases like 7.0.1 and 7.0.2 install themselves on most sites through background updates and do not need a decision from you. Major releases like 7.1 still require you to click Update, which is where the decision, and this cluster of articles, comes in.
The admin redesign: what moved and what did not
The left-hand menu is still the left-hand menu. Settings is still Settings. Almost nothing was relocated. What changed is the screens you spend the most time inside:
- The Posts, Pages and Media list screens use the new data views instead of the old plain tables. You get filters, saved views, layout choices and bulk selection that behaves consistently across all three.
- The command palette moved out of the block editor, where it had lived, and now covers the whole admin.
- Font management got its own page under Appearance, and it works for classic and hybrid themes, not only block themes. That is a genuine change: font management used to be a block-theme feature.
- Revisions became visual. You can scrub through revision versions and see the difference rather than reading two columns of text.
- The admin color scheme was modernized, which is why your dashboard may look unfamiliar even though nothing functional changed.
- Moving between admin screens animates instead of doing a hard page reload.
The practical consequence is not that you have to relearn WordPress. It is that almost every tutorial and screenshot published before May 2026 now shows a screen you do not have. If a guide you are following looks nothing like your admin, that mismatch is the reason, and it is not a sign your site is broken.
AI arrived in core, and what that does and does not mean
WordPress 7.0 added an AI Client to core, an Abilities API for registering capabilities, and a Connectors screen for managing connections to AI providers. It is worth being precise about what this gives a site owner, because the coverage of it has been loose.
What it is: a credential store and a shared plumbing layer. You put a provider key in one place, and plugins built against WordPress’s AI Client can use that connection instead of asking you for a separate key each.
What it is not: a content generator. Installing WordPress 7.0 does not give you a “write my post” button. Core ships the connection, not the feature. Whether anything useful happens depends entirely on which plugins you have and whether they were built to use it.
If you want to set it up, the Connectors setup guide covers choosing a provider, getting a key from the provider’s own dashboard, and the two questions worth answering first: whether the key is safe once it is in your database, and what it will cost you. What you should then do with anything an AI produces, including whether it is accurate enough to publish, is an editorial question and not one this site answers.
New blocks and responsiveness controls
7.0 added a Breadcrumbs block, an Icons block, a lightbox slideshow for galleries, and block-level custom CSS. It also added controls for hiding and revealing blocks by device, and a customizable navigation overlay built from blocks and patterns.
These are optional. Nothing on your existing site starts using them because you updated. The Breadcrumbs block in particular is worth one clarification: it is a block that outputs a breadcrumb trail, and whether and how breadcrumbs should be used as a search feature is a separate subject that this site does not cover.
The requirement that quietly breaks sites: PHP
This is the change most likely to have caused you actual trouble, and it is the least discussed.
- WordPress requires PHP 7.4 or greater. Support for PHP 7.2 and 7.3 ended with the 7.0 release.
- WordPress.org recommends PHP 8.3 or greater. Its requirements page is blunt about why: 7.4 still functions but has reached end of life, so it no longer receives security fixes.
- The database floor is MariaDB 10.11+ or MySQL 8.0+, with older versions still working but unsupported.
- HTTPS is listed as required for every install.
You can see which PHP version you are running without asking your host. Go to Tools > Site Health > Info and expand the Server section. Site Health will also raise a critical issue on the Status tab if your PHP version is outdated.
The reason PHP shows up in an article about a WordPress update is that the two failures look identical from the outside. A site that breaks the day after a host moves it to a newer PHP version presents exactly like a site that broke because of a WordPress update, and the fix is completely different.
What tends to break after a major update, in rough order
This is the ordered suspect list, not a prediction about your site:
- A plugin that has not been updated in a long time. By far the most common cause. The plugin did not change; the ground under it did.
- A plugin that modifies the admin interface. 7.0 rebuilt the screens these plugins hook into, so admin-customizing plugins, custom-column plugins and list-screen filters are the highest-risk category on this release specifically.
- A caching layer serving the old version of everything, which makes a completely successful update look like a failure.
- Theme customizations that lived in theme files rather than in a child theme, which a theme update overwrote.
- PHP-version mismatches, as above.
Two things are worth knowing before you rely on a plugin’s own page to judge that risk. The compatibility figure printed on it is declared by the developer and verified by nobody, which is why what “Tested up to” really means is worth five minutes. And there is a faster way through a long plugin list than checking every entry, which is the tiering method in how to find out which of your plugins will break.
If something is broken right now, start with the plugin-broke-after-updating path if a single feature died, or the critical error walkthrough if you are looking at “There has been a critical error on this website.” If you have decided you want to undo the update rather than diagnose it, rolling back without losing content covers the three separate rollback procedures and the case where restoring a backup is the better answer.
Does this affect you? Three site types, three answers
A classic-theme site with a handful of plugins. You will notice the admin redesign and nothing else. Font management under Appearance now works on your theme, which it previously did not. Your risk on a major update is low but not zero, and it sits almost entirely with your oldest plugin.
A block-theme site with a page builder or a shop. You have the most surface area and the most to check. Page builders and commerce plugins are large, they hook deeply into the editor and the admin, and they are the two categories where waiting for the plugin vendor to confirm compatibility is genuinely worth the delay.
A site you have not updated in a year or more. Do not treat this as one update. You are crossing a PHP floor change and a full admin redesign at once, and the order of operations matters more than the individual steps. This is the case where testing on a copy first stops being optional advice.
What is coming on 2026-08-19
WordPress 7.1 is scheduled for 2026-08-19, timed to the final day of WordCamp US in Phoenix, and reached Beta 1 on 2026-07-15. The changes announced for it include a native Tabs block, Playlist and Table of Contents blocks, styling for hover and focus states and for tablet and phone breakpoints without writing CSS, a substantially expanded Notes system for asynchronous feedback, and improved media handling.
Because 7.1 is a major release, it will wait for you to click Update. That is a decision, and there is a version-by-site-type answer in the 7.1 release guide. Before release day, the two things worth doing are running the twenty-minute pre-update checklist and, if your site earns money, testing the update on a copy first.
What a site owner does not need to learn
WordPress 7.0’s release notes include an Abilities API, server-side block and pattern registration in PHP, a more extensible site editor with routing and route validation, and a new boot package for custom site-editor pages. Every one of those is real and none of them is yours. They are tools for people writing code against WordPress.
The line is worth stating plainly because the feature lists do not draw it: if a 7.0 feature requires you to write PHP or JavaScript to use it, it is not a feature you are missing out on. It is infrastructure for the plugins and themes you already run, and you will experience it as those products improving, not as work you have to do.
If you want the mechanism rather than the feature list, what actually happens during a WordPress update walks through the five phases of the process, which is the fastest way to make the common error messages stop being mysterious.
