WordPress 7.1 brings responsive styles, pseudo-states and an always-iframed editor

WordPress 7.1 has been available since 19 August 2026, released on the final day of WordCamp US in Phoenix. The version builds on the technical groundwork laid by 7.0 and focuses on the design experience: native responsive styles, pseudo-states in theme.json, and a public API for the editor’s SVG icons. A quieter change deserves theme developers’ attention: the post editor is now always rendered inside an iframe.

#Responsive styles move into the editor

Until now, adapting a block for mobile meant writing media queries by hand in a theme stylesheet. WordPress 7.1 moves that control into the editor: styles can be defined for tablet and mobile viewports, both in Global Styles per block type and on an individual block instance. Themes declare their breakpoints through settings.viewport in theme.json, defaulting to 480 px for mobile and 782 px for tablet.

{
  "version": 3,
  "settings": {
    "viewport": {
      "mobile": { "width": "480px" },
      "tablet": { "width": "782px" }
    }
  }
}

The 782 px threshold is not arbitrary: it is the same limit the WordPress admin already uses to switch to its mobile layout. Aligning content breakpoints with that value avoids mismatches between the editor preview and the front-end render.

#Pseudo-states and the SVG Icon API

Version 7.1 adds support for the :hover, :focus, :focus-visible and :active states in theme.json and in the editor. The feature is first limited to the Button and Navigation Link blocks, the two cases where the hover state was previously impossible to set without extra CSS.

Another effort reaches maturity: the SVG icon set shipped with the editor since WordPress 7.0 becomes a proper public API. A plugin or theme can now register its own collection and reuse the icons server-side as well as in the Icon block.

<?php
add_action( 'init', function () {
    wp_register_icon_collection( 'mastudio', array(
        'label' => 'Mail Studio',
    ) );

    wp_register_icon( 'mastudio/rss', array(
        'label' => 'Flux RSS',
        'path'  => 'M4 11a9 9 0 0 1 9 9M4 4a16 16 0 0 1 16 16',
    ) );
} );

// Rendu côté serveur, par exemple dans un template de bloc :
echo wp_get_icon( 'mastudio/rss', array( 'size' => 24 ) );

WordPress 7.1 also adds the helper functions wp_get_tooltip() and wp_get_toggletip(), along with two new block supports, background.gradient and dimensions.minWidth. React stays at version 18.3: the move to React 19 is pushed to a later release.

#The always-iframed editor: the real thing to watch

For several versions, the block editor had been migrating toward an iframe render to isolate content styles from admin styles. WordPress 7.1 takes the last step: the post editor is now always iframed, regardless of theme type, including the classic themes that had so far escaped the switch.

In WordPress 7.1 the post editor is iframed regardless of theme type, classic themes included.

The consequence is concrete for anyone maintaining a classic theme: editor styles injected through a plain admin stylesheet, without going through the intended registration mechanism, no longer cross the iframe boundary. They must be declared with add_editor_style() or registered as editor assets to reappear in the preview.

#What changes, at a glance

#Key takeaways

WordPress 7.1 moves into the editor several settings that used to live in theme CSS: responsive styles, pseudo-states, icons. For authors, that is control gained without code. For developers, the real checkpoint before updating remains the always-iframed editor, which can make preview styles disappear on poorly wired classic themes. A version to test first on staging, theme by theme.

#Going further

The full developer rundown, from the primary source: What’s new for developers (August 2026) — WordPress Developer Blog.

#Also on Mail Studio

WordPress hardening: the minimal security baseline
CloudPanel: self-hosted WordPress without a heavyweight panel