WordPress 7.1 ships on August 19, 2026 — the last day of WordCamp US in Phoenix. RC2 is already out, the feature set is locked, and the Field Guide dropped on August 5. If you maintain a WordPress site or build themes and plugins, you have five days to test. That's not a suggestion.

This release has two changes that will actually affect how you build sites, plus a handful of under-the-hood work that makes the editor more consistent. Let's skip the press-release energy and get into what's worth your attention.

Responsive block styles are finally in Core

For years, the block editor let you style things for one screen size and then hope the cascade worked out on mobile. Theme developers built workarounds with custom CSS, and everyone else just lived with blocks that looked fine on desktop and cramped on phones.

WordPress 7.1 fixes this with native responsive block styles. You can now define separate styles for desktop, tablet, and mobile directly in Global Styles or in your theme.json. That means different font sizes, spacing, and visibility per breakpoint — without writing a single media query.

The practical impact is immediate. If you've been shipping custom themes, you can drop the hacky CSS overrides and let the editor handle responsive behavior natively. If you're using a block theme and editing through the Site Editor, you'll see new per-device controls appearing in the style panel. It's not every property yet, but the critical ones — typography, spacing, and layout — are covered.

For agencies managing multiple client sites, this also means fewer support tickets. The number of "why does this look weird on mobile" messages is about to drop significantly.

The SVG Icon API goes public

WordPress 7.0 introduced a built-in SVG icon set for the block editor and the core/icon block, but it was internal-only. In 7.1, the SVG Icon API becomes a proper public API with a clean registration system.

Here's how it works. You create an icon collection — a named group of icons — and register individual SVGs inside it. Each icon gets a namespace prefix, so your custom icons never collide with WordPress core icons. You can add them, remove them, and browse by collection in the Icon block's picker.

What makes this genuinely useful is the server-side rendering. WordPress 7.1 introduces wp_get_icon(), a PHP function that returns the SVG markup directly. No more copying inline SVGs into templates or bundling an icon font just to get a social media icon in a header. Register your collection once, reference it by name, and WordPress handles the markup.

The icons are also available through the REST API, which means JavaScript-heavy themes and headless WordPress setups can pull icon data without touching PHP.

If you've been shipping custom icon sets with your themes or using third-party icon plugins, this is the point where you can simplify your stack. One registration call, one naming convention, and the editor, the frontend, and the API all speak the same language.

The editor is always iframed now

This one is less flashy but important for plugin developers. The post editor in 7.1 is always running inside an iframe. Previously, it was iframed only under certain conditions — block themes, specific settings, and so on. Now it's consistent.

What this means in practice: if your plugin injects styles or scripts into the editor by targeting the main document, those injections may stop working. You need to enqueue styles and scripts through the proper block editor APIs so they land inside the iframe. The WordPress developer blog published a detailed migration guide, and if you haven't read it yet, now is the time.

Also worth knowing

WordPress 7.0.2 and 7.0.3 both shipped in the past month with security fixes — one critical, one high severity, plus a dozen smaller patches. WordPress.org pushed forced updates for affected versions, so most sites should already be current. If you manage anything that might have missed auto-updates, check before you focus on 7.1.

The Abilities API got updates. Accessible tooltips arrived in the admin. The Design System theming work for admin interfaces is progressing. And the 40px component opt-in is officially gone — everything uses the standard size now.

What to do right now

If you run a WordPress site on a block theme: update on August 19, check your mobile layouts, and explore the new responsive controls. If you develop plugins or themes: test against 7.1 RC2 today. The iframe change and the SVG API are the two things most likely to touch your code.

Five days. That's your window.