WordPress 7.2 Beta 1: New Features You Can Test Now

WordPress 7.2 Beta 1 was released on Tuesday, October 20, 2026. It pulls in features from Gutenberg 23.7 through 24.3, and it is the last major release planned for 2026. Beta 2 is scheduled for October 27, Release Candidate 1 for November 17 and the final release for December 8, 2026.

We covered the schedule in our post on the WordPress 7.2 release date. This time we have actually tested the beta, so here is what is new, what got pushed back and what it means for your site.

1. Notes now sit in the margin

Notes, the block level commenting feature added earlier this year, has moved out of the sidebar and onto the editor canvas. Comments now sit in the margin beside the block they refer to, much like Google Docs. You can keep Notes open while the block settings sidebar is also open, react with emoji and minimize the whole Notes panel when you want a clean view.

For agencies and content teams, this is the most visible change in 7.2. Reviewing a draft with a client is now far less clumsy.

2. A new Secrets API for API keys

Plugins have stored API keys in the database in all sorts of ways for years, often as plain text in the options table. 7.2 introduces a standard Secrets API with encryption at rest, credential rotation and support for custom storage providers. It works through WP-CLI in this release, and an admin settings screen is planned for 7.3.

This matters more every month as sites connect to AI services, payment gateways and shipping APIs. Once plugin developers adopt it, a database leak becomes much less likely to expose live keys.

3. Text shadows without custom CSS

Text shadow is now a proper block support. You can add it from block settings, and theme authors can define shadow presets in theme.json. It is a small thing, but it removes one of the most common reasons people add a line of custom CSS.

4. Style buttons, inputs and selects from the editor

Form elements such as buttons, text inputs and select menus can now be styled without writing CSS. Block inspector controls also show values inherited from Global Styles, so you can finally see where a style is coming from. A new Global Styles filter called “Customized” lists every block whose styles have been changed.

5. Responsive controls for more blocks

Responsive design controls have been extended to more blocks. The Gallery block is the best example: columns, crop and aspect ratio can now change per breakpoint, and there is a new grid layout. Position can also vary by viewport. If you build with blocks rather than a page builder, this closes a big gap.

6. Client side image processing

The Media Library can now resize, compress and convert images in the browser before they upload. That means less work for your server and smaller files by default. For people on cheap shared hosting, where large uploads sometimes fail, this could be quietly one of the most useful changes.

7. Faster admin screens

Admin scripts and stylesheets now load individually, which helps caching, and a prefetching system loads resources for the screen you are most likely to open next. Dashicons in the admin bar and sidebar have been replaced with icons from the WordPress icon library, and about 330 core icons are now stroke based.

8. An “On This Day” dashboard widget

A new dashboard widget shows posts you published on the same date in previous years. It is a nice nudge for bloggers and publishers to refresh and reshare older content, which is good for SEO too.

9. Ipsum, the new default theme

WordPress is dropping the “Twenty” naming. The new default theme is Ipsum, a minimal blog theme. The team says every style variation meets WCAG AA contrast, which is a solid base for accessible sites.

What was pushed to WordPress 7.3

Suggestion mode for Notes, which lets people propose edits that can be accepted or rejected. It was meant to be the headline feature and has now missed two releases.
The Table of Contents block, in development since 2022.
The Secrets API settings screen.

A full React 19 upgrade is also unlikely to land completely in 7.2, although the Gutenberg plugin now runs React 19 by default.

Changes developers should know about

wp_kses() is being rebuilt on the HTML API, targeting 7.2 or 7.3. A wp_kses_force_legacy_parser filter restores the old behaviour temporarily.
NO_BACKSLASH_ESCAPES is disabled by default for WordPress database sessions.
Several components, including Divider, Scrollable and ZStack, are deprecated for removal in 7.4.
The Abilities API has been expanded, but the MCP Adapter and AI features still live in separate plugins, not in core.

How to test WordPress 7.2 Beta 1 safely

Never test on a live site. Use a staging copy or WordPress Playground.
On a staging site, install the WordPress Beta Tester plugin, or run wp core update --version=7.2-beta1.
Test your theme, page builder, forms and checkout.
Check custom code that filters HTML, since the wp_kses() rebuild could change output.
Report bugs on WordPress Trac or the Gutenberg GitHub repository.

What this means for businesses in the US, UK and Australia

For most business owners the advice is the same wherever you are: do not update your live site on December 8. Wait one or two minor releases, until 7.2.1 or 7.2.2, and let Elementor, WooCommerce and your SEO plugin catch up.

Timing matters too. In the US, December 8 sits right after Cyber Monday and in the middle of holiday shipping. UK retailers will be in peak Christmas trading, and Australian stores will be heading into Boxing Day sales. Plan the update for January, when traffic is quieter.

The accessibility focus is a plus everywhere. The Americans with Disabilities Act, the UK Equality Act and Australia’s Disability Discrimination Act all push businesses toward accessible websites, and a WCAG AA default theme helps.

A quick 7.2 readiness checklist for site owners

You do not need to be a developer to get ready for 7.2. Before December, work through this short list with whoever looks after your site:

Update PHP first. After the critical PHP fixes on October 21, every site should be on a patched release of PHP 8.2 or newer. Our PHP security update guide explains how to check.
Remove plugins you no longer use. Every inactive plugin is one more thing that can clash with a major update.
Find where your API keys live. Payment, email and AI plugins often store keys in settings. Once those plugins support the Secrets API, switch them over.
Check your image workflow. If you use an image optimisation plugin, see whether its developer plans to work with the new client side processing, so images are not compressed twice.
Book a staging test for January. Put a date in the calendar now, rather than updating on impulse when the notice appears in your dashboard.

Doing this now means the 7.2 update becomes a fifteen minute job instead of an emergency.

Want a closer look at the new default theme? Read Ipsum: WordPress 7.2’s new default theme explained.

Sources

Need a hand with this on your own site? See our WordPress development services.

Frequently asked questions

When is WordPress 7.2 released?

The final release is planned for December 8, 2026. Beta 2 is due October 27 and RC1 November 17.

Is WordPress 7.2 Beta 1 safe for my live site?

No. Betas are for testing only. Use a staging site or WordPress Playground.

Will WordPress 7.2 break Elementor?

It should not, but page builders usually ship compatibility updates around launch. Wait for those before updating a live site.

Can Web Brick Studio test my site for 7.2?

Yes. We set up a staging copy, test 7.2 against your theme and plugins and fix anything that breaks before you update. Get in touch.

WordPress 7.2 Beta 1 Is Out: 9 New Features Worth Testing Before December