WordPress 7.0 Arrives May 20: Native AI Client, DataViews Admin, and PHP-Only Blocks

WordPress 7.0 releases May 20, 2026. It is the most structurally significant WordPress release in years — a version number that historically signals a shift in direction, and 7.0 delivers one. Three changes stand out for developers.

WP AI Client: AI built into core

The biggest architectural addition is the WP AI Client, a unified interface in core for integrating external AI models. WordPress 7.0 ships with native support for three providers at launch: OpenAI, Anthropic (Claude), and Google (Gemini). Plugins and themes can hook into this client via a standardized API rather than each rolling their own integration.

This is a meaningful shift. For the past two years, AI in WordPress has meant a patchwork of competing plugins each maintaining their own API keys, prompt engineering, and UI patterns. The WP AI Client standardizes the plumbing. Users configure one API key per provider in the dashboard; all AI-aware plugins draw from the same session.

The API is designed to be provider-agnostic — request completion, ask for a JSON-structured response, pass an image for vision analysis — all through the same interface regardless of which model is backing it. That’s a genuinely useful abstraction for plugin developers.

DataViews replaces legacy admin tables

The classic WordPress admin list tables — the thing you see when you browse posts, pages, or users — have been replaced by DataViews. It’s a modern, React-based data grid that ships with sortable columns, filterable views, inline bulk actions, and a density toggle between list, grid, and table layouts.

This isn’t just cosmetic. Legacy list tables have been a known performance bottleneck on large datasets. DataViews is paginated by default, requests only the fields the current view needs, and is accessible from launch (keyboard navigation, screen reader labels). Sites with 100,000+ posts and custom admin screens should see meaningful speed improvements immediately.

PHP-only blocks

The block editor has, until now, required React for every block. WordPress 7.0 introduces PHP-only blocks — a way to register blocks that render server-side without any JavaScript bundle required. The Block API v4 spec allows a block to declare render_callback only, with no edit component, and it will appear in the block inserter with a live server-side preview in the editor.

This matters for performance and for the long tail of WordPress developers who aren’t comfortable writing React. Custom blocks for things like dynamic query outputs, server-rendered widgets, and template parts no longer require a JS build step.

What didn’t ship

Real-time collaboration (RTC) was cut from 7.0 after concerns about race conditions, server load, and memory efficiency at scale. It remains in development and is expected for a future release. Block-locking for collaborative editing, commenting on specific blocks (which does ship in 7.0), and async presence indicators are the closest features to RTC in this release.

Upgrading

WordPress 7.0 requires PHP 8.2 minimum. Sites on PHP 8.1 will stop receiving WordPress updates after this release. The automatic update flow will check PHP version before offering 7.0, so managed hosting environments on older PHP will be held back until the host updates.

Run wp core check-update to confirm eligibility, and wp core update once the release drops on May 20.