WordPress 7.0 is shaping up to be one of the biggest shifts in what the platform aims to be. This release isn't just adding features; it signals a reorientation toward collaboration, AI integration, and more visual content tools. Here’s a concise breakdown of what’s new and what it means for typical users and developers.
Release date: May 20, 2026.
1) Real-time collaboration (RTC) The headline feature: multiple people can now edit the same post or page in real time, with edits appearing live for collaborators. The implementation details matter:
- Uses CRDTs (Conflict-free Replicated Data Types) to resolve concurrent edits.
- Built on HTTP polling so it will work across many hosts without specialized infrastructure.
- Initially limited to two simultaneous collaborators, a choice made to limit resource and hosting impacts.
- Hosts can swap transport/storage providers; developers can tweak polling via JS filters.
- RTC is disabled if metaboxes are present, signaling plugin authors to modernize integrations.
Should you care? Real-time editing is clearly aimed at enterprise teams and newsrooms. For solo writers or small teams it may be unnecessary or even intrusive — many authors prefer drafts untouched while composing. The feature is currently opt-in after some community pushback, and it’s only the first iteration. Expect evolution over the next year or two.
2) AI foundation: Connectors API + WP AI client Rather than shipping a built-in “WordPress AI,” 7.0 provides the plumbing so others can build AI features consistently and securely. Key parts:
- A new Connectors screen in wp-admin to manage external API credentials (OpenAI, Anthropic, Google, etc.).
- Connectors API for plugins needing external service credentials; not limited to AI use cases.
- A provider-agnostic PHP function (wp_ai_client_prompt()) developers can call to send prompts to LLMs without handling provider-specific logic.
Should you care? If you’re a developer, yes — this makes building AI-powered features easier and more secure by centralizing credential handling and standardizing calls. For users, it keeps WordPress neutral: core doesn’t force a specific AI provider but enables an ecosystem of integrations.
3) Visual revisions Revisions move from a separate screen to an inline, visual experience on the editor screen. Highlights:
- New timeline slider in the header to browse versions.
- Color-coded changes: yellow for modified, red for deleted, green for added.
- Minimap on the scrollbar showing where changes occur.
- A Restore button appears when you’re viewing older versions.
Should you care? The UI is friendlier for non-technical users, but it drops some of the old revision strengths: you no longer see raw HTML/source code and you can’t arbitrarily compare any two historical revisions — comparisons are against the immediately preceding version. Power users who rely on granular diffs might find the new approach limiting; casual users may appreciate the visual simplicity.
Developer standouts
- PHP-only block registration: You can now register blocks with PHP only (register_block_type with autoRegister and a render_callback), removing the need for a JS build step for simple server-rendered blocks.
- Pattern overrides for custom blocks: Synced patterns can now let specific content change per instance while keeping layout consistent, and support is expanded to any block using Block Bindings.
- Client-side Abilities API: A JS counterpart to the server-side abilities from 6.9, split into @wordpress/abilities (state) and @wordpress/core-abilities (REST-connected). This hints at future agent/extension integrations.
- Custom CSS per block instance: A CSS field appears in the block sidebar where you write declarations (no selectors) and use & for nesting — useful for per-instance styling without custom classes.
Design and content editing wins
- Navigation overlays: Better control for mobile hamburger menus, with built-in patterns, an always-visible submenu toggle, and the ability to create pages from the Navigation block.
- Content-focused pattern editing: Patterns now default to content-only mode with a clean sidebar showing editable fields — handy for client handoffs and preventing accidental layout changes.
- Viewport-based block visibility: Show or hide blocks per device type (desktop, tablet, mobile) directly from the toolbar. What used to require plugins is now in core.
Command Palette reminder WordPress includes a Command Palette accessible with ⌘K / Ctrl+K that lets you jump to settings and editor actions from anywhere. It’s not new to 7.0, but it’s worth remembering as a fast navigation tool.
Verdict Overall, this is a strong release. Some features (RTC and visual revisions) will spark debate about usefulness for everyday users, but the broader direction is sensible: WordPress positioning itself as a neutral orchestration layer for AI services, improving collaboration tools, and making editing and developer workflows smoother. The Connectors API and PHP-only block registration are especially promising for extending WordPress without reinventing credentials or build tooling.
What are you most excited (or worried) about in WordPress 7.0?
