WordPress 7.2 release date: 8 December 2026, and what to test before it

The WordPress 7.2 release date is 8 December 2026, according to the Beta 1 announcement WordPress.org published on 20 October. That makes it the third major WordPress release of 2026, after 7.0 in May and 7.1 in August. This page gives the full timetable, what changes, which sites should test carefully, and a plan that also covers the PHP 8.2 deadline three weeks later.

When is WordPress 7.2 released?

WordPress 7.2 is scheduled for 8 December 2026. The Beta 1 announcement of 20 October 2026 says: "The scheduled final release date for WordPress 7.2 is December 8, 2026." The core team's release party schedule gives the full timetable, all at 15:00 UTC:

The schedule post itself warns that "there may be last-minute adjustments", and that is not a formality. WordPress 7.0 was described in January as "currently scheduled for release in April 2026" and actually shipped on 20 May 2026. Treat 8 December as the plan, not a promise. We will update this page when the date changes or 7.2 ships.

Why 2026 has three major releases

WordPress shipped two major releases in 2025 and is on course for three in 2026. Here is the record from the WordPress.org releases page:

More releases mean more chances for a plugin to fall behind, and more update weekends for whoever looks after the site. They also mean the "tested up to" line on plugin pages goes stale faster. Our WordPress statistics page shows how many directory plugins have not been tested against a recent major version.

What is new in WordPress 7.2

7.2 is mostly an editor and admin release, with one security feature that developers will care about. The list below comes from the Beta 1 post and the call for testing published the same day.

For editors and site owners

• Responsive design controls extend to more tools, including Gallery settings.
• Global Styles gets a "Customized" filter so you can see what has been changed from the theme's defaults, plus text shadow controls.
• Notes, the editorial comments added in 6.9, gain emoji reactions and a minimized mode.
• Client-side image processing before uploads, now expanding into the Media Library. The testing post says animated GIF and WebP sub-sizes should "retain full animation by default".
• A new default theme, Ipsum. It is a block theme. It will not replace your theme; it is only bundled.
• Admin changes: SVG icons replace the old icon font in the admin bar and menu, a new DataForm-based post inspector, and a Screen Options toggle to stop accidental dragging of meta boxes.
• An "On This Day" dashboard widget and faster admin loading.

For developers

• Secrets API, with WP-CLI support, "to securely handle credentials". Testers are asked to confirm secrets are encrypted in the database and redacted from REST API responses, debug logs and exports.
• Expanded Abilities, Interactivity and HTML APIs, including a new data-wp-html directive and HTML API hardening.

What could break on your site

Most sites will update without trouble. The risk sits in a few specific places, and the testing post points at most of them.

The testing post asks testers to check whether "any plugins or themes deactivated automatically after the update". That is the failure most owners notice first, usually as a form or a payment method that quietly disappears.

Does 7.2 change the PHP requirement?

No change has been announced. The Beta 1 post and the testing post mention no new PHP or MySQL requirement. The current rules come from the core team's May 2026 PHP clarification: "The minimum supported PHP version is 7.4 since WordPress 7.0" and "The minimum recommended PHP version remains at 8.3." WordPress 7.0 raised the floor from 7.2 after the January 2026 proposal, which cited PHP 7.2 and 7.3 usage "below 4% of monitored WordPress installations".

The PHP deadline that matters this winter is not WordPress's. PHP 8.2 loses security support on 31 December 2026, three weeks after 7.2. If you are testing 7.2 on staging anyway, test it on PHP 8.3 or 8.4 at the same time and do both upgrades in one window. Details in PHP 8.2 end of life.

How to plan the update

1. Now: update to 7.1.3 if you have not. It carries security fixes. See WordPress core exploited in 2026.
2. Now: make a staging copy of the site.
3. From 17 November (RC 1): install the release candidate on staging. Features are frozen by then, so what you test is close to what ships.
4. Test the paths that earn money: forms, checkout, bookings, member login. A homepage that loads proves little.
5. Check plugin pages for "Tested up to 7.2" as authors update them through November.
6. 8 December or soon after: take a full backup, then update the live site in a quiet hour.
7. The following week: watch error logs and Site Health. Apply 7.2.1 when it arrives. First point releases are mostly bug fixes: 6.9.1 fixed 49 bugs and 7.0.1 fixed 31, according to their release posts.

Should you update on release day? For a simple brochure site with few plugins and good backups, yes. For a store or a site with custom code, waiting a few days for plugin updates and the first point release is a reasonable choice. Do not wait months. Major versions are where new security hardening lands.

Deadline checklist

• Today: confirm you are on WordPress 7.1.3.
• By 10 November: staging copy ready, backups tested.
• 17 November to 1 December: test 7.2 RC on staging, ideally on PHP 8.3 or 8.4.
• Before 8 December: list plugins without a recent update and decide whether to replace them.
• 8 December onwards: update live, monitor, apply 7.2.1.
• Before 31 December: off PHP 8.2 or older.

We will update this page when the 7.2 schedule changes or the release ships.