WordPress 7.2 is scheduled for release on . It is currently in beta, so nothing described here is final until the release post goes out. Features can still change or be pulled before launch.

This guide covers what the official Beta 1 announcement and the Roadmap to 7.2 say is planned, which roadmap items were not mentioned in the beta, and a practical update checklist so your site is ready without rushing.

Status as of 29 October 2026: WordPress 7.2 is in beta testing. Everything below describes planned features from official WordPress.org posts, not shipped functionality. Please do not install betas on a live site.

When Is WordPress 7.2 Coming Out?

The release schedule on make.wordpress.org lists these milestones. The older WordPress.org roadmap page still showed 10 December, but the release schedule and the beta announcements both say 8 December.

Timeline of WordPress 7.2 milestones from Beta 1 on 20 October to the target release on 8 December 2026
The official schedule, checked on 29 October 2026. Dates can still move.
DateMilestone
20 October 2026Beta 1 (feature freeze)
27 October 2026Beta 2
28 October 2026Beta 3, released alongside 7.1.4
3 and 10 November 2026Beta 4 and Beta 5
17 November 2026Release Candidate 1
24 November and 1 December 2026RC 2 and RC 3
8 December 2026Planned final release

What's Planned for WordPress 7.2?

The Beta 1 announcement on 20 October 2026 lists the following. I have grouped them by who they matter to.

For editors and site owners

Two-column graphic comparing features announced in WordPress 7.2 Beta 1 with roadmap items not mentioned in the beta post
What the beta post announced versus what the earlier roadmap hoped for.

For developers

Glowing vault drawer holding sealed key cards with a rotation symbol above, representing the planned Secrets API
The planned Secrets API aims to give plugins one standard, safer place for credentials.

The Secrets API is the item I am watching most closely. Today, the Connectors screen in WordPress 7.0 stores database-saved API keys masked but not encrypted, which is why I recommend keeping keys in wp-config.php or environment variables. See how to set up AI Connectors safely for the current approach.

Which Roadmap Features Might Not Make It?

The Roadmap to 7.2, published on 18 September 2026, also mentioned several items that were not included in the Beta 1 announcement:

The roadmap also names a new default theme called Ipsum. The Beta 1 post only alludes to it in its closing haiku, so look for the details in later beta notes and the release post.

The roadmap itself says that what it lists "doesn't necessarily mean each will make it into the final release". Some coverage has reported that several of these did not make the feature freeze. I would treat them as "maybe in a later release" until the final 7.2 release post or Field Guide confirms otherwise.

How Should You Prepare Your Site for WordPress 7.2?

Most of the work happens before 8 December. Here is the order I follow for client sites.

1. Stay current on 7.1.x now

Security releases come first. WordPress 7.1.4 shipped on 28 October 2026, and my 7.1.4 security update guide covers what it means for you. There is no benefit to waiting for 7.2 while running an unpatched 7.1.

2. Check your PHP version

Look under Tools → Site Health → Info → Server. If you are still on PHP 8.2, plan that upgrade separately, as explained in the PHP 8.2 end-of-life guide. Do not combine a PHP upgrade and a major WordPress update on the same day.

3. Test the beta or RC on staging

Staging server under a scanning beam beside a website mock-up being inspected with magnifying glasses and warning markers
Test on a copy of the site, never on production. Release candidates are the best time to catch problems.

Clone the site to staging and test with the WordPress Beta Tester plugin or WP-CLI. On a staging copy only, replacing the version with the latest beta or RC number:

wp core update --version=7.2-beta2

Then check the journeys that matter: editing posts, the Site Editor, forms, checkout, logins, and any custom blocks. If you have custom plugins that use the Abilities API, read the 7.2 dev notes as they are published.

4. Wait a few days after release, then update

For business sites, I usually wait a few days after a major release for early fixes, unless a security fix is involved. Take a fresh, tested backup first. If you need a refresher, see how to restore WordPress from a backup, and what a good maintenance plan includes.

Never test betas on a live site. WordPress.org says the same in every beta announcement. A beta can break editing, plugins or front-end layout, and rolling back a database is far harder than restoring a staging copy.

WordPress 7.2 Update Checklist

Eight-point WordPress 7.2 update checklist from staying on the latest 7.1 release to updating live and monitoring
Print it, or copy it into your maintenance ticket.

Frequently Asked Questions

When is WordPress 7.2 released?

The official release schedule lists 8 December 2026 as the planned release date. Beta 1 arrived on 20 October 2026, and Release Candidate 1 is scheduled for 17 November 2026. Dates can still change.

Is the Table of Contents block in WordPress 7.2?

It was on the Roadmap to 7.2 but was not mentioned in the Beta 1 announcement. Treat it as uncertain until the final release post confirms it.

What is the WordPress 7.2 Secrets API?

According to the Beta 1 post, it is a planned standard way for developers to store sensitive credentials such as API keys, with encryption at rest, credential rotation and customisable storage providers.

Should I update to WordPress 7.2 on release day?

For most business sites, test on staging during the release candidates, then update live a few days after release with a fresh backup. Apply security releases promptly as always.

Final Thoughts

WordPress 7.2 looks like a steady, practical release: better design controls, a faster admin and, if it lands as planned, a proper Secrets API for developers. None of it needs panic. It needs a backup, a staging site and a bit of time before 8 December.

If you would rather someone else handled the testing and update, that is exactly what my website maintenance service covers.

Plan early, test on staging, and update when you are ready rather than on day one.

Official References

Sources checked on 29 October 2026: