WordPress 7.0 feels like more than a routine update — it’s a statement about what WordPress intends to be going forward. This release pushes the platform toward collaboration, AI integrations, and a more visual editing experience. Some changes are incremental, others are foundational. Here’s a concise run-through of what’s new and why it matters.

Release date

Current planned release: May 20, 2026 (see WordPress Core announcements for updates).

1) Real-time collaboration (RTC)

The headline feature: simultaneous editing, similar to Google Docs. Multiple people can edit the same post or page at the same time and see live changes.

Key technical and UX details:
– Uses CRDT (Conflict-free Replicated Data Types) to resolve editing conflicts.
– Built on HTTP polling so it works across a wide range of hosting environments.
– Initially limited to two simultaneous collaborators to reduce load on smaller hosts.
– Hosts can swap transport/storage implementations, and JS filters allow developers to tweak polling intervals.
– RTC is disabled when metaboxes are present, pushing plugin authors toward updated implementation patterns.

Should you care?
It’s a compelling enterprise/newsroom feature, but its usefulness for solo bloggers or small teams is unclear. It was intended to be enabled by default, but backlash made it opt-in. This is the first iteration — expect gradual improvements and broader adoption if hosts and plugin ecosystems adapt.

2) AI foundation: Connectors API + WP AI client

Rather than shipping built-in AI features, WordPress 7.0 provides the framework for AI integrations.

What’s included:
– A new Connectors screen in wp-admin for managing API keys (OpenAI, Anthropic, Gemini, etc.).
– A Connectors API plugins can use to store and manage external-service credentials.
– A provider-agnostic PHP function (wp_ai_client_prompt()) that sends prompts to configured LLMs without each plugin re-implementing credential handling.

Should you care?
Yes, especially if you’re a developer. This architecture keeps WordPress neutral while making it much simpler to build AI-powered tools. For users it means plugins can integrate with LLMs more safely and consistently.

3) Visual revisions

The classic revisions page is replaced with an inline, more visual history UI on the post-edit screen.

New UX highlights:
– A timeline slider in the header to browse versions.
– Color-coded changes (yellow = modified, red = deleted, green = added).
– A minimap on the scrollbar showing where changes occur.
– A Restore button appears when viewing older versions.

Caveats:
– You see rendered content rather than source HTML.
– You cannot compare any two arbitrary revisions; comparisons are to the immediately preceding version only.

Should you care?
For non-technical editors this is more approachable. Long-time revision users who rely on HTML diffs or flexible comparisons may find it limiting. Worth trying to see if it fits your workflow.

Developer standouts

PHP-only block registration
– You can now register blocks using only PHP (no JS build step). Use register_block_type with autoRegister and a render_callback for server-rendered blocks that don’t need interactivity.

Pattern overrides for custom blocks
– Synced pattern capabilities extend beyond basic core blocks: any block that supports Block Bindings can participate in pattern overrides, which helps with repeatable layouts that need instance-specific content.

Client-side Abilities API
– A JavaScript counterpart to the server-side Abilities API introduced earlier. Two packages: @wordpress/abilities (state-only) and @wordpress/core-abilities (REST-connected). This hints at future agent/AI interoperability and richer capability checks in the UI.

Custom CSS per block instance
– Each block sidebar can now include a small CSS input for instance-specific styles. You write declarations only (no selectors) and can use & for nesting.

Design and content editing wins

Navigation overlays
– More control over mobile hamburger menus with customizable overlay template parts, built-in patterns, submenu visibility toggles, and the ability to create pages directly from the Navigation block.

Content-focused pattern editing
– Patterns now default to a content-only editing mode, showing editable fields in a simplified sidebar. You can detach if you need the full block tree. This is particularly handy for client handoffs where layout safety matters.

Viewport-based block visibility
– Show or hide blocks per device type (desktop, tablet, mobile) directly from the toolbar — functionality that previously required plugins.

Command Palette reminder

WordPress includes a global Command Palette (invoke with ⌘K / Ctrl+K) for quickly finding settings, actions, and navigation from anywhere in the admin.

Verdict: good release

Overall, 7.0 is a strong release. Not every new feature will excite every user, but the direction is clear: WordPress is positioning itself as a neutral orchestration layer for modern workflows, especially around collaboration and AI. The Connectors API in particular opens a lot of possibilities for third-party developers without forcing WordPress to pick favorites.

I’m optimistic about how connectors and RTC will evolve, and about the kinds of plugins and tools developers will build on top of these foundations. Congratulations to everyone who contributed.

What do you think? Which feature are you most excited about?

Bonus: site speed crash course

If you want to speed up your WordPress site, consider joining our crash course. Small changes can often reduce load times by 50–80%. By signing up you’ll receive weekly tips and resources — you can unsubscribe anytime.

