WordPress 7.0: What’s New and Why It Matters

WordPress 7.0 is the biggest WordPress release in years. Scheduled for May 20, 2026, it moves WordPress from a traditional content management system into an AI-ready, collaborative platform.

This is not a routine bug fix update. WordPress 7.0 introduces built-in AI infrastructure, visual revisions, new core blocks, a refreshed admin dashboard, responsive editing controls, and significant performance improvements under the hood.

Whether you run a blog, an online store, a business website, or manage sites for clients, this update changes how you work inside WordPress. Here is everything you need to know before you hit that update button.

Key Features in WordPress 7.0

For those who want the highlights first, here is what WordPress 7.0 brings to the table.

Built-in AI infrastructure adds a new Settings > Connectors screen, the WP AI Client, and the Abilities API. You can now connect your WordPress site to AI providers like OpenAI, Google Gemini, or Anthropic Claude from one central location, and every compatible plugin on your site can use that connection.

Visual revisions replace the old text-based comparison screen with a color-coded visual view that shows changes exactly as they appear in the editor.

New core blocks for Breadcrumbs and Icons eliminate the need for separate plugins to add these common features.

Refreshed admin dashboard with a modern color scheme, smoother transitions between screens, and DataViews replacing old list tables.

Responsive block visibility lets you show or hide any block based on screen size (mobile, tablet, or desktop) without custom CSS.

Performance improvements include faster block rendering, client-side media processing, and React 19 under the hood.

PHP minimum version is now 7.4, with PHP 8.3 or higher recommended for best performance.

Let me break down each of these in detail.

AI Infrastructure Built Into WordPress Core

This is the headline feature of WordPress 7.0, and it changes the relationship between WordPress and AI permanently.

Until now, every AI-powered WordPress plugin had to build its own connection to AI services. If you used an AI content writer, an AI SEO tool, and an AI image generator, each one needed its own API key setup, its own settings page, and its own way of communicating with the AI provider. That meant duplicate work, scattered credentials, and no consistency.

WordPress 7.0 fixes this with three connected systems.

The Connectors Screen (Settings > Connectors)

After updating to WordPress 7.0, you will see a new page under Settings > Connectors. This screen shows a list of AI providers you can connect to your site. By default, it includes three providers: OpenAI (ChatGPT), Google (Gemini), and Anthropic (Claude).

To connect a provider, you activate its connector plugin and enter your API key. Once connected, every compatible plugin on your site can use that provider without needing separate configuration.

This is a big deal for site owners who use multiple AI tools. Instead of entering your OpenAI key in five different plugins, you enter it once. All your AI-powered plugins share the same connection.

WordPress 7.0 ships with official provider plugins for OpenAI, Google, and Anthropic. Support for additional third-party providers is planned for WordPress 7.1.

The WP AI Client

The WP AI Client is the engine behind the Connectors screen. It is a provider-agnostic PHP API that lets any plugin send prompts to AI models and get results through a single, consistent interface.

For developers, this means you can write AI-powered features without worrying about which AI provider the site owner has chosen. Your code stays the same whether the site runs on Claude, GPT, or Gemini. WordPress handles the translation.

For site owners, this means you can switch AI providers without breaking your plugins. If you start with OpenAI but later want to move to Anthropic, you just change the connection in Settings > Connectors. Your plugins keep working.

The WP AI Client supports text generation, structured JSON responses, temperature controls, and model preferences. Plugin developers can specify preferred models, but the system will fall back to whatever compatible model is available on the site.

The Abilities API

The Abilities API is the part that makes WordPress 7.0 truly future-ready. It lets plugins, themes, and WordPress core expose their capabilities in a format that AI agents can discover and use.

In simple terms: your WordPress site can now tell an AI agent what it is capable of doing. A WooCommerce store can expose product management abilities. A content plugin can expose publishing abilities. An SEO plugin can expose optimization abilities.

