WordPress 7.0 Release Candidate 1 is ready for testing
RC1 is available now, with the final release still scheduled for . Read the official announcement on WordPress.org.
This build is still under development and should not be installed on production or mission-critical sites. Treat RC1 as a pre-release validation step on staging, local, or disposable environments where you can safely test upgrades, workflows, and edge cases.
RC1 includes over 134 updates and fixes since Beta 5, tightening stability as the release approaches the final cut.
Safe ways to test RC1 on WordPress infrastructure
Plugin-based testing via WordPress Beta Tester
Install and activate the WordPress Beta Tester plugin, then select the “Bleeding edge” channel and the “Beta/RC Only” stream. This approach is useful when you need repeatable, GUI-driven upgrades on a staging clone.
Direct download and manual install
Download the RC1 zip and install it on a test site. This is a practical route when you want a clean-room environment to isolate regressions, or when you are testing a specific hosting image or container build.
WP-CLI upgrade path
For automated pipelines and scripted staging refreshes, upgrade using WP-CLI with wp core update --version=7.0-RC1. This is well suited to hosting platforms that validate upgrades across fleets and configurations.
Browser-only testing with WordPress Playground
WordPress Playground allows quick feature checks without any setup. It is ideal for validating new UI flows, admin interactions, and editor behaviour before you commit to deeper infrastructure testing.
What changed in RC1: features that matter to site owners and developers
AI Connectors Screen and extensible provider registration
RC1 introduces an admin screen for connecting AI providers to a site, plus an API designed to register additional providers. It also adds support for non-AI providers on the Connectors screen, signalling an intent to standardise integrations under a single management surface.
Operationally, this means you should review how your environment handles outbound requests, secrets management, and provider-specific firewall rules, particularly on locked-down hosting where external connectivity is tightly controlled.
Command Palette shortcut in the admin bar
The Command Palette is now accessible using ⌘K or Ctrl+K via the admin bar. This is a workflow change that can affect admin usability testing, accessibility checks, and any documentation or training materials you maintain for editorial teams.
Real Time Collaboration (RTC) becomes opt-in by default
RC1 shifts RTC to opt-in by default, adds a new activation hook to enable RTC by default, and introduces a WP_ALLOW_COLLABORATION constant to control collaboration behaviour at the configuration level.
There are also tuning changes such as increased polling intervals and a toggle for RTC session notifications. For performance-minded site owners, these adjustments are worth validating under load, especially when object caching, aggressive page caching, or restrictive admin-ajax policies are in play.
Controls for LLM-related features
A single configuration option is now available to disable all LLM-related features. This is particularly relevant for regulated environments, enterprise security reviews, and agencies that deploy WordPress across multiple clients with different compliance positions.
Revisions and block-level change visibility
Revisions now expose changed block attributes in the sidebar, improving editorial traceability during content reviews. This is likely to surface new testing scenarios for complex block setups, custom blocks, and sites that rely on heavily structured content.
Site Health gains OPCache visibility
OPCache information is now shown in Site Health under Info > Server. This is a practical diagnostic improvement for WordPress hosting, making it easier to confirm whether opcode caching is enabled and to align performance expectations with server configuration.
What to test before the final 7.0 release
Prioritise upgrade-path testing from your current production version to RC1 on a staging clone, including database upgrades, plugin update routines, and any MU-plugin bootstrapping you rely on for caching, security headers, or environment detection.
Validate Real Time Collaboration behaviour in the editor, including notification settings, opt-in defaults, and any policies you enforce through wp-config.php or deployment templates.
Exercise pattern editing and content-only interactivity flows using real content, not sample data, as these are the areas most likely to reveal theme-level edge cases and editorial workflow friction.
Guidance for hosting providers, agencies, and plugin/theme authors
Hosting platforms should run distributed compatibility tests across supported PHP versions, caching stacks, and container images, paying close attention to admin performance and collaboration-related polling behaviour.
Plugin and theme authors should finish compatibility testing now and update the “Tested up to” value to 7.0 once verification is complete. If issues surface, report them with clear reproduction steps so they can be triaged before the final release window narrows.
Translation contributors should note that RC1 marks the hard string freeze point for the 7.0 release cycle, with strings expected to become available for translation at RC2.
FAQ
Can I install WordPress 7.0 RC1 on a live site?
No. RC1 is pre-release software and should be tested only on non-production environments such as staging, local development, or disposable test instances.
What is the scheduled final release date for WordPress 7.0?
The final release is scheduled for .
How can I test WordPress 7.0 RC1 quickly?
You can use WordPress Playground for browser-only checks, the WordPress Beta Tester plugin for managed upgrades, a direct zip install for clean-room tests, or WP-CLI with wp core update --version=7.0-RC1 for scripted pipelines.
What are the headline additions in RC1?
RC1 adds the AI Connectors screen and provider registration API, enables the Command Palette shortcut (⌘K/Ctrl+K) in the admin bar, and refines Real Time Collaboration by making it opt-in by default with new configuration controls.
What should I focus on when testing as a site owner or agency?
Test the upgrade process on a staging clone, validate Real Time Collaboration defaults and performance, and verify pattern editing and content-only interactivity against your real theme, plugins, and content model.
Where is the official RC1 announcement?
You can read it on WordPress.org.