WordPress 7.0 is shaping up to be one of the biggest directional updates in years — not just a set of incremental tweaks, but a statement about what WordPress wants to be moving forward.

Release date: May 20, 2026.

High-level summary

This release adds real-time collaboration, a neutral AI integration layer, more visual revisions, and a collection of developer and editing refinements. Some changes are clearly aimed at larger organizations (newsrooms, enterprise), while others are practical quality-of-life upgrades for everyday site builders and developers.

1) Real-time collaboration (RTC)

The marquee feature of 7.0 is live, simultaneous editing for posts and pages. It behaves much like Google Docs: multiple people can edit the same document and see updates in real time. Under the hood WordPress uses CRDTs (conflict-free replicated data types) for merging changes and relies on HTTP polling to maintain broad hosting compatibility.

Key limitations and details:
– Initially limited to two concurrent collaborators to reduce load on hosts.
– Hosts can replace the transport and storage backends; developers can adjust polling intervals via JS filters.
– The feature is disabled when metaboxes are present, which encourages plugin authors to update how they integrate with the editor.
– After pushback, real-time collaboration will be opt-in rather than enabled by default.

Who should care?
It’s a clear win for teams and editorial workflows, but many solo writers and small teams may find it unnecessary or even intrusive. This is an early iteration; expect it to expand and mature over time.

2) AI foundation: Connectors API + WP AI client

Rather than shipping a single WordPress-branded AI, 7.0 provides the scaffolding for many AI integrations. The idea is neutrality and extensibility.

What’s included:
– A new Connectors screen in wp-admin to manage API keys (OpenAI, Anthropic, Google, etc.).
– A Connectors API plugins can use to store and access external service credentials, not limited to AI providers.
– A provider-agnostic PHP helper (wp_ai_client_prompt()) that developers can call to send prompts to an LLM without wiring provider-specific code.

Who should care?
Developers building AI features will appreciate not having to reinvent credential handling or client plumbing. For site owners, this opens the door to many future AI plugins that rely on a consistent core API.

3) Visual revisions

Revisions are now integrated into the main editor with a more visual interface: a timeline slider, color-coded change highlights (yellow = modified, green = added, red = deleted), a minimap on the scrollbar, and a Restore button when browsing past versions.

Trade-offs:
– The new view shows rendered content rather than raw HTML/source.
– You can only compare a selected revision against its immediate predecessor, not any two arbitrary revisions like the old revisions screen allowed.

Who should care?
Non-developers may find the new UI friendlier for spotting content changes. Power users who relied on HTML diffs or flexible comparisons might miss the older capabilities. Worth trying to see which workflow you prefer.

Developer features to note

– PHP-only block registration: You can now create blocks without a JS build step using register_block_type with the autoRegister flag and a render_callback. Great for simple server-rendered blocks.

– Pattern overrides for custom blocks: Pattern overrides are no longer restricted to a short list of block types — any block supporting Block Bindings can participate, which helps control instance-specific content while keeping layout synced.

– Client-side Abilities API: A JavaScript counterpart to the server Abilities API, split into @wordpress/abilities (state-only) and @wordpress/core-abilities (REST-connected). Mentions of browser agents and WebMCP hint at future agent/AI interoperability.

– Custom CSS per block instance: Blocks now have a CSS input in the sidebar where you can write declaration-only rules (use & for nesting). Handy when you need scoped styling without editing theme CSS.

Design and editing improvements

– Navigation overlays: More control over mobile hamburger menus with overlay template parts and built-in patterns; you can toggle submenu visibility and even create pages from the Navigation block.

– Content-focused pattern editing: Patterns now default to a simplified, content-only editing mode that exposes only editable fields in the sidebar. You can detach to edit the full block tree if needed — good for client handoffs.

– Viewport-based block visibility: Toggle block visibility per device (desktop, tablet, mobile) from the toolbar — functionality many sites previously needed plugins for is now in core.

Command Palette reminder

WordPress includes a Command Palette accessible with ⌘K / Ctrl+K from anywhere in the admin. It’s a fast way to jump to settings, blocks, and other actions.

Verdict: good release

Overall, 7.0 is a solid release that clarifies WordPress’ direction: it wants to be an extensible, neutral orchestration layer — especially around AI — while improving collaboration and editing ergonomics. Some features (RTC, visual revisions) are early iterations and come with trade-offs, but the underlying platform choices (Connectors API, php-only blocks, per-block CSS) are pragmatic and useful.

I’m excited to see how developers leverage the AI connectors and how real-time collaboration evolves. If you’re a developer or run a multi-person editorial workflow, there’s plenty to test. Solo creators may selectively adopt features as they mature.

What about you? Which new feature are you most interested in trying?

P.S. If you want help speeding up a WordPress site, consider our crash course — small changes can often cut load times dramatically.