WordPress 7.1: what actually changes for site owners

What is interactive states styling?

It lets you style hover, focus and active states from the editor interface rather than writing CSS. Pick a button, set what it looks like when someone hovers it, done.

This sounds small and is not. Until now, any client who wanted a button to change colour on hover needed either a developer or a page builder that bolted its own styling system on top. Both options add cost, and the second adds weight to every page.

The practical effect for anyone handing a site to a non-technical team: fewer support tickets for changes that were never really development work.

Why does client-side image resizing matter?

Because it moves the work from your server to the visitor's browser, before the file is ever uploaded.

The old behaviour is familiar to anyone who has run a WordPress site: someone uploads a photo straight off a phone, the server tries to generate a dozen resized versions, and on cheap shared hosting it runs out of memory and fails. The upload appears to hang. The client calls you.

Doing the resize in the browser means the server receives a file that is already the right size. Less memory, faster uploads, and one entire category of support call that stops happening.

This is the change most likely to save you real time on client sites. It is also the least exciting to demo, which is why most coverage of 7.1 leads with the new blocks instead.

What are the new blocks?

Two: Tabs and Playlist. Tabs does what you would expect and removes a reason to install a plugin. Playlist handles audio with a waveform visualisation.

Tabs is the more useful of the pair for most business sites. Tabbed content has been a plugin dependency for years, and every plugin you can remove is one fewer thing to update, one fewer security surface, and one fewer thing that breaks during a core upgrade.

What changed in the editor?

A reorganised command palette, an admin bar that persists across editors rather than vanishing, and shareable links to specific revisions.

That last one is quietly useful when working with clients. Being able to send a link to exactly the version you mean, rather than describing it, removes a surprising amount of back and forth.

The Notes feature also gains suggestion mode and emoji reactions, which makes asynchronous review feel closer to a document editor than a comment box.

Should you update straight away?

For most sites, yes, after the usual caution. 7.1 is additive rather than structural — nothing here rearranges how themes or blocks fundamentally work, which is what makes major releases risky.

The standard process still applies: update on staging, click through your key pages and your checkout if you have one, then update production. If you are on a care plan, this is exactly the sort of thing it exists to handle.