WordPress 7.0 is shaping up as one of the more consequential updates in years — not just in features, but in intent. This release signals a shift in what WordPress aims to be: a collaborative, extensible platform that embraces AI and modern editing workflows while remaining host-friendly.
Release date
May 20, 2026.
Here are the headline changes and what they mean for typical users, developers, and teams.
1. Real-time collaboration (RTC)
This is the marquee feature. WordPress now supports simultaneous editing of posts and pages so multiple people can see edits as they happen — very Google Docs–like.
Key technical points:
– Conflict resolution uses CRDTs (Conflict-free Replicated Data Types).
– Transport is built on HTTP polling to maximize compatibility with many hosts.
– Initially limited to two concurrent collaborators to reduce load and protect shared hosting environments.
– Hosts can replace the underlying transport/storage; developers can tweak polling via JS filters.
– RTC is disabled if metaboxes are present, nudging plugin authors toward updated implementations.
Should you care? RTC is most useful for newsrooms, editorial teams, or enterprise setups where synchronous collaboration matters. For solo authors it’s less appealing (and can feel intrusive). The feature is opt-in for now, and this first iteration focuses on safety and broad compatibility rather than full Google-Docs parity.
2. AI foundation: Connectors API and wp_ai_client_prompt()
Instead of shipping a single WordPress AI feature, 7.0 provides the plumbing so plugins and tools can safely hook into external AI services.
What’s included:
– A Connectors screen in wp-admin to manage API keys for OpenAI, Anthropic, Gemini, etc.
– A Connectors API that plugins can use for any external-service credentials (not just AI).
– A provider-agnostic helper, wp_ai_client_prompt(), so developers can send prompts to an LLM without wiring every provider themselves.
Should you care? If you develop plugins or plan AI integrations, this is huge: WordPress becomes a neutral orchestration layer that handles credentials and basic communication, simplifying secure integrations and encouraging interoperability rather than a single “WordPress AI” product.
3. Visual revisions
Revisions get a major UX refresh and are now available directly in the post editor as a visual timeline.
New things:
– A timeline slider in the editor header to browse versions.
– Color-coded highlights: yellow for modified, red for deleted, green for added.
– A minimap on the scrollbar showing where changes occur.
– A Restore button appears when browsing history.
Caveats:
– The new UI shows rendered content, not raw HTML/source.
– You can’t compare two arbitrary revisions side-by-side — it compares a selected past version to its predecessor.
Should you care? The visual layout is more approachable for non-technical users, but power users who relied on HTML-level diffs or flexible comparisons may miss the old behavior. Worth testing to see whether it fits your workflow.
Developer standouts
– PHP-only block registration: You can now register blocks using only PHP (register_block_type with autoRegister and a render_callback). No build step required for simple server-rendered blocks.
– Pattern overrides for custom blocks: Synced patterns can now preserve layout while allowing instance-level content edits for any block that supports Block Bindings.
– Client-side Abilities API: The JS counterpart to the server Abilities API is now available via @wordpress/abilities and @wordpress/core-abilities, helping client code respect user capabilities and hinting at future agent/extension integrations.
– Custom CSS per block instance: Add declarations directly in the block sidebar (no selector needed; use & for nesting). Handy for fine-tuning styles without touching theme files.
Design and content editing improvements
– Navigation overlays: More control over mobile hamburger menus, built-in overlay patterns, submenu visibility toggles, and the ability to create linked pages directly from the Navigation block.
– Content-focused pattern editing: Patterns default to a content-only mode so clients can edit text/images without altering the overall structure; you can detach if you need full block access.
– Viewport-based block visibility: Show or hide any block by device type (desktop, tablet, mobile) from the toolbar — functionality many sites previously required a plugin for.
Command palette
WordPress includes a global Command Palette accessible with ⌘K / Ctrl+K to quickly search settings, pages, and editor actions from anywhere in the admin.
Verdict: good release, with a clear direction
Overall, 7.0 is a strong release. Some features are clearly aimed at larger teams and enterprises, but many changes benefit smaller sites and developers too. The real win is the strategic approach to AI: instead of choosing a single path, WordPress provides neutral infrastructure so the ecosystem can innovate.
I’m particularly excited to see how connectors and provider-agnostic APIs evolve — they could unlock a wide range of safe, interoperable AI features without centralizing control.
What do you think? Which 7.0 features are you most eager to try?
P.S. If you want to speed up your WordPress site, look for crash courses and guides on performance optimization — even small changes can significantly reduce load times.
