WordPress 7.2 Beta 1 shipped on October 20, 2026, giving developers and agencies their first real look at what’s landing in the next major core release. The beta is for testing only, not production sites, and it marks feature freeze: what’s in Beta 1 is close to what ships when WordPress 7.2 goes stable on December 8, 2026, according to the official WordPress Core announcement. The headline addition is a new Secrets API for storing credentials in encrypted form, alongside a faster-loading admin and a reworked block inspector.
A Secrets API That Finally Gives Credentials a Proper Home
Right now, plugins that need to store an API key or OAuth token mostly roll their own storage, and the results vary a lot in how carefully that data gets handled. WordPress 7.2 introduces a standardized Secrets API with encrypted storage, built-in rotation, and support for customizable storage providers. For agencies managing client sites with several integrations each holding their own credentials, this is the kind of plumbing change that doesn’t show up in a changelog highlight reel but matters once a plugin actually adopts it instead of writing secrets to an options row in plaintext.
Editor and Admin Changes Worth Testing Now
Most of what’s in Beta 1 is editor-facing, and some of it touches markup and settings UI in ways worth checking against custom blocks and themes before the stable release:
- Responsive controls now extend to more blocks, including per-screen settings for Gallery columns, cropping, and aspect ratios.
- Global Styles gets a “Customized” filter for finding blocks with modified styles, plus an inspector view that shows inherited values and new styling controls for form elements.
- New text shadow controls, settable per block or as
theme.jsonpresets. - A DataForm-based block inspector replaces the older settings panels with what the core team calls a refreshed experience.
- Legacy Dashicons in the admin bar and sidebar are swapped for the newer WordPress icon library.
- The Media Library can resize, compress, and convert images in the browser before upload even starts.
- Admin itself loads faster: assets load individually for better caching, and resources for screens you’re likely to visit next get prefetched.
None of this is breaking by itself, but the block inspector rework and the Dashicons swap are the two most likely to surface visual regressions in a theme or plugin that assumed the old markup would stay put.
What to Do Before December
Beta 1 isn’t something to run on a live site, but it’s worth pulling onto a staging copy of anything with custom blocks, a heavily customized admin, or plugins that touch credential storage. You can test it through the WordPress Beta Tester plugin, a direct zip download, WP-CLI with wp core update --version=7.2-beta1, or WordPress Playground if you just want to poke at it without touching a real environment. Bugs go to the support forum’s Alpha/Beta area or Trac.
If you’re running client sites with custom block editor work built up over a few major releases, checking it against a beta before release candidates land is exactly the kind of compatibility pass we run as part of our WordPress development work, since catching a block inspector regression in October beats finding it from a client in January.
