WordPress 7.0 is one of the most notable updates in years — not just a set of incremental changes, but a clear redefinition of what WordPress wants to be.
If you think of WordPress as the place where one person writes a post and clicks Publish, 7.0 nudges that image in new directions: real-time collaboration, a built-in but provider-agnostic AI layer, and a more visual approach to post revisions. Below is a concise rundown of the main additions and what they mean for writers, site owners, and developers.
Release date
WordPress 7.0 is scheduled for May 20, 2026.
1. Real-time collaboration (RTC)
The headline feature is real-time editing: multiple people can work on the same post or page simultaneously and see changes as they happen — very Google Docs–style.
Key technical details:
– Conflict resolution uses CRDTs (Conflict-free Replicated Data Types).
– The initial transport mechanism uses HTTP polling for maximum host compatibility.
– The alpha implementation limits collaboration to two simultaneous users to reduce hosting strain.
– Hosts can replace the transport/storage layer; developers can tweak polling intervals via JavaScript filters.
– Real-time editing is disabled when traditional metaboxes are present, signaling plugin authors to adapt their approaches.
Should you care?
This feature seems aimed at enterprise teams and newsrooms rather than individual bloggers. Some users will love it; others — especially solitary writers who prefer drafts untouched — may find it intrusive. It was originally planned to be on by default, but pushback moved it to opt-in. This is a first iteration; expect the feature to evolve over time.
2. AI foundation: Connectors API and WP AI client
Rather than shipping a single WordPress-branded AI assistant, 7.0 includes the infrastructure to let developers and site owners plug in AI services safely and consistently.
What’s included:
– A new Connectors screen in wp-admin for managing API keys to services like OpenAI, Anthropic, Gemini, and others.
– A Connectors API that plugins can use whenever they need external credentials — not limited to AI but ideal for it.
– A provider-agnostic PHP helper (wp_ai_client_prompt()) to send prompts to LLMs without each plugin managing credentials and provider specifics.
Should you care?
If you’re a developer, this is a big convenience: the core handles the plumbing so plugins can focus on features. For site owners, it promises a neutral orchestration layer for AI tools — WordPress won’t push one vendor, but will make it easier to connect to many.
3. Visual revisions
Revisions get a major UI overhaul, moving from a separate screen to an inline, visual timeline in the editor.
What’s new:
– A timeline slider in the post header to browse versions.
– Color-coded changes: yellow for modified, red for deleted, green for added.
– A minimap on the scrollbar showing where changes live.
– A Restore button appears when viewing past versions.
Limitations to be aware of:
– You see rendered content, not the raw HTML/source.
– You cannot compare any two arbitrary revisions — comparisons are between the selected version and the one immediately before it.
Should you care?
The UI makes revisions more approachable for non-technical users, but power users who relied on old revision comparisons or raw source diffs may find it less useful. Worth trying to see if it fits your workflow.
Developer standouts
PHP-only block registration
– You can now register blocks without a JavaScript build step. Use register_block_type with autoRegister and a render callback to create server-rendered blocks with automatically generated sidebar controls for basic attributes. Great for simple blocks that don’t need interactivity.
Pattern overrides for custom blocks
– Synced patterns can now let specific content change per instance while keeping layout consistent. Previously limited to a handful of core blocks, this now works for any block that supports Block Bindings — a boon for client work and reusable, controlled layouts.
Client-side Abilities API
– The JavaScript counterpart to the server-side Abilities API includes packages for pure state and REST-connected abilities. Mentions of browser agents and extensions hint at future AI agent integrations.
Custom CSS per block instance
– Blocks can now accept custom CSS declarations in the sidebar. You write CSS properties (no selector) and use & for nesting, making small per-block tweaks easy without editing theme files.
Design and content editing wins
Navigation overlays
– Full control over mobile hamburger menus via overlay template parts, with built-in patterns and toggles for submenu visibility. You can create pages directly from the Navigation block.
Content-focused pattern editing
– Patterns default to a content-only editing mode that shows editable fields in a simplified sidebar, reducing the chance clients will break layouts. You can detach to get full block control if needed.
Viewport-based block visibility
– Show or hide blocks per device (desktop, tablet, mobile) directly from the toolbar. Previously done with plugins, this is now native.
Command palette reminder
WordPress includes a Command Palette accessible from anywhere with ⌘K / Ctrl+K to quickly find settings, pages, and actions. It’s not brand new but worth remembering.
Final verdict
Overall, 7.0 is a meaningful release. Some features (real-time collaboration, visual revisions) will attract debate, and their usefulness depends on your workflow. The AI connectors and developer-focused improvements are more clearly forward-looking: they position WordPress as a neutral orchestration layer for third-party AI services and make it easier for developers to build without reimplementing common integrations.
Is this a must-upgrade? If you rely on collaborative editing or plan to add AI features, yes. If you run a small static blog, the changes are interesting but not essential right away. Either way, the release signals the project’s priorities: collaboration, extensible AI integration, and smoother editing workflows.
What do you think of WordPress 7.0? Which feature are you most curious to try?