WordPress 7.2 Beta 1 is out: in-browser image resizing, Secrets API, Abilities API
The first beta of WordPress 7.2 was published for testing on October 20, 2026, with the final release planned for December 8, 2026. One highlighted change lets the browser shrink, compress and convert images before they are uploaded. The beta should stay off live or mission-critical sites.
The first 7.2 beta is out, with the final planned for December 8
An announcement on the WordPress.org news site, signed by David Baumwald, says 7.2 Beta 1 is ready to download and test. It states plainly that "This beta release is intended for testing and development only." The post asks readers to keep it off production and mission-critical sites and to use a test environment or a local site instead.
Four ways to try it are listed: pick the "Bleeding edge" channel and the "Beta/RC Only" stream in the WordPress Beta Tester plugin, install the wordpress-7.2-beta1.zip download, run wp core update --version=7.2-beta1, or open a WordPress Playground instance in the browser with no setup. The scheduled final date is December 8, 2026. According to the post, 7.2 will also ship features that were previously only in the Gutenberg plugin, and it points to Gutenberg releases 23.7 through 24.3.
What changes in the editor, media, admin and developer tools
In the editor, the screen-size styling controls that began in 7.1 reach more tools and blocks, and the Gallery block gains responsive settings for columns, image cropping and aspect ratio. Blocks get text shadow controls, which can also be defined as presets in theme.json. From the Site Editor sidebar, menu items can be added, organized and edited. Notes get emoji reactions and a new toolbar icon, move into the editor margin and gain a minimized mode. The post also mentions a "Customized" filter for Global Styles, clearer error messages and a new block settings panel built on DataForm.
For uploads, client-side processing extends to the Media Library: images can be resized, compressed and converted in the browser before they reach the server. The post says this may speed up uploads, lower server resource use and improve support for modern image formats, particularly on hosts with limited image-processing ability. The dashboard gets an "On This Day" widget that surfaces posts published on the same date in earlier years. Admin assets now load as separate files for better browser caching, and the admin prefetches resources for the screen a user is likely to open next. For developers, the Secrets API offers encryption at rest, credential rotation and swappable storage providers for items such as API keys and tokens. The Abilities API gains new ways to access and query WordPress data, and the Interactivity API adds options for rendering trusted HTML and handling reactive navigation.
Image weight and AI integrations meet in one release
WordPress underpins a large share of the web, so even a modest media change can alter upload behavior across many sites. Doing image work in the browser shifts part of the effort from the server to the device of the person uploading; per the post, this can help most on hosts with limited image-processing capabilities. The Secrets API aims to give plugins a common answer to how API keys get stored, while the Abilities API expansion points toward more consistent access for automation and AI-powered tools.
Keep the caveat in view: this is a beta announcement, and the listed features may change before the final build. Still, agencies and plugin authors have a clear window to test theme and plugin compatibility on a staging site. We covered the previous release's security fixes in our WordPress 7.1.1 article.
The source says nothing about Türkiye, so this section is commentary
The announcement carries no information about Türkiye, Turkish-language users or local hosts. This section is therefore not a fact drawn from the source but explicitly UNALSOFT commentary.
Our reading: many business sites in Türkiye run on WordPress, and image weight is often their first performance problem. Browser-side image handling is interesting from that angle, but how it behaves on your own site is something only a test environment will show. The unknowns, for the record: the post gives no dates for Beta 2 or the release candidates and links to the full schedule elsewhere; it does not detail which image formats the browser conversion targets; and it does not name a minimum PHP version. It also offers nothing on the effect for users or hosts in Türkiye.
The UNALSOFT view
We read this less as an "update now" alert and more as a preparation calendar. A beta does not go on a live site, but before the December 8 target it is reasonable to run a copy of your site on it and watch how the theme, plugins and media flow behave. Your image upload setup, the keys your plugins store and your editors' habits are the main things to check. On the web design side we trial version jumps like this in a test environment first. Because the source carries no data about Türkiye, this article proposes no local conclusion.
Sources
WordPress.org News, WordPress 7.2 Beta 1 is ready for download and testing
Is your WordPress site ready for the next release?
A short conversation is enough to plan testing your theme, plugins and media flow on a staging site.