WordPress 7.2 Beta 1 Is Out: New Design Settings and Editor Tools
WordPress 7.2 Beta 1 brings responsive design settings, updated editor tools, and new features for developers. The beta is for testing, not for use on live sites.
On October 20, the WordPress team released the first beta of WordPress 7.2, as reported by WordPress News. It expands design settings for different screen sizes, changes how notes and media files work, and introduces new tools for developers. The beta is strictly for testing: it should not be installed on a live or mission-critical site.
What’s changing in the editor and design settings
WordPress 7.2 offers more settings that can be configured separately for different screen sizes. In the Gallery block, for example, you can change the number of columns, image cropping, and aspect ratio based on screen width. This builds on the responsive design changes introduced in WordPress 7.1.
Managing a site’s overall appearance should get easier, too. A new Customized filter helps you find blocks whose styles have been changed, while inherited global style values are now visible directly in block settings. Styling for form elements has been added. Text now has shadow settings: you can set a shadow on a block or save it as a preset in theme.json to keep styling consistent across the site.
Menus can now be built and edited in the Site Editor sidebar: you can add items, reorder them, and edit links without leaving the page-editing workflow. Block settings also have an updated inspector built on DataForm. Its purpose is to make controls more consistent and provide a foundation for future editor changes.
Collaboration notes have moved onto the editor canvas, closer to the content being discussed. They now support emoji reactions and have a dedicated toolbar icon. You can keep notes and the block settings sidebar open at the same time; if discussions get in the way, you can collapse them. The developers have also improved error messages and other everyday editor interactions.
Media, the admin area, and developer features
Browser-side image processing now extends to the Media Library. Images can be resized, compressed, and converted before they’re sent to the server. This may speed up uploads and reduce server load, especially on hosting plans with limited image-processing capabilities. For now, this is a beta feature, not a guaranteed speed boost for every site.
The dashboard has a new On This Day widget showing posts published on the same date in previous years. In the admin interface, outdated Dashicons are being replaced with icons from the WordPress icon library. Script and style loading is changing, too: rather than being bundled into large files, they’re loaded separately to improve browser caching. Prefetching resources for the next likely screen should make moving between admin sections faster.
For developers, a notable addition is the Secrets API. It offers a standard way to store sensitive data, such as API keys and tokens, with encryption at rest, credential rotation, and a choice of storage methods. The Abilities API is also being expanded to support access to and queries of WordPress data. The Interactivity API is gaining support for rendering trusted HTML and managing reactive navigation. HTML handling has been improved, and custom block developers get more control over how their blocks look and display across devices.
Another new feature is a URL that takes visitors to a randomly selected post. It could help readers discover older content. WordPress 7.2 will also include features that were previously available only through the Gutenberg plugin.
What site owners and teams should test
For site owners and marketers, the most straightforward things to test are the responsive gallery, form styling, menu-editing workflow, and finding older posts through the new widget. If several people work on your pages, you can see whether it’s convenient to discuss edits in notes while keeping block settings open. Developers should test their custom blocks and integrations against the new APIs and editor settings.
But all of this should be tested on a staging or local site, not a live one. The beta is intended for development and bug hunting; changes will continue to be refined before the final version. WordPress 7.2 is scheduled for release on December 8, 2026. Users are encouraged to report issues in the support forum’s Alpha/Beta section or, if they can put together a reproducible report, through WordPress Trac.
My take
What interests me most in this beta is the settings for different screen sizes: when you’re laying out a page, you quickly discover that one good-looking image isn’t enough for every size. But I’d test the gallery and forms on a local site first, and only then think about bringing the changes to a live one. A beta and a live site make for a pairing with a questionable sense of humor.
I also like that some edits can be made right in the editor, without jumping between screens. That said, new settings don’t replace the basics: for now, I’d get more out of learning regular CSS than chasing every new layer of tools.
Sources
Where the news comes from. The text is a retelling in the author’s own words; the facts come from the source, the opinion is the author’s.
- WordPress 7.2 Beta 1 is ready for download and testing! wordpress.org
Junior frontend developer
I practice web layout and try different code editors while building a site for a café I know. Sometimes I open too many tutorials—now I’m trying to finish one page first.
All posts by the authorRelated articles
WordPress 7.1.4 Fixes 22 Vulnerabilities, Including a Core Update Risk
WordPress 7.1.4 fixes 22 vulnerabilities, including a potential remote code execution risk during core updates. Site owners should check whether the update is installed.
Jetpack 16.3 Adds Video and Meeting Booking Blocks to WordPress
Jetpack 16.3 introduces blocks for VideoPress playlists and Zoom meeting bookings. The update also expands Forms and reorganizes the plugin’s settings.
WordPress 7.1.3 Fixes Seven Vulnerabilities and an Image Upload Failure
WordPress 7.1.3 fixes seven vulnerabilities and a critical bug that prevented image uploads on some hosting setups. Site owners are advised to install the update.
Discussion 5
Paulo Figueira
For the responsive Gallery settings, do the per-screen-size values carry over cleanly to existing sites, or will teams need to review and adjust galleries after updating? I’d want to know what staff should check before scheduling the upgrade.
Andreas Pavlou
@paulo.figueira In my guesthouse, gallery layouts often get tweaked to fit seasonal photos, so I’d test a few existing pages at phone and desktop widths before upgrading; I wouldn’t assume the new per-screen settings will preserve every intended layout without a check.
David Galstyan
@andreas.pavlou One extra check: compare the Gallery block’s saved column count and aspect ratio at each breakpoint, not just the rendered desktop and phone views. The new settings may expose differences that were previously hidden in a single layout.
Zdeněk Damberg
@davit_galstyan That breakpoint-by-breakpoint comparison is useful; I’d also check whether the gallery’s image-cropping setting still looks intentional on narrow screens, since the new responsive controls can make a previously shared crop behave differently across widths. For a site team, a quick pass through a few content-heavy pages before updating would catch that without needing to inspect every block.
Paweł Mazurek
@zdenek_dev Does Beta 1 document how existing shared crop values map to the new responsive settings, or is that still something teams need to verify on their staging site?