WordPress | 7.1 RC1 Moves Responsive Styling Toward Release

WordPress 7.1 has reached Release Candidate 1, putting its new responsive styling controls, collaboration tools, media improvements, and developer changes into the final testing stage. Released on August 5, 2026, RC1 includes more than 145 updates and fixes since Beta 4, with 57 changes in the Editor and 88 in Core, as theme and plugin developers prepare for the scheduled WordPress 7.1 release.


WordPress 7.1 Release Candidate 1 with responsive styling and editor improvements

{getToc} $title={Table of Contents}

WordPress 7.1 moves its new design controls into final testing


One of the most relevant changes for theme and site creators is the broader set of styling tools arriving with WordPress 7.1. Responsive styling allows blocks to use different visual settings across screen sizes directly from the editor, while theme authors can define responsive breakpoints through theme.json.


Interactive state styling also brings controls for states such as hover and focus into Global Styles and individual blocks. These additions move more responsive and interactive design work into WordPress itself, reducing the number of common visual adjustments that require custom CSS.



Notes and revisions improve collaborative editing


WordPress 7.1 continues expanding Notes as a collaboration layer inside the editor. Notes support rich text formatting, searchable @mentions, multiple conversations on the same block, and comments attached to specific text selections instead of only entire blocks.


RC1 also adds email notifications for @mentions and shareable revisions. A specific revision can be shared through a link, giving editors, designers, and other collaborators a more direct way to review a particular version of a page or post without navigating through the complete revision history first.


Responsive design is joined by stronger media and block tools


The broader WordPress 7.1 release also improves media handling with client-side processing, support for formats including HEIC, UltraHDR, AVIF, and WebP, more resilient uploads, and a dedicated media editing modal. The Media Library gains infinite scrolling by default, while attached images become easier to find when working on content.


Block creators receive several useful additions as well. WordPress 7.1 introduces Playlist and Tabs blocks, allows background gradients and images to work together, adds a decorative-image control for accessibility, and lets the HTML block contain editable nested blocks. These changes give site builders more native options for structuring and styling content without immediately turning to plugins or custom implementations.


Theme and plugin developers should finish compatibility testing


Release Candidate status means WordPress 7.1 is still development software and should not be installed on production or mission-critical websites. WordPress recommends testing RC1 on a separate environment using the Beta Tester plugin, a direct download, WP-CLI, or WordPress Playground.


Theme and plugin authors are specifically encouraged to conclude compatibility testing and update their products' Tested up to value to WordPress 7.1 when appropriate. Developers should also review changes such as the enforced iframed post editor, new icon registration APIs, expanded Block Bindings, and other Core and Gutenberg updates that may affect existing extensions.


IMPORTANT: WordPress 7.1 RC1 is development software and should be tested on a staging, local, or dedicated test environment rather than a production or mission-critical website.{alertWarning}

Daisuki's Take: What This Means for Web Designers


The responsive styling controls are the most important part of WordPress 7.1 for visual site building. Giving designers native control over how blocks change across screen sizes brings the editor closer to workflows that previously required custom CSS or more specialized page builders.


That also makes RC testing particularly relevant for theme creators. Responsive settings, interactive states, editor isolation, new blocks, and media changes can affect both how a theme is authored and how existing designs behave inside the editing environment.


We would use this stage to test real templates rather than only exploring individual features. Checking responsive layouts, Global Styles, block interactions, media handling, and existing plugins together is the best way to identify compatibility problems before WordPress 7.1 reaches production sites.



Sources and Recommended Links