WordPress 7.0 RC1 Drops Tomorrow: The Complete Developer Preview of Every Major Feature

WordPress 7.0 RC1 Arrives March 24 — Here’s Everything Developers Need to Know

WordPress 7.0 Release Candidate 1 is scheduled to drop tomorrow, Tuesday March 24, 2026 at 11:00 AM EDT (15:00 UTC) — and it’s shaping up to be one of the most significant WordPress releases in years. After an extra beta cycle (Beta 6 shipped on March 20 with 132+ fixes), the team is confident the release is ready. Here’s a complete breakdown of every major feature landing in RC1.

🤝 Real-Time Collaboration (RTC) — Now Opt-In by Default

The headline feature of WordPress 7.0 is finally here. Real-Time Collaboration in the Block Editor uses Yjs CRDT (Conflict-free Replicated Data Type) technology for conflict-free simultaneous editing. Key implementation details:

  • Uses HTTP polling sync provider (replacing unreliable WebRTC) for universal hosting compatibility
  • CRDT data stored persistently via post_meta on a special wp_sync_storage internal post type
  • RTC is opt-in by default — controlled via the WP_ALLOW_COLLABORATION constant in wp-config.php
  • 4x increase to polling intervals to minimize HTTP requests and server load
  • Client-side code initially limits simultaneous collaborators to two (hosts can adjust via config)
  • Classic meta boxes automatically disable collaboration mode for compatibility

🤖 AI Infrastructure: Connectors API & Provider Packages

WordPress 7.0 introduces a full AI provider framework built around the php-ai-client package. Three official provider plugins are now in the Plugin Directory:

The new Connectors screen in the admin handles credentials storage and provider selection as platform-level infrastructure. Write features once against the shared interface — switching AI providers becomes a simple configuration change.

🎨 In-Editor Visual Revisions

The block editor’s revisions panel now shows color-coded change overlays directly in the document inspector:

  • 🟢 Green outlines — added blocks / added text (underlined)
  • 🔴 Red outlines — removed blocks / removed text (strikethrough)
  • 🟡 Yellow outlines — blocks with modified settings or format-only changes

The overlay can be toggled off. Uses a two-step process: quick check for changed blocks, then full rich-text comparison only on flagged blocks.

🖼️ New Icon Block with SVG Registration API

A new Icon block lets designers add SVG icons from a pre-selected library, backed by a new server-side SVG Icon Registration API. A REST endpoint at /wp/v2/icons is available for searching and filtering. Third-party icon collection registration is planned for WordPress 7.1.

📱 Navigation Overlays — Now Stable

Navigation blocks now feature fully customizable overlays for mobile menus. The feature is no longer experimental and ships stable in 7.0. A Create overlay button guides setup with patterns for various designs.

📝 Content-Only Pattern Editing by Default

Patterns now default to Content-Only editing mode — presenting fields with block icons and grouped attributes in flyout menus, reducing design clutter for content creators. Administrators can opt out via:

add_filter( 'block_editor_settings_all', function( $settings ) {
    $settings['disableContentOnlyForUnsyncedPatterns'] = true;
    return $settings;
} );

🖼️ Gallery Lightbox Navigation

The Gallery block lightbox now supports back/next navigation between images using buttons and arrow keys. Images with lightbox disabled are automatically skipped.

🔧 PHP-Only Block Registration

You can now register a fully functional block using only PHP with the new autoRegister support flag — no JavaScript required. A major DX improvement for server-rendered blocks.

🎨 Pseudo-Element Support in theme.json

Theme developers can now style :hover, :focus, :focus-visible, and :active states directly on blocks and their style variations in theme.json — no custom CSS needed.

⚙️ New WP-CLI Commands

WP-CLI is getting two new command sets ahead of WP-CLI v3.0:

  • wp block — read-only access to block entities, with pattern/template export support
  • wp ability — new ability commands for capability checking

📦 What Was Pulled: Client-Side Media Processing

The Client-side Media Processing feature was reverted from 7.0 due to image optimization and package size concerns discovered during Beta 5 testing. It will be reconsidered for a future release.

📅 Release Timeline

  • RC1: March 24, 2026 at 11:00 AM EDT
  • RC1 Release Party: March 24 at 3:00 PM UTC on WordPress Slack #core
  • Final Release: April 9, 2026

Key Takeaway: WordPress 7.0 RC1 represents a massive leap forward — real-time collaboration, a full AI provider framework, visual revision tracking, and dozens of developer-facing improvements. If you haven’t tested Beta 6 yet, now is the time before RC1 lands tomorrow.

Hashtags: #WordPress #WordPress7 #WebDevelopment #WP7 #BlockEditor #RealTimeCollaboration #WordPressDev #PHP #OpenSource

Resources:

Search

Categories

Archives