WordPress 7.0: What Actually Shipped (And What Got Cut)

WordPress 7.0 releases May 20, 2026. It marks the official start of Phase 3 of the Gutenberg project (the Collaboration phase), and it’s the most substantial core release since the block editor itself launched in WordPress 5.0.

The release almost looked entirely different.

Real-time collaboration was the headline feature of the entire development cycle. It caused the original April 9 launch to slip by six weeks.

Then, on May 7, it was cut entirely. If most of the pre-release coverage you read was about RTC, that feature is not in this version.

What is in 7.0 is still a lot. Here’s a quick peek:

• A rebuilt AI infrastructure layer, including a central hub for connecting AI providers.
• A modernized admin dashboard with a new color scheme, smooth screen transitions, and a command palette.
• Three new blocks.
• A rebuilt visual revisions tool.
• Meaningful improvements to pattern editing, responsive design tools, and navigation overlays.
• A set of developer changes, including a new PHP minimum, that will affect every site still running an older server configuration.

I tested the beta on my own site and went through the official Field Guide, the RC4 release notes, and developer posts to put this together.

Let me show you what to expect from WordPress 7.0!

Table of Contents

What Is WordPress 7.0 and Why Does This Release Matter?

WordPress releases follow the Gutenberg roadmap, a phased plan for rebuilding how WordPress works from the ground up.

Phase 1 introduced the block editor. Phase 2 built out the Site Editor, giving users control over headers, footers, and templates without touching code. Phase 3 is about collaboration, and WordPress 7.0 is its official starting point.

Real-time collaboration was supposed to be the centerpiece. It wasn’t ready. But the infrastructure, the tooling, and the architectural work that surrounds it did ship, and there’s more here than any other single release in recent memory.

The numbers back that up. WordPress 7.0 closes 419+ Core Trac tickets. That includes 300+ bug fixes, 76+ enhancements and feature requests, 411 Gutenberg enhancements, and 486 Gutenberg bug fixes.

This release touches everyone. If you’re a blogger or site owner, you’ll notice the admin looks different and works faster. If you build sites for clients, the pattern editing and responsive tools change how you work.

If you develop plugins or themes, there are new APIs, a new PHP minimum, and deprecations that need attention before you update production.

AI Integrations in WordPress 7.0

“AI integration” has been part of the 7.0 marketing since the cycle began, and the reality is more nuanced than it sounds.

What shipped are two things: infrastructure built into core and an optional plugin that sits on top of it.

Here’s how they break down.

The Connectors Screen: One Place to Manage External Services

The Connectors screen is a centralized hub for managing connections to external services, including AI providers. Find it at Settings » Connectors in your wp-admin dashboard.

You connect your preferred provider once, enter your API key, and that connection becomes available to any compatible plugin on your site. You won’t have to enter the same credentials in five different plugin settings screens.

Three AI providers are available by default:

• OpenAI (ChatGPT)
• Google (Gemini)
• Anthropic (Claude)

Plugin developers can register additional providers using the Connectors API.

This is a platform-level change. It standardizes how WordPress sites talk to outside services — not just AI tools, but any plugin that needs to connect to an external API.

The WP AI Client: Infrastructure for Plugin Developers

The WP AI Client is a new core PHP library that gives plugins a standardized way to communicate with AI providers.

Before 7.0, every plugin that wanted to use AI had to build its own connection logic. Now they can use a shared abstraction layer and let users switch providers without breaking anything.

If you’re not a developer, you won’t interact with the WP AI Client directly. But you’ll benefit from it when the plugins you use start building on top of it.

The Optional AI Plugin: Where the Actual Tools Live

The editor-facing AI tools (generating titles and excerpts, creating and editing images, suggesting alt text) are not in core. They come from an optional AI plugin that you install separately.

After updating to WordPress 7.0, you won’t see an AI button in your editor. You’ll see the Connectors screen. The writing and image tools come from the plugin.

Once you install it, you can enable AI to generate content like meta descriptions, alt text, review notes, images, and titles.

There are also experimental features for using AI to handle comment moderation and the Abilities API.

I think this is the right call. Shipping AI infrastructure into core without locking every WordPress site into a specific set of AI behaviors gives plugin developers and site owners more control over what they actually use.

The Client-Side Abilities API

The Client-Side Abilities API is the JavaScript counterpart to the PHP abilities system introduced in WordPress 6.9. It ships as two packages: @wordpress/abilities for state management and @wordpress/core-abilities for WordPress integration.

Plugins can use it to expose AI-powered actions in the command palette and editor toolbar with consistent UI patterns, input/output schemas, and permission callbacks.

