WordPress 7.1 ships on August 19, 2026 — the final day of WordCamp US. It's the second major release of the year, led by Anne McCarthy, and it's currently in Beta 4. If you build sites for clients or maintain more than a handful of WordPress installs, this one changes your workflow more than you'd expect from a point release.

The Big One: Responsive and Hover Styling Without CSS

The feature that matters most to anyone who actually builds with WordPress: you can now define responsive breakpoints and interactive states directly inside the editor. No custom CSS. No page builder. Just settings.

Responsive styling lets you set different block appearances at different screen sizes from inside the editor. Want a smaller font on mobile? It's a control now, not a media query. It works both globally (every instance of a block type) and per-block. Theme authors get viewport breakpoint customization through theme.json, so the snap points aren't hardcoded by Core anymore.

Interactive state styling covers hover, focus, and active states. Making a button change color on hover has meant custom CSS or a third-party builder for years. In 7.1, it's a checkbox. Same deal — global or per-block.

Together, these two features eliminate the most common reasons people still reach for custom stylesheets or Elementor for simple sites. If you're maintaining client sites, expect this to genuinely cut build time.

Notes Got an Upgrade. Real-Time Collaboration Didn't.

The editorial commenting system (Notes) got a proper overhaul: inline formatting, @mentions, selection-level commenting instead of block-level, multiple conversation threads per block, and collapsible notes for cleaner margins.

What's still missing is real-time collaboration — the Google Docs-style co-editing feature that was pulled from WordPress 7.0 twelve days before release. It's not in 7.1 either. The team has been open about why: unresolved questions about storage mechanisms and whether to ship the full feature or just the architecture. A dedicated testing outreach is running alongside this release.

The honest read: if you were waiting for real-time co-editing in WordPress, two releases have now shipped without it. The groundwork keeps moving, but the feature itself keeps getting held back. That's probably the right call — shipping it broken would be worse than shipping it late.

New Blocks: Playlist and Tabs

Two new Core blocks show up in the beta.

The Playlist block collects audio files into a single player with an optional waveform visualization. If you've been bolting on a podcast plugin just to embed multiple audio files, this replaces that. The Tabs block organizes content into clickable panels — another thing that previously required a third-party block.

Several existing blocks improve too. 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 (aimed at AI-generated content arriving as raw HTML). The Image block gets a "Mark as decorative" toggle for accessibility. And pasting a shortcode into the Embed block now creates a real Embed block instead of leaving raw text.

The Media Overhaul Nobody Talks About

This might be the most practical change for day-to-day use. Media processing moves into the browser with support for HEIC (iPhone's default format), UltraHDR, AVIF, and WebP, plus GIF-to-video conversion. If you've ever had a client email photos because their phone uploads wouldn't go through, this fixes that.

Uploads get resilient too — progress indicators and automatic retries when your connection drops. A new Media Editor Modal replaces the old inline cropper with cropping, rotation, and metadata editing in one place. Galleries can pull media already attached to a post. The Media Library scrolls infinitely instead of making you click "Load more."

Admin Tweaks You'll Actually Notice

The admin bar now follows you into the Site Editor and Block Editor (the "omnibar"). The command palette groups results into Recent, Matching, and Suggestions instead of one flat list. The Site Editor finally respects your admin color scheme.

Smaller stuff: site title, tagline, and icon move into a dedicated Identity section. The Posts list shows excerpts. A new "On This Day" widget surfaces past content. And — only a decade overdue — you can finally change a comment's parent from the Edit Comment screen instead of touching the database.

What Developers Need to Watch

The post editor now always runs inside an iframe. This isolates the canvas from admin styles so viewport units and media queries measure the canvas, not the browser window. If your blocks still use Block API version 2 or lower, they need updating to v3. WordPress has a migration guide, and if you ignored it for 7.0, you can't ignore it anymore.

Should You Update on Day One?

For the average site: wait a week. Let the community find edge cases. For sites you actively develop on: update in staging immediately, test your block library, and push to production once you've confirmed nothing breaks. The media improvements and responsive controls alone make this worth the effort.

August 19. Mark it.