WordPress 7.1: What to Expect (Releasing August 19, 2026)

WordPress 7.1 is scheduled for August 19, 2026, landing on the final day of WordCamp US. It is the second major release of 2026, led by Anne McCarthy, and it is currently in beta. The headline for most people is styling: responsive design and hover states are becoming built-in editor controls rather than things you write CSS for.

Below is what has actually landed in the betas, what is still on the roadmap but unconfirmed, and the one big feature that is missing again. Everything here reflects Beta 4, and beta features can still change or be pulled before release.

The Headline: Responsive and Hover Styling Without CSS

Two long-requested features are arriving together, and they are the reason this release matters to people who build sites rather than plugins.

Responsive styling lets you define how a block looks at different screen sizes from inside the editor. Set a smaller font size on mobile without opening a stylesheet. It works both in Global Styles, applying to every instance of a block, and on individual blocks. Theme authors also get viewport breakpoint customization, so the breakpoints those controls snap to can be defined in theme.json rather than being fixed by Core.

Interactive state styling covers the other half: hover, focus, and active states as standard controls. Making a button change color on hover has, until now, meant custom CSS or a page builder. In 7.1 it becomes a setting, again available both globally and per block.

Taken together these close two of the most common reasons people still reach for custom CSS or a third-party builder. If you maintain client sites, this is the change most likely to shorten your build time.

Collaboration: Notes Grew Up, Real-Time Editing Did Not Arrive

Notes, the editorial commenting system, got most of the collaboration work this cycle. You can now use inline formatting (bold, italic, code, links, emoji), tag colleagues with @mentions, leave a note on a text selection rather than a whole block, start multiple separate conversations on the same block, and collapse long notes to keep the margin readable.

What is not there is real-time collaboration. It was pulled from WordPress 7.0 twelve days before that release, and it does not appear in the 7.1 beta announcements either. The 7.1 roadmap is candid about why: the team still has open strategic questions, including whether to ship the full feature or just the underlying architecture, and which storage mechanism to use. A dedicated testing outreach effort is running alongside the release.

The practical read: if you were waiting on Google Docs style co-editing in WordPress, keep waiting. Two releases have now passed with the groundwork moving but the feature itself held back, which suggests the team would rather ship it late than ship it unstable.

New Blocks and Block Improvements

Two new Core blocks are confirmed in the beta. The Playlist block collects audio files into a single player with an optional waveform visualization, which covers podcast and music use cases that previously needed a plugin. The Tabs block organizes content into clickable panels, another job that has meant a third-party block until now.

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

A Genuine 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), UltraHDR, AVIF, and WebP, plus GIF-to-video conversion for lighter files. Anyone who has had a client email photos because their phone uploads would not go through will appreciate this one.

Uploads also get more resilient, with a progress indicator and automatic retries if 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, and the Media Library grid scrolls infinitely instead of making you click “Load more” (you can turn that off in your profile).

If you are dealing with oversized uploads today, our guides to large image scaling and increasing the max upload size still apply.

Admin Quality-of-Life Changes

The admin bar now follows you into the Site Editor and Block Editor, which the team has been calling the omnibar. The command palette (Ctrl+K, or Cmd+K on Mac) groups results into Recent, matching, and Suggestions rather than one flat list, and remembers what you used recently. The Site Editor also finally respects your chosen admin color scheme instead of always rendering on a fixed dark background.

A few smaller additions are the sort of thing you notice daily. Site title, tagline, and icon move into a dedicated Identity section instead of being scattered. The Posts list shows an excerpt for each entry. A new On This Day dashboard widget resurfaces what you published on this date in previous years. And in a fix that is overdue by roughly a decade, you can finally change a comment’s parent from the Edit Comment screen, so untangling a misthreaded comment no longer means editing the database by hand.

What Developers Need to Know

The change most likely to break something is the enforced iframed editor. The post editor now always runs inside an iframe, isolating the canvas from admin styles so viewport units and media queries measure the canvas rather than the browser window. Blocks still using Block API version 2 or lower need updating to version 3 to work correctly, and WordPress publishes a block migration guide for exactly this.

