I have used WordPress for over 15 Years and whenever a new update is there it gets me curious. WordPress 7.1 Beta 3 just landed, and if you’ve been keeping half an eye on the release cycle, this is the point where things start feeling real. We’re now three betas deep, the feature set is essentially locked, and what’s left is the unglamorous but genuinely important work of finding and fixing the rough edges before the stable release ships on August 19, 2026.
I want to walk you through what’s actually in this release, what changed specifically in Beta 3, and — because I know a good chunk of you reading this run client sites or manage WordPress properties professionally — what I’d suggest doing with this information right now versus what can wait.
First, the Standard (But Important) Disclaimer
Before anything else: this is a beta. WordPress has been consistent and clear about this with every pre-release build, and I’ll be just as clear here. Do not install Beta 3 on a production or client-facing website. Beta software exists specifically to surface bugs before they reach the millions of live sites running WordPress, and that only works if testing happens in safe, disposable environments — a local install, a staging site, or a throwaway sandbox.
Check this plugin also: WordPress Beta Tester Plugin
If you want to poke around without any setup at all, WordPress Playground now has a dedicated Beta 3 instance you can spin up directly in your browser, no installation required. For anyone comfortable with a bit more control, the WordPress Beta Tester plugin (set to the “Bleeding edge” channel, “Beta/RC Only” stream) is the easiest way to keep a test install tracking each new beta automatically. If you’d rather do it manually, there’s a direct zip download, and if you live in the terminal, a single WP-CLI command handles it too.
The Big Picture: What WordPress 7.1 Is Actually About
Zooming out from the individual features, WordPress 7.1 reads like a release focused on three things: giving creators more native styling control without touching custom CSS, making the media and editing experience noticeably smoother, and tightening up the admin so it feels less like a tool you tolerate and more like one that adapts to how you actually work.
A lot of what’s landing in 7.1 has actually been available in the Gutenberg plugin for months, spread across several point releases. This release folds that accumulated plugin work into WordPress core, which is the usual pattern — Gutenberg acts as the testing ground, and Core absorbs what’s proven stable.
Notes Grow Into a Real Collaboration Tool
If you’ve used the Notes feature since it landed, you know it’s been useful but fairly basic — essentially sticky comments on blocks. That changes meaningfully in 7.1. Notes now support inline text formatting: bold, italic, code, links, and emoji, each with its own keyboard shortcut, so leaving feedback doesn’t mean breaking your writing flow to reach for a toolbar.
The addition I think will get the most real-world use is @mentions. Typing “@” inside a note pulls up a searchable list of collaborators, letting you tag someone directly rather than hoping they scroll past your comment eventually. For teams managing editorial workflows — which, if you’re running any kind of content operation, is probably you — this closes a real gap.
You can also now start multiple separate note threads on the same block instead of everything collapsing into one conversation, and notes can be attached to a specific text selection rather than an entire block, which matters a lot when you’re giving feedback on a single sentence inside a longer paragraph. Long notes also collapse by default now with a “show more” toggle, so a detailed comment doesn’t dominate your margin.
Responsive and Interactive Styling Without Writing a Line of CSS
This is, in my opinion, the headline feature of the release for anyone doing site design work in WordPress. You can now define how a block looks at different screen sizes directly inside the editor — for both Global Styles and individual block instances — without touching custom CSS at all. This has been one of the most requested capabilities in the block editor for years, and seeing it land natively in Core is a big deal for agencies and freelancers who’ve been relying on theme-specific workarounds or third-party plugins to get this kind of control.
Theme authors also get more say in how this works, since viewport breakpoints can now be customized directly in theme.json rather than being locked to fixed defaults.
Alongside responsive styling, 7.1 introduces interactive state styling — a standardized way to control how a block responds to hover or focus, like a button changing color when someone’s cursor is over it. Again, this used to mean custom CSS or a workaround plugin. Now it’s a built-in control, available consistently across Global Styles and individual blocks.
If you build or maintain client sites, I’d genuinely recommend testing this specific feature early. It has real implications for how you scope future design work and what you can now offer clients natively instead of bolting on a plugin.
Media Handling Gets a Meaningful Upgrade
Anyone who’s dealt with a client uploading an iPhone photo and watching WordPress choke on the HEIC format will appreciate this section. Image and media processing now happens client-side in the browser, with broader native format support — HEIC, UltraHDR, AVIF, and WebP are all handled properly, and GIF files can now be converted to video on upload for lighter, more efficient files. Uploads are also more resilient now, with progress indicators and automatic retry behavior if a connection drops mid-upload.
There’s a new dedicated Media Editor Modal replacing the old inline cropping tool, bringing cropping, rotation, and metadata editing into one consolidated workflow instead of scattering them across different interfaces. Galleries got smarter too — they can now automatically pull in and sort media already attached to the current post, cutting down on manual setup. And after you upload images to a post, the inserter now surfaces them automatically in a new “Attached images” section, which is a small thing but genuinely saves time during content production.
One more quality-of-life change worth flagging: the Media Library grid now scrolls infinitely by default instead of requiring a “Load more” click, which will be a welcome change for anyone managing a media-heavy site. If you’d rather keep the old behavior, it can be disabled from your user profile.
Beta 3 Specifically: Styling Refinements and Bug Fixes
Now, what actually changed between Beta 1 and Beta 3, since that’s the release we’re technically covering here. Beta 2 shipped alongside the 7.0.2 security release on July 17 and mainly carried those security fixes forward. Beta 3, released July 22, addresses more than 71 issues logged since Beta 1 and introduces two specific styling improvements worth knowing about.
The first is a refinement to the “Apply globally” option in the block inspector. Previously, applying local style changes globally was an all-or-nothing action — every tweak you’d made locally got pushed out site-wide whether you wanted it to or not. Beta 3 adds a quick review step, letting you choose exactly which modified styles get applied globally while the rest stay as local overrides. This is a genuinely thoughtful fix for anyone who’s accidentally blown out their global styles trying to update one small local change.
Beyond that, Beta 3 focuses heavily on media upload stability: long animated GIF uploads no longer hang indefinitely, images rotated using EXIF metadata now process correctly instead of displaying sideways, and uploading a single HEIC image in Safari no longer creates duplicate entries in the media library. There are also further fixes to Notes, responsive styling behavior, and custom CSS handling. On the developer side, WordPress Coding Standards has been bumped to version 3.4.0.
One notable scope change: Unicode email address support, which had been planned for 7.1, will not be included in the final release. That work will continue as a community plugin instead, allowing broader testing of compatibility, security, and data-handling implications before it’s considered for a future Core release. If you were specifically tracking that feature, it’s worth adjusting your expectations accordingly.
A More Personal Admin Experience
The admin area itself gets a round of genuinely useful refinements. The toolbar — now referred to as the Omnibar — travels with you into the Site Editor and Block Editor instead of disappearing, with a series of polish improvements throughout. The command palette (Ctrl/Cmd+K) is more refined too, now grouping results into Recent, Matching, and Suggestions sections instead of dumping everything into one flat list, which makes finding what you need noticeably faster once you’re used to it.
The Site Editor also now reflects your chosen admin color scheme instead of defaulting to a fixed background, the Posts list view shows short excerpts for each entry, and there’s a new picker layout for browsing revision history with clearly labeled autosaves. A dedicated Identity section now houses your site title, tagline, and icon settings in one clearly labeled place in the Site Editor. There’s even a small On This Day widget on the dashboard, resurfacing what you published on this date in previous years — a nice, low-key nudge to both reflect and keep writing.
One fix I’d specifically call out for anyone managing an active comment section: you can now change a comment’s parent directly from the Edit Comment screen via a dropdown, rather than needing to edit the database to untangle a misthreaded conversation.
New Blocks and Under-the-Hood Developer Work
On the block side, 7.1 introduces a Playlist block for presenting audio collections with an optional waveform visualization, and a Tabs block for organizing content into clickable panels instead of a long scroll — both useful additions that reduce reliance on third-party plugins for fairly common content patterns. Background gradients and background images no longer silently conflict with each other across several blocks including Group, Verse, Accordion, Pullquote, Post Content, and Quote. The HTML block now supports editable nested blocks, which specifically helps when working with AI-generated content that often arrives as raw HTML. Images also gained a “mark as decorative” toggle for better accessibility handling with screen readers.
For developers, the Abilities API continues expanding with better querying, filtering, and input validation, Block Bindings now extend to List Items, and the post editor now always runs inside an iframe for more predictable, isolated rendering — a change that means blocks still using Block API v2 or lower should be updated to v3 for compatibility going forward.
What I’d Actually Recommend Doing Right Now
If you manage WordPress sites professionally, this is the moment to start testing in a sandbox environment, not the moment to deploy anything live. Spin up a Playground instance or a local install, specifically poke at the responsive styling controls and the new media upload flow, since those are the changes most likely to affect ongoing client work once 7.1 goes stable.
If you’re a theme or plugin developer, pay close attention to the iframed editor change and the Block API v3 requirement — that’s the kind of shift that quietly breaks things if you’re not paying attention ahead of time.
For everyone else, there’s nothing urgent to do yet beyond staying aware. WordPress 7.1 is scheduled for a stable release on August 19, and between now and then we’ll likely see at least one more beta and a release candidate before it’s genuinely ready for production use.
