On August 19, 2026, WordPress shipped version 7.1, code-named "Mary Lou" after the jazz pianist Mary Lou Williams. It landed on the last day of WordCamp US in Phoenix, which is either great event planning or a cruel joke for the release team. Either way, the update is live, and if you manage a WordPress site, there are a few things in here that will genuinely change how you build pages.
The headline feature is responsive block styling baked directly into the Site Editor. For years, the workaround for making blocks look right on mobile was custom CSS media queries, a responsive plugin, or just hoping the theme handled it. WordPress 7.1 kills that workaround. You can now set how any block looks at different screen sizes from Global Styles or individual block settings, and preview the changes at different viewport widths as you work. Block themes can also define custom mobile and tablet breakpoints in theme.json, overriding the defaults. If you have ever written @media (max-width: 768px) inside a WordPress site, this update is for you.
The admin bar follows you everywhere
This one sounds small until you use it. The WordPress admin bar now stays visible across every editor — post editor, site editor, template editor, all of it. Previously, the admin bar would disappear the moment you entered certain editing contexts, which meant losing quick access to the dashboard, your profile, and plugin-added shortcuts. Now it sticks around. There are also some visual polish updates to the bar itself. It is a quality-of-life change that makes the whole admin feel less fragmented.
A real media editor
The old inline cropping tool has been replaced with a proper media editor modal. It handles freeform and aspect-ratio cropping, horizontal and vertical flipping, fine-grained rotation with snap controls, and metadata editing — all in one place. The Crop button still works the way you expect; it just opens something much more capable now.
On top of that, image compression, resizing, and thumbnail generation now happen in the browser instead of on the server. That means fewer PHP memory limit errors, fewer upload timeouts, and smaller file sizes. WordPress 7.1 also adds native support for AVIF, HEIC, and HDR gain maps — the formats your phone is already producing but WordPress previously could not handle without a plugin.
Notes get useful
Notes in the block editor were already a thing, but they were limited. You could leave a comment on a block, and that was about it. WordPress 7.1 expands Notes significantly. You can now leave a note on a specific piece of text within a block, not just the block itself. Notes support rich text — bold, italic, code, links — and you can type @ to mention a collaborator and trigger a notification. Multiple conversations can happen on the same block, and longer notes collapse to keep the margin clean. If you use WordPress for any kind of editorial workflow or client review, this is the feature that makes Notes actually worth using.
Two new blocks and a custom icon API
WordPress 7.1 adds a Playlist block for grouping multiple audio tracks with optional waveform visualization, and a Tabs block for organizing content into tabbed panels. The Tabs block is the one most people will reach for immediately — it is a clean way to present related information without dumping everything onto the page at once.
For developers, the new SVG Icon API lets you register custom icon collections that show up alongside the built-in icon library in the editor. If you have been shipping custom icon sets through plugins or themes, this gives you a proper, supported way to integrate them.
Interactive button styles
Button blocks now support hover, focus, and active state styling directly in the editor. You can set styles for a single button or apply them across all buttons site-wide. This is another one of those features that previously required custom CSS or a block library plugin, and now it just works.
The browser extension
One more thing worth mentioning: on August 13, WordPress released an official browser extension for Chrome and Safari. It hides the admin bar on sites you choose while keeping the shortcuts accessible in the browser toolbar, shows whether the current site runs WordPress, and includes developer tools like block boundary overlays, phone-sized preview windows, and cache-busting reloads. It is open source, stores everything locally, and sends nothing to external servers. If the new admin bar in 7.1 is not your thing, the extension gives you another option.
What to do right now
If you are running WordPress 7.0.x, your site should have auto-updated already — there were two security releases in the past month (7.0.2 on July 17 and 7.0.3 on August 6) that triggered forced updates for affected versions. If you are still on an older version, update before you do anything else.
For 7.1 specifically, update your site, open the Site Editor, and try setting responsive styles on a block. It is the kind of feature that makes you wonder how you ever worked without it. Then go check the new media editor on an image — the browser-side compression alone is worth the upgrade.
If you maintain plugins or themes, test against 7.1 now. The always-iframed post editor, the moved list table row headers, and the new Abilities API updates could all affect your code. The Field Guide has the full breakdown.
WordPress 7.1 is not a flashy release. It does not reinvent the editor or overhaul the admin. What it does is remove a dozen small friction points that have been bothering people for years, and it adds a few features that should have been there from the start. That is exactly the kind of release that makes a platform better.
Sources: