WordPress has shipped the first beta of its final major release of 2026. WordPress 7.2 Beta 1 landed on October 20, 2026, opening a roughly seven-week testing window before the release candidate on November 17 and the final release on December 8. For site owners, agencies, and developers, that window is the only moment when feedback can still change what ships — and the only safe moment to discover what the update changes before it reaches client sites.

This is not a quiet maintenance release. Version 7.2 ships a new default theme that breaks a decade of naming tradition, a standardized Secrets API for storing credentials, client-side media processing in the Media Library, and a rebuilt admin loading pipeline — alongside several changes that can quietly break markup, styles, and database code. Here is what actually matters, who it affects, and what to test now.

Meet Ipsum, the default theme that breaks the naming tradition

The most visible change is one users will never install as an update: WordPress 7.2 ships with a brand-new default theme — and it is not named after the year. After more than a decade of year-named themes, core is switching to standalone names that change when the design calls for it rather than when the calendar turns. The new theme is called Ipsum, named after lorem ipsum, “the placeholder that fills a page until real content arrives.”

According to the October edition of the WordPress Developer Blog, Ipsum is an intentionally minimal blog theme — a blank canvas with dotted underlines, a handful of typesets, and headers, heroes, and sidebars that stay out of the way while you write. Its style variations go further than most: they “re-ink” the whole page, images included. Notably, the team says every combination of styles meets WCAG AA accessibility standards, not just the default design.

The theme is open for testing now in its public GitHub repository. For agencies, Ipsum matters less as a theme to deploy and more as a signal: default themes no longer reset on an annual clock, and the design direction — minimal, type-led, accessibility-first — is a preview of where core’s visual language is heading.

The editing experience gets sharper

Most of what end users will feel lands in the block editor. Building on the responsive design improvements introduced in 7.1, WordPress 7.2 expands viewport-specific styling to more design tools and blocks — including responsive Gallery settings where columns, image cropping, and aspect ratios can all vary by breakpoint.

Global Styles becomes easier to reason about: a new Customized filter finds blocks with modified styles, and inherited values now display directly in block inspector controls. The headline smaller additions:

• Text shadow controls — through block settings and theme.json presets, for consistent typography site-wide.
• Notes improvements — emoji reactions, notes in the editor canvas margin, and Notes openable alongside the block settings sidebar. Collaboration is a growing theme across editors this year: real-time co-editing recently landed in ChatGPT Slides too.
• Easier navigation management — links addable, organized, and editable from the editor sidebar.
• Gallery grid variation — a Grid layout alongside Flex, with rules scoped to the layout in use.
• “On This Day” dashboard widget — resurfaces content published on the same date in prior years, a nudge to refresh or reshare older posts.
• A DataForm-powered block inspector — a refreshed, more consistent approach to block settings.

Under the hood: the changes that matter for site health

The most consequential half of 7.2 is invisible to content editors — and it is where this release earns attention.

A real Secrets API

WordPress 7.2 introduces a Secrets API: a standardized, secure way for developers to store sensitive credentials such as API keys and authentication tokens, with encryption at rest, credential rotation, and customizable storage providers. If you have ever seen a plugin store an API key in plain text in the options table, this is the replacement core finally provides — though the roadmap notes it is tentative and CLI-only in 7.2, with a settings UI planned later. The broader direction echoes an industry-wide shift we recently covered in Microsoft’s new AI agent controls: treat credentials and access as managed infrastructure, not strings scattered across settings screens.

Client-side media processing reaches the Media Library

WordPress 7.2 expands client-side media processing to the Media Library: images can be resized, compressed, and converted directly in the browser before upload. That means faster uploads, less server resource usage, and better support for modern image formats — particularly on hosting with limited image-processing capabilities. Until browsers took over the job, the pragmatic fix was converting and compressing images before upload — the kind of task free browser-based utilities like WebReOn Tools handle well.

A faster administration experience

WordPress 7.2 modernizes how admin scripts and stylesheets load: instead of combining assets into large files, it loads them individually for better browser caching, while a prefetching mechanism anticipates your next admin screen and loads its resources in advance. Dashboard, post list, and editor navigation should all feel snappier.

New APIs and the shape of WordPress’s AI era

The Abilities API expands with new capabilities for querying WordPress data — a consistent foundation for integrations, automation, and AI-powered tools. The Interactivity API gains ways to render trusted HTML and manage reactive navigation. Notably, the core roadmap keeps dedicated AI work, such as Abilities and the MCP Adapter, in the AI and MCP Adapter plugins rather than core itself: core is building the plumbing, not the product.

What could break: a testing checklist for agencies and developers

This is the part that justifies a staging site. Most 7.2 changes are additive, but several can quietly break markup, styles, or database code. The developer blog’s October edition — an unusually practical walkthrough this month — flags the following. Test each before December 8.

