Skip to content
WordPress Core

WordPress 7.0 Release Candidate 4 Arrives: Final Testing Phase Before May 20 Launch

WordPress 7.0 Release Candidate 4 is now available for final testing before its scheduled launch on May 20, 2026. This release candidate focuses on stability and bug fixes.

WordPress 7.0 Release Candidate 4 Arrives: Final Testing Phase Before May 20 Launch
Photo: Markus Winkler on Pexels

WordPress 7.0 Release Candidate 4 (RC4) is now available for download and testing, marking a critical milestone in the final stretch before the full launch scheduled for May 20, 2026. This release candidate signals feature completeness and near-final stability but remains a pre-release version not intended for production use.

Key Takeaways

  • WordPress 7.0 RC4 is ready for testing, with the stable release planned for May 20, 2026.
  • Testing RC4 ensures issues are identified and resolved before general availability.
  • Multiple testing methods are supported: Beta Tester plugin, direct download, WP-CLI, and WordPress Playground.
  • RC4 marks the hard string freeze point, locking translations for the release.
  • Community participation in testing and translation remains vital to WordPress 7.0’s success.

Understanding the Role of Release Candidate 4 in WordPress 7.0’s Development

The WordPress 7.0 development cycle has reached an important phase with Release Candidate 4. Release candidates represent versions considered feature complete and nearly stable, but they require extensive real-world testing to catch any remaining bugs or regressions. RC4 is the final candidate before the official 7.0 release, signaling that the core development team believes the software is close to ready for broad use.

For most WordPress sites, the jump from the last beta to an RC means minimal new features but a focus on stability, performance improvements, and bug fixes. The core team uses these release candidates to gather feedback from the community and plugin/theme developers to ensure compatibility and smooth upgrades.

How to Test WordPress 7.0 RC4

Testing RC4 is essential to ensure that WordPress 7.0 rolls out with maximum stability and minimal disruption. WordPress offers four primary ways to test this release candidate:

  • Beta Tester Plugin: Install and activate the WordPress Beta Tester plugin, choose the “Bleeding edge” channel and the “Beta/RC Only” stream, and update your site to RC4 automatically.
  • Direct Download: Download the RC4 zip archive from the official WordPress.org release page and install it on a test environment.
  • WP-CLI Command Line: Use the command wp core update --version=7.0-RC4 on your test site to upgrade to the release candidate.
  • WordPress Playground: Test the release candidate instantly in a browser with no setup required by using the WordPress Playground environment.

We strongly advise against installing RC4 on production or mission-critical sites. Instead, use staging or local development environments to evaluate new features, test compatibility with existing plugins and themes, and report any bugs encountered.

What’s New and Fixed Since RC3?

While RC4 does not introduce new features, it includes a series of bug fixes and refinements addressing issues identified since Release Candidate 3. These improvements stem from both Core Trac tickets and Gutenberg plugin commits, reflecting close coordination between the core team and the block editor developers.

For developers and site operators who want to dive deeper, the WordPress 7.0 Field Guide offers detailed notes on changes and known issues. The continuous integration of Gutenberg commits into Core underscores WordPress’s commitment to an improved block editing experience with each major release.

The Importance of Community Involvement

WordPress’s success hinges on its vibrant community of contributors. Testing release candidates is a highly impactful way for users, developers, and agencies to contribute even if they are not writing code. Reporting bugs, verifying fixes, and testing plugin and theme compatibility directly shape the quality of the final release.

Additionally, RC4 marks the hard string freeze, meaning no further changes to user-facing text will be accepted. This is a critical point for translators worldwide to finalize translations, enabling WordPress 7.0 to be accessible in over 100 languages.

Participating in testing and translation boosts the chances that WordPress 7.0 will be both stable and globally usable from day one. WordPress’s open source model thrives on this collective effort, and new contributors are always welcome through forums, Make Core blog updates, and the #core-test Slack channel.

What This Means for WordPress Users

With WordPress 7.0 RC4 available, site owners and developers should begin preparing for the transition. Testing on staging environments now helps prevent last-minute surprises when the official update drops on May 20. Agencies should prioritize compatibility testing with client sites, especially for custom plugins and themes that interact deeply with Core or Gutenberg.

Developers can use this phase to finalize plugin and theme updates aligned with WordPress 7.0’s new features and bug fixes. Early testing also allows time to report regressions and receive feedback on compatibility issues, which can be addressed before the final release.

The RC4 milestone signals that WordPress 7.0 is stable enough for broader testing but still requires community eyes to catch edge cases. For the hosting ecosystem, this release will likely prompt updates to managed WordPress hosting platforms and toolchains like WP-CLI to support the new version seamlessly.

In real-world deployments, the release candidate phase is crucial to ensure that the final version minimizes disruptions and maximizes performance and security. We recommend that all WordPress professionals participate in testing and prepare their environments accordingly.

Frequently Asked Questions

Can I use WordPress 7.0 RC4 on my live website?

No, RC4 is a pre-release version intended for testing only. Installing it on production or mission-critical sites is not recommended due to potential bugs and unfinished features.

How do I report bugs found in WordPress 7.0 RC4?

You can report bugs in the Alpha/Beta section of the WordPress support forums or directly on the WordPress Trac system if you can provide reproducible details.

What does “hard string freeze” mean in this release?

Hard string freeze means no further changes to user-visible text strings are allowed, enabling translators to finalize translations for the release.

Where can I find detailed technical notes about WordPress 7.0?

The WordPress 7.0 Field Guide and Core Trac tickets provide detailed information on new features, fixes, and ongoing issues.

Related News