WordPress 7.2 Release Candidate 1 shipped on Tuesday 17 November 2026, and it is the first version of the release that is close enough to final for serious testing. The final release is scheduled for 8 December 2026, giving the community three weeks to test themes, plugins and hosting setups. WordPress 7.2 RC1 brings the new Ipsum default theme, a Secrets API for encrypted credentials, faster media uploads, expanded responsive design controls and a modernised admin. One rule matters more than any feature: RC1 is still under development, so test it on a staging site only, never on a live or mission-critical website.
Key takeaways
- WordPress 7.2 RC1 shipped on 17 November 2026. The final release is scheduled for 8 December 2026 at 15:00 UTC.
- RC1 is for testing only. WordPress states plainly that it must not be installed, run or tested on production or mission-critical websites.
- The headline changes are the new Ipsum default theme, the Secrets API, faster media uploads, expanded responsive design and Gallery controls, and a modernised admin built on SVG icons.
- Test on staging with the Beta Tester plugin, a direct download, WP-CLI or WordPress Playground, and report what breaks before the final release.
What WordPress 7.2 RC1 is, and what it is not
A release candidate is the stage of a WordPress release where the feature list is frozen and the remaining work is fixing bugs. WordPress 7.2 RC1 is not the 7.2 release, and it is not a beta. The beta phase, which ran from Beta 1 through Beta 5 on 10 November, was for landing features and finding problems. RC1 is for confirming that the release is stable enough to ship.
Three things happen at RC1: the string freeze takes effect, so interface text stops changing and translators can finish; the 7.2 release branch is created; and the Field Guide publishes, collecting the developer notes that explain every change. Developers can now test against something that will not move under them, apart from bug fixes. The warning still stands: a release candidate can still contain a bug that corrupts data or breaks a plugin in a way that only appears on a real site.
WordPress 7.2 release schedule
WordPress 7.2 is the last major WordPress release of 2026, per the Make WordPress Core release page.
| Milestone | Date | What it means |
|---|---|---|
| Beta 5 | 10 November 2026 | Last beta before the release candidates |
| Release Candidate 1 | 17 November 2026 | String freeze, release branch, Field Guide |
| Release Candidate 2 | 24 November 2026 | Further bug fixes only |
| Release Candidate 3 | 1 December 2026 | Final candidate before release |
| Final release | 8 December 2026, 15:00 UTC | WordPress 7.2 ships to all sites |
The dates after RC1 are targets. The window for reporting problems is now, while fixes can still land.
What is new in WordPress 7.2 RC1
The most visible change is the new Ipsum default theme, which ships with WordPress 7.2 as the default theme for fresh installs. A default theme sets the tone for what a new WordPress site looks like out of the box. Site owners who already have a theme active will not see their site change, because a new default theme only applies to new installs and to sites that switch to it deliberately.
The block editor gains expanded responsive design and Gallery controls, improved Global Styles and typography tools, enhanced Canvas Notes and collaboration, and a new DataForm block settings inspector. The responsive design controls matter most for site owners who build pages in the editor, because they make it easier to adjust how a layout behaves on different screen sizes without writing custom code. Media handling is faster too: uploads are faster on the client side, and image processing inside the browser is faster.
The admin is modernised, with SVG icons and faster navigation and asset loading. WordPress 7.2 also adds a new “On This Day” widget, a random post discovery feature and better translation update management, plus accessibility and security improvements and PHP 8.6 compatibility.
The Secrets API: encrypted credentials in core
The most important developer change in WordPress 7.2 is the Secrets API, which gives plugins a standard way to store sensitive credentials encrypted at rest instead of as plain text in the database. Until now, plugins that needed an API key, a token or an OAuth client secret usually stored it in the options table, where anyone with database access could read it. The Secrets API encrypts those values with libsodium, never autoloaded, with one previous version kept so credentials can be rotated safely.
Plugins use two new functions, wp_set_secret and wp_get_secret, and a new manage_secrets capability gates who can read and write secrets. The encryption depends on a new WP_SECRETS_KEY constant in wp-config.php. Without a usable key, the API stores nothing. New installs get the key automatically, while existing sites need the line added by hand, and once secrets are stored that value must never change.
There is no admin screen for secrets in 7.2, so for now the API is a developer tool that plugins adopt, not something site owners manage directly. One caution: a request to remove the API was raised on 13 November. As of RC1 it remains in the release, per the developer note and the November developer roundup, but the final release could still change it, so developers should follow the Field Guide rather than assume it is settled.
Fixes since Beta 5
RC1 is mostly a bug-fix release relative to Beta 5: fixes to client-side media uploads, improvements to the new random-content redirect feature, better keyboard navigation through a skip link in the admin bar, improved plugin dependency messaging and script module translations, and better reliability for the HTML and Interactivity APIs. Developers also get Abilities API refinements and updates to bundled libraries, including PHPMailer, Requests, getID3 and sodium_compat.
The block editor gets its own round of fixes: duplicated block content, keyboard interactions on iOS, revision previews, plugin installation workflows, featured image compatibility and link suggestions. For plugin and theme developers, the old load-scripts.php and load-styles.php endpoints now return a 410 Gone response, so any code that still calls them needs updating, and authors should update the “Tested up to” version in their readme files to 7.2.
How to test WordPress 7.2 RC1 safely
WordPress offers four ways to test RC1, all on a staging site or a local install: the WordPress Beta Tester plugin (Bleeding edge channel, Beta/RC Only stream), a direct download of the RC1 zip, WP-CLI (wp core update –version=7.2-RC1), or WordPress Playground, which runs WordPress in the browser with no setup and is the best option for a quick look without touching any server.
Before you test, back up the staging site, including its files and database. Then work through what matters to you: activate your theme and check the front end, run through your key plugins, test the editor with your usual blocks, and try the new features that affect your site. If you find a problem, report it in the WordPress support forums or on the relevant Trac ticket, because that is how fixes land before 8 December. For a full backup method, see our WordPress backup guide.
Frequently asked questions
Is WordPress 7.2 RC1 safe to install?
No, not on a live site. RC1 is still under development, and WordPress states plainly that it must not be installed, run or tested on production or mission-critical websites. Use a staging site, a local install or WordPress Playground, and wait for 8 December 2026.
When is the WordPress 7.2 final release?
The final release is scheduled for 8 December 2026 at 15:00 UTC, after RC2 on 24 November and RC3 on 1 December.
What is the Ipsum theme in WordPress 7.2?
Ipsum is the new default theme shipping with WordPress 7.2, confirmed in the official RC1 announcement. It applies to fresh installs. Existing sites keep their current theme unless the owner switches to Ipsum.
What does the Secrets API do?
The Secrets API lets plugins store credentials such as API keys encrypted at rest, instead of as plain text in the database. It needs a WP_SECRETS_KEY constant in wp-config.php and has no admin screen in 7.2. It remains in RC1, though a removal request was raised on 13 November.
Conclusion
WordPress 7.2 RC1 is the point in the release cycle where testing stops being optional and starts being useful. The feature list is frozen, the strings are frozen, the Field Guide is published, and the final release is three weeks away. The Ipsum theme, the Secrets API, faster media handling and a quicker admin give site owners and developers plenty to check. What the release still needs is testers: people running their real themes and plugins against RC1 on staging sites and reporting what breaks. That work starts now, on a test site, and ends on 8 December with a final release tested by the community it serves.
Sources and Further Reading
- WordPress.org News, “WordPress 7.2 Release Candidate 1”, 17 November 2026
- WordPress Developer Blog, “What is new for developers? (November 2026)”
- Make WordPress Core, “WordPress 7.2 Secrets API: Secure Credential Storage Guide”, 11 November 2026, updated 13 November 2026
- Make WordPress Core, WordPress 7.2 release schedule
- Digital Matters, “WordPress 7.2 RC1: Test Plan and Client Notes”
