WordPress 7.1 Beta 1 shipped on July 15, 2026, and the final release is locked for August 19 — timed to land during WordCamp US. If you updated to 7.0 back in May and have been waiting to see what the next point release actually delivers, the short version is: it delivers the editor features people have been requesting for years, and it punts the one feature everyone assumed would be here by now.

The Tabs block finally exists

This is the headline. A native Tabs block is in core. You can now create clickable tabbed panels with full block support inside each panel, which means you no longer need a third-party plugin to split long content into tabs. It sounds small until you realize how many sites were stacking everything vertically because the editor gave them no alternative.

WordPress 7.1 also ships a Playlist block for audio and video collections and a Table of Contents block that auto-generates from your headings. The Table of Contents block is the one I find most useful in practice — a heading-based TOC used to mean installing a plugin or writing custom code. Now it's a core block you drop onto the page.

Responsive styling without writing CSS

For anyone who has ever had to write custom media queries to make a block look decent on a phone, this is the feature that matters. WordPress 7.1 adds viewport breakpoint customization directly in the block inspector. You can set different font sizes for mobile, tighter spacing for tablets, and different layouts for desktop — all through the visual interface. No stylesheet required.

Alongside that, interactive state styling lets you define how blocks respond to hover and focus states. A button that changes color when you mouse over it, a link that shifts on focus — these are now set visually in the inspector panel instead of requiring custom CSS. Both features close a gap that has existed since the block editor launched.

Notes becomes a real collaboration tool

The Notes system got a significant upgrade. In 7.1, notes support text formatting, @mentions with a searchable collaborator list, and the ability to leave a note on a specific text selection rather than an entire block. The roadmap also lists suggestion mode, emoji reactions, reply and follow notifications, and an "apply suggestions" action. If you have used Google Docs comments and suggestions, the pattern will be familiar.

This is where the collaboration story gets interesting — and where it gets complicated. Notes in 7.1 is a solid asynchronous workflow. You can leave feedback on specific paragraphs, tag your teammate, and they can apply or dismiss the suggestion without touching the rest of the post. But the feature a lot of people were actually expecting — real-time multi-author editing, where two people type in the same document simultaneously — is not in this release. It got deferred again.

What else changed

The media library gets a real overhaul. WordPress 7.1 moves image processing to the browser with client-side support for HEIC, UltraHDR, AVIF, and WebP formats. There is a new Media Editor Modal for quick edits like cropping, and infinite scrolling is now the default in the Media Library. The roadmap also mentions GIF-to-video conversion, which is a quiet win for page load times.

The Persistent Admin Bar is a smaller change but one that fixes an annoyance: the admin bar now stays visible as you scroll through long pages in the editor, so you do not have to scroll back to the top to access it.

What got deferred

Real-time collaboration is the big one. The WordPress core team has been working on multiplayer editing for several releases now, and it is not ready. The Notes upgrade in 7.1 is a stepping stone toward that goal, but if you are an agency waiting for Google Docs-style simultaneous editing in WordPress, you are still waiting.

There is no confirmed timeline for when real-time collaboration will land. The team has been deliberate about not overpromising, which is the right call. Shipping a half-baked multiplayer experience would be worse than shipping none at all.

What to do right now

If you want to test 7.1 before it goes final, WordPress Playground lets you spin up a beta instance in your browser at playground.wordpress.net — no local setup needed. If you run client sites and have been using plugins for tabs or table of contents, now is the time to test whether the core blocks cover your use case. If they do, that is one less plugin to maintain after August 19.

If you are on WordPress 7.0.x and already patched to 7.0.2 (which you should be, given the WP2Shell situation from last week), the 7.1 update will be a straightforward point release upgrade. No breaking changes, no PHP version bumps, no deprecations to worry about.

The final release ships August 19. Between now and then, the beta cycle continues with weekly releases. If you find bugs, the team is actively triaging on Trac. This is the window where your feedback actually shapes the release.