WordPress 7.0 is shaping up to be one of the most significant releases in recent years — or the most ambitious rebranding of what WordPress thinks it is. Put simply: version 7.0 represents the biggest shift in what WordPress actually wants to be in years.
We all know WordPress as a place where one person writes a post, hits publish, and occasionally sees a “someone else is editing this” lock screen. Version 7.0 introduces simultaneous editing reminiscent of Google Docs, a provider-agnostic AI layer, and more visual post revisions. Here’s what’s new and what it means for your workflow.
Status check
Current release date for WordPress 7.0: May 20th, 2026.
1. Real-time collaboration (RTC)
This is the flagship feature. You can now work on a post or page with others in real time and see their edits as they happen — much like Google Docs.
Key details:
– Uses CRDT (Conflict-free Replicated Data Types) for conflict resolution.
– Built on HTTP polling for broad host compatibility.
– Initially limited to 2 simultaneous collaborators to protect hosts.
– Hosts can provide their own transport/storage; JS filters let developers adjust polling.
– Disabled when metaboxes are present, nudging plugin devs to modernize implementations.
Should you care?
RTC is interesting but clearly aimed at enterprise users and newsrooms. Many individual writers might find it intrusive. It was intended to be enabled by default but is now opt-in after backlash. This is only the first iteration; it may evolve into something more broadly useful.
2. AI foundation (Connectors API + WP AI client)
Arguably the most forward-looking addition. Instead of shipping AI features, WordPress ships the scaffolding so plugins can deliver AI features.
What’s included:
– A new Connectors screen in wp-admin to manage API keys for OpenAI, Claude, Gemini, etc.
– A Connectors API for plugins that need external service credentials (not limited to AI).
– wp_ai_client_prompt(): a provider-agnostic PHP function to send prompts to LLMs.
Should you care?
This is smart architecture. WordPress positions itself as a neutral orchestration layer for AI services rather than offering a single WordPress-branded AI. Developers benefit from not handling credentials themselves and can build AI features more easily.
3. Visual revisions
Revisions get a visual overhaul and now live on the main post-editing screen with a color-coded preview system.
Notable changes:
– Timeline slider in the header for browsing versions.
– Color codes: yellow = modified, red = deleted, green = added.
– Minimap on the scrollbar to show where changes exist.
– “Restore” button replaces “Publish” when browsing history.
Should you care?
This makes revisions more approachable for non-developers, but it loses some power-user features of the old revisions screen: you no longer see source HTML, and you can’t compare any two arbitrary revisions (only a chosen past version vs. the one before it). It’s worth testing to see if the new UI fits your workflow.
Developer standouts
– PHP-only block registration: Create blocks with only PHP (no JS build step). Call register_block_type with autoRegister and a render_callback; WordPress auto-generates appropriate sidebar controls. Great for simple server-rendered blocks.
– Pattern overrides for custom blocks: Synced patterns can now allow instance-specific content while keeping layout consistent. Any block supporting Block Bindings can use Pattern Overrides — handy for client work.
– Client-side Abilities API: The JavaScript counterpart to 6.9’s server-side Abilities API. Includes @wordpress/abilities (state) and @wordpress/core-abilities (REST-connected). Mentions of browser agents and WebMCP hint at AI agent interoperability.
– Custom CSS per block instance: Add CSS directly in the block sidebar using declarations only (no selectors), with & for nesting.
Design and content editing wins
– Navigation overlays: Full control over mobile hamburger menus with customizable overlay template parts, built-in patterns, a toggle for always-visible submenus, and the ability to create pages directly from the Navigation block.
– Content-focused pattern editing: Patterns default to content-only mode, showing editable fields in a clean sidebar while preserving layout. Detach when you need full control — useful for client handoffs.
– Viewport-based block visibility: Show or hide any block per device type (desktop, tablet, mobile) from the toolbar — a feature that used to require plugins.
Command Palette reminder
WordPress now has a Command Palette available anywhere via ⌘K / Ctrl+K to quickly find settings and actions.
Good release or nah?
Overall, a good release. Some features (like RTC) may feel niche at first, but the direction is clear: WordPress is positioning itself for the “age of AI” by providing neutral, extensible infrastructure (Connectors API, wp_ai_client_prompt) rather than shipping opinionated AI features. The release contains meaningful developer and editor UX improvements that many will find useful.
I’m excited to see how AI connectors evolve and what developers build on top of this foundation. Congrats to everyone involved!
What do you think of WordPress 7.0? Is there anything in particular you’re excited about?
How to Speed Up Your WordPress Site
With some simple fixes, you can reduce loading times by 50–80% 🚀
By entering your email above, you’re subscribing to our weekly newsletter. You can change your mind at any time. We respect your inbox and privacy.