WordPress 7.0: Everything You Need to Know About the Biggest Release in Years

WordPress 7.0 is shaping up to be the most significant WordPress release since Gutenberg first landed in version 5.0 back in 2018. This is the release that officially delivers Gutenberg Phase 3: Collaboration, bringing real-time multi-user editing, native AI infrastructure, a refreshed admin interface, and a stack of new blocks and design tools into WordPress core.

Originally scheduled for April 9, 2026, to coincide with WordCamp Asia in Mumbai, the release was pushed back after testing revealed that the real-time collaboration feature's database architecture needed rework. A revised release schedule is expected by April 22, with the final release now anticipated for mid-to-late May 2026. The delay is a good sign. It means the core team is prioritizing stability over spectacle, which is exactly what enterprise teams need from a platform update this large.

Here is everything you need to know about what is coming in WordPress 7.0.

Real-Time Collaboration

The headline feature of WordPress 7.0 is real-time collaboration. Multiple users can now edit the same post or page simultaneously, with live cursors, presence indicators, and instant content syncing. If you have ever wished your WordPress editor worked like Google Docs, this is it.

Under the hood, the feature is powered by Yjs, an open-source CRDT (Conflict-free Replicated Data Type) engine that handles conflict resolution when multiple people edit the same content at the same time. The default sync method is HTTP polling, chosen specifically for compatibility with standard hosting environments. Hosts and plugin developers can upgrade to WebSocket-based syncing for faster real-time performance.

The collaboration feature also includes offline editing with automatic sync when the connection is restored, and real-time editorial Notes that let editors leave contextual comments directly within the editing experience.

For the initial rollout, real-time collaboration is opt-in. Site administrators can enable it from the settings screen, giving teams time to test the feature in staging before rolling it out to production.

For enterprise editorial teams, this is a significant shift. Instead of relying on external collaboration tools or plugins for real-time editorial workflows, core WordPress now provides the foundation natively. It reduces tooling complexity and brings collaborative editing into the same environment where content is published.

If you want to go beyond what core offers — custom editorial workflows, role-based approvals, and inline suggestions — Multicollab adds that layer on top. Here's a quick look:

AI Infrastructure: Connectors API, WP AI Client, and Abilities API

WordPress 7.0 does not add a chatbot to your dashboard. What it does is build the plumbing for AI-powered features at the platform level, giving developers and site owners a standardized way to integrate AI without the fragmented, plugin-by-plugin approach that exists today.

Three new systems make this possible:

Connectors API introduces a framework for registering and managing connections to external services, starting with AI providers. A new admin screen at Settings > Connectors gives site administrators a central place to configure API keys and manage service connections. This replaces the current pattern where every AI plugin manages its own credentials independently.

WP AI Client is a core PHP library that provides a standardized interface for communicating with AI models. It is provider-agnostic by design. Switching from one AI provider to another becomes a configuration change, not a code rewrite. This is a significant architectural decision that prevents vendor lock-in at the platform level.

Abilities API adds two new JavaScript packages (@wordpress/abilities and @wordpress/core-abilities) that register and run AI-powered "abilities" in the browser. These connect to server-registered abilities via the REST API.

Official provider plugins for Anthropic (Claude), Google, and OpenAI ship alongside core, with community plugins available for OpenRouter, Ollama, and Mistral. For organizations that do not want AI features at all, a single configuration option disables everything.

One enterprise consideration worth noting: API key storage is currently unencrypted in the database, with encryption planned for a future update. Organizations handling sensitive data should evaluate this against their security requirements before enabling AI connectors in production.

For enterprises already exploring AI-powered content workflows, WordPress 7.0's AI infrastructure provides a much cleaner foundation than the current patchwork of individual plugin integrations.

Admin Redesign and UX Improvements

WordPress 7.0 gives the admin interface its most noticeable visual update in years. The default color scheme changes from "Fresh" to "Modern," and a CSS-only visual reskin brings the classic wp-admin screens closer to the visual language of the block and site editors. This is not a full admin rewrite, but it meaningfully improves the visual coherence between the traditional dashboard and the modern editing experience.

Cross-document view transitions now provide smooth, app-like navigation between admin screens instead of full page reloads. Visual Revisions let you compare page versions side by side within the editor, making it easier to review changes before publishing.

The Command Palette, accessible via Cmd+K (Mac) or Ctrl+K (Windows), is now available globally from the admin bar, not just within the editor. This gives power users a fast way to navigate anywhere in the admin without clicking through menus.

On the content management side, DataViews replace the legacy WP_List_Table on Posts, Pages, and Media screens. The new interface brings modern filtering, sorting, grouping, and a new Activity layout that presents content in a timeline-style feed. For content teams managing large volumes of posts and pages, this is a meaningful workflow improvement.

Download a Free Actionable Guide: 45+ Actionable Tips to Boost WordPress Speed for High-Traffic Sites (Includes Impact Score)

• 15 Key Optimization Areas: Optimize performance with ad optimization, database tweaks, media optimization, and more.
• 45+ Actionable Strategies: Each strategy comes with links to plugins, tools, and resources for easy implementation.
• Impact Scores for Prioritization: Each tip is rated from 1 to 10 to help you prioritize high-impact optimizations.

Email Download Now

Thank You for Downloading!

Your PDF has been successfully downloaded. If you are not redirected to the file automatically, please click the button below to access the file.

Download Now

New Blocks, Design Tools, and Content Features

WordPress 7.0 ships a substantial collection of new blocks and design capabilities that give content teams and designers more control without needing developer intervention.

New blocks include Breadcrumbs and Icons, two of the most commonly requested additions. The Cover block now supports video embeds as backgrounds. The Grid block is responsive-enabled, and the Gallery block adds lightbox support. The Navigation block receives significant improvements, including customizable overlays as template parts with configurable mobile breakpoint settings.

A standout addition is the responsive editing mode, which allows content teams to show or hide blocks based on screen size. Marketers can now control what content appears on mobile versus desktop without filing a developer ticket, something that previously required custom CSS or theme-level code.

Client-side media processing moves image resizing and compression into the browser, reducing server load and improving the upload experience. The Font Library screen (Appearance > Fonts) is now available for all themes, not just block themes, giving every WordPress site access to centralized font management.

Pattern editing also gets new capabilities, including Spotlight mode and Isolated Editor mode for focused content creation within patterns.

Developer and Infrastructure Changes

WordPress 7.0 raises the minimum server requirements. PHP 7.2 and 7.3 are no longer supported. The new minimum is PHP 7.4, with PHP 8.3 recommended. On the database side, the minimum jumps to MySQL 8.0 (up from 5.5.5), with MariaDB 10.6+ also supported and MySQL 8.4 LTS recommended.

This release merges Gutenberg versions 22.0 through 22.6 into core. Block API v3 is now the recommended standard, with the iframed editor detection shifting from registration-based to usage-based. Blocks using API v3+ render inside the iframe; blocks using v2 or lower disable iframe mode for that post. Full iframe enforcement is not happening in 7.0, but developers should begin preparing, as it is coming in a future release.

PHP-only block registration with auto-generated inspector controls lowers the barrier for simpler blocks, allowing developers to register blocks entirely from PHP without writing JavaScript.

Styles enqueued via admin_enqueue_scripts no longer reach the editor in iframe mode. Developers must re-enqueue editor-specific styles via enqueue_block_editor_assets. This is a breaking change that will affect themes and plugins relying on the legacy approach.

What This Means for Enterprise Teams

WordPress 7.0 addresses several pain points that enterprise organizations have dealt with for years.

Real-time collaboration reduces dependency on external tools for multi-author content workflows. For organizations running large editorial teams across time zones, native collaborative editing eliminates a layer of tooling complexity and keeps everything within the WordPress environment.

The AI infrastructure creates a standardized foundation that prevents the fragmented, plugin-dependent approach most organizations currently use. Instead of each team or department choosing different AI plugins with different credential management, WordPress 7.0 centralizes this at the platform level.

The admin redesign and DataViews improvements directly impact content team productivity. Faster navigation, better content filtering, and a more modern interface reduce onboarding time for new team members and improve daily workflows for existing ones.

For organizations running enterprise WordPress at scale, these changes represent a meaningful step forward in platform maturity. Combined with WordPress VIP hosting for mission-critical deployments, WordPress 7.0 strengthens the case for WordPress as a long-term enterprise platform.

Preparing for the Upgrade

Before upgrading to WordPress 7.0, enterprise teams should take these steps:

• Check server requirements. Verify that your hosting environment meets the new minimums: PHP 7.4+ and MySQL 8.0+ (or MariaDB 10.6+). Sites still running PHP 7.2 or 7.3 will stay on the 6.9 branch.
• Audit plugins and themes. Test all active plugins and themes for compatibility with Block API v3 and iframe mode changes. Any plugin enqueuing editor styles via admin_enqueue_scripts will need updates.
• Test in staging first. Use a staging environment or WordPress Playground to test the upgrade before touching production.
• Plan for real-time collaboration. Decide whether to enable RTC immediately or phase it in. The opt-in approach gives you control over the rollout timeline.

WordPress 7.0 is a release worth paying attention to. It is not just an incremental update. It is the culmination of years of work on the Gutenberg project, and it lays the groundwork for where WordPress is heading next.

If your organization needs help planning the upgrade, auditing plugin compatibility, or optimizing your WordPress infrastructure for what is ahead, connect with the Multidots team. With 16+ years of enterprise WordPress experience and 300+ successful migrations, we have seen every kind of WordPress deployment and can help yours make the most of what 7.0 has to offer.