WordPress 7.1 lands on 19 August 2026, and for once I don’t think that’s an exaggeration when I say it’s a proper release. Not a “few tweaks and a new default theme” release, mind, a genuine “people have been asking for this for years” release. I sat down and went through it properly for my latest YouTube video, cherry picking 14 features to actually test rather than just read about, and a few of them are worth talking about here on their own.
Responsive styles has finally landed
This is the big one everyone’s been shouting about, and fair enough. For years the answer to “can I make this font smaller on mobile without writing custom CSS” has been a shrug and a trip to the theme.json file, or worse, a plugin. As of 7.1 you can now set styles for tablet and mobile viewports, both through Global Styles and on individual blocks, directly in the editor.
The defaults are sensible too. Mobile kicks in at 480px and below, tablet covers 480px to 782px, and theme authors can override both if their design needs different breakpoints. It covers typography, colour, spacing, borders and layout, which is a genuinely wide net.
Now here’s my honest bit, because I said I’d fact check myself and I meant it. If you’re building on a properly set up block theme with intrinsic, fluid design already baked in (clamp() for type scales, flexible grids, that sort of thing), you’re probably not going to reach for this feature very often. The whole point of intrinsic design is that it adapts without you having to define three separate states. So if that’s how you already work, don’t expect this to scratch much of an itch day to day.
But that’s not a knock on the feature. Plenty of builders don’t work that way, plenty of client sites need a genuine one off override on a specific block for a specific screen size, and for the people who’ve been asking for this since forever, it’s finally here. I’ve written before about dealing with mobile breakpoints the hard way in the block editor, so believe me when I say I’m not sniffy about this landing, I’m just not going to pretend it’s the feature I’ll open every single day.
Hover, focus and active states without touching a stylesheet
This is the one I’m actually most excited about, and I don’t say that lightly. WordPress 7.1 adds a “States” dropdown to block style controls, letting you define different styles for :hover, :focus and :active right there in the editor. No plugin, no custom CSS, no telling a client “yeah that’ll need a developer.”
Why does this matter more than it sounds? Focus states are one of the most overlooked bits of accessibility on the web. A site that looks lovely but gives a keyboard user no visible clue where they are on the page is a site that’s failing a chunk of its visitors, full stop. Baking hover, focus and active states into core, front and centre in the interface rather than buried in a “read the docs” corner, is a proper nudge in the right direction for site builders who’d never think to add them otherwise.
Worth knowing though, at beta stage the full per block state controls are really only fleshed out on the Button block and the Navigation Link block, with everything else getting the states through Global Styles rather than individual block level control. That might widen by the time 7.1 is stable, but if you go looking for it on every block and it’s not quite there yet, that’s why.
The new Tabs block
Tabs has been one of the most requested blocks for years, and it’s finally shipping in core alongside a Playlist block. It does what it says on the tin, lets you organise content into clickable panels instead of dumping everything on the page at once, which is exactly the kind of thing FAQs, product specs and comparison tables have wanted forever.
It’s built following the standard accessible tab pattern, so keyboard navigation and the right ARIA roles are there rather than bolted on as an afterthought, which matters because plenty of the third party tabs plugins over the years have got that bit wrong. I’ll be honest, out of everything in 7.1 this is the block I reckon I’ll use the most. Realistically it’ll end up in most of the sites I build going forward, simply because it’s one of those genuinely useful, unfussy blocks rather than a novelty.
Worth the update
Between responsive styles, proper interactive states and a native Tabs block, 7.1 earns its place as one of the more significant releases in a while, even if not every feature lands the same way for every kind of builder. I went through 14 of the new features properly for my YouTube channel, testing them rather than just describing them, so if you want to see how they actually behave before you update a live site, that’s where to look.
For the full technical breakdown straight from the source, the WordPress 7.1 Source of Truth is worth a read too.
Leave a Reply