Introduction: the last big WordPress release of 2026 is now testable
I have a rule I learned the expensive way: never judge a WordPress release by its announcement post, and never install a beta on a live site. The first rule keeps me honest. The second has saved more client weekends than I can count.
WordPress 7.2 Beta 1, announced on October 20, 2026 by release coordinator David Baumwald, is the final major WordPress release of the year. The final release is scheduled for December 8, 2026, and Beta 2 is due today, October 27. That gives site owners about six weeks to find problems that only show up on real sites, with real plugins and real content, before the update reaches everyone.
This release is built around unglamorous work that makes WordPress safer and easier to build on: a standard way to store credentials, a better way to leave feedback on a post, a cleaner default theme, and performance work under the hood. If you build with Elementor the way I do, those changes quietly affect your daily work.
The road to December 8: the beta schedule
WordPress 7.2 rolls in features from Gutenberg versions 23.7 through 24.3. After Beta 1, the published schedule is: Beta 2 on October 27, Beta 3 on November 3, Beta 4 on November 10, Release Candidate 1 on November 17, Release Candidate 2 on November 24, Release Candidate 3 on December 1, a dry run on December 7, and the final release on December 8, 2026 at 15:00 UTC.
Dates can still shift during the beta cycle, and features are only truly locked once the release candidates arrive. The release team is public: Matt Mullenweg is the release lead, David Baumwald runs release coordination, and George Mamadashvili and Peter Wilson are the technical leads. Start testing now, while a fix can still land.
The Secrets API: the headline feature, and why it matters
The change developers will notice first is the new Secrets API. In plain terms, it gives WordPress a standard, built-in way to store sensitive credentials, such as API keys and authentication tokens, instead of every plugin inventing its own method.
If you have ever audited a WordPress site, you know why this matters. One plugin stores an API key in plain text in the options table. Another hides it in wp-config.php. A third encrypts it with its own scheme nobody else can read or rotate. With no standard, there is no consistent answer to basic questions: is this key encrypted, and how do I rotate it if it leaks?
The Secrets API, tracked in Trac ticket 66187, aims to fix that at the core level. It provides encryption at rest, supports credential rotation, and lets developers plug in a custom storage provider. A small blog and a large agency site do not need the same storage backend, and a standard API with swappable providers means plugins can stop rolling their own crypto and use the same well-reviewed path.
Be honest about the limits, though. This is a developer API in Beta 1, not a settings screen you will click through as a site owner. The visible payoff arrives over following releases, as plugins adopt it — but the timing is good, since AI plugins, payment integrations, and email services all need API keys now, and 7.2 starts giving the question "where are my keys?" one answer instead of five.
Notes move into the margin, and they finally stay out of your way
Notes, the commenting and feedback feature that shipped in WordPress 6.9, gets the most visible rework in 7.2. In Beta 1, Notes move into a margin the editor reserves beside the canvas, so you can read feedback and keep the block settings sidebar open at the same time. They also pick up emoji reactions, a new toolbar icon, and a minimized mode to reduce clutter.
That sounds small until you have reviewed a long post with a client. In the previous layout, feedback and settings competed for the same space, and you kept switching between reading a comment and editing the block it referred to. The margin layout removes that friction: you read the note, look at the block, fix it, and never lose your place.
Ipsum: a new default theme that is deliberately almost nothing
WordPress 7.2 introduces Ipsum, a minimal block theme described by the core team as a "blank canvas" for blogs. Default themes are not supposed to compete with premium themes or page builders. Their job is to give a brand-new install something clean, fast, and readable on day one.
For developers, Ipsum is also a useful reference: a clean baseline to test whether a problem comes from the theme or a plugin. Switch to Ipsum, and if the problem disappears, you know where to look. If you run Elementor or a custom theme, Ipsum changes nothing about your live site. Its value is for new sites and for testing.
Design tools: text shadows and form styling arrive in Global Styles
WordPress 7.2 adds text shadows to the design tools, and form element styling to Global Styles, letting you style forms consistently from the site-wide settings rather than wrestling each form plugin's output into shape.
Form styling is the bigger deal of the two. Forms are where many WordPress sites fall apart visually: the theme styles one thing, the form plugin styles another, and the result looks like it belongs to a different website. Bringing form styles into Global Styles means one place to set the look, applied consistently. Text shadows fill a smaller gap: a standard tool for headings over images.
Under the hood: faster admin, smarter media handling, and a quiet database change
First, the admin gets faster in a structural way. WordPress 7.2 loads admin scripts and stylesheets individually instead of in large combined files, for better browser caching, and it adds prefetching, which loads the likely next admin screen ahead of time. It also permanently drops load-scripts.php and load-styles.php, two files inherited from WordPress 2.3. That cleanup is also a compatibility flag: any custom admin code depending on the old combined loading needs checking now, not after the December release.
Second, client-side media processing extends to the Media Library. Images can now be resized, compressed, and converted in the browser before upload, which helps particularly on hosting with limited image-processing capabilities. On budget shared hosting, image processing is often the first thing to time out, so doing more of that work in the browser means fewer failed uploads and less server load.
Third, a quiet database change: the NO_BACKSLASH_ESCAPES SQL mode is now turned off by default, according to a Make Core development note. Most site owners will never notice. But if you run custom database code, add it to your test list.
What got pushed to 7.3, honestly
A good beta report says what is missing. Two headline items on the 7.2 roadmap will not ship in this release, and both have now missed two releases in a row. Suggestion mode for Notes, which would let people on the same post propose edits for acceptance or rejection, has been punted to 7.3. Automattic's Architecture and Open Source Director Anne McCarthy flagged that it still felt too early to merge confidently, despite good publisher feedback, and suggested developing it as a Gutenberg plugin experiment first. The Table of Contents block was also punted to 7.3.
I respect that call. A delayed feature is disappointing for a week; a broken collaboration feature is a trust problem for months. Real-time collaboration and React 19 are not part of this release either, and nothing here is locked until Release Candidate 1.
What this means if you build with Elementor
WordPress 7.2 does not change how Elementor works, and nothing in Beta 1 suggests Elementor users need to do anything special. But every major release is a compatibility event for a page-builder site, and 7.2 has three things I would check on staging.
First, test your forms. Form styling in Global Styles is new, and Elementor sites often have forms styled by Elementor, a form plugin, and the theme at the same time. Check they still look right. Second, test your media workflow: run a full upload, resize, and replace cycle on staging, especially if you rely on a media or image optimisation plugin. Third, test anything custom in the admin, since the removal of the old combined asset loading is the change most likely to catch custom admin code off guard.
My broader checklist is boring in the best way. Clone the live site to staging, including the database. Update WordPress to the beta there, and nothing else, so you know what caused any problem. Click through the homepage, a post, a page, and the contact form, then update plugins one at a time, and only then the theme. One more rule: never run a beta on production. Betas contain bugs. That is their job. Your live site is not the place to find them.
Conclusion: a foundation release, and that is a compliment
WordPress 7.2 Beta 1 will not make headlines the way a new editor would, and that is fine. The releases I trust most are the ones that fix foundations: a standard way to store secrets, a feedback tool that stays out of your way, a clean default theme, faster admin loading, and media handling that works on modest hosting.
If you build WordPress sites, the next six weeks are your window. Spin up a staging copy, test your forms, your media, and your admin customisations, and report what you find — core bugs on WordPress Trac, editor bugs in the Gutenberg repository. I will be testing it on staging this week, starting with the Secrets API and form styling. The beta is free, the Playground instance takes minutes, and the worst outcome of testing is learning your site is already ready.
FAQ
When will WordPress 7.2 be released?
December 8, 2026 at 15:00 UTC, after four betas and three release candidates. Beta 2 is due October 27, 2026, with Beta 3 on November 3 and Beta 4 on November 10.
Is WordPress 7.2 Beta 1 safe for a live website?
No. The WordPress team explicitly asks people to test on a staging site, not on production or mission-critical sites. Betas can contain bugs that break themes or plugins.
What is the Secrets API in WordPress 7.2?
A new standard way for WordPress and plugins to store credentials such as API keys and authentication tokens, with encryption at rest, credential rotation, and custom storage providers. It is a developer API in Beta 1, not a dashboard settings screen.
What is Ipsum, the new default theme?
A minimal block theme described by the core team as a "blank canvas" for blogs. It gives new installs a clean starting point and serves as a baseline for testing whether a problem comes from a theme or a plugin.
How do I test WordPress 7.2 Beta 1?
Use the WordPress Playground Beta 1 instance, the Beta Tester plugin on a staging site, WP-CLI with wp core update --version=7.2-beta1, or a manual download from WordPress.org. Never test on a production site.
What happened to Notes suggestion mode and the Table of Contents block?
Both were punted to WordPress 7.3. Suggestion mode was judged still too early to merge, and the core team suggested developing it as a Gutenberg plugin experiment first.
