WordPress 7.1, code-named "Mary Lou" after jazz pianist Mary Lou Williams, launched on August 19, 2026 at WordCamp US in Phoenix. It's a feature release rather than a security patch — the kind of update that changes how site owners actually build pages, not just what's patched under the hood.

A release built in public

WordPress releases are developed entirely in the open, and 7.1 leaned into that harder than most: it welcomed more than 170 first-time contributors and shipped over 1,500 enhancements and fixes by the time it reached general availability. That volume of small, community-driven improvements is easy to overlook next to headline features, but it's a big part of why WordPress core has stayed stable at the scale it operates at.

If you followed the release candidates, RC1 alone landed more than 145 updates since Beta 4 — 57 in the block editor and 88 in core — which gives a sense of how much testing happens before a version like this reaches production sites.

Codename"Mary Lou," after Mary Lou Williams
LaunchedWordCamp US, Phoenix — August 19, 2026
Headline featureResponsive styling in the Site Editor
Also newUnified media editor, Playlist and Tabs blocks

Responsive styling without writing custom CSS

The feature most people will actually touch is responsive styling directly inside the Site Editor. Previously, adjusting how a block looked at a specific screen width meant reaching for custom CSS or a third-party plugin. WordPress 7.1 brings that control into Global Styles and individual block settings, with a live preview at different viewport sizes as you work.

This matters for the same reason we've written about building responsive layouts beyond fixed breakpoints: most real design problems live in the space between the standard mobile and desktop previews, not exactly at them. Being able to nudge spacing, type size, or visibility at an arbitrary width — without a plugin or hand-rolled media query — closes a real gap for site owners who aren't comfortable writing CSS themselves.

A unified media editor

WordPress 7.1 also merges what used to be several separate editing tools — freeform cropping, aspect-ratio cropping, horizontal and vertical flipping, rotation, and metadata editing — into one streamlined media editor. It's a smaller change than responsive styling, but it removes a genuine point of friction for anyone managing a content-heavy site, where resizing and cropping images correctly is a daily task rather than an occasional one.

The practical takeaway

None of this requires an immediate redesign. The value is that routine editing tasks — adjusting layout at a specific width, cropping an image, organizing content into tabs — now take fewer tools and less custom code than they did a version ago.

New blocks and easier collaboration

Two new core blocks ship in this release: a Playlist block for audio content, and a Tabs block for organizing content into tabbed panels without a plugin. WordPress 7.1 also adds notes that can be attached anywhere in content and mentions for collaborative editing, plus an admin bar that stays accessible across the entire dashboard instead of scrolling out of view. Individually these are minor; together they read as WordPress continuing to close the gap with dedicated page builders and collaboration tools, from inside core.

Should you update now?

Unlike the WordPress 7.0.3 security release we covered last month, 7.1 isn't an emergency update — there's no known vulnerability forcing your hand. That said, the same discipline applies: back up the site, check active plugin and theme compatibility, and test the update on staging before pushing it to a production site with custom functionality.

  • Content-heavy sites get the clearest immediate benefit from the unified media editor.
  • Sites edited by non-developers benefit most from responsive styling built into the Site Editor.
  • Sites relying on page-builder plugins for tabs or responsive visibility controls should check for overlap or conflicts before updating.

Where this fits in WordPress's direction

Taken together with recent releases, 7.1 continues a pattern: WordPress core is absorbing capabilities — responsive design controls, media editing, structured content blocks — that used to require a plugin. That's a relevant data point if you're currently weighing WordPress against Webflow for a new project, since a lighter plugin footprint means less ongoing maintenance surface, which is exactly the kind of thing ongoing website care has to account for.

This article is an original summary and analysis based on the official WordPress 7.1 "Mary Lou" release announcement.