This opens the door for AI assistants that can interact with your entire WordPress site, not just generate text, but actually take actions like creating posts, updating products, or managing settings.

WordPress 7.0 also includes an MCP (Model Context Protocol) Adapter. MCP is an open standard for how AI assistants communicate with external tools. With this adapter, any MCP-compatible AI client can discover and interact with your WordPress site’s registered abilities.

What AI Features Work Right Now?

It is important to understand that the AI infrastructure in WordPress 7.0 is a foundation, not a finished product. When you connect an AI provider, here is what becomes possible for plugins that support it:

Smart content suggestions for readability and SEO improvements. Auto-generated alt text for images. One-click content summaries and excerpts. AI-powered meta description generation. Translation suggestions for multilingual sites. Custom CSS and block pattern generation from natural language.

These features require compatible plugins. The Connectors screen itself does not add AI features to your editor automatically. It provides the plumbing that plugins use to deliver AI-powered functionality.

If you do not connect an AI provider, your site works exactly like it did before. AI in WordPress 7.0 is entirely optional.

Visual Revisions

WordPress has always had a revision system. Every time you save a post or page, WordPress stores a copy so you can go back to an earlier version. But comparing revisions in older versions of WordPress meant looking at raw HTML or plain text side by side. For most users, this was confusing and unhelpful.

WordPress 7.0 replaces that system with visual revisions for pages. You can now see exactly how your content looked at each saved version, rendered as it would appear in the editor, not as raw code.

Changes are highlighted with a color-coded system. Green marks new content that was added. Red marks content that was deleted. Yellow highlights sections that were modified. Block-level changes (like moved or restructured blocks) get their own visual treatment.

A mini-map along the scrollbar shows where changes exist in long documents. You can jump directly to modified sections without scrolling through the entire page. The sidebar displays a summary of changes for each revision.

When you find the version you want to restore, the “Update” button changes to a “Restore” button. One click brings back the previous version.

This feature is especially useful for content-heavy sites where posts go through multiple rounds of editing. If someone accidentally deletes a pricing table, removes an image gallery, or reformats a section incorrectly, you can see the visual difference immediately and restore the correct version.

Currently, visual revisions are available for pages. Support for posts and other post types is expected in future releases.

New Core Blocks: Breadcrumbs and Icons

WordPress 7.0 adds two blocks that users have been requesting for years. Both previously required third-party plugins, so having them built into core means one fewer plugin to install and maintain.

Breadcrumbs Block

Breadcrumbs are the small navigation links you see near the top of pages. They show the path to your current location on the site. For example: Home > Blog > WordPress Tips > This Post.

The new Breadcrumbs block is not just decorative. It works with custom post types, archives, and query loops out of the box. It automatically reflects your site’s navigation hierarchy and supports the theme.json schema, so it adapts to your site’s global styles without custom CSS.

For SEO, breadcrumbs help search engines understand your site structure and can appear as breadcrumb trails in search results. Having this built into WordPress core means you no longer need plugins like Yoast or Rank Math just for breadcrumb functionality (though those plugins offer many other features).

Developers also get filters to control the output, making the block flexible enough for custom implementations.

Icons Block

The Icons block lets you insert SVG icons directly into your content from a curated, built-in icon library. No plugin needed, no custom code, no manual SVG uploads.

You can search the library, select an icon, adjust its size and color, and drop it anywhere in your layout. This is useful for feature lists, service descriptions, call-to-action sections, and UI elements.

The initial icon library is smaller than third-party options like Font Awesome. But it covers the icons most commonly used by WordPress site owners. Extensibility for third-party icon collections is planned for WordPress 7.1.

Block Editor Improvements

Beyond the two new blocks, WordPress 7.0 brings several improvements to the block editor that affect everyday content creation.

Responsive Block Visibility

You can now show or hide individual blocks based on screen size without writing CSS or installing a plugin. The visibility options include mobile, tablet, and desktop.

