On July 7, 2026, the WordPress Core team quietly reversed one of the most controversial decisions of the 7.1 cycle. The Classic block, which had been slated for removal from the block inserter, will stay. No deprecation notice. No hidden-by-default compromise. It remains a standard block. Then on July 22, Beta 3 landed with that decision baked in, along with a pile of features that make 7.1 look less like a maintenance release and more like the update that actually finishes what 7.0 started.

If you have been holding off on testing because "betas are for contributors," Beta 3 is the one worth downloading. Here is why.

The Classic block reversal, and why it matters

The plan, announced in early June, was to remove the Classic block from the inserter in 7.1. Existing instances would still render, but you could not insert new ones. The rationale was straightforward: the block editor has been the default since WordPress 5.0, released in December 2018. Eight years is long enough to stop supporting a crutch.

The community disagreed. Loudly. The Make WordPress Core comments section filled with real-world cases: agencies managing hundreds of client sites where content teams still paste from Word documents into Classic blocks. Membership sites with thousands of posts using Classic blocks that nobody has time to convert. Plugin developers whose shortcodes depend on the Classic editor context. The argument was not that the block editor is bad. It was that removing the Classic block broke workflows that work, with no practical migration path.

On July 7, Core committer Jonathan Desrosiers posted the reversal. The Classic block stays in the inserter. The team acknowledged that the block editor's parity with the classic editing experience is not complete enough to force the transition. This is the right call. Forcing users off a working tool before the replacement covers all their use cases is how you lose users, not how you modernize a platform.

What Beta 3 actually ships

Beyond the Classic block drama, Beta 3 is feature-dense. The headline items that are worth testing now:

Responsive styling in the Site Editor. You can now define how blocks behave at different viewport widths without writing CSS. Click "Responsive editing" in the block sidebar, switch between desktop, tablet, and mobile views, and adjust font sizes, spacing, and layout per breakpoint. Developers can customize breakpoints in theme.json. This has been the number one feature request from theme builders for years, and the implementation is clean.

Interactive state styling. The editor now supports native :hover, :focus, and :active pseudo-class controls for blocks. The button block is the first to support it, with the architecture designed to extend to navigation links, form fields, and image links in future releases. You set hover and focus styles visually, and the preview updates in real time. No custom CSS required.

Enhanced Notes for collaboration. The asynchronous collaboration feature, called Notes, gets suggestion mode (track changes, basically), rich text formatting, and emoji reactions. If you manage a site with multiple editors, this is the feature to test. The team is running a dedicated collaboration testing program for this cycle.

AI Client gets streaming and embeddings. Building on the provider-agnostic AI Client that shipped in 7.0, version 7.1 adds streaming responses (so AI-generated content appears progressively instead of loading all at once) and embeddings support for semantic search, recommendations, and content clustering. A new "Guidelines" feature lets site administrators set boundaries for what AI can and cannot do on their site.

New core blocks: Tabs and Playlist. Two new blocks that fill gaps in the block library. Tabs for organizing content into tabbed interfaces, and Playlist for audio and video collections. Both are straightforward but long overdue.

The React 19 warning

Here is the part that should make you pay attention. WordPress 7.1 includes initial preparation for the React 19 upgrade. The enforced iframe mode for block themes is now the default. If you run custom blocks or older plugins that have not been updated for iframe compatibility, things may break.

This is not theoretical. The Gutenberg 23.5 plugin, released July 1, raised the minimum required WordPress version to 6.9. Plugin developers who have not tested against the iframe mode will see issues. The release candidate phase, starting August 5, is when the Core team locks features and focuses entirely on stability. If your plugins break in Beta 3, they will break in RC1 too, and there will be no feature changes to fix it.

Test now. Not in August. Now.

The schedule from here

Beta 4 drops July 29. Release Candidate 1 arrives August 5, which is the feature freeze. RC2 follows August 12. The final release is August 19, timed with WordCamp US.

Between now and August 5, the priorities are: install Beta 3 on a staging site, test your theme's responsive behavior, verify your custom blocks work in iframe mode, and check whether your plugins handle the new Notes collaboration features without conflicts. You can also test everything in WordPress Playground without installing anything locally.

WordPress 7.1 is shaping up to be the release that makes the block editor feel finished. Responsive styling, real collaboration, AI that actually integrates instead of bolting on. The Classic block reversal is not a sign of weakness — it is a sign that the Core team is listening. That is a good place to be heading into a major release.

Sources: WordPress Developer Blog (July 2026 roundup), Raidboxes WordPress 7.1 guide, WordPress.org releases page