The third Release Candidate (RC3) for WordPress 7.0 is now available for download and testing, marking a crucial milestone on the path to the final release scheduled for May 20, 2026. This version includes over 140 fixes and improvements since RC2, reflecting continued polish and refinement of the next major WordPress update.
Key Takeaways
- WordPress 7.0 RC3 is ready for testing but not for production or mission-critical sites.
- Over 140 issues have been addressed since the previous release candidate.
- Real Time Collaboration has been postponed to WordPress 7.1 and is not included in 7.0.
- Testing can be done via multiple methods including WP-CLI, Beta Tester plugin, and WordPress Playground.
- Plugin and theme developers should finalize compatibility testing and update their tested version metadata.
WordPress 7.0 RC3: A Critical Step Toward Final Release
WordPress 7.0 has reached Release Candidate 3 status, signaling that development is nearing completion and that the software is entering its final testing phase. This release candidate is a snapshot of the software that is very close to what users will experience in the stable release. While not recommended for live sites, it offers a vital opportunity for developers, testers, and hosting providers to validate compatibility and identify any remaining issues.
RC3 includes over 143 fixes and enhancements since RC2, addressing bugs reported by the community and contributors. These fixes range from core functionality improvements to stability and performance tweaks, reflecting the iterative approach WordPress core development takes at this stage.
How to Test WordPress 7.0 RC3
Testing is essential to delivering a stable final release. WordPress offers several convenient methods to run RC3 in a safe environment:
- Plugin: Install the WordPress Beta Tester plugin and select the “Bleeding edge” channel with the “Beta/RC Only” stream for automatic updates to RC3.
- Direct Download: Download the RC3 zip package directly from the official WordPress repository and install it on a test site.
- Command Line: Use the WP-CLI command
wp core update --version=7.0-RC3to upgrade a test environment. - WordPress Playground: Test the release candidate instantly in a browser instance without setup.
These testing options cater to a range of technical skill levels and workflows, from casual testers to developers and hosting providers.
Technical Highlights and Postponed Features
For those interested in the technical details, the WordPress 7.0 Developer Notes provide an in-depth look at changes and new features. Notably, the Real Time Collaboration feature, initially planned for 7.0, has been deferred to 7.1. This decision ensures that the released version maintains high stability and quality by focusing on refinements and bug fixes.
The postponement of Real Time Collaboration indicates the development team’s commitment to a measured release process, prioritizing tested and proven functionality over shipping experimental features prematurely. Hosting providers and plugin developers should take note, as this affects integration and compatibility planning.
Impact on Plugin and Theme Developers
Plugin and theme authors play a pivotal role in WordPress’s ecosystem. As WordPress 7.0 approaches final release, it is critical that developers complete their compatibility testing with the new core version. Authors should update the “Tested up to” value in their readme files to 7.0 once testing concludes successfully.
Any compatibility issues discovered should be reported promptly in support forums or directly in WordPress Trac if developers can provide reproducible bug reports. Early testing and reporting help ensure that the broader WordPress user base experiences a smooth transition when upgrading to 7.0.
Hosting Providers’ Role in Testing and Deployment
Web hosts underpin the WordPress ecosystem and must verify that their infrastructure supports new releases without issues. Several major hosts, including Kinsta, Bluehost, and GoDaddy, contributed to testing earlier phases of WordPress 7.0.
Distributed testing on hosting platforms is essential to catch environment-specific bugs and to prepare for smooth update rollouts. Hosting providers are encouraged to participate in testing and report findings to help improve WordPress’s compatibility and performance across diverse server configurations.
Community Contributions and String Freeze
WordPress is driven by its global community. This release candidate marks the hard string freeze, meaning no further changes to user-facing text strings will be accepted for 7.0. This freeze helps translators finalize translations for over 100 languages, enabling WordPress 7.0 to be accessible worldwide upon release.
Contributors continue to be encouraged to join testing efforts, report bugs, and help translate WordPress. Resources and guides on contributing are available, making it easy for anyone with varying levels of technical expertise to get involved.
What This Means for WordPress Users
With WordPress 7.0 RC3 ready, we are entering the home stretch for what promises to be a significant core update. For most WordPress site operators, this means preparing for a smooth upgrade by ensuring plugins and themes are tested and compatible. Agencies and freelancers should advise clients to delay production upgrades until the final release, but encourage testing on staging environments.
Developers should focus on final compatibility checks and updating their plugins and themes to declare support for WordPress 7.0. Hosting providers must continue their testing to ensure their platforms are ready for the update wave expected after May 20.
This release cycle also signals WordPress’s ongoing commitment to stability and incremental improvement. The decision to postpone Real Time Collaboration underscores a cautious, quality-focused approach that benefits all stakeholders by avoiding premature feature releases that could cause instability.
We recommend developers and site owners subscribe to the Make WordPress Core blog and engage with the community via the #core-test Slack channel to stay informed and contribute to testing efforts.
Frequently Asked Questions
Is it safe to install WordPress 7.0 RC3 on a live site?
No. Release candidates are for testing purposes only. They should not be installed on production or mission-critical sites as they may contain bugs or unfinished features.
How can I test WordPress 7.0 RC3?
You can test RC3 using the WordPress Beta Tester plugin, direct download and install, WP-CLI command line update, or by using the WordPress Playground in a browser without setup.
What happened to the Real Time Collaboration feature?
Real Time Collaboration has been postponed to WordPress 7.1 due to stability concerns and will not be included in the 7.0 release.
How should plugin and theme developers prepare for WordPress 7.0?
Developers should complete compatibility testing, update their “Tested up to” version to 7.0 in plugin readme files, and report any compatibility issues in support forums or WordPress Trac.
What role do hosting providers have in the WordPress 7.0 release?
Hosting providers must test WordPress 7.0 on their platforms to ensure compatibility and smooth update rollouts, reporting any issues to help improve the release’s stability.