Beyond that, the Abilities API introduced in 7.0 gains better querying, filtering, and input validation. Block Bindings extend to List Item blocks. New functions let plugin and theme authors register custom icons for use throughout the editor, building on the Icon API that shipped in 7.0. The wordpress/theme package stabilizes with design tokens and a public React ThemeProvider. And the Connectors screen adds username and application password authentication alongside API keys, which is worth knowing if you use application passwords for integrations.

On the Roadmap, But Not Confirmed

The 7.1 roadmap lists more than the beta announcements confirm, and the roadmap itself carries a warning that not everything on it will ship.

One item is already settled, and in the opposite direction to what was announced. The Classic block was going to be hidden from the block inserter in 7.1, a change that was merged in late June. On July 7 it was reverted. The Classic block stays in the inserter exactly as it is today, the wp_classic_block_supports_inserter filter has been removed, the deprecation notice inside Classic blocks is gone, and the companion Enable Classic Block plugin is being closed as unnecessary. The stated reasoning was that the approach “had things largely backward” and that the Classic block “should become obsolete by choice, not by force.” If you still use the Classic block, nothing changes for you in 7.1 and no migration is required.

These are the remaining items that were on the roadmap but have not appeared in the beta feature lists, so treat them as uncertain rather than expected:

• Real-time collaboration, as covered above, with the scope decision still open.
• Table of Contents block, which was on the roadmap alongside Playlist and Tabs but is not in the beta feature list.
• Guidelines, a system for encoding editorial rules and brand voice for AI tooling. Discussion on the roadmap suggests it was being reworked into a broader concept before release.
• The React 19 upgrade, which the roadmap describes as landing in the Gutenberg plugin first with a path to Core later.

Beta 1 is the canonical feature list for this release. The Beta 4 announcement points readers back to it for “details and highlights,” and Betas 2 through 4 have been bug fixes rather than new features (Beta 4 alone carried 114 fixes since Beta 3). The final Field Guide, published around Release Candidate 1, will be the authoritative word.

Release Schedule and How to Test It

Beta 1 landed July 15, followed by three more betas through July 29. Release Candidate 1 is due August 5 and RC2 on August 12, with a dry run on August 18 and the release itself on August 19, 2026.

If you maintain plugins or a heavily customized theme, testing now is worth the hour, particularly because of the iframed editor change. The safest route is a staging site, never production. You can install the WordPress Beta Tester plugin and choose the Bleeding edge channel, pull the current build with WP-CLI using wp core update --version=7.1-beta4 (swap in 7.1-RC1 once it lands on August 5), or spin up a throwaway instance in WordPress Playground without installing anything at all.

Should You Update on Day One?

For most sites, wait roughly a week or two. Let plugin authors ship their 7.1-compatible releases first, then update a staging copy, then push to production. The exception is a brand-new site with few plugins, where there is no reason to start on 7.0.

Before you update anything, take a full backup you have actually tested restoring. If you are not sure what version you are on right now, our WordPress version checker will tell you in a couple of seconds.

Frequently Asked Questions

When is WordPress 7.1 released?

August 19, 2026, timed to the last day of WordCamp US 2026. It is the second major release of 2026, following 7.0 in May.

Does WordPress 7.1 include real-time collaboration?

It does not appear in the beta announcements. Real-time collaboration was removed from 7.0 shortly before release, and the 7.1 roadmap describes open decisions about scope and storage that are still unresolved. Notes received the collaboration investment in this cycle instead.

Will 7.1 break my site?

The most likely source of trouble is the enforced iframed editor, which affects blocks built on Block API version 2 or lower. If you run custom or older third-party blocks, test on staging before updating. Most sites running mainstream, actively maintained plugins will be fine.

Does 7.1 have a codename yet?

Not publicly. WordPress names major releases after jazz musicians, and the name is traditionally announced with the release itself. WordPress 7.0 was “Armstrong.”

Wrapping Up

WordPress 7.1 is a less dramatic release than 7.0, and that is not a criticism. Where 7.0 introduced an AI framework and a redesigned dashboard, 7.1 mostly finishes things: responsive and hover styling that should have been editor controls years ago, media handling that copes with the formats phones actually produce, and a pile of small admin fixes that remove daily friction.

We will update this post as the Field Guide is published and the final feature list firms up. In the meantime, see what shipped in WordPress 7.0 “Armstrong”, or browse the full WordPress version history from 0.7 to today.