Admin Redesign: The wp-admin Dashboard Gets a New Look

If you’ve been using WordPress for a while, the admin dashboard has looked more or less the same for years. WordPress 7.0 changes that in ways you’ll notice the moment you log in.

The Modern Color Scheme and View Transitions

The new default color scheme is called “Modern.” It brings a refreshed color palette, higher contrast, and upgraded typography across the entire dashboard.

The bigger change is how the dashboard moves. WordPress 7.0 adds smooth slide transitions between admin screens.

When I tested this in the beta, it made the dashboard feel noticeably more like a native app and less like a series of disconnected page loads. The transitions respect OS-level reduced motion preferences, so users who have that setting enabled won’t see them.

The Command Palette

Press ⌘K on Mac or Ctrl+K on Windows from anywhere in the admin, and you’ll immediately access a command palette.

The command palette gives you quick access to editing tools, settings pages, and navigation without leaving your current screen. The tasks you reach for most often are always one keystroke away.

If you’ve used command palettes in VS Code or Figma, this is the same idea applied to wp-admin. It’s one of those features that sounds minor until you’ve used it for a week.

The Font Library

WordPress 7.0 adds a dedicated font management page to the dashboard.

Before this, managing fonts in WordPress depended heavily on your theme. Block themes had one workflow, classic themes had another, and neither was straightforward.

The Font Library centralizes it. You can manage, upload, and install fonts in one place, regardless of whether you’re running a block theme, a hybrid theme, or a classic theme.

DataViews Replace Traditional Content Lists

The list of your posts, pages, and media has a new look in WordPress 7.0. DataViews replace the traditional wp-admin list tables with a modern, app-like interface.

Filtering and sorting happen inline, without a page reload. On content-heavy sites where you’re regularly hunting through hundreds of posts, that’s a meaningful speed improvement.

Visual Revisions: Compare Any Two Versions Side-by-Side

WordPress has had a revision history for years. The problem was always using it.

The old revisions screen showed you a text diff — additions highlighted in green, deletions in red — but gave you no sense of how the page actually looked at that point. If you were trying to figure out which of two versions had the right layout, you were guessing.

WordPress 7.0 replaces that with a visual comparison tool. A timeline slider lets you scrub through every saved version of your post or page.

When you find the version you want, you restore it in one click.

I found this genuinely useful in testing. Revision history is one of those features that most WordPress users know exists but rarely use because the old interface made it harder than it needed to be. The new version is actually faster to reach for than opening a previous draft manually.

New Blocks and Block Enhancements

WordPress 7.0 ships three new blocks and meaningful improvements to several existing ones.

Three New Blocks

The Icons block lets you insert scalable SVG icons anywhere on your page from a curated core library. You get controls for size, color, alignment, and borders without a plugin.

If you’ve ever installed a visual plugin just to get an icon or two into a feature list, this replaces that.

The Breadcrumbs block automatically reflects your site’s navigational hierarchy. Drop it into your header or page template, and it builds the breadcrumb trail based on your site structure.

Developers get filters for customizing the output, and you can specify taxonomy and term display.

The Headings block brings all heading level variations into a single block with easy sidebar toggling and one-click level transforms.

It’s a refinement more than a revolution, but it tidies up a workflow that involved more friction than it should have.

Gallery, Cover, and More

The Gallery block gets two additions: lightbox support with a slideshow option and keyboard navigation between images when the lightbox is open.

The Cover block can now use a YouTube video as a looping section background. It also supports video embeds more broadly as full-bleed backgrounds, with optimized lazy-loading.

The Paragraph block picks up two new typography options in this release: a columns layout for arranging text in multiple columns and text indent support via the new textIndent block support property.

On the design tools side, button blocks now support pseudo-state styling (:hover, :focus, :focus-visible, :active) directly in theme.json, and dimensions support gets preset values for width, height, and min-height

Responsive Editing and Pattern Editing

These two changes matter more to people building sites than just writing posts.

Responsive Editing Mode

WordPress 7.0 lets you hide or show any block based on device type (mobile, tablet, or desktop) without writing a line of CSS.

The controls live in the block toolbar, the inspector sidebar, and the command palette. You can also change styles per breakpoint and customize the breakpoint sizes themselves.

List View shows an icon on any block with active visibility rules, so you can see at a glance what’s being conditionally shown.

One thing developers need to know: visibility is implemented via CSS, not DOM removal. A block hidden on mobile is still in the HTML; it’s just not displayed. If you have code that checks for the DOM presence of a block to determine visibility, it’ll behave differently than expected.

