WordPress 7 is here. Here’s what’s new and what to do.

Earlier draft titles (kept for the audit trail):

“WordPress 7: What Changed, What Matters, and What to Actually Do About It” (original — christopher persona flagged as tricolon AI-tell)

“WordPress 7 is here. Here’s what is in it, what to do, and what to leave alone.”

“WordPress 7 has shipped. The honest read.”

Pillar: High-end WordPress authority (primary). Local Niagara reader can follow the whole thing.

Audience tier: T1 (high-end WP) lead, T3 (local Niagara) friendly. The post reads cleanly to a procurement-buyer at a school board AND to the bakery owner who took WP101.

Approximate word count: 2,800-3,200

Published: 2026-05-20 (WordPress 7.0 release day)

Schema: Article (BlogPosting), Christopher as author with full author schema, FAQPage block at the bottom for the “should I update now” question cluster.

Featured image: Photographer-pipeline; brief: a WordPress dashboard mid-keystroke, the Command Palette open with “⌘K” visible — captured at the moment of “oh, that’s new.” Not a stock-photo desk scene.

SEO: target query “wordpress 7 release,” secondary “what’s new in wordpress 7,” “should I update to wordpress 7.” Slug: `/wordpress-7-whats-new/`.

Internal links (load-bearing): WP101 course page, the WP 7 quick-reference download, the WP 7 update module landing (when live), the monthly maintenance routine post if one exists, the “Three lines you don’t cross” lesson reference.

WordPress 7 shipped today.

If you run a WordPress site, you have heard about it from someone by now — your developer, your agency, a notification in the dashboard, a panicked email from a colleague. The short version: the update is real, it is safe to take, and there is no fire. You do not need to act before lunch. The rest of this post is the longer version.

I have been on WordPress since 2007 and have written about every major release for years, and the shape of those posts is usually the same. There is a list of new features, a list of breaking changes, a recommendation to update, and a closing note that everything will be fine. That post is useful the day it goes live and stops being useful two weeks later, because what most site owners actually need is not a feature changelog. It is a translation. What changed in the abstract, and what does that change in the work you do on your own site this week?

So that is the shape of this one. The features are in here, but they are not the point. The point is what to do with them, and what to leave alone.

The headline

Four things in WordPress 7 are worth knowing about before you log in tomorrow morning. Three are in the release. One was pulled twelve days before launch.

AI Connectors. A new settings screen at Settings → Connectors that lets you connect your WordPress site to an AI provider (such as OpenAI, Anthropic, or Google) once. From that point forward, any plugin that uses AI on your site uses the credentials you set there, instead of asking you for an API key every time.

The Command Palette. A new keyboard shortcut, ⌘K on a Mac or Ctrl+K on Windows, that opens a search bar at the top of the dashboard. You type the name of any page, any setting, any tool, and you jump straight to it. The single biggest quality-of-life change in the release.

A new admin look. The dashboard you log into tomorrow morning will look slightly different. New default colour scheme called “Modern,” new typography, small animations when you click between screens. None of the buttons moved. Nothing you knew how to do yesterday is in a different place.

What got pulled. Real-time collaboration, the feature that would have let two editors work on the same page at the same time, was removed from the release at the eleventh hour. The reasons are interesting, and worth a paragraph below.

That is the whole headline. Everything else in this post is detail.

Should you update? Yes. Here is how.

Yes. The update is safe. There are no known showstoppers. The release has been through four release candidates and a code freeze, and the deprecations are the kind that affect plugin developers more than they affect site owners.

But the rule for any major WordPress release is the same one I have written into every monthly maintenance routine I have ever taught: back up first, update on a non-publishing day, and have a way to roll back. If your host provides one-click snapshots, take one before you hit the update button. If your host does not, take an UpdraftPlus or BackWPup backup manually. Then update WordPress core, then update your plugins, then update your theme, then load the front page in an incognito window and click around. If something looks off, you have a snapshot to revert to and the rest of the week to investigate.

For most sites, the entire process takes under fifteen minutes. For some sites, it takes a couple of hours because a single old plugin is the bottleneck. There is no reliable way to predict which kind of site you have until you take the backup and start.

If you would rather not do it yourself, the right shape is to get on your developer’s calendar for the week after launch, not the week of. Major-release week is when every WordPress consultant on the continent is booked. The week after, the queue clears.

What “AI Connectors” actually is, and what it isn’t

AI Connectors is the news item in this release that I think will get the most coverage and create the most confusion. So here is what it actually is.

Connectors is a settings screen — the same shape as the screen where you tell WordPress your SMTP credentials so it can send email. A place to put credentials once so other things can use them. It is not artificial intelligence inside WordPress.

