WordPress 7.2 is scheduled for release on December 8, 2026. It will be the year’s final major WordPress release, with work planned across security, blocks, design tools, collaboration, media, performance, accessibility, and the Site Editor.
The key word is planned. The official WordPress 7.2 roadmap describes work contributors are actively pursuing, but it isn’t a final list of features. Some items may change, move to a later release, or remain in plugin testing.
With that in mind, here is what WordPress developers should be watching.
Security improvements
Security is one of the larger areas of work for WordPress 7.2.
The roadmap includes several Application Password improvements. Planned work covers email notifications when an application password is created, clearer handling of local and non-HTTPS environments, safer default-role behavior, and support for the SameSite cookie attribute.
WordPress is also considering a new Secrets API. The proposal would give Core and plugins a standard way to store credentials and other sensitive values. The proposal includes WP-CLI support, with a dedicated graphical interface planned for a later release.
Developers should not interpret this as a command-line-only feature. The proposal is for a programmatic API with WP-CLI integration. You can read the full Secrets API proposal on Make WordPress Core.
Initial work is also beginning on a possible “sudo mode.” This would require users to authenticate again before carrying out especially sensitive administrative actions, even when they are already logged in. The roadmap treats this as early-stage work rather than a confirmed WordPress 7.2 feature.
Core contributors are also continuing to improve WordPress’s HTML processing. The aim is to make parsing and handling markup safer and more reliable.
New blocks and API work
WordPress 7.2 may add two useful blocks to the standard block library.
A new Description List block would provide native support for semantic <dl>, <dt>, and <dd> markup. This is useful for glossaries, product specifications, metadata, and other term-and-description layouts.
The long-running experimental Table of Contents block is also being prepared for stable use. The current plan moves it to server-side rendering so the editor and front end use the same heading data.
The Icon block may gain keyword search. This would let searches like “hamburger” or “navigation” find a menu icon even when those words aren’t part of the icon’s visible label.
The Interactivity API has two main initiatives planned for this cycle. One adds a data-wp-html directive for reactively rendering markup that application code has explicitly marked as trusted. The other gives developers a supported way to observe client-side navigation and determine what initiated it.
The technical work is tracked in the official Interactivity API issue for WordPress 7.2.
React 19 is unlikely to arrive in full
Work continues to make Gutenberg compatible with React 19. Types, dependencies, and rendering fixes are progressing, but the Core roadmap says the upgrade is unlikely to land fully in WordPress 7.2.
Plugin and theme developers should therefore avoid treating React 19 as a confirmed part of this release. Watch the development notes and test against the beta rather than changing production requirements based on the roadmap alone.
Better block design tools
WordPress 7.2 is expected to continue the design work introduced in earlier releases.
Global Styles may gain an interface for styling common form elements, including buttons, text inputs, select fields, labels, and interactive states. Some of this support already exists in theme.json; the planned work makes it available through the editor.
Responsive styling is also being expanded. The team is working on support for more controls and a public API that third-party blocks can use with responsive styles.
Custom block states are another area to watch. The current plan includes a -current state for Navigation Link and Tabs blocks, along with more color, border, and spacing controls for navigation links.
The editor may also begin showing inherited Global Styles in individual block settings. For example, if paragraph text is set to red globally, that value should appear when someone inspects a Paragraph block. This should make the difference between global values and local overrides easier to understand.
These projects are listed in the WordPress 7.2 roadmap’s design and editor section.
A more extensible Site Editor
The WordPress team is building a new foundation for the Site Editor using the @wordpress/boot routing package.
The important change for plugin developers is extensibility. The planned server-side view configuration would let plugins register screens and settings inside the Site Editor instead of building separate APIs and administrative pages for every integration.
DataViews and DataForms follow the same direction. Work is underway to register views, forms, fields, and actions on the server. We’re also developing a DataForm-based post inspector to handle fields such as featured image, excerpt, status, date, author, and template.
Other planned admin work includes:
- Clearer error messages with a copy button
- Better navigation editing in the Site Editor sidebar
- Further work on the Omnibar and command palette
- Replacing more Dashicons with SVG icons
- A possible “On This Day” dashboard widget for resurfacing older content
The “On This Day” widget was postponed during the WordPress 7.1 cycle, so it should still be treated as tentative.
Notes will improve, but real-time collaboration is not planned
The WordPress 7.2 roadmap deliberately excludes full collaborative editing. Architectural work continues, but the Core team does not expect real-time multi-user editing to ship in this release.
Notes, also known as block comments, are a different story.
The centerpiece of the current Notes work is suggestion mode. This would let someone propose an edit that another user can accept or reject. Emoji reactions and a block-toolbar shortcut for adding notes are also planned.
This distinction matters. WordPress 7.2 may deliver better editorial collaboration without delivering simultaneous document editing. The team is tracking this work in the WordPress 7.2 Notes iteration.
Accessibility work
Accessibility improvements run through many of the planned WordPress 7.2 projects, but the roadmap also identifies several dedicated efforts.
These include making admin notices easier for assistive technology to announce, improving keyboard navigation and dismissal behavior, and introducing automated axe-core testing to help catch regressions.
The team also wants to let users disable metabox rearranging. This may reduce accidental layout changes and visual complexity, especially on smaller screens. Another proposal would remove the old widget accessibility mode, reducing the number of separate widget-management experiences WordPress must maintain.
Media improvements
Client-side media processing will continue to mature in WordPress 7.2. The work includes a more reliable upload pipeline, support for more formats, and further performance improvements.
The media inserter is also being redesigned for websites with large media libraries. Dynamic galleries may gain more content sources, while static galleries may receive additional sorting options.
Work on the Media Editor modal focuses on attached media and the relationship between original images and cropped versions. WordPress currently creates cropped images as separate attachments without formally tracking their origin. The proposed work would preserve that relationship and reduce confusion in the Media Library.
Performance work
The Performance team is pursuing two main projects for WordPress 7.2.
The first would remove script and stylesheet concatenation in favor of prefetching. The second continues work on responsive images so browsers can make better loading decisions.
Developers can help test the image work through the official Enhanced Responsive Images plugin.
As with the other roadmap items, these are active projects rather than final release guarantees.
Visual revisions will receive more polish
WordPress 7.0 introduced a visual revisions experience. The WordPress 7.2 cycle focuses on improving that interface so users can compare changes and restore a previous version more easily.
This work is mostly polish rather than introducing a new revisions system. Plugin developers who integrate with editing history or revision screens should still test their interfaces during the beta period.
Ipsum may become the new default theme
Ipsum is the proposed default theme for WordPress 7.2.
Instead of a year-based name, Ipsum uses its own identity and follows a deliberately minimal, blank-canvas approach. It’s a simple blogging foundation that users can reshape with patterns, styles, and the Site Editor.
The theme is still under review and testing. Its inclusion is not final until the release work is complete. The Core team has published a separate introduction with testing information: Introducing Ipsum, the new default theme.
AI development remains experimental
WordPress AI work continues, but most of it happens in plugins rather than WordPress Core.
Current projects include expanding the WordPress Abilities system, updating the MCP Adapter, experimenting with browser-based agent access, defining auditable identities for agents, testing reusable site instructions, adding shared embedding support, and streaming responses from the PHP AI Client.
The roadmap clearly states the status of this work. These features must demonstrate adoption and practical value before the team considers adding them to Core. Developers should not present them as confirmed WordPress 7.2 features.
WordPress 7.2 release schedule
The current release schedule is:
- Beta 1: October 20, 2026
- Beta 2: October 27, 2026
- Beta 3: November 3, 2026
- Beta 4: November 10, 2026
- Release Candidate 1: November 17, 2026
- Release Candidate 2: November 24, 2026
- Release Candidate 3: December 1, 2026
- Final release: December 8, 2026
The complete timetable is available on the official WordPress 7.2 release page.
What WordPress developers should do now
Plugin and theme developers should start by reviewing the official WordPress 7.2 roadmap and identifying which projects affect their code.
Pay particular attention if your product works with the Site Editor, block supports, responsive styles, the Interactivity API, media processing, revisions, Application Passwords, or administrative screens.
Begin compatibility testing when Beta 1 becomes available. Test again during the Release Candidate phase, since roadmap items can change or miss the release. Watch Make WordPress Core for Field Guide posts and developer notes that describe the changes that actually landed.
WordPress 7.2 has an ambitious roadmap, but a roadmap is not a changelog. Early testing is the best way to learn which changes affect your product and to report problems while contributors still have time to address them.
Leave a Reply