WordPress 7.1 ships on August 19, 2026 — three days from now — timed to the final day of WordCamp US. It is the second major release of the year, led by Anne McCarthy, and it has already hit the release candidate stage. The feature list is frozen. What follows is what actually ships, not what might.

The headline is styling. Responsive design and hover states are becoming built-in editor controls instead of things you write CSS for. If you maintain client sites or build anything with the block editor, this release will change how you work.

Responsive Styling Inside the Editor

Starting Tuesday, you can define how a block looks at different screen sizes without opening a stylesheet. Want a smaller font on mobile? Set it in the editor. Need padding to collapse on narrow viewports? Same place.

This works at two levels. Global Styles lets you set responsive rules for every instance of a block type. Individual block settings let you override on a per-block basis. Theme authors also get viewport breakpoint customization through theme.json, so the snap points are not hardcoded by Core anymore.

For anyone who has been writing @media (max-width: 768px) rules by hand or loading a page builder just to handle responsive tweaks, this is the feature that makes that habit obsolete. The controls are not as granular as raw CSS, but they cover the 80% case that most sites actually need.

Hover, Focus, and Active States as Settings

The other half of the styling story is interactive states. Making a button change color on hover has meant custom CSS or a third-party builder since WordPress shipped the block editor. In 7.1 it becomes a native control.

Hover, focus, and active states are available both globally and per block. Set a hover color for all Button blocks in your theme, then override it on a specific call-to-action. No stylesheet touched. This is the kind of feature that sounds small until you realize how many sites ship with zero hover feedback because nobody wanted to write the CSS for it.

Taken together, responsive and interactive state styling close two of the most common reasons people still reach for custom code or a page builder. If you run an agency, expect client requests for "can you make the buttons change color" to get a lot cheaper.

Notes Grew Up, Real-Time Editing Did Not Arrive

The editorial commenting system called Notes got most of the collaboration work this cycle. You can now use inline formatting, tag colleagues with @mentions that send email notifications, leave notes on text selections rather than whole blocks, start multiple conversations on the same block, and collapse long notes to keep the margin readable. Shareable revision links let you hand out access to a specific revision for review.

What is still missing is real-time collaborative editing. It was pulled from WordPress 7.0 twelve days before that release, and it is not in 7.1 either. The Field Guide states plainly that it "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 for Google Docs-style co-editing in WordPress, keep waiting. Two releases have now passed with the groundwork moving but the feature held back. The team would rather ship it late than ship it unstable, and honestly that is the right call.

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 needed a plugin now have a native option. The Tabs block organizes content into clickable panels, another job that has meant installing a third-party block until now.

The Table of Contents block did not make it into 7.1. If you need one, keep using a plugin for now.

Several existing blocks also improved. Background gradients and background images no longer conflict on Group, Verse, Accordion, Pullquote, Post Content, and Quote blocks. The Custom HTML block supports editable nested blocks, which is aimed at AI-generated content that arrives as raw HTML. The Image block gains a "Mark as decorative" toggle to hide ornamental images from screen readers. And shortcode handling got smarter — pasting a shortcode into the Embed block now produces a real Embed block instead of leaving raw text sitting there.

A Genuine Media Overhaul

Media processing moves into the browser in 7.1, and the format support is the practical win. HEIC, which is the default format for iPhone photos, is now natively supported. So are UltraHDR, AVIF, and WebP. GIF-to-video conversion handles lighter files automatically. Anyone who has had a client email photos because their phone uploads would not go through will appreciate this one.

Uploads get more resilient too, 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. The Media Library grid scrolls infinitely instead of making you click "Load more."

For sites with heavy image workflows, this is the release that makes the default media handling actually competent instead of merely functional.

What This Means for Your Monday

If you run client sites on WordPress, here is the practical impact. Responsive and hover styling will cut the time you spend on basic CSS for new builds. The media overhaul means fewer support tickets about upload failures. Notes improvements make editorial collaboration less painful even without real-time editing.

If you build themes, check your theme.json. The new viewport breakpoint customization needs explicit support to unlock the responsive controls. And if your blocks are still on Block API v2 or lower, update them — the post editor is now always iframed in 7.1, and older block APIs will break.

The release drops Tuesday. If you want to test before then, the release candidate is available now through the WordPress Beta Tester plugin.

Sources: SmartWP WordPress 7.1 preview, WordPress 7.1 Field Guide