WordPress 7.1 Beta 3 landed July 22. The final release ships August 19 alongside WordCamp US — less than four weeks away. Three things define this release for developers: responsive styling without writing a single line of CSS, a full iframe editor enforcement that will silently break any block still relying on global document access, and two new core blocks (the Table of Contents was punted to 7.2). If you maintain custom blocks, plugins, or themes, the clock is running.
Responsive Styling Without CSS
This is the one WordPress developers and site builders have been asking for since block themes existed. In 7.1, you can define how any block looks at different screen sizes directly inside the editor — no custom CSS required, no plugin, no theme workaround.
The workflow is desktop-first. Toggle “Responsive editing” from the device-preview dropdown in the toolbar, switch the canvas to tablet or mobile, and adjust any style property. Font size, spacing, colors — anything with a block support property. The change is saved per-breakpoint and previewed live in the editor canvas, with a viewport badge to show which breakpoint you are modifying.
Interactive states are included. You can now style :hover, :focus, and :active pseudo-classes on blocks directly inside the editor, without touching a stylesheet. For block developers, theme.json gains a new breakpoints key so theme authors can define their own responsive breakpoints instead of relying on WordPress defaults.
The “Apply globally” improvement deserves attention. Before 7.1, applying local style changes globally was all-or-nothing — every modification went site-wide. Now it opens a review step where you choose which changes to propagate globally and which to keep as local overrides. That sounds minor. It will save hours of undoing unintended global style changes.
The Iframe Editor Is No Longer Optional
This is the urgent one. Starting August 19, the WordPress post editor always runs inside an iframe — regardless of the apiVersion your block declares. In WordPress 7.0, blocks on API v2 or lower could still opt out of the iframed editor. That escape hatch closes in 7.1.
What this breaks: any JavaScript in your block’s edit component that accesses document or window from the admin page and expects to reach editor content. The editor DOM now lives in a separate iframe. A document.querySelector call in the parent frame returns nothing from the editor. Any library your block depends on that makes global scope assumptions will fail silently — or loudly, with cryptic errors.
The fix is straightforward for most blocks:
// block.json
{
"apiVersion": 3,
"name": "my-plugin/my-block"
}That one-line change updates your block to v3. The real work comes after: auditing every edit component and every third-party library it pulls in for document or window references. The official migration guide covers the full scope. Run this audit now against Beta 3 — not the week before the August 19 release.
Two New Blocks, Not Three
WordPress 7.1 ships with two new core blocks.
The Tabs block organizes content into clickable tabbed panels, with full block support inside each tab panel — meaning you can embed any other block inside a tab, not just text. The Tabs block went through multiple refactoring rounds in recent Gutenberg releases, so it arrives in 7.1 in solid shape. Tab reordering via toolbar buttons is included.
The Playlist block handles audio and video collections, with waveform visualization for audio tracks. Useful for podcast sites and media-heavy publications that currently stitch together media embeds manually.
The Table of Contents block was deferred to 7.2. It auto-generates navigable links from post headings. If you were waiting on it, move it to your 7.2 planning list.
React 19 and Media Upload Fixes
React 19 is still targeting WordPress 7.1, but the approach is more careful than the first attempt — which shipped in Gutenberg, broke a notable number of plugins, and was reverted within 48 hours. The 7.1 strategy adds a compatibility layer for plugins that bundle their own copy of React, plus an experimental feature flag at /wp-admin/admin.php?page=experiments-wp-admin. Enable “React 19” there and run your full plugin test suite now. The target date is still August 19.
Media uploads received quiet but practical fixes. Long animated GIF uploads no longer hang. EXIF-rotated images process correctly. Uploading a single HEIC image in Safari no longer generates duplicate entries. If you handle uploads programmatically via the REST API, the attachment endpoint now exposes output_format, progressive, and quality fields.
What to Do Before August 19
- Install Beta 3 via the WordPress Beta Tester plugin or direct download
- Audit all custom blocks for
documentandwindowreferences ineditcomponents — set apiVersion to 3 in each - Enable the React 19 experiment and run your full plugin test suite
- Review theme.json if you maintain a block theme — the responsive breakpoints key is now available
- Test media upload flows, especially HEIC and animated GIF handling
- Read the full July 2026 developer roundup for the complete
@wordpress/componentsdeprecation list
August 19 is a hard deadline — the release is timed to WordCamp US. Four weeks is enough time to test and fix, but not enough to ignore it.
