WordPress 7.0, named after Louis Armstrong, shipped on 20 May 2026. It is the largest release in years, and unlike most major versions the headline features are infrastructure rather than things you can see.
We updated our own site and several client sites over the following weeks. This is what actually changed, what broke for us, and how to decide when to update.
Why it was late
7.0 was originally scheduled for 9 April to coincide with WordCamp Asia. The core team pushed it back roughly six weeks, and the reason is worth knowing because it tells you something about the release.
Real-time collaboration was the flagship feature, and it was storing sync data in post meta. That had a side effect nobody wanted: opening the block editor was inadvertently disabling WordPress query caches site-wide. The six-week delay was meant to buy time to rebuild that layer on a proper database table.
It did not work out. Roughly two weeks before release, real-time collaboration was pulled from 7.0 altogether, over concerns about race conditions, server load, memory efficiency and recurring bugs surfaced by fuzz testing. It did not make WordPress 7.1 either. If you have been waiting for Google Docs style editing in WordPress, you are still waiting.
The AI layer, and what it does not do
The most discussed part of 7.0 is AI infrastructure in core: an AI Client, an AI Services Registry and a Connectors hub for AI providers, building on the Abilities API foundation that landed in 6.9.
Here is the important bit that gets lost in the noise: none of this does anything to your site on its own. WordPress has not added AI features to your editor. It has added a standard way for plugins to talk to AI providers, so that every plugin does not have to build its own integration and ask you for its own API key.
The Abilities API is the genuinely interesting piece for developers. Plugins can register what they are capable of, in a form an AI assistant can discover and use. If you have ever wanted an assistant that could actually operate your site rather than just write text into it, this is the plumbing that makes it possible.
It is opt-in and plugin-based by design. If you install nothing, nothing happens.
The admin redesign is the change you will feel
The dashboard has been rebuilt in React using the DataViews system, and this is what your clients and content team will actually notice:
- Command Palette — press Cmd+K or Ctrl+K and search for anything: a page, a setting, an action. Once you get used to it, clicking through menus feels slow.
- Visual revision scrubbing — scrub through post revisions and see them rather than reading a diff.
- A dedicated font management page — fonts finally live somewhere sensible instead of being buried in theme settings.
The Command Palette is the one that changes daily habits. Once pressing Cmd+K to jump anywhere becomes reflex, clicking through admin menus feels slow.
What did not ship
Two headline items were cut. Real-time collaboration, as above. And client-side media processing — browser-side image resizing before upload — was also pulled from 7.0 and is arriving in 7.1 instead.
What you do get for collaboration is Notes: asynchronous comments and suggestions attached to specific blocks. It is not live co-editing, but for a business where a marketing person drafts and a manager reviews, it removes most of the exporting-to-Google-Docs dance.
New blocks and design tools
7.0 adds Tabs and Icon blocks to core, expanded Style Variations, and responsive editing controls that let you customise mobile menus and hide blocks by viewport.
The Tabs block is quietly significant for anyone building without a page builder — tabbed content was previously a reason to install a plugin. That is one fewer plugin on the site, which is one fewer thing to update, break and patch.
Should you update now?
The release has been out since May and the early compatibility patches have landed, so the risk profile is much better than it was on day one. Our advice, in order:
- Check your PHP version first. 7.0 recommends PHP 8.3 or greater. The technical minimum is 7.2.24, but running anything that old is a security problem in its own right. If you are below 8.0, sort that out before anything else.
- Take a real backup. Files and database, downloaded somewhere you control, not just a host snapshot you have never tested restoring.
- Test on staging. Specifically test page builders, SEO plugins, multilingual plugins and WooCommerce extensions. Those four categories customise the editor most heavily and are where compatibility issues concentrate.
- Then update production, ideally not on a Friday afternoon.
If your site is running an abandoned plugin that has not been updated in two years, 7.0 is the release that finally forces the conversation. That is not a bad thing, but budget time for it rather than discovering it mid-update.
What broke for us
Honestly, less than expected. The issues we hit were all in the same category: plugins that heavily customise the admin UI, which had to catch up with the React rebuild. Everything settled within a few weeks as those plugins shipped updates.
The one thing we would flag: if you have custom admin styling or a white-labelled dashboard for clients, check it carefully. That is the area most likely to look wrong after the redesign, and it is also the area nobody thinks to test.
The short version
WordPress 7.0 is an infrastructure release that sets up the next several years rather than a feature drop you will enjoy on day one. The AI parts do nothing until you install something that uses them. The admin redesign and client-side media processing are the changes you will actually feel day to day. Get on PHP 8.3, test on staging, then update.
Frequently asked questions
Is it safe to update to WordPress 7.0 now?
Much safer than it was at launch. The release has been out since May 2026 and the early compatibility patches have landed. Check your PHP version is 8.3 or greater, take a full backup you control, and test on staging first, paying particular attention to page builders, SEO plugins, multilingual plugins and WooCommerce extensions.
Does WordPress 7.0 add AI features to my website?
No. It adds infrastructure — an AI Client, an Abilities API and a Connectors hub — that plugins can use to talk to AI providers through a standard interface. Nothing is switched on automatically and no AI features are injected into your site. If you install nothing, nothing changes.
What PHP version does WordPress 7.0 need?
PHP 8.3 or greater is recommended. The technical minimum is 7.2.24, but anything that old carries security risks regardless of WordPress version. Most decent hosts let you change PHP version from the control panel in a couple of clicks.
What is the Command Palette in WordPress 7.0?
Press Cmd+K on Mac or Ctrl+K on Windows anywhere in the admin and you get a search box for pages, settings and actions. It is powered by the Abilities API and it is genuinely faster than navigating menus once the habit forms.
Does WordPress 7.0 have real-time collaboration?
No. It was the headline feature throughout development but was removed roughly two weeks before release, over concerns about race conditions, server load and memory efficiency. It did not ship in WordPress 7.1 either. What 7.0 does include is Notes, which gives you asynchronous comments and suggestions on individual blocks.
What is most likely to break when updating to WordPress 7.0?
Plugins that heavily customise the admin interface, because the dashboard was rebuilt in React. If you have custom admin styling or a white-labelled client dashboard, check that specifically — it is the area most likely to look wrong afterwards and the one people forget to test.