WordPress 7.1 RC1 is scheduled for release on August 5, 2026. The full release follows on August 19 — the final day of WordCamp US in Phoenix. That's not a coincidence. The WordPress team has been timing major releases to flagship events for a while now, and dropping 7.1 during the biggest North American WordPress gathering of the year guarantees maximum attention for what might be the most builder-friendly release in recent memory.
Anne McCarthy is leading this one. If that name sounds familiar, she also steered the 7.0 release. Two major versions back-to-back from the same release lead is unusual in the WordPress world, and the continuity shows. 7.1 picks up threads that 7.0 started and actually finishes some of them.
The feature everyone's been waiting for
Responsive styling and interactive state controls are the headline, and they deserve the attention. Starting in 7.1, you can define how a block looks at different screen sizes directly from the editor. Smaller font on mobile? Adjust padding on tablet? You do it in the block settings sidebar, not in a stylesheet. The controls work both in Global Styles (affecting every instance of a block type) and on individual blocks.
Interactive states get the same treatment. Hover, focus, and active effects become standard editor controls. Making a button change color on hover has meant custom CSS or a page builder for the entire history of the block editor. In 7.1, it's a dropdown.
Theme authors aren't left out either. The breakpoints those responsive controls snap to are defined in theme.json, so you can customize them per theme rather than accepting whatever Core ships. If you maintain client sites, these two features alone will probably shave hours off every build. The number of times I've written @media (max-width: 768px) for something that should have been a toggle is embarrassing.
Two new blocks, zero new plugins needed
The Playlist block collects audio files into a single player with an optional waveform visualization. Podcasters and anyone embedding music clips just lost their reason to install yet another audio plugin. The Tabs block organizes content into clickable panels — another job that previously required a third-party block.
Existing blocks get love too. Background gradients and background images no longer conflict on Group, Verse, Accordion, Pullquote, Post Content, and Quote blocks. The Custom HTML block now supports editable nested blocks, which matters more than it sounds — it's specifically designed for AI-generated content that arrives as raw HTML. And the Image block gains a "Mark as decorative" toggle to hide purely ornamental images from screen readers, which is a small accessibility win that adds up across large sites.
The media library finally works like it's 2026
Media handling gets a genuine overhaul. HEIC support means iPhone photos upload without conversion. AVIF, WebP, and UltraHDR are all native now. GIF-to-video conversion handles the format nobody should still be using but everyone still sends.
Uploads get resilient: a progress indicator and automatic retries when connectivity drops mid-upload. The new Media Editor Modal replaces the old inline cropper with a single workflow for cropping, rotation, and metadata editing. Galleries can pull in and sort media already attached to a post. The Media Library grid scrolls infinitely instead of making you click "Load more" every thirty images.
If you've ever had a client email you photos because their phone uploads wouldn't go through, this is the release that fixes that specific pain.
Notes grew up. Real-time editing did not arrive.
Notes, the editorial commenting system, got the collaboration investment this cycle. You can now use inline formatting, tag colleagues with @mentions, leave notes on text selections rather than whole blocks, and collapse long conversations to keep the margin readable.
What's still missing is real-time collaboration. It was pulled from 7.0 twelve days before release, and it's not in 7.1 either. The team has been transparent about why: open strategic questions about whether to ship the full feature or just the architecture, and which storage mechanism to use. If you were waiting on Google Docs-style co-editing in WordPress, you're waiting at least one more release.
Developer breaking changes
The post editor is now always iframed. This isolates the canvas from admin styles so viewport units and media queries measure the editor canvas rather than the browser window. Blocks still on Block API version 2 or lower need updating to version 3 to work correctly. WordPress has a migration guide, but if you maintain a block plugin, test against RC1 tomorrow.
The Abilities API gets execution lifecycle filters and improvements. jQuery UI updates to 1.14.2. The Site Editor respects your admin color scheme instead of forcing a dark background. The command palette groups results by recency. And in a fix that's overdue by roughly a decade, you can finally change a comment's parent from the Edit Comment screen.
What to do right now
RC1 drops tomorrow. If you maintain a WordPress site, a theme, or a block plugin, install it on a staging environment and break things before August 19. The full release lands during WordCamp US, which means the core team will be in one place for immediate feedback — and the community will be watching.
The dev notes are already published on Make/Core. The Abilities API changes, the iframed editor migration, and the design system theming guide are the ones most likely to affect existing sites. Read them now, not on release day.
WordPress 7.1 doesn't reinvent the editor. It makes the editor finally capable of the things people have been asking for since the block editor shipped. Responsive controls, hover states, proper media handling, and audio playlists without plugins. That's not flashy. It's useful. And for a platform that powers over 40% of the web, useful matters more than flashy every time.