This is a feature that page builder plugins like Elementor have offered for years. Having it in core means every WordPress site gets this capability natively.

For example, you might want to show a simplified version of a pricing table on mobile while showing the full version on desktop. Or hide a large decorative image on phones to improve load speed.

Improved Heading Block

Each heading level (H1 through H6) is now its own block variation. Instead of inserting a generic Heading block and then changing the level from a dropdown, you can pick the specific heading level directly from the block inserter.

This seems small, but it encourages better content structure. Writers and editors now select heading levels as intentional content elements rather than formatting afterthoughts.

Cover Block Video Backgrounds

Video embeds can now be used as backgrounds in the Cover block. This opens up options for more dynamic hero sections and landing pages without custom code.

Responsive Grid Block

The Grid block now handles responsiveness natively. Grid-based layouts adapt more smoothly across screen sizes without manual breakpoint configuration.

Gallery Lightbox

The Gallery block now includes built-in lightbox support. Visitors can click on gallery images and browse through them in an overlay viewer. This previously required a plugin or custom JavaScript.

Improved Image Editing

Image editing in the editor has been revamped. Cropping, rotating, and zooming are now easier and more intuitive. The Image block also supports focal point controls and aspect ratio adjustments for wide and full-width alignments.

HTML Block Redesign

The HTML block now works as a modal-based editor with separate tabs for HTML, CSS, and JavaScript. This makes it more useful for custom elements that need all three languages working together in a single block.

Per-Block Custom CSS

You can now add custom CSS to individual block instances directly, without needing to create a custom class or go to the Site Editor’s global Custom CSS. This makes quick style overrides much simpler, especially for content editors who do not have access to the Site Editor.

Font Library for All Themes

The Font Library screen is now available globally for all themes, including classic PHP-based themes. Previously, it was mostly limited to block themes. You can browse Google Fonts, upload local font files, and manage typography collections regardless of which theme you use. You can find it at Appearance > Fonts.

Command Palette Shortcut

The command palette is now accessible from the upper admin bar using Ctrl+K (Windows/Linux) or Cmd+K (Mac). It lets you search for and jump to any screen, setting, or action in wp-admin without navigating through menus. This is a significant time-saver for power users who manage content and settings frequently.

Refreshed Admin Dashboard

The WordPress admin interface has not had a meaningful visual update since 2013. WordPress 7.0 changes that with a modern refresh that makes the dashboard feel like a current web application.

Updated Visual Design

The dashboard gets a new default color scheme, updated typography, and cleaner spacing. The layout structure stays familiar, so you will not feel lost. But the overall look is lighter, more modern, and more consistent with the block editor’s design language.

DataViews

DataViews is a new system that replaces the traditional WordPress list tables (the tables you see on Posts, Pages, and Users screens) with a modern, React-based interface. The experience includes inline filtering without page reloads, consistent spacing and alignment, and a unified look that connects the admin panels with the editor.

Smooth View Transitions

Cross-document view transitions replace the old hard page reloads when moving between admin screens. Clicking through settings pages, post lists, and editor views now feels like navigating a single-page application rather than loading separate pages.

Performance Improvements

WordPress 7.0 includes several under-the-hood performance optimizations.

Client-side media processing moves some image handling tasks from the server to the browser. This reduces server load during image uploads and can speed up the media workflow.

Faster block rendering on both the editor and front-end through optimized rendering pipelines.

React 19 upgrade brings performance improvements to the block editor. This is a potentially breaking change for custom blocks built on older React APIs, so plugin developers should test thoroughly.

PHP-only blocks can now be registered and rendered entirely in PHP without any JavaScript build pipeline. This is a significant improvement for theme developers who want to ship custom blocks with lower overhead.

PHP Requirements

WordPress 7.0 requires a minimum of PHP 7.4. Sites running PHP 7.2 or 7.3 will not be able to update until their PHP version is upgraded.

For best performance, PHP 8.3 or higher is recommended. Most quality hosting providers already support PHP 8.3, but check with your host before updating.