Pattern Editing: Patterns Now Behave Like Single Blocks

Before 7.0, dropping a pattern onto a page meant working through nested blocks to find the element you wanted to change. In 7.0, patterns behave like a single block by default.

Drop a pattern in, swap the text and images, adjust styles from the inspector, and keep moving. You don’t have to dig into the block structure unless you want to.

When you do need deeper access, there are two named editing modes.

Spotlight mode activates for unsynced patterns. Click Edit pattern or double-click the pattern body, and the surrounding blocks fade out, giving you full editing access in context.

Isolated Editor activates for synced patterns and template parts. Click Edit original and you’re taken into a dedicated canvas where you can edit the underlying pattern or template part without affecting the page you were on.

For anyone building sites with synced patterns, this is worth testing on staging before pushing to production. The contentOnly mode is now the default for patterns with unrestricted inner block editing, and there’s a disableContentOnlyForUnsyncedPatterns setting if you need to opt out.

What Developers Need to Know About WordPress 7.0

If you maintain plugins, build themes, or manage WordPress at a technical level, there’s a lot here that needs attention before you update production sites.

PHP 7.4 Is Now the Minimum

WordPress 7.0 drops support for PHP 7.2 and 7.3.

If your server is running either version, WordPress 7.0 will not function correctly. Check your hosting control panel before updating.

PHP 8.2 is the recommended version; 8.3 if you want to be ahead of the curve.

This is the number one technical blocker for older sites. Deal with it before anything else.

PHP-Only Block Registration

You can now register and render simple custom blocks using only PHP — no JavaScript build pipeline, no Node.js, no webpack, no React.

Add 'supports' => array( 'autoRegister' => true ) to your block registration, and WordPress handles the rest. PHP-registered attributes become editable in the editor automatically, and DataForm inspector controls are generated for you.

This lowers the barrier significantly for plugin authors who prefer PHP or are building straightforward blocks that don’t need a JavaScript-heavy setup.

Interactivity API Changes

Three changes to note in 7.0.

• The new watch() function lets you subscribe to signal changes in @wordpress/interactivity: a cleaner pattern for side effects than what was available before.
• The data-wp-watch directive handles DOM element lifecycle events.
• state.url is now populated server-side during directive processing, which enables better navigation tracking.

One deprecation: state.navigation is gone. Update any code using it.

Build Tooling: @wordpress/build

The new @wordpress/build package replaces the webpack/Babel pipeline with an esbuild-based engine.

It automatically generates PHP registration files from package.json, which removes a step that previously had to be handled manually. Migration from @wordpress/scripts is lower-friction than past tooling transitions.

It’s not a required change for 7.0, but it’s worth evaluating. Esbuild is substantially faster than webpack for most plugin build workflows.

Other Developer Changes Worth Noting

A few smaller but relevant updates.

The CodeMirror editor (used in the custom CSS, HTML, and file editors in wp-admin) is updated to v5. CSSLint, HTMLHint, and JSONLint are included. Esprima is replaced with Espree, which adds proper ES6 support to JavaScript linting.

External library updates: backbone.js to 1.6.1, the Requests library from 2.0.11 to 2.0.17, and PHPMailer to 7.0.2, which fixes a Sender address bug worth knowing about if you handle transactional email on WordPress.

On the security side, Administrator and Editor roles are removed from the new user default role selector. If your site previously had either of those set as the default role for new registrations, Site Health will alert you.

The new default_role_dropdown_excluded_roles filter gives you programmatic control over which roles appear in that dropdown.

What Is NOT in WordPress 7.0

A lot of pre-release coverage was written before May 7. Some of it describes features that didn’t make the final release. Here’s what to know.

Real-time collaboration is not in 7.0.

It was the headline feature of the entire development cycle. The April 9 release was pushed to May 20 specifically to give the team more time to stabilize it.

Then, twelve days before the new date, Matt Mullenweg made the call to cut it entirely.

The reasons cited were server load concerns, memory efficiency issues, and recurring bugs that kept surfacing in testing. The code was removed from core for RC3. The team has committed to a plan for a future release, but no version has been named.

What you can use for collaboration: Notes.

Notes is a separate feature that’s been in core since WordPress 6.9. It lets editorial teams leave threaded, block-level comments inside the editor with @mention notifications. Nothing appears on the frontend.

WordPress 7.0 adds reliability fixes to Notes, including email notifications when someone adds a note to a post you authored and a fix preventing notes from incorrectly incrementing the post’s comment count.

It’s asynchronous, not simultaneous. But it removes the “copy the draft into Google Docs, comment there, paste it back” workflow that many editorial teams are still running.

There’s no built-in AI writing assistant in core.

The AI layer in 7.0 is infrastructure: the Connectors screen, the WP AI Client, and the Abilities API. Core does not generate titles, write copy, or suggest edits. Those tools exist in the optional AI plugin, which is a separate install.

If you update to 7.0 and don’t see an AI button anywhere, that’s expected.

A few other features that didn’t make it:

• Client-side media processing (browser-based image compression on upload) was reverted during Beta 6.
• There is no Twenty Twenty-Six default theme. The next default theme is Twenty Twenty-Seven, planned for 2027.

How to Update to WordPress 7.0 Without Breaking Your Site

WordPress 7.0 changes more under the hood than most major releases. New PHP requirements, block API updates, and a rebuilt admin interface mean there are more ways for something to go wrong than a typical point release.

That doesn’t mean you should avoid updating. It means you should update carefully.

Here’s the order that matters.

Back Up Your Site Before You Do Anything

If WordPress 7.0 conflicts with a plugin, breaks a theme layout, or trips over your PHP configuration, you need to get back to exactly where you were.

This is where I use Duplicator Pro. It creates a full-site backup and lets you restore in minutes.

If WordPress 7.0 breaks your site badly enough that you can’t get into the dashboard at all, Duplicator Cloud lets you restore without WordPress being functional. You just need to send a full-site backup to the cloud.

Then, make sure the recovery connector is set up with your FTP/SFTP credentials.

If anything goes wrong, you can restore this pre-update backup without needing your site functional.

I’ve used this once on a client site after a botched update, and it saved what would have been hours of manual recovery work.

Test on Staging Before Touching Production

A backup is your safety net. Staging is how you avoid needing it.

Duplicator Pro turns any full-site backup into a staging site. You won’t need a separate hosting account or manual file transfers to a local dev environment.

Clone your live site, apply the WordPress 7.0 update on staging, and test everything. If something breaks on staging, you fix it there. Your live site never goes down.

Check Your PHP Version First

WordPress 7.0 drops support for PHP 7.2 and 7.3. Updating WordPress before updating PHP on an incompatible server can break your site.

Log into your hosting control panel and check which PHP version your site is running. If you’re on 7.2 or 7.3, upgrade to at least PHP 7.4 before touching WordPress. PHP 8.2 is the recommended version.

Audit Your Plugins Before You Update

Most well-maintained plugins will handle 7.0 without issues. A few categories are worth checking first.

• Plugins that use classic meta boxes are the most likely to surface unexpected behavior, particularly around the iframed editor changes in 7.0.
• Plugins with their own AI integrations may overlap or conflict with the new Connectors screen.
• Page builders and block editor extensions are worth a close look — check the “Tested up to” field on each plugin’s WordPress.org page before updating.

Consider Waiting for 7.0.1

This one is optional and depends on your site.

The first patch release after a major version — typically 7.0.1, arriving one to two weeks after launch — lets the broader community surface edge-case bugs that testing didn’t catch.

For sites where downtime has real cost, waiting for 7.0.1 and watching the support forums for a week is a reasonable approach.

For those sites, staging plus a fresh backup is the path that gives you the most control regardless of when you update.

Frequently Asked Questions (FAQs)

WordPress 7.0 Is a Foundation, Not a Finish Line

Phase 3 of the Gutenberg project officially launched. The Collaboration phase begins with a modernized admin, an AI infrastructure layer, better design tools, and a cleaner pattern editing experience.

The honest complexity here is that 7.0 is a big update with real technical requirements.

The PHP 7.4 minimum will catch sites that haven’t kept up with server maintenance. The block API changes will surface issues in older plugins. The pattern editing defaults have changed in ways that affect sites built with synced patterns.

None of this is a reason to delay indefinitely, but it’s a reason to test before you update and to have a fresh backup you can restore from if you need to.

If something goes wrong mid-update, you need a restore point from right before you clicked update. Use Duplicator Pro to create a full backup in minutes, store it off-site with Duplicator Cloud, and restore with one click if anything goes sideways.

If this post got you thinking about keeping your site safe through the WordPress 7.0 transition, these guides are worth reading next.

• How to Update WordPress (And Stay Ahead of the Curve)
• How to Disable WordPress Auto Updates (3 Methods)
• How to Update Your PHP Version in WordPress
• WordPress 6.9 Update Guide: New Features + How to Update Safely
• How to Create a WordPress Staging Site (For Safe Testing)
• How to Restore WordPress From a Backup (In Less Than 5 Minutes)