WordPress 7.2 Release Candidate 1 is ready for testing. The final release is scheduled for December 8, 2026.
A release candidate is a near-final build. It is the last chance to catch problems before everyone gets the update. WordPress.org says not to run it on production or mission-critical sites.
How to test it
Use a staging copy or a local site. You have four options:
- Install the WordPress Beta Tester plugin and pick the “Bleeding edge” channel with the “Beta/RC Only” stream.
- Download the RC1 zip and install it on a test site.
- Update through WP-CLI, the command-line tool for WordPress, using the command in the WordPress.org announcement.
- Open WordPress Playground in your browser. No setup is needed.
What changed since Beta 5
RC1 is mostly polish. WordPress.org lists these fixes:
- Fixes to client-side media uploads, which process images in your browser.
- Improvements to the new random-post redirect. We covered the /random/ URL earlier this month.
- A skip link in the admin bar, which helps keyboard users move around.
- Clearer messages when a plugin needs another plugin.
- Block editor fixes for duplicated block content, keyboard use on iOS, and revision previews.
What 7.2 brings
WordPress.org highlights these features:
- A new default theme called Ipsum, which we covered in September.
- Expanded responsive design and Gallery controls.
- Better Global Styles and typography tools.
- Improved Canvas Notes and collaboration.
- Faster media uploads, faster admin navigation, and a new “On This Day” widget.
- Accessibility, security, and PHP 8.6 compatibility improvements.
Our Beta 1 write-up covers the earlier test build.
What to do
Test your key pages, forms, and checkout on a staging site. Check that your important plugins and theme still work. Report problems on WordPress.org before December 8, while they can still be fixed.
End of article