WordPress 7.1 Ships Today. Responsive and Hover Styling Without Writing CSS.

WordPress 7.1 lands today, August 19, 2026, on the final day of WordCamp US. It is the second major release of the year, led by Anne McCarthy, and the feature list is frozen — what is in the release candidate is what ships. If you build sites for clients or maintain your own WordPress install, this is the release that finally kills two of the most common reasons you open a stylesheet.

The Big One: Responsive and Interactive Styling in the Editor

Responsive styling lets you define how a block looks at different screen sizes without touching CSS. Set a smaller font on mobile, adjust padding for tablets, change layout at narrow widths — all from inside the block editor. It works in Global Styles for site-wide rules and on individual blocks for one-off overrides. Theme authors get viewport breakpoint customization through theme.json, so the snap points are not hardcoded by Core anymore.

Interactive state styling covers the other half of the equation. Hover, focus, and active states are now standard editor controls. Making a button change color on hover used to mean custom CSS or a page builder. In 7.1, it is a setting. Available globally per block type and per individual block, just like the responsive controls.

These two features together eliminate the most common reasons site builders reach for custom CSS. If you maintain client sites, this is the change that will actually save you time on every build.

Notes Grew Up. Real-Time Editing Did Not Arrive.

The editorial commenting system called Notes got the bulk of the collaboration investment this cycle. You can now use inline formatting — bold, italic, code, links, emoji — tag colleagues with @mentions, leave notes on text selections rather than whole blocks, and start multiple conversations on the same block. Long notes collapse to keep the editor margin readable.

Two additions that shipped with the release candidates matter for editorial teams. @mentions now trigger email notifications, so tagging a colleague actually reaches them outside the editor. Shareable revisions let you hand out a link to a specific revision, which covers a lot of what people wanted from real-time editing: getting feedback on a draft.

What is not there is real-time collaborative editing. It was pulled from WordPress 7.0 twelve days before release and it is not in 7.1 either. The Field Guide is blunt about it: real-time editing "received extensive testing and feedback during the WordPress 7.1 cycle, but it is not enabled in the final release." Work continues on conflict handling before Core integration. If you were waiting on Google Docs style co-editing, keep waiting. The team would rather ship it late than ship it broken.

Two New Blocks: Playlist and Tabs

The Playlist block collects audio files into a single player with an optional waveform visualization. Podcast and music use cases that previously required a plugin are now a core block. The Tabs block organizes content into clickable panels, another job that has meant reaching for a third-party block until now.

Several existing blocks improve too. Background gradients and background images no longer conflict with each other, a fix that covers Group, Verse, Accordion, Pullquote, Post Content, and Quote. The Custom HTML block supports editable nested blocks, which is aimed at AI-generated content arriving as raw HTML. The Image block gains a "Mark as decorative" toggle to hide ornamental images from screen readers. Pasting a shortcode into the Embed block now produces a real Embed block instead of leaving raw text sitting there.

The Table of Contents block did not make it into 7.1. If you have been waiting on that one, it is still a plugin away.

A Real Media Overhaul

Media processing moves into the browser, and the format support that comes with it is the practical win. HEIC — the default format for iPhone photos — now works natively. So does UltraHDR, AVIF, and WebP. GIF-to-video conversion handles oversized animations. Anyone who has had a client email photos because their phone uploads would not go through will appreciate this immediately.

Uploads get more resilient with a progress indicator and automatic retries when connectivity drops mid-upload. A new Media Editor Modal replaces the old inline cropper, bringing cropping, rotation, and metadata editing into one workflow. Galleries can pull in and sort media already attached to a post. The inserter surfaces images attached to the current post in a new "Attached images" section. The Media Library grid scrolls infinitely instead of making you click "Load more."

Admin Quality-of-Life

The admin bar now follows you into the Site Editor and Block Editor — the team calls it the omnibar. The command palette groups results into Recent, Matching, and Suggestions instead of one flat list, and it remembers what you used last. The Site Editor finally respects your chosen admin color scheme instead of forcing a fixed dark background.

Site title, tagline, and icon move into a dedicated Identity section. These sound like small touches, but they add up when you are in and out of the editor all day.

What to Do Now

Update your sites. If you run custom CSS for responsive breakpoints or hover states, test whether 7.1's built-in controls replace your code. If you maintain client sites, this release shortens every build going forward. If you are on Block API v2 or lower, update to v3 — the post editor is now always iframed, and older block APIs will break.

WordPress 7.1 is not flashy. It is the kind of release that makes the editor feel more like a tool and less like a compromise. That is worth more than any single headline feature.