WordPress 7.0 Shipped AI — Real-Time Editing Got Cut

WordPress 7.0 shipped on May 20, 2026, and the headline most outlets ran with was simple: AI is now native. The story most missed is the one worth telling. Real-time collaborative editing was on the roadmap for this release, and it got cut to make the date.

That contrast is the whole story of WordPress 7.0. It is a release that traded a flashy feature for a stable platform move, and the trade is going to shape WordPress plugin development for the next two years.

The scale of WordPress 7.0

WordPress 7.0 was the first major release of 2026 and was built by more than 750 contributors under release lead Matias Ventura. That number matters because WordPress is not a small team shipping a side project. When a release of this size adds AI as a first-class concept, the rest of the web notices, and plugin authors start planning around it.

The release was originally scheduled for April 9, 2026. It slipped about six weeks to May 20 to stabilize the features that made it in. That slip is the cleanest signal of what the team prioritized: ship a stable platform, not a flashy demo.

What shipped: the AI hub at Settings → Connectors

The headline feature is called AI Foundations, and the part the site owner actually sees is a new screen at Settings → Connectors. It is a single hub for managing API keys and connections to external services. One screen, one place to look.

AI providers like OpenAI, Anthropic, and Google are first-class citizens of this screen, but it is not AI-only. Any plugin that needs to talk to an outside service can register through the same standardized system. That standardization is the real story for plugin authors.

An optional separate AI plugin sits on top of Connectors. Once a provider is wired up, that plugin adds title generation, excerpt generation, image generation and editing, and alt-text suggestions directly inside the block editor. None of it is forced. The site owner opts in by installing the plugin and choosing a provider.

The official framing

WordPress 7.0 hands you more of the controls, and trusts you to use them.

Joen Asmussen, WordPress 7.0 release announcement

That line tells the developer what philosophy to expect. More decisions are being pushed to the site owner, especially around which AI provider to trust with content. Connectors is the mechanism that makes that choice tractable instead of overwhelming.

What did not ship: real-time collaboration

Real-time collaborative editing, the Google-Docs-style multi-user editing experience inside the block editor, was originally planned for WordPress 7.0. It did not make the release. The roughly six-week slip from April 9 to May 20 was the team holding the door open for real-time collab, and then closing it when the feature was still not stable enough.

This is normal WordPress engineering discipline. When a feature is not ready, the feature gets cut, not the date. The release goes out on a workable schedule, and the unstable work moves to the next train. That is the discipline the project has held to for years and it held again here.

Why WordPress 7.0 matters for existing sites

Two reasons WordPress 7.0 matters to the developer running existing sites today. First, WordPress 7.0 did not break backward compatibility on PHP. PHP 7.4 is still supported. PHP 8.3 is the recommended version. The much-feared major version bump that draws a hard line at PHP 8 did not happen, which makes the PHP 8.x upgrade path a soft recommendation rather than a hard requirement.

Second, the AI integration is opt-in. A site that ignores the Connectors screen and skips the optional AI plugin keeps the WordPress it already had, just running on a newer admin theme. Nothing is forced on a site owner who does not want it.

For headless setups where the front end is rendered outside WordPress, the Connectors API still applies wherever the admin handles credentials. A headless WordPress architecture can use Connectors-managed keys for any service the back end touches, without exposing them in the front-end JavaScript bundle.

The supporting cast

The smaller features that shipped alongside AI Foundations round out the release. None of these are headline material, but together they shape the day-to-day editor experience.

• Navigation overlay designer for mobile menus: a dedicated canvas, columns, font sizing, alignment.
• Visual revisions: a timeline slider for scrubbing post history, block-by-block diff markers, one-click restore.
• Patterns as single blocks: drop a pattern and it behaves like one block, with swap controls in the inspector.
• Font library for all themes: previously block-themes-only, now works across classic themes too.
• Per-screen-size block visibility: show or hide blocks at mobile, tablet, and desktop without custom CSS.
• Icon block: a new core block with a built-in icon library.
• Command palette: Cmd + K or Ctrl + K for fast navigation throughout the dashboard.
• Refreshed admin color scheme: quieter defaults, updated buttons, page fades instead of jumps.

Full coverage of every dev note is on the WordPress 7.0 Field Guide on Make WordPress Core, which links the per-feature dev notes for plugin and theme authors.

WordPress 7.0 outlook

The read on WordPress 7.0 is this. It is the AI platform release, and the Connectors hub is the piece plugin authors will be building against for the rest of the year. The much-feared backward-compatibility break did not happen, which makes this a smooth upgrade for almost every existing site.

Real-time collaborative editing is on the next train, not gone. The pattern of cutting a feature to hold a date is healthy engineering discipline, not a failure. The platform is in good hands going into the rest of 2026.

Watch the companion video above for the five-minute walkthrough of WordPress 7.0’s headline features and the one feature they cut.