--- title: "WordPress 7.2: Release Date, Ipsum Theme, And Every Feature On The Roadmap" url: https://nexterwp.com/blog/wordpress-7-2/ date: 2026-09-28 modified: 2026-09-28 lang: en author: "Aditya Sharma" description: "On September 18, 2026, the WordPress core team published the Roadmap to 7.2, and two days earlier it introduced Ipsum, the theme it plans to bundle as the new default...." image: https://nexterwp.com/wp-content/uploads/2026/09/wordpress-7-2-featured-1024x538.jpg word_count: 2395 --- # WordPress 7.2: Release Date, Ipsum Theme, And Every Feature On The Roadmap ## Key Takeaways - WordPress 7.2 is due in December 2026, with the WordPress 7.2 Call for Volunteers proposing a final release date of Wednesday, December 9, 2026 and Beta 1 set for October 20 to 22. - Ipsum is the planned new default theme for WordPress 7.2, and the core team describes it as an intentionally minimal blog theme with a blank canvas, style variations, and WCAG AA contrast across combinations. - WordPress updates to 7.2 do not switch an existing site’s active theme, and Ipsum becomes active only on fresh installs; hosts or developers can also set the CORE_UPGRADE_SKIP_NEW_BUNDLED constant to skip adding the bundled theme. - Nexter Theme is presented as a different choice from Ipsum, with a lightweight starter theme built on vanilla JavaScript and no jQuery dependency, plus Nexter Blocks and Nexter Extension for page building, theme building, and site utilities. - The 7.2 roadmap adds editor and block changes such as Form Elements in Global Styles for button, textInput, select, and label elements; a Description List block; a Table of Contents block moving to server-side dynamic rendering; and Notes suggestions with emoji reactions. On September 18, 2026, the WordPress core team published the [Roadmap to 7.2](https://make.wordpress.org/core/2026/09/18/roadmap-to-7-2/), and two days earlier it introduced [Ipsum](https://make.wordpress.org/core/2026/09/16/introducing-ipsum-the-new-default-theme/), the theme it plans to bundle as the new default. WordPress 7.2 is the last major release of 2026, and it is due in December. That leaves roughly ten weeks between now and the final release, and a lot of the roadmap is still marked as work in progress. I build and maintain block-based WordPress sites, so I read roadmaps with one question in mind: what changes for the sites I already run, and what should I test before it ships? This post answers that for 7.2. It covers the release schedule, the new Ipsum theme, and every roadmap area, with a clear line between what is planned and what is only being explored. Table of Contents ## When Does WordPress 7.2 Come Out? The [WordPress 7.2 Call for Volunteers](https://make.wordpress.org/core/2026/08/12/wordpress-7-2-call-for-volunteers/) proposes a final release date of Wednesday, December 9, 2026. Development did not wait for 7.1 to ship: 7.2 alpha began in trunk on August 10, 2026, and WordPress 7.1.2 is the current stable version while this cycle runs. Here is the proposed schedule from that post. Every date is a window rather than a single day, and the core team says all of them can move with development progress. | Milestone | Proposed Date (2026) | | --------- | -------------------- | | Alpha | Began in trunk on August 10 | | Beta 1 | October 20 to 22 | | Beta 2 | October 27 to 29 | | Beta 3 | November 3 to 5 | | Beta 4 | November 10 to 12 | | Release Candidate 1 | November 17 to 19 | | Release Candidate 2 | November 24 to 26 | | Release Candidate 3 | December 1 to 3 | | Dry run | December 7 to 9 | | Final release | December 8 to 10 (December 9 proposed) | ![WordPress 7.2 Call for Volunteers post showing the proposed December 9, 2026 release date](https://nexterwp.com/wp-content/uploads/2026/09/wordpress-7-2-call-for-volunteers-schedule.png)The WordPress 7.2 Call for Volunteers on Make WordPress Core, which sets the proposed December 9 date. Beta 1 is the date that matters most if you maintain client sites or ship a plugin. From that point the feature set is frozen, and anything that breaks on your stack is a bug the core team wants to hear about before the release, not after. ## What Is Ipsum, The New Default Theme? Ipsum is the proposal for the next default theme, planned to be bundled with WordPress 7.2. The [introduction post](https://make.wordpress.org/core/2026/09/16/introducing-ipsum-the-new-default-theme/) describes it as an intentionally minimal blog theme that centers on a blank canvas you make your own. The name comes from lorem ipsum, the placeholder text that fills a layout until real content arrives. ![Ipsum, the proposed WordPress 7.2 default theme, shown on a laptop mockup](https://nexterwp.com/wp-content/uploads/2026/09/wordpress-7-2-ipsum-default-theme-preview.png)A preview of the Ipsum theme published by the WordPress core team with the introduction post. Three details from the introduction post stand out to me: - Style variations re-ink the whole page, images included, and the core team says every combination passes WCAG AA contrast. - Headers, heroes, and sidebars are available when you reach for them, but stay out of the way when you just want to write. - The build reflects the design work so far. A formal development review is still ahead, and the team is asking people to test it and report what breaks. It also marks the end of year-based names. After Twenty Twenty-Five, default themes will carry their own names and change when the design calls for it rather than every calendar year. The team had been building a more expressive theme called Mētis, but after review with Matt Mullenweg it switched to the simpler blank-canvas direction. Mētis continues as a separate theme and will not ship with this release. ![WordPress/ipsum theme repository on GitHub](https://nexterwp.com/wp-content/uploads/2026/09/wordpress-ipsum-theme-github-repository.png)The Ipsum theme is developed in the open in the WordPress/ipsum repository on GitHub. If you want to try it before the beta, the theme is available from the WordPress/ipsum repository on GitHub. Install it on a local or staging site, not on production. The build is explicitly pre-review. ## What Ipsum Means If You Build On Nexter Theme Or Any Other Theme A new default theme sounds bigger than it is for existing sites. Updating a site to WordPress 7.2 never switches your active theme. At most, the core update adds the new bundled theme to your themes folder, and hosts or developers who do not want that can set the CORE_UPGRADE_SKIP_NEW_BUNDLED constant. Ipsum becomes the active theme only on fresh installs. Where Ipsum does matter is as a signal. The default theme is how the core team shows what the block editor can do today, and a blank-canvas blog theme says the team wants the starting point to be simple, with the design system doing the heavy lifting through style variations and Global Styles. If you are still deciding between approaches, our comparison of [block themes and classic themes](https://nexterwp.com/blog/wordpress-fse-block-themes-vs-classic-themes/) walks through the trade-offs. ![Nexter Theme product page on nexterwp.com](https://nexterwp.com/wp-content/uploads/2026/09/nexter-theme-lightweight-wordpress-theme.png)The Nexter Theme product page on nexterwp.com. [Nexter Theme](https://nexterwp.com/nexter-theme/) takes a different route to the same goal. Its product page describes it as a lightweight starter theme built on vanilla JavaScript with no jQuery dependency, and it pairs with Nexter Blocks and Nexter Extension for page building, theme building, and site utilities. It is not a replacement for Ipsum, and Ipsum is not a replacement for it. They answer different questions: - Choose Ipsum when you want the default, core-maintained blog theme and you are happy to style it through Global Styles and style variations. - Choose a starter theme like Nexter Theme when you need a site builder workflow: custom headers and footers, template conditions, and a block library beyond core. - Either way, test your current theme against the 7.2 betas, because the editor changes below affect every theme, not only the default one. If you are comparing starter themes, see how [Nexter Theme compares with Astra](https://nexterwp.com/blog/nexter-vs-astra/). ## Design And Editor Changes Planned For 7.2 This is the section most site builders will feel day to day. The roadmap lists six areas: ### Block Editor Paper Cuts A broad quality-of-life sweep that fixes dozens of small, persistent problems in writing flow, selection, paste, drag and drop, and mobile editing. None of these will make a headline on their own. Together they are the work that decides whether the editor feels finished. ### Form Elements In Global Styles theme.json already supports styling the button, textInput, and select elements. The 7.2 work adds an interface for them in Global Styles, adds the missing label element, and improves interactive input states. The goal is consistent form styling without custom CSS or hand-editing theme.json. ### Responsive Style States And Custom States Responsive styling arrived in 7.1. For 7.2, the team plans to expand which controls support it and add a public API so third-party blocks with custom controls can use it. A related project adds a -current custom state for the Navigation Link and Tabs blocks, so you can style the active menu item or tab directly in the editor, along with color, border, and spacing support for Navigation Link. ### View Inherited Styles Today, a block that inherits a value from Global Styles does not show that value in its own settings panel. The planned change surfaces it, so if paragraphs are red globally you see red when you open a paragraph block. The roadmap notes that design decisions are still open here, including how to indicate an override and how to reset one. ### Expanded Block Supports Work continues on backgrounds, dimensions, and position supports, and on replacing one-off block controls with consistent shared supports. ## New Blocks And Developer APIs Four items on the Blocks and APIs list are worth knowing about, plus one that is unlikely to land: - Description List block: three new static blocks that output semantic
,
, and
markup, which suits glossaries, specifications, and metadata. - Table of Contents block: the long-experimental block is set to go stable by moving to server-side dynamic rendering, so the editor and the front end share one source of headings. That closes the gap we flagged when 7.1 added Tabs but not a table of contents, covered in [do you still need a blocks plugin](https://nexterwp.com/blog/do-you-still-need-a-gutenberg-blocks-plugin/). - Icon block keyword search: typing hamburger, navigation, or list will find the menu icon, instead of search matching the label only. - Interactivity API: a new data-wp-html directive for rendering trusted markup reactively, plus router work that lets developers observe client-side navigations. - React 19: work continues, but the roadmap says it is unlikely to fully land in 7.2. If you are new to how blocks are structured in the first place, start with [what Gutenberg is and how it works](https://nexterwp.com/blog/what-is-gutenberg/). ## Notes, Media, And Admin Updates ### Notes Get Suggestions And Emoji Reactions Notes, the block commenting feature, is getting a suggestion mode where you leave proposed edits that others accept or reject. Emoji reactions and a dedicated toolbar shortcut for adding notes are also planned. Real-time collaborative editing is a separate project, and the roadmap says it is intentionally left off the 7.2 list because more architectural decisions are needed. ### Media - Client-side media processing continues, with a hardened upload pipeline and wider format support. - The media inserter is being redesigned for large libraries, dynamic galleries get more sources, and the static gallery block gets sorting. - The Media Editor modal from 7.1 will track the relationship between cropped images and their originals, so crops stop piling up as unrelated attachments. ### Admin - DataViews and DataForms continue, with the post inspector (featured image, excerpt, status, date, author, template) moving to a DataForm. - Error messages become clearer and get a copy button, which makes them easier to search for or share with support. - The Site Editor gets an extensible foundation that lets plugins register their own screens and settings for the first time. - The Omnibar from 7.1 is iterated on, including SVG icons replacing Dashicons in the admin bar and menu. - An On This Day dashboard widget that resurfaces past content gets another attempt after being dropped from 7.1. ![Roadmap to 7.2 post on Make WordPress Core, published September 18, 2026](https://nexterwp.com/wp-content/uploads/2026/09/wordpress-7-2-roadmap-make-wordpress-core.png)The Roadmap to 7.2 post on Make WordPress Core, which this article follows section by section. ## Security Changes: Sudo Mode, Secrets API, And Application Passwords Security is the part of this roadmap I would watch most closely, because some of it is still at an early stage: - Sudo mode: initial work has started on possibly gating highly privileged admin actions behind a re-authentication prompt, even when you are already logged in. The roadmap says a proposal and call for collaboration are still to come. - Secrets API: WordPress has no first-class way to store a credential. A proposal describes a Secrets API with WP-CLI support, with a proper UI planned for a later release. - Application Passwords: an email notification when one is added, better detection of local and HTTPS environments, protection against dangerous default_role values, and SameSite cookie support. - HTML processing: continued hardening built on the HTML API. Plugins that store API keys in plain options are the obvious beneficiaries of a Secrets API, including AI and SEO plugins. That ties into the AI work below and into how the [WordPress Abilities API](https://nexterwp.com/blog/wordpress-abilities-api/) hands actions to external tools. ## AI, Accessibility, And Performance The AI section carries the strongest caveat on the whole roadmap. The 7.1 cycle concluded that AI features must first show real adoption and practical value before they are considered for core, so this work is happening in the AI plugin with no guarantee it lands in 7.2. The list includes: - More abilities, including write abilities and read-only coverage for media, taxonomies, and comments. - An MCP Adapter updated for the latest MCP specification, published in the WordPress.org plugin directory. - A simpler way for administrators to enable MCP and choose which abilities are exposed. - Agent identity and delegation, so agents get auditable identities and permissions separate from human accounts. - Shared embeddings for semantic search, and streaming responses in the PHP AI Client. This is the same foundation that [Nexter Abilities](https://nexterwp.com/nexter-abilities/) builds on: Nexter registers its abilities with the WordPress Abilities API, and you connect an AI client through an MCP bridge such as the MCP Adapter. For the background, read our explainer on [the Model Context Protocol in WordPress](https://nexterwp.com/blog/model-context-protocol-wordpress/). Accessibility work is spread across the release, but four items are called out: admin notices that are announced properly to assistive technology, axe-core automated testing to catch regressions, an option to turn off metabox rearranging, and removing the widget accessibility mode. Performance work focuses on removing script and style concatenation in favor of prefetching, and on enhanced responsive images, which you can test today with the Enhanced Responsive Images plugin from the Performance team. Visual revisions from 7.0 also get a polish pass. ## How To Test WordPress 7.2 Before December You do not need to be a core contributor to test a release. This is the routine I would follow for any site that matters: - Clone the site to staging. Never run a beta on production. - Install the WordPress Beta Tester plugin on the staging copy and choose the Beta or RC channel once Beta 1 lands on October 20 to 22. - Update, then walk through the pages that earn money or leads first: checkout, forms, landing pages, and your header and navigation. - Open the block editor and the Site Editor, edit a few real posts, and try paste, drag and drop, and undo, since those are where the paper-cut fixes land. - Check your error logs and browser console after each update. - Report anything broken to the plugin or theme author first, and to WordPress core if the problem reproduces with a default theme and no plugins. ![WordPress Beta Tester plugin page on WordPress.org](https://nexterwp.com/wp-content/uploads/2026/09/wordpress-beta-tester-plugin.png)The WordPress Beta Tester plugin lets a staging site switch to the Beta or Release Candidate channel. If you want a sense of how a release lands in practice, our [WordPress 7.1 overview](https://nexterwp.com/blog/wordpress-7-1/) and the [August 2026 Nexter update](https://nexterwp.com/blog/august-2026-update/) cover what 7.1 actually changed once it shipped. ## What This Doesn't Cover This post is based on the Roadmap to 7.2, the Ipsum introduction, and the 7.2 Call for Volunteers as published on Make WordPress Core. The roadmap itself says that what it lists is being actively pursued but will not necessarily all make the final release, so treat every feature here as planned, not promised. I have not tested the 7.2 betas yet because Beta 1 is not out, I have not covered the Gutenberg plugin releases that feed 7.2, and I have left out collaborative editing because the core team has left it off this roadmap. I will update this post as the betas and the field guide arrive. ## Suggested Reading - [WordPress 7.1: What’s New and What Got Deferred](https://nexterwp.com/blog/wordpress-7-1/) - [WordPress Block Themes vs Classic Themes: 6 Key Differences](https://nexterwp.com/blog/wordpress-fse-block-themes-vs-classic-themes/) - [The WordPress Abilities API: What It Is and Why AI Tools Need It](https://nexterwp.com/blog/wordpress-abilities-api/) - [August 2026 Update: WordPress 7.1 Ships, Nexter’s Biggest Security Hardening Pass, and a Customizer Redesign](https://nexterwp.com/blog/august-2026-update/) #### Stay updated with Helpful WordPress Tips, Insider Insights, and Exclusive Updates – Subscribe now to keep up with Everything Happening on WordPress! Subscribe