Real-Time Collaboration (Removed from 7.0)

One important note: real-time collaboration was originally planned as a headline feature of WordPress 7.0. It would have allowed multiple users to edit the same post or page simultaneously, similar to Google Docs.

However, on May 8, 2026, the WordPress core team announced that real-time collaboration has been removed from the 7.0 release due to performance issues and bugs discovered during the testing phase. The feature is not cancelled. Work continues, and it is expected to ship in a future version.

This is worth knowing because many early previews and beta articles highlighted real-time collaboration as a primary feature. If you were planning your workflow around this capability, you will need to wait a bit longer.

How to Prepare for the WordPress 7.0 Update

Major WordPress updates require careful preparation, especially if your site uses custom themes, multiple plugins, or an eCommerce setup. Here is how to update safely.

Step 1: Back up your entire site. Create a full backup of your database and files before doing anything else. Use your hosting provider’s backup tool or a plugin like UpdraftPlus.

Step 2: Check your PHP version. WordPress 7.0 requires PHP 7.4 or higher. Log into your hosting dashboard and verify your PHP version. If you are below 7.4, upgrade PHP first (on a staging site to test compatibility).

Step 3: Update all plugins and themes first. Make sure every plugin and theme on your site is running its latest version. Major plugins like WooCommerce, Yoast SEO, ACF, and Elementor have already shipped WordPress 7.0 compatibility updates.

Step 4: Test on a staging site. Clone your live site to a staging environment. Apply the WordPress 7.0 update on staging first. Check that your theme displays correctly, all plugins work without errors, forms, checkout flows, and membership features function properly, custom blocks render as expected, and the admin dashboard loads without visual issues.

Step 5: Review plugin compatibility. Check the “Tested up to” version on each plugin’s WordPress.org page. If a plugin has not been tested with WordPress 7.0 yet, contact the developer or look for alternatives.

Step 6: Update your live site. Once staging testing is complete and everything works, apply the update to your production site. Monitor the site for the first few hours after updating to catch any issues quickly.

Step 7: Test AI Connectors (optional). If you want to use the new AI features, go to Settings > Connectors after updating. Activate a provider plugin (OpenAI, Google, or Anthropic), enter your API key, and test with a compatible AI plugin.

What WordPress 7.0 Means for Plugin and Theme Developers

If you build WordPress plugins or themes, here are the key changes to pay attention to.

AI Client API: The wp_ai_client_prompt() function is the recommended entry point for any AI-powered functionality. It handles provider selection, error handling, and WordPress conventions automatically. If your plugin currently has its own AI integration, consider migrating to the core API for consistency and easier maintenance.

Abilities API: Register your plugin’s capabilities so AI agents can discover and interact with them. This is what makes your plugin “AI-ready” in the WordPress 7.0 ecosystem.

Connectors API: If you are building a plugin that connects to an external AI provider, register with the WP AI Client’s provider registry. The Connectors API will automatically create the admin UI for your provider.

React 19: The block editor now runs on React 19. Test all custom blocks for compatibility. Breaking changes are possible if your blocks rely on deprecated React APIs.

PHP-only blocks: You can now register blocks entirely in PHP without a JavaScript build step. WordPress auto-generates inspector controls for common attribute types.

Iframe post editor: The post editor now runs inside an iframe by default, isolating theme styles from editor styles. This reduces visual conflicts but may affect plugins that inject styles or scripts into the editor.

What’s Coming After WordPress 7.0

WordPress 7.0 is the first release of the 7.x cycle. Here is what is planned next.

WordPress 7.1 (August 2026): Expected to bring third-party icon collection support for the Icons block, expanded Connectors API for additional AI providers, and the first stable implementation of real-time collaboration.

WordPress 7.2 (December 2026): Planned to include expansion of collaboration features and early steps toward native multilingual support in WordPress core.

Frequently Asked Questions