WordPress 7.1 is scheduled for release on 2026-08-19, timed to coincide with WordCamp US, and reached Beta 1 on 2026-07-15. The headline changes are interactive-state styling for blocks (hover, focus, and active states without custom CSS), three new core blocks (Tabs, Playlist, and Table of Contents), a richer Notes system for asynchronous feedback, the return of client-side media processing, and an AI Guidelines feature that lets you set your site's voice once instead of retyping it into every prompt. Real-time collaboration, cut from 7.0 in May, is confirmed not to ship in 7.1 either. Whether to update on day one depends mostly on what kind of site you run, covered below by site type.
This is a living post. Everything below reflects the WordPress 7.1 beta as confirmed on 2026-07-31; beta features can still change before the final release, and this page will be updated on release day with what actually shipped.
The 10-second version
- Release date: 2026-08-19.
- Headline features: interactive-state block styling, three new blocks (Tabs, Playlist, Table of Contents), enhanced Notes, client-side media processing returns, an AI Guidelines system.
- Deferred again: real-time collaboration, not in 7.1 either.
- Our recommendation, in short: hobby and personal sites can reasonably update in the first week; business and WooCommerce sites should wait for 7.1.1 unless a specific 7.1 feature is worth the small extra risk. Details by site type below.
What's confirmed in the 7.1 beta
Interactive-state styling. You'll be able to style a block's hover, focus, and active states directly from the block editor's interface, without writing custom CSS. This is aimed squarely at the readers who currently use a custom CSS box or a separate plugin just to make a button change color on hover.
Responsive styling controls. Alongside interactive states, 7.1 adds viewport-based breakpoint controls, letting you adjust a block's appearance differently at different screen widths from inside the editor rather than through custom media queries.
Three new core blocks. Tabs is described as the most mature of the three heading into release. Table of Contents is the one most likely to slip past 7.1 if testing surfaces problems, so treat its arrival as tentative until release day. Playlist adds a waveform visualization for audio.
Notes, expanded. The Notes feature (in-admin commenting, not a public-facing tool) gains text formatting, @mentions with a searchable list of collaborators, and the ability to attach a note to a specific text selection rather than a whole block. This is WordPress's answer to the asynchronous side of collaborative editing.
Client-side media processing returns. Browser-side image conversion and cropping before upload, which did not make it into 7.0, is back in 7.1. Practically, this means some image handling happens in your browser before the file ever reaches your server.
AI Guidelines. A new settings layer lets you define your site's voice and preferences once, so AI-assisted features that use your Settings → Connectors credentials apply that guidance automatically instead of you re-explaining it with every request. This sits on top of the Connectors setup from WordPress 7.0; if you haven't configured a provider key yet, our Connectors setup guide covers that first step.
A smaller addition: an "On This Day" dashboard widget, surfacing what you published on the same date in past years.
What got deferred or cut
Real-time collaboration, the multi-user simultaneous-editing feature originally expected in 7.0, was pulled from that release on 2026-05-08, twelve days before launch, and it is confirmed not to arrive in 7.1 either. The Notes enhancements above are WordPress's asynchronous alternative in the meantime; live co-editing has no confirmed release version as of this writing.
Table of Contents is confirmed as beta-stage but flagged by core contributors as the block most likely to slip if testing turns up problems between now and release day. If it does slip, it would ship in a later release rather than 7.1.
Should you update on day one? By site type
Hobby or personal blog, low traffic, few plugins. Updating in the first week is reasonable. The blast radius of anything going wrong is small, and you get the interactive-state styling and new blocks immediately. Take a backup first regardless.
Small business site, some traffic, a handful of plugins from different developers. Waiting one to two weeks for 7.1.1, or at least until your key plugins confirm compatibility via their "Tested up to" flag, is the safer call. Nothing in the confirmed feature list above is urgent enough to justify updating before your plugins have caught up.
WooCommerce or any site processing transactions. Wait for 7.1.1 unless you have a staging environment to test on first. None of 7.1's confirmed features are commerce-specific, so there is little upside to being first, and a checkout-breaking incompatibility is the worst possible timing for a store.
Any site, regardless of type, that skipped testing before the 7.0 update. Use this release as the moment to build that habit rather than repeating the same risk. A staging copy of your site, even a basic one, catches most update problems before they reach your live site.
Get ready this week: the pre-update basics
Whatever your timeline, three things are worth doing before 7.1 lands rather than after: take a full backup, files and database both; check each active plugin's "Tested up to" flag on its WordPress.org page, since a flag still showing 7.0 or earlier is a signal to wait on that specific plugin; and confirm your host's PHP version meets WordPress 7.0's existing minimum of PHP 7.4, since 7.1 does not lower that bar. If a plugin did misbehave after the 7.0 update earlier this year, our guide to diagnosing and fixing that walks through the same triage that applies again here, and if an update ever leaves you looking at a critical error instead, our recovery mode walkthrough covers both the locked-out and partial-error cases.
How we'll keep this post updated
This page will be revised on 2026-08-19 itself, once 7.1 actually ships, to confirm which of the beta features above made the final cut and to add anything that changed between beta and release. If you're reading this after that date and something below looks different from what you're seeing on your own site, that is the update working as intended, not an error in this guide.
FAQ
Is WordPress 7.1 a major version like 7.0 was? It is a smaller release than 7.0's admin overhaul. 7.1 adds styling controls, new blocks, and Notes/AI improvements on top of the interface 7.0 already introduced, rather than redesigning anything further.
Do I need to do anything before updating, beyond a normal backup? No new prerequisite beyond what any WordPress update needs: a full backup and, ideally, a staging test. WordPress 7.1 does not raise the PHP minimum beyond what 7.0 already requires.
Will real-time collaboration ever ship? It has no confirmed release version as of 2026-07-31, having been deferred from both 7.0 and 7.1. The enhanced Notes system in 7.1 is the asynchronous alternative in the meantime.
What if my admin looks completely different from what this article describes? If you are still running a pre-7.0 version, everything above about the admin builds on the 7.0 redesign; our walkthrough of that redesign is the starting point before any of 7.1's additions make sense.
Written against the WordPress 7.1 beta as of 2026-07-31. Final release and this page's update expected 2026-08-19.
