WordPress 7.1 Beta 1 Hands-On: Responsive Styling, New Blocks, and a Smarter Media Library

WordPress 7.1 Beta 1 dropped on July 15, and I’ve already spun it up in a test environment. The final release is scheduled for August 19, 2026, timed with WordCamp US — which means you have about a month to get familiar with what’s coming and make sure your sites and client projects are ready. After spending a couple of days with the beta, I can tell you this: 7.1 is one of those releases that quietly removes a lot of custom CSS from my workflow.

Here’s my hands-on breakdown of the features that actually matter for developers and site owners, plus how to test the beta safely.

Responsive Styling: The Feature We’ve Waited Years For

This is the headline for me. WordPress 7.1 lets you define how a block looks at different screen sizes directly in the editor — for both Global Styles and individual blocks — without writing a single media query.

If you’ve built client sites with the block editor, you know the pain: the design looks perfect on desktop, then a heading is too large on mobile, and suddenly you’re registering a custom stylesheet just to fix font sizes at breakpoints. In 7.1, those adjustments live in the editor UI where clients can actually see and understand them.

Custom breakpoints in theme.json

Theme authors can now define their own responsive breakpoints in theme.json. This is a big deal for agencies with design systems — your editor breakpoints can finally match the breakpoints in your front-end CSS instead of fighting them.

Interactive State Styling

Alongside responsive controls, 7.1 adds standardized controls for styling interactive states — hover, focus, and so on. A button that changes color on hover no longer needs custom CSS or a third-party block library. For accessibility work, having proper focus states configurable in Global Styles is a genuine win, and it nudges site owners toward better keyboard navigation by default.

A Much Smarter Media Pipeline

Media handling gets some of the most practical upgrades in this release:

• Client-side media processing — Image processing moves into the browser, with built-in support for HEIC (the iPhone default), AVIF, WebP, and UltraHDR, plus GIF-to-video conversion. If you’ve ever had a client email you because their iPhone photos “won’t upload,” this fixes that conversation forever.
• Resilient uploads — Uploads now show a progress indicator and automatically retry if the connection drops. Small thing, huge quality-of-life improvement on mobile connections.
• New Media Editor modal — Cropping, rotation, and metadata editing now live together in one dedicated modal instead of the old inline cropping tool.
• Infinite scrolling in the Media Library — The grid view loads items as you scroll. On sites with thousands of images, this alone is worth the upgrade.

New Blocks: Tabs and Playlist

Two blocks I’ve been recreating with plugins for years are finally in core:

• Tabs block — Organize content into clickable tabbed panels. Perfect for product specs, FAQs, and service comparisons without reaching for a page builder.
• Playlist block — A collection of audio files with an optional waveform visualization. Podcasters and musicians get a native solution with zero third-party dependencies.

Every plugin I can remove from a client site is one less update to manage, one less compatibility risk, and usually a faster page. Core blocks are almost always the better long-term bet.

Collaboration: Notes Grow Up

The Notes feature introduced earlier gets a serious expansion: inline notes on text selections, @mentions with a searchable collaborator list, rich text formatting inside notes, and multiple conversation threads on the same block. If you work with content teams, this starts to feel like the commenting workflow they know from Google Docs — inside WordPress, with no plugin.

Developer Notes Worth Your Attention

A few under-the-hood changes deserve a spot on your pre-upgrade checklist:

• Enforced iframed editor — The post editor now always runs inside an iframe. If you maintain custom blocks still on Block API v2 or lower, update them to v3 now, before August.
• Abilities API expansion — Better querying, filtering, and input validation. This is the foundation AI tooling will increasingly build on, so it’s worth watching even if you’re not using it yet.
• Block Bindings for List Items — Dynamic data sources can now connect to list items without custom code.
• Custom icon registration — Plugin and theme authors can register their own icons for use throughout the block editor.

How I’m Testing the Beta (And How You Should)

First rule: never on production. Here are the easiest paths:

• WordPress Playground — Test 7.1 Beta 1 directly in your browser with zero setup. This is the fastest way to just look at the new features.
• Beta Tester plugin — On a staging or local site, install the WordPress Beta Tester plugin and select the “Bleeding edge” channel with the “Beta/RC Only” stream.
• WP-CLI — wp core update --version=7.1-beta1 on a disposable environment.

My testing checklist for client work: activate your production theme and plugin stack on staging, check custom blocks against the iframed editor, verify any CSS that targets editor styles, and test media uploads with real HEIC files from a phone.

My Verdict So Far

WordPress 7.1 feels like a release built from real-world friction. Responsive styling and interactive states eliminate the most common reasons I write custom CSS on block themes. The media improvements solve actual client complaints. And Tabs plus Playlist will let me retire at least two plugins across most of the sites I manage.

Betas follow weekly through the end of July, with the final release on August 19. If you maintain WordPress sites — yours or clients’ — spend an hour in Playground this week. It’s the cheapest insurance you’ll buy this summer.

Need help preparing your site for WordPress 7.1, or auditing custom blocks before the upgrade? Get in touch — this is exactly the kind of work I do every day.