What the Connectors screen does is solve a real problem. For the last two years, every WordPress plugin that wanted to use an AI provider, for generating titles, for writing alt text, for drafting summaries, has had to build its own settings screen, its own API-key field, its own error handling. If you had four AI-aware plugins on your site, you had four places to enter the same OpenAI key. Connectors collapses those four places into one. You set your provider and your key at Settings → Connectors, and from then on, any plugin that knows about Connectors uses what you set.

That is genuinely useful, and it sets up the future where more plugins integrate with it. But it does not, on its own, add a single AI feature to your site. To actually use AI for anything, you install a plugin that takes advantage of the Connectors API. The WordPress team has indicated an official plugin will ship alongside the release to handle title, excerpt, and alt-text generation as a starting point. I will link to it from this post once it is named on launch morning.

My recommendation for the WP101 audience: if you are not already paying for OpenAI or Anthropic or Google for some other reason, the right move is to wait. AI Connectors is not going anywhere. The plugins that depend on it will get more useful over the next year. There is no urgency to set one up just because the screen now exists. If you are already paying for one of those services, the value of Connectors is the consolidation — set it up once and your future AI-using plugins will pick it up automatically.

For the high-end WordPress audience (agencies, school boards, organisations with internal AI policy already in place), the Connectors screen matters more, because it is the first time WordPress core gives you a documented, sanctioned place to manage that integration. Your information-security person is going to thank the WordPress team for giving them one place to manage that credential instead of asking every plugin author to invent their own.

The Command Palette is the change you will actually use

I have been using the Command Palette for the last four release candidates, and I cannot imagine going back to clicking through menus to find the screen I want.

Here is what it does. You press ⌘K on a Mac, or Ctrl+K on a Windows machine, anywhere in the admin. A search bar opens at the top of the screen. You type a few letters of the name of the thing you want to do — “users,” “menus,” “permalinks,” “plugins” — and the matching admin screens, settings pages, and registered actions appear underneath. You arrow down to the one you want and press Enter, and you are there.

If you have used the same shortcut in modern code editors, in Slack, in Figma, in Notion, the pattern will be familiar within ten seconds. If you have not, it will feel strange for a day, and then you will not want to go back.

The reason this matters more than it sounds is that the WordPress admin has, fairly, been described for years as a place where the menu structure is impossible to learn. Some things are under Settings, some under Tools, some under Appearance, some under their own top-level item that a plugin added last week. The Command Palette stops asking you to remember where things are. You just remember what they are called.

For the person who got handed the keys to a WordPress site and is still working out what each menu does, this is the single best thing in the release. It is also the easiest to overlook, because it is a keyboard shortcut that does not have an on-screen button to draw your eye. So this is the paragraph I will be re-reading to my training clients for the next six months: press ⌘K. Type “users.” Press Enter. That is the new way of getting around.

The Fonts page, and the plugin you can probably uninstall

WordPress 7 adds a dedicated Fonts management page under Appearance. For most site owners, this is a “huh, that is nice” moment. For some site owners, it is a “wait, I can uninstall a plugin now” moment.

If you have ever used a plugin called Use Any Font, or Google Fonts Typography, or any of the dozen other plugins built to solve the “how do I add a font to my theme” problem, the Fonts page is the answer that finally lives in WordPress core. You upload the font file, or you choose from the curated library, and the font is available across your site without a plugin in the middle.

This is a Module 3 conversation in WP101 — the moment when adding a plugin is the right answer versus the moment when core has caught up and the plugin is now baggage. WordPress 7 catches up on fonts. If you have a fonts plugin installed for no reason other than fonts, the next monthly maintenance pass is when you replace it with the built-in page and remove the plugin. Fewer plugins is fewer things that can break.

The pattern of “WordPress core caught up — uninstall the plugin” repeats every release or two. When it happens, the right move is not loyalty to the plugin; it is removing it and letting core do the work.

Visual Revisions is finally what revisions should have always been

The old WordPress revisions screen has been with us for over a decade, and it has always been technically accurate and practically frustrating. You could see that something changed. You could not see what changed at a glance. You had to scan two columns of nearly identical text and find the one word that was different.

Visual Revisions in WordPress 7 is the version of this screen that the feature should have been all along. Pick any two revisions of a post or page. The new view shows them side by side with the differences highlighted — yellow where you modified text, red where you deleted it, green where you added it. A timeline slider at the bottom of the screen lets you walk through every save event. The page you wrote three weeks ago and the version that is live now are now legible to each other.

