WordPress 7.2 is in public beta, and the final release is only weeks away. This guide is for site owners, freelancers and agencies who want to know what is changing and how to check their sites against the beta before December. Everything below comes from official WordPress.org and Make WordPress pages. Release dates are targets, and the schedule itself warns that last-minute adjustments are possible.
Contents
Where the 7.2 schedule stands
According to the official WordPress 7.2 release schedule on Make WordPress, Beta 1 was due on October 20, 2026, and Beta 2 on October 27. The announcement posts for both are live on wordpress.org/news. The same schedule lists the following milestones, all at 15:00 UTC:
| Date (2026) | Milestone |
|---|---|
| November 3 | Beta 3 |
| November 10 | Beta 4 |
| November 17 | Release Candidate 1 |
| November 24 | Release Candidate 2 |
| December 1 | Release Candidate 3 |
| December 7 | Dry run and 24-hour code freeze |
| December 8 | WordPress 7.2 final release |
Treat these as planning dates, not promises. The schedule post says changes will be announced in a new post. Check it before you book client work around a specific day.
What is in 7.2 so far
The Beta 1 announcement groups the highlights into editing features and developer features. The Beta 2 post says it adds enhancements and fixes but does not list individual changes, so the list below reflects Beta 1 plus the testing call. Features can still change before the final build.
Enjoying this? Get our best tips by email
Practical SEO, link building and content strategies, straight to your inbox.
For editors and designers
- Responsive controls: viewport-specific styling reaches more tools, including Gallery settings for columns, cropping and aspect ratios.
- Global Styles: a “Customized” filter finds blocks with modified styles, inherited values show in block inspector controls, and form elements can be styled.
- Text shadows: controls per block, or as presets defined in theme.json.
- Notes: emoji reactions, a new toolbar icon, margin display, and a minimized mode. Notes and block settings can stay open together.
- Media uploads: client-side processing in the Media Library can resize, compress and convert images in the browser before upload.
- Navigation: menu items can be added, organized and edited from the Site Editor sidebar.
- Dashboard and admin: an “On This Day” widget, admin bar and sidebar Dashicons replaced with icons from the WordPress icon library, and admin assets that load individually for better caching, plus prefetching of likely next admin screens.
For developers
- Secrets API: a standard way to store sensitive credentials, with encryption at rest, credential rotation and customizable storage providers.
- Random content redirects: a dedicated URL sends visitors to a randomly selected post.
- Abilities API and Interactivity API: further additions, including new ways to render trusted HTML in the Interactivity API.
- HTML API and block supports: improvements to markup processing and styling control.
The official testing call also mentions a new default theme named Ipsum, test cases for media inserter changes, and a setting to disable metabox rearranging. If you have read our explainer on the WordPress 7.0 AI features, the Abilities API work here is the continuation of that thread.
Never test on a live site
Both beta announcements say the same thing: the beta is for testing and development only, and should not be run on production or mission-critical sites. Use a local site or a staging copy. If your host offers one-click staging, that is the simplest route. Otherwise clone the site by hand.
Before you copy anything, make sure you have a restorable backup of the live site. Our guide to automatic off-site WordPress backups covers that setup. Also make sure the staging copy cannot send real emails, process real payments or ping live APIs, and that search engines are blocked from indexing it.
Four ways to run the beta
1. WordPress Beta Tester plugin
Install and activate the WordPress Beta Tester plugin on the staging site. Go to Tools, then Beta Testing, choose the “Bleeding edge” channel and the “Beta/RC Only” stream, and save. Then open Dashboard, then Updates, and update to the beta. The Make Test post also lists a nightly option, which is less stable than the beta stream.
2. WP-CLI
From the WordPress root of the staging site, run wp core update --version=7.2-beta2. The testing post notes you can substitute later builds, such as 7.2-RC1, as they appear. This suits agencies that script their staging refreshes.
3. WordPress Playground
Playground runs WordPress in your browser with no setup. The beta announcements link to a 7.2 instance on PHP 8.3 with networking off. It is good for a quick look at the editor changes, but it does not contain your theme, plugins or content, so it cannot replace a staging copy.
4. Direct zip download
Download the beta zip from wordpress.org and install it on a test site manually. This is the fallback when you cannot use the plugin or WP-CLI.
A staging checklist for themes and plugins
The Make Test post includes a general checklist. Here is a version adapted for client sites:
- Turn on debugging in
wp-config.phpin staging, then update all themes and plugins to their latest versions. - After the core update, check whether any plugin or theme deactivated itself.
- Open Site Health and look for new warnings.
- Review templates, patterns, posts and pages for layout or spacing changes. Pay extra attention to anything using galleries, navigation or custom styles, since those areas are changing.
- Click through links and permalinks looking for 404s. Check media, sitemap and robots.txt.
- Log in as each user role and confirm the right tools appear.
- Create and edit a post, paste content, and add media while watching the browser console and PHP error log.
- Verify scheduled tasks, backups, forms, payment gateways and analytics tags.
- Test in several browsers, on mobile, and on a slow connection. Spot-check keyboard navigation and contrast.
Extra checks based on 7.2 changes
- Custom admin CSS or scripts: the admin icon swap and the change to loading assets individually could affect plugins that style or depend on admin assets. Check your admin screens at several zoom levels and color schemes.
- Embedded or custom HTML: the testing post asks people to try nested HTML, custom tags, script tags and shortcodes after the HTML API hardening. Look for truncated or broken content.
- Image uploads: try animated GIFs and WebP, plus AVIF and HEIC, in Media, then Add New. The post says Chromium browsers use client-side processing, and Safari and Firefox should fall back to server-side processing. If you run an image optimization plugin, confirm the two do not conflict.
- Plugins that store API keys: the Secrets API is new, so existing plugins will not use it automatically. Developers can review it now to plan adoption.
- Permalinks: the random redirect feature adds a “Random base” field under Settings, then Permalinks. Check it does not clash with an existing URL.
Common mistakes
- Testing on the live site because staging “takes too long”.
- Testing once on Beta 1 and never again. Later betas and release candidates change the code, so rerun your checklist on RC 1.
- Skipping role testing. Editors and shop managers often hit problems admins never see.
- Reporting “it broke” without versions, steps or logs.
How to report a problem
Use the Alpha/Beta area of the WordPress support forums for questions, WordPress Trac for reproducible core bugs, and the Gutenberg GitHub repository for editor bugs. Include the WordPress version, PHP and database versions, theme, active plugins, exact steps and any error logs or screenshots. If you maintain a plugin or theme that breaks, tell the developer before December so a fix can ship alongside the release.
Key takeaways
- WordPress 7.2 is targeted for December 8, 2026, with release candidates planned from November 17. These dates can change.
- Highlights so far include responsive design controls, Notes improvements, client-side image processing, a Secrets API and random content redirects.
- Test only on staging or a local copy, never on production.
- Use the Beta Tester plugin, WP-CLI or Playground, and rerun your checklist on the release candidates.
FAQ
When is WordPress 7.2 released?
The official schedule targets December 8, 2026. It is a target, and the schedule post says last-minute adjustments are possible.
Can I install the beta on my live website?
No. The official announcements say the beta is for testing and development and should not run on production or mission-critical sites.
What is the easiest way to try 7.2 without risk?
WordPress Playground needs no setup and runs in the browser. To test your own theme and plugins, use a staging copy or local site with the Beta Tester plugin or WP-CLI.
Where do I find developer notes for 7.2?
The Beta 1 post does not link a dedicated field guide. It points to the Make Test “what to test” post and the Gutenberg “What’s New” posts. Watch the Make WordPress Core blog for dev notes and a field guide closer to the release candidates.
