WordPress 7.0 has arrived, and its most important feature is not a feature in the usual sense. It is infrastructure. The release introduces a native AI connector inside WordPress itself, and that single addition reshapes how every plugin and theme in the ecosystem will work with artificial intelligence going forward.
The rest of the release is a steady set of refinements: a faster dashboard, a relocated command palette, editor changes for developers, and one notable feature that was cut. Here is the full breakdown, starting with the part that matters most.
The headline: a native AI connector
The biggest change in WordPress 7.0 is the new connector screen, a dedicated place in the WordPress admin where you activate AI providers. From there you can add API keys for Anthropic, Google, and OpenAI directly inside your WordPress installation.
To understand why this matters, consider how AI worked in WordPress until now. Every plugin or theme that wanted to use an AI model had to build its own connection point. One plugin asked for your API key in its settings. Another plugin asked again, somewhere else. A theme with AI features asked a third time. The result was a fragmented mess of duplicated configuration, with your credentials scattered across the dashboard.
WordPress 7.0 replaces that with a single source of truth. You connect your AI providers once, in the connector screen, and any plugin or theme that needs AI routes through that central connection. WordPress core handles the plumbing. Plugins and themes simply ask for access.
This is deliberately not a flashy, end-user-facing feature. There is no chatbot and no “write my post” button shipped in core. What 7.0 ships is the foundation that those features will be built on.
WordPress powers a very large share of the web, and it has just standardized AI access at the platform level. Instead of thousands of plugins each reinventing AI integration, the entire ecosystem now has a common base to build on. This is the groundwork for an AI-native CMS, delivered as quiet infrastructure rather than a headline feature.
A dashboard that finally feels like an app
The second thing you will notice in 7.0 is that the admin simply feels different.
The dashboard has a refreshed color scheme, but the more meaningful change is how pages load. WordPress 7.0 moves to a more JavaScript-driven view that behaves like a native application. Clicking through the admin no longer triggers a full page reload that repaints the entire dashboard. Instead, screens transition with smooth ease-in and ease-out animations. The practical effect is that WordPress feels noticeably quicker and more responsive, even where the underlying speed has not changed.
The command palette has also moved. Long available through Command+K on Mac, it is now anchored permanently to the toolbar in the upper-left corner, where it can be clicked to open. For now it is a simple input field. The interesting question is where it goes next. A persistent, always-accessible command palette is a natural home for more powerful interactions down the line: executing WordPress commands directly, running WP-CLI queries, or talking to a chatbot built on the new AI connector. The placement in 7.0 looks like a foundation being laid.
Two smaller wins round out the experience. The font library has been updated, making it easier to load and preview fonts in the appearance menu. And visual revisions now let you see content changes directly in the editor rather than compressed into a separate revisions panel.
What got cut: real-time collaboration
Not everything made it into 7.0. Real-time collaboration, the long-anticipated feature that would let multiple people edit the same WordPress content simultaneously, was removed from the roadmap for this release.
The stated reason is focus. Cutting the feature lets the development team concentrate on improving WordPress where the work is most needed. It is a reasonable call, and visual revisions, which did ship, may have originated from the same collaboration effort before being delivered on its own.
A feature being cut is not always bad news. Real-time collaboration is genuinely hard to do well, and shipping it half-finished would have been worse than delaying it. The decision signals a team prioritizing a stable release over a complete feature list.
Under the hood: changes for developers
Several 7.0 changes are aimed squarely at the people who build for WordPress.
The editor now runs inside an iframe. In principle, this isolation makes it easier for developers to build and style blocks and interfaces within the editor, since a block’s styles no longer collide with the editor’s own. Anyone who has fought to make a custom plugin look right inside the block editor will recognize why this is welcome.
Developers can also now build blocks with PHP alone when they only need server-side rendering. Previously, building blocks often meant mixing PHP and JavaScript even for tasks that did not require an interactive front end. For server-rendered blocks, that JavaScript requirement is gone.
Block visibility controls have also moved into core. WordPress 7.0 includes more built-in options for showing or hiding specific blocks on mobile, tablet, and desktop views. This is the kind of capability that previously required a separate plugin or a theme that happened to bundle it. Having it in core removes a common reason to reach for an add-on.
The developer-facing changes share a theme: removing friction. An iframe editor, PHP-only blocks, and core visibility controls each take something that used to require a workaround and make it a native part of the platform.
The slow rebuild of the WordPress admin
One quieter thread in 7.0 is the continued development of Data Views and Data Forms, the standardized interfaces for displaying and editing structured content in the admin.
Adoption is still not widespread, and most users will not notice them directly. But these experiences are the building blocks of what a modernized WordPress admin will eventually look like: an admin where content, data, and plugin interfaces are presented through a consistent, composable system. WordPress 7.0 continues to refine them. The full admin revamp they point toward is still ahead.
Accessibility also received a round of improvements across the admin, the kind of ongoing work that rarely makes headlines but consistently matters.
Before you update
If your host has not yet pushed WordPress 7.0 to your site, treat the gap as a testing opportunity rather than a waiting period.
Two approaches are worth using. The official WordPress Playground, at playground.wordpress.net, lets you experiment with WordPress 7.0 in your browser without touching your live site. And if your hosting provider offers staging environments, which the large majority now do, clone your site into staging and confirm that your theme and plugins behave correctly under 7.0 before the update reaches production.
A release that changes editor internals, adds an iframe layer, and introduces new core systems is exactly the kind of update worth verifying against your specific setup first.
Frequently Asked Questions
What is the WordPress 7.0 AI connector?
It is a new screen in the WordPress admin where you activate AI providers by adding API keys for Anthropic, Google, or OpenAI. Once connected, plugins and themes that use AI route through this single central connection instead of each requiring their own separate setup.
Does WordPress 7.0 include built-in AI writing tools?
No. The 7.0 release ships the connector infrastructure, not end-user AI features. There is no chatbot or content generator in core. The connector is the foundation that plugins, themes, and future WordPress features will build AI capabilities on.
Why does the WordPress 7.0 dashboard feel faster?
The admin moved to a more JavaScript-driven, app-like view. Navigating no longer triggers a full page reload of the entire dashboard. Screens transition with smooth animations instead, which makes the interface feel quicker and more responsive.
What happened to real-time collaboration?
It was removed from the WordPress 7.0 roadmap. The development team cut it to focus on other priorities for this release. Visual revisions, which lets you view content changes in the editor, did ship and may have come out of the same effort.
Should I update to WordPress 7.0 immediately?
Test first. Use the WordPress Playground at playground.wordpress.net to try 7.0 in your browser, or clone your site into a staging environment if your host provides one. Confirm your theme and plugins work correctly under 7.0 before updating your live site, since this release changes editor internals and adds new core systems.
What changed for WordPress developers in 7.0?
Three main things. The editor now runs in an iframe, which isolates block styling and makes building editor interfaces easier. Developers can build server-side-rendered blocks with PHP alone, without mixing in JavaScript. And block visibility controls for mobile, tablet, and desktop are now part of core.