For an organisation where more than one person writes — which is almost every organisation I work with — this is a quietly enormous change. The conversation that used to be “I think someone changed the second paragraph last week, can you check” becomes a thirty-second look at the timeline. The team member who quietly removed the legal disclaimer two months ago is now traceable in the colour-coded diff. The post you accidentally overwrote with a half-finished draft is now recoverable in three clicks.

The change does not require any setting to be turned on. The next time you open the Revisions screen on any post, the new view is there.

The new admin look

The dashboard you log into tomorrow morning will look slightly different from the one you log into tonight. The default colour scheme has changed from one called “Fresh” to one called “Modern.” Typography has been refreshed. Buttons have new shapes. Cards on the dashboard home have new borders. When you click between screens, there is a small CSS animation where the old screen fades out and the new one fades in.

None of this changes how the dashboard works. The Posts menu is still where Posts has always been. The Pages menu is in the same place. Every keyboard shortcut you know still does what it did. The decision the design team made — and I think it was the right one — was to update the look without moving anything that anyone has learned the position of.

If you preferred the old “Fresh” colour scheme, it is still in the list at Users → Profile → Admin Colour Scheme. You can switch it back. I am leaving mine on Modern, because I think the new one is cleaner, and because in a year’s time anyone learning WordPress will be learning it on Modern, and I would rather be looking at the same dashboard they are.

The View Transitions animation between screens is the bit I expected to find tiring. It turns out to take 180 milliseconds and add nothing to my workload. I notice it the first time I click between screens each morning and then I forget it is there.

The feature that got pulled, and why that is the right call

WordPress 7 was supposed to ship with real-time collaboration. The idea was that two editors could open the same post at the same time, see each other’s cursors, edit together, the way Google Docs has worked for fifteen years. This was the marquee feature in the early-2026 announcements. It was on the WordCamp Asia schedule earlier this year and discussed widely after. It was in three release candidates.

On May 8, with twelve days to go before launch, the WordPress team announced that real-time collaboration was being removed from the release. The reasons published in the announcement are the kind of reasons that I think every site owner should know about, because they are also the reasons your site is mostly stable: race conditions when two writers save simultaneously, server load when sync events fire at scale, memory efficiency on long editing sessions.

I want to be clear about why I think this was the right call. WordPress runs more sites than any other CMS on the open web. A feature that falls over at scale isn’t ready, no matter how good the demo looks. The team tested it, found the cases where it fell over, and pulled it back into the lab. The feature will land in a future release, when those cases are solved. In the meantime, the storage approach the engineers developed has been kept as the recommended path for whoever finishes the work.

This is the kind of release-engineering decision that does not make the headlines and should. The temptation to ship the feature anyway and patch it later is real, and the team did not give in. That is what I would want my own engineering team to do.

The deprecations and breaking changes that affect a few people

For most site owners, the breaking changes in WordPress 7 are invisible. For a few, they matter.

PHP 8.3 or higher is recommended. WordPress will still run on older PHP versions, but anything below the recommended floor will surface as a “your site is at risk” warning in the dashboard. If your hosting account is on an old PHP version, this is the week to log into your hosting dashboard and switch up. Most hosts let you do this in two clicks.

The author-link template tags lost their tooltip attributes by default. This affects custom themes that use `get_the_author_link()`, `the_author_link()`, or `the_author_posts_link()` and relied on the “Posts by Author” title attribute. If your developer maintains your theme, this is a five-minute fix once they read the relevant deprecation page on the WordPress developer handbook. If you are on a major commercial theme, the theme will have shipped an update for this already.

The HTML5 script theme support flag was removed. Again, a developer-side change. Themes built in the last five years are not affected.

CodeMirror, the syntax-highlighting library used in WordPress’s built-in code editors, has been updated to version 5. If you use plugin or theme file editors inside WordPress to write code — which you should not be doing anyway, but I am not your developer — the editor will look slightly different.

If you are not a developer and none of the above made sense, that is fine. You can stop reading this section. None of it affects what you do on your site.

What I am going to do this week

Three things, in order.

I am going to update WordPress 7 on my own production sites Tuesday morning, after backing them up. Tuesday is my low-traffic day. I am going to leave a note for myself to check the Visual Revisions screen on the next thing I publish, because it is the change I am most curious to use.

I am going to set up a Connectors entry with the AI provider I already pay for, because there is no cost to having it ready for the next plugin that wants to use it.

I am going to spend ten minutes each day next week using the Command Palette as my only way of getting around the admin, because that is the muscle memory I want to build. By the end of next week, I expect to be using it by reflex.

Everything else in the release is fine to leave alone. Visual Revisions appears when I need it. The Modern colour scheme is the new default. The Fonts page is there when I am ready to remove a plugin. There is no rush.

Last reviewed May 18, 2026.