On July 1, 2026, Gutenberg 23.5 shipped. Tucked inside it was the machinery for something WordPress has never had in seventeen years of existence: per-viewport responsive styling built directly into the editor. No plugin. No theme hack. No custom CSS class that nobody documented and someone will break in six months. The feature is now in Beta 1 of WordPress 7.1, scheduled for general release on August 19, and if you build sites with the block editor, this is the release that removes the last big reason you kept a page builder installed.

What actually shipped

The testing call went live on July 3 from Nikunj Hatkar on the WordPress Test team. The core work landed in PR #75121 by t-hamano after fifty commits of iteration. Here is what it does in plain terms: you toggle responsive editing on, pick a viewport width from the device dropdown, change a style property — font size, padding, whatever — and that change applies only at that width. Desktop stays untouched. Tablet stays untouched. The editor canvas itself resizes to show you what you are editing, and the front end renders the same thing.

The plumbing is smarter than it sounds. Instead of three discrete device buckets (the old Desktop / Tablet / Mobile toggle that plugins have been hijacking for years), the new system treats canvas width in pixels as the single source of truth. The responsive editing state is global, driven by which viewport you selected, not stored per block. New private APIs expose getCanvasWidth, isResponsiveEditing, and getStyleStateViewport to core. The old getDeviceType public API stays for backwards compatibility, so existing plugins do not break.

It works in both Global Styles and on individual blocks. Theme authors can define custom breakpoints in theme.json. And it sits on top of the same style-states mechanism that powers hover, focus, and active pseudo-states — also new in 7.1. That means you can finally make a button change color on hover without writing a stylesheet.

Why this matters more than it sounds

Every agency has a version of this story: a client wants a heading that is 48px on desktop and 28px on mobile, or a product grid that goes from four columns to two on tablet. The block editor could not do this natively. So you wrote a custom class, or you added a media query to the theme, or you installed Elementor and paid £75 a year for the privilege of clicking a dropdown that said "Tablet" and changing a number.

That dropdown was the entire page builder pitch for a huge chunk of the WordPress market. Not the template library. Not the popup builder. Just the ability to say "this padding, but smaller on mobile." WordPress 7.1 removes that argument from the table.

The 365i team ran the UK maths on this: if your only reason for running a page builder was responsive controls, the licence saving from dropping it almost never pays for the rebuild. That is true. But for new sites, the calculation flips entirely. If the free editor can handle viewport-specific styling out of the box, the barrier to choosing a block theme over a builder theme just got a lot lower.

What did not make Beta 1

The roadmap promised more than Beta 1 delivered. The inherited-styles indicator — the "why is this button still blue?" feature that would show you where a style is coming from — is still an open proof of concept on GitHub. Suggestion mode and emoji reactions for Notes (the new inline feedback feature) did not land. And Google Docs-style collaborative editing is not in this cycle.

The responsive styling itself is the real headline, and it is in. But the gap between what was promised and what shipped is worth noting if you are planning client work around 7.1 features.

What to test right now

The WordPress Playground build lets you try everything without a local install. Resize the editor canvas, toggle responsive editing, change a font size at tablet width, and check the front end. Try it with Patterns and the Navigation editor. Confirm that per-viewport edits survive save and reload. If something breaks, file it against Gutenberg referencing PR #75121.

Beta 1 pins trunk on July 15. The release party schedule puts the general availability at August 19. That gives the community about five weeks of testing. For a feature this significant, that window feels tight. Test early.

The bottom line

WordPress 7.1 does not replace page builders. It does not convert your existing Elementor pages to blocks. It does not handle forms, popups, or WooCommerce template building. But it takes the single most common reason people reach for a builder on a new project and makes it a native feature. For anyone building with blocks, that is not a small thing. That is the moment the block editor stops being the thing you tolerate and starts being the thing you choose.