WordPress released the first beta of WordPress 7.2 on October 20, 2026. It is meant for testing only and should not run on a live site. The final release is scheduled for December 8. Anyone running a WordPress site has about seven weeks to check that their theme and plugins work with it.
What we know
- The date: the official post, by David Baumwald on wordpress.org on October 20, sets the final release for December 8, 2026. More betas and release candidates will come before that, according to the same post.
- The warning: WordPress asks people not to install, run or test this version on production or mission-critical sites, and points to a test environment or a local site instead.
- Images handled in the browser: the post says the Media Library will be able to resize, compress and convert images in the browser before they are uploaded. It mentions "better support for modern image formats" without naming which ones.
- Safer storage for keys: a new Secrets API gives developers a standard way to store credentials, with encryption at rest, rotation and pluggable storage providers.
- A faster admin: admin scripts and stylesheets will load as separate files for better browser caching, and a prefetching mechanism will anticipate the next admin screen, according to WordPress.
- Editor: responsive controls for more blocks (gallery columns, image cropping and aspect ratio), text shadow, improvements to Notes, navigation items managed directly from the editor sidebar and an "On This Day" dashboard widget. Everything shipped in the Gutenberg plugin from version 23.7 to 24.3 is included.
- How to test it: with the WordPress Beta Tester plugin ("Bleeding edge" channel, "Beta/RC Only" stream), the zip download, WP-CLI (`wp core update --version=7.2-beta1`) or WordPress Playground in the browser.
What changes and what doesn't
Nothing changes on a live site today: the beta only reaches sites where someone installs it on purpose. What changes is the deadline. Plugins and themes that are not ready by December 8 may cause problems once the final 7.2 is installed.
The post gives no minimum PHP version for 7.2 and no count of fixed bugs. It also does not say whether in-browser image processing replaces optimization plugins. The Secrets API will only protect a plugin's keys if its developer adopts it.
How to check if it affects you
- Confirm your site runs WordPress and which version: it shows at the bottom right of the dashboard, or under Dashboard > Updates.
- Test on a copy, never on the live site. Many hosts offer a staging environment. Without one, Playground is enough to look at the new features, though it won't have your plugins.
- Install the beta on the copy with the WordPress Beta Tester plugin or the WP-CLI command from the post.
- Check what brings you traffic and customers first: that page titles and meta descriptions still appear in the page source, the sitemap loads, forms send and checkout works.
- Upload a couple of images and compare their file size and dimensions with what you usually get. If you use an optimization plugin, make sure it is not compressing the same image twice.
- If something breaks, tell the plugin or theme developer, or post in the Alpha/Beta forum on wordpress.org. Put December 8 in your calendar and update the live site afterwards, with a fresh backup.
Related: WordPress 7.1.3 Fixes 7 Security Flaws: Update Your Site Now
Sources
Updates: if WordPress moves the final release date or publishes the 7.2 requirements, it will be added here with a link.