On June 19, 2026, Automattic's Anne McCarthy published the WordPress 7.1 roadmap on the Make WordPress Core blog. It is her first cycle as release lead, and the post is genuinely packed. Beta 1 lands July 15. The final release is scheduled for August 19, the closing day of WordCamp US in Phoenix. That gives the project under four weeks of lockdown between beta and ship, which is tight enough that some items on the roadmap will either slip or land behind feature flags.
The roadmap is framed around collaboration. That word appears throughout the post. But if you read the actual list of what is confirmed versus what is still being debated, a different picture emerges. WordPress 7.1 is two releases in one: a solid set of styling, media, and platform improvements that will genuinely ship on August 19, and a collaboration story that core committers are still arguing about in the open.
The feature that keeps getting deferred
Real-time collaboration was supposed to be the headline feature of WordPress 7.0. It was pulled from the 7.0 milestone on May 8, roughly two weeks before that release shipped. It now appears in the 7.1 roadmap wrapped in what McCarthy describes as "big, open strategy questions" rather than a confirmed ship date. At WordCamp Europe 2026, core committers openly questioned whether the full real-time collaboration feature set belongs in core at all. One floated model was a Chrome-style canary deployment with feature flags, where experimental features ship to a subset of users before a full rollout. The strong opinion loosely held among several committers is that only the underlying architecture should live in core, not the full Google Docs-style editing experience.
That is a significant strategic shift. If you have been waiting for WordPress to become a real-time collaborative editor, the honest answer is that nobody knows when or whether that happens in core. The foundations are in 7.0. The feature itself remains a question mark.
What will actually ship
The genuinely confirmed items in 7.1 are less flashy and more useful than the collaboration framing suggests. Here is what matters.
Responsive styling is the quiet headline. Until now, controlling how a block looks at different screen sizes meant custom CSS, a plugin, or fighting the editor. WordPress 7.1 brings per-breakpoint block styling into the editor itself, alongside interactive-state styling for hover, focus, and active states, and a "display inherited styles" view so you can see where a style actually comes from. If you build sites for clients, this removes a daily friction point. It reduces the plugin count and the custom CSS that every site otherwise accumulates. It is the kind of platform maturity that does not make headlines but quietly removes a category of support tickets.
React 19 arrives as an internal upgrade. WordPress is moving the editor from React 18 to React 19, landing first in the Gutenberg plugin before reaching core. For most sites this changes nothing visible. For anyone maintaining custom blocks or editor interfaces, it is a reason to test against React 19 before August rather than discovering breakage after the release.
Classic block deprecation is the more interesting under-the-hood change. The Classic block carries TinyMCE, a heavy editor that most modern WordPress sites no longer need. The plan is to lazy-load it and phase the block out. Existing content does not break, but sites still leaning on the Classic editor or Classic block should treat this as the formal start of a migration clock. For performance-sensitive builds, especially WooCommerce stores where every kilobyte of editor weight is measured, shedding TinyMCE from pages that never needed it is a real gain.
The AI angle that is not just a chat box
The roadmap leans into AI, but in a more disciplined way than "add a chatbot to your dashboard." The standout feature is Guidelines, which lets a site define editorial rules and brand voice in one place. Those guidelines then feed the editor's AI tooling so that generated content follows the rules automatically. There is also an AI Client iteration adding generation streaming, image generation support, and a tutorial for developers building on top of the new AI APIs that shipped in 7.0.
This is the right approach to AI in a CMS. Instead of bolting on a generic chat interface, WordPress is building the infrastructure for AI to respect the editorial standards a site already has. If you run a brand blog with specific tone requirements, Guidelines means you can set those rules once and have AI-generated drafts follow them from the start. That is a workflow improvement, not a gimmick.
New blocks and smaller wins
Three new blocks are planned for 7.1: Playlist, Table of Contents, and Tabs. There is an expanded Icon API, extended Unicode support including Unicode email addresses, and a persistent admin bar across editors. Notes, the block-level commenting feature that arrived in 6.9, gets emoji reactions and suggestion mode. None of these are transformative on their own, but together they round out the editing experience in ways that reduce plugin dependency.
What to do right now
If you manage WordPress sites, the practical playbook for 7.1 is straightforward. Test your custom blocks against React 19. Audit whether any of your sites still depend on the Classic block or Classic editor, because the deprecation clock is now official. If you run WooCommerce, watch the Classic block deprecation closely — the performance gains from dropping TinyMCE are measurable. And if you have been holding off on upgrading to 7.0 because of the styling regressions that hit hard enough to generate hundreds of Reddit complaints, the 7.0.1 release on July 9 should stabilize things before 7.1 beta arrives six days later.
The collaboration release that WordPress 7.1 promises may or may not arrive in full. The responsive styling, React 19 migration, and Classic block cleanup that it definitely delivers are worth more to most site owners than real-time editing ever was.