1. The wp_kses() rebuild. WordPress’s HTML sanitizer is being rebuilt on top of the HTML API, targeting 7.2 or 7.3 depending on testing. The new parser normalizes its output, strips the contents of <script> and <style> elements, and rejects some malformed SVG, MathML, and comments. If your code sanitizes HTML and then compares, hashes, caches, or snapshot-tests the result, output may no longer match. There is a temporary escape hatch (the wp_kses_force_legacy_parser filter) and a dedicated testing tool — use both, and treat the filter as a stopgap, not a fix.
2. Stroke-based core icons. Roughly 330 core icons are now stroke-based, each setting fill: none inline. A fill prop or CSS fill rule no longer recolors them — use CSS color instead. Audit admin styles targeting core icons, and update @wordpress/icons and @wordpress/components together: mixing the new icons with an older Icon component can silently drop the merged styles.
3. New link-color classes. The Accordion, Tabs, Tab Panel, and Post Template blocks now output has-link-color and related classes. If your theme styles links inside any of those, check for specificity collisions before 7.2.
4. Gallery CSS scoping. Gallery rules are now scoped to :where(.is-layout-flex). Specificity did not change, but any theme CSS that assumes gallery rules always apply should be tested against a Grid gallery.
5. NO_BACKSLASH_ESCAPES. wpdb now strips this SQL mode from WordPress’s own database session. Most sites will never notice — but if one you maintain depends on it, the only fix is the incompatible_sql_modes filter from a db.php drop-in; plugins and mu-plugins load too late.
6. Deprecated components. Gutenberg 24.1 deprecated Divider, ResponsiveWrapper, Scrollable, ZStack, and Elevation in @wordpress/components. They are marked deprecated since 7.2 with removal planned for 7.4 — replace with plain CSS (aspect-ratio for ResponsiveWrapper) or the Separator component.
7. Custom blocks you may not need. The design-tools work in Gutenberg 24.1 switched on existing block supports — background images, gradients, shadows, borders, text columns — for core blocks that lacked them. As one developer analysis put it, this is a good moment for an honest inventory: if a core block now does 90% of what your custom block does, migrating it cuts your testing burden for every future core update.

Also worth knowing: icon collections can now be private via the public argument in wp_register_icon_collection() — hidden from the REST API, and the Icon block will not render them on the front end. Useful for plugin-internal icon sets. And if you ship plugins to the WordPress.org directory, releases now pass through an automated security review — AI models and Jetpack Scan score each new release during the cooldown, high-risk releases are blocked automatically, and committers get emailed the findings. Make sure that email address is one someone reads.

At a glance

How to test WordPress 7.2 Beta 1 safely

The official announcement is explicit: do not install, run, or test the beta on production or mission-critical websites. Use a staging environment, a local install, or a disposable test site. Four routes are available:

• WordPress Beta Tester plugin — install on a test site, select the “Bleeding edge” channel and “Beta/RC Only” stream.
• Direct download — grab the Beta 1 zip and install it on a test website.
• WP-CLI — wp core update --version=7.2-beta1 on a staging instance.
• WordPress Playground — a one-click 7.2 Beta 1 instance in your browser, no setup required. Recent Playground additions (a Dev Tools terminal and an email-capture tool) make it surprisingly realistic for debugging.

Found something? Share it in the Alpha/Beta area of the support forums, or file a reproducible report via WordPress Trac — check it against the known-bugs list first. Scheduled test scrubs run through the cycle; joining one is the fastest way to get a bug in front of the release team while it can still be fixed.

Housekeeping note from the developer blog: September brought three security releases (7.1.1, 7.1.2, 7.1.3) — if any site you maintain missed the auto-updates, handle that before spending an hour on beta testing.

Why this release matters beyond December

Zoom out, and 7.2 looks like a transition release. The DataForm-powered inspector is the visible edge of a deeper admin rebuild. The Secrets API and Application Passwords hardening show core treating credentials as first-class infrastructure. And Ipsum’s naming break is small but symbolic: default themes now evolve on design merit rather than the calendar. Beta 1 is your invitation to help decide what comes next — but only if you test it before December 8. Gutenberg 24.2 and the October developer roundup are good places to track what lands between now and RC1.

Frequently asked questions

Is WordPress 7.2 Beta 1 safe to install?

Only on test environments. Betas can contain unresolved bugs and breaking changes — the whole point of the beta period is to find them. Never install a beta on a production or mission-critical site.

When is the final release of WordPress 7.2?

December 8, 2026, with Release Candidate 1 on November 17. It is the last major WordPress release of 2026.

Do I need to do anything as a site owner?

No immediate action. Auto-updates will bring 7.2 after the final release. If you have a staging copy, testing the beta there — especially media uploads and theme styling — is the best preparation.

Will my theme or plugins break?

Probably not, but there are specific risks: the wp_kses() rebuild can change sanitized output, stroke-based icons need CSS color instead of fill, and new block classes can collide with theme styles. Plugin and theme authors should test during the beta window.

What is Ipsum?

The new default theme shipping with WordPress 7.2 — the first not named after a year. A minimal, blog-focused theme whose style variations restyle the whole page, images included, with every combination meeting WCAG AA standards.

Where can I follow what changes between Beta 1 and the final release?

The “What’s new in Gutenberg” series on Make WordPress Core, the WP-CONTENT.CO weekly newsletter, and the Gutenberg plugin page (wordpress.org/plugins/gutenberg) track new features as they land.

The bottom line

WordPress 7.2 Beta 1 is a release about infrastructure maturing in public: credentials get a proper API, media handling moves into the browser, the admin gets measurably faster, and the editor picks up the kind of polish that only comes from dozens of small refinements. The headline risks — wp_kses(), icons, deprecated components — are all knowable in advance, which is exactly why the beta exists. Test on staging, run the checklist, file what you find, and December 8 will be boring. That is the goal.