WordPress 7.1 Beta 1 landed on July 15, 2026. The final release is scheduled for August 19, timed with WordCamp US. Anne McCarthy is the release lead. If you run a WordPress site, build plugins, or maintain themes for clients, the feature list in this beta is the contract you are going to live with in about three weeks. Everything that is not in this build has to justify itself as an exception to get in, and everything that is in it is what you will be expected to support on day one.
This is the most visible WordPress cycle in a while. Not because of one headline feature, but because several things that have been cooking across multiple releases finally landed in a state that feels finished rather than experimental.
Responsive styling without writing CSS
This is the one people have been waiting for. You can now define per-viewport values for font size, spacing, and block visibility directly inside the block editor. No custom CSS. No media queries. No child theme overrides for a client who wants slightly tighter line height on mobile.
Theme authors can customize breakpoints. Interactive-state styling for hover, focus, and active states rides on the same mechanism. The way it works in practice is that the resizable canvas in the editor now syncs with a device dropdown, so the canvas width in pixels is the single source of truth for which viewport you are editing. You drag the canvas to 375 pixels wide, you are editing the mobile view. You set a font size, it applies to that viewport. The editor writes the responsive CSS behind the scenes.
This is the payoff of work that has been building across Gutenberg 23.4 and 23.5. If you have been ignoring responsive styling as an experimental flag, it is time to stop ignoring it. It is in Beta 1, which means it ships in August.
Notes finally grew up
Notes, the inline commenting system for the block editor, got a significant upgrade. Inline formatting now supports bold, italic, code, links, and emoji. You can tag collaborators with @mentions. Multiple conversations can live on a single block. You can comment on selected text within a block, not just the block itself. Long threads are collapsible.
This matters because Real Time Collaboration, the feature that would let multiple people edit the same post simultaneously like Google Docs, was pulled from WordPress 7.0 in May and remains in limbo with "strategic decisions pending" in the official roadmap language. Notes is what the project can ship confidently while RTC gets sorted out separately. For editorial teams that need a review workflow now, asynchronous collaboration through Notes is the practical option, and in 7.1 it stops feeling like a proof of concept.
Media processing moves into the browser
Client-side media pipelines now handle HEIC, UltraHDR, AVIF, WebP, and GIF-to-video conversion. A dedicated media editor modal replaces the old inline crop UI. The media library gets infinite scrolling and auto-population of attached images.
For anyone running a photo-heavy site, this is a meaningful quality-of-life improvement. When someone drops a 40 MB HEIC file from their iPhone into the media library, the browser converts it to WebP before it ever hits the server. No more server-side processing bottlenecks for image uploads. No more "your upload timed out" errors on shared hosting.
The admin bar is back in the editors
The persistent toolbar now shows in both the Post Editor and the Site Editor by default. The ambiguous "W" logo becomes a proper back chevron. Configured site icons appear in the toolbar. The Site Editor is now a first-class toolbar surface, which means any plugin that registers custom admin bar nodes needs to be tested inside both editors. If your plugin assumed the toolbar was hidden in the block editor, that assumption is now wrong.
There is also a new command palette with grouped results, a Site Editor admin color scheme, a visual revision picker, post excerpts in list view, and an "On This Day" widget. None of these are individually earth-shattering, but together they make the admin feel more cohesive than it has in any previous release.
New blocks and developer APIs
Two new core blocks ship in Beta 1: a Playlist block with waveform visualization for audio collections, and a Tabs block for tabbed content. On the developer side, the Abilities API gets an expansion, Block Bindings now work with list items and nested content, custom icon registration is available, and the iframed editor is enforced for block themes. React 19 is back behind an experimental flag with a compatibility layer. Speculative loading defaults shift from conservative to moderate when caching is detected.
What you should do right now
If you maintain plugins or themes, test against Beta 1 this week. Three specific things to audit: custom admin bar nodes rendering inside the Site Editor, any code that assumes direct DOM access from the top-level document (the iframed editor is now non-optional for block themes), and any media processing hooks that depend on server-side handling of modern image formats.
If you just run a WordPress site and do not build for it, wait for the stable release on August 19. But start thinking about responsive styling, because the next time a client asks you to make the font bigger on mobile, the answer is going to be a dropdown in the editor instead of a custom CSS snippet.
Sources: