WordPress 7.1 Mary Lou: What Changes for Site Owners

WordPress 7.1 is code-named "Mary Lou" after the jazz pianist, arranger and composer Mary Lou Williams, continuing the project's habit of naming major releases after musicians. More than 800 contributors worked on it, over 170 of them for the first time, and the release carries more than 1,500 enhancements and fixes.

The important distinction is that this is a major version, not a maintenance patch. WordPress ships automatic background updates for minor and security releases, so 7.0.1 through 7.0.4 largely installed themselves across the estate earlier this summer. Major versions still need a deliberate decision on most sites. That makes 7.1 something to schedule rather than something that simply arrives, and one change inside it (a fully iframed post editor for every theme) is worth testing on staging before it reaches a live client site.

How it works

The headline change is responsive styling without custom CSS. Until now, controlling how a block looked at different screen sizes meant either writing media queries by hand or relying on whatever breakpoint behaviour a theme happened to provide. In 7.1 those controls sit directly in Global Styles and in individual block settings, alongside the existing show and hide options, and the editor can preview a layout at different viewport widths while you work. Block themes can also define their own mobile and tablet breakpoints in theme.json, overriding the defaults for both responsive styles and block visibility.

Media handling has been rebuilt around the browser rather than the server. Compression, resizing and thumbnail generation now run client side through a WebAssembly build of the libvips image library, which means the PHP memory limit and the upload timeout stop being the two things that break large image uploads. WordPress 7.1 also adds native support for AVIF, HEIC and HDR gain maps, so the formats that modern phones and cameras produce no longer need a conversion step before they will upload. Alongside that, uploads gain progress indicators and automatic retries when a connection drops, GIF to video conversion is available as an opt in, and the Media Library switches to infinite scrolling by default with a per user setting to go back to pagination.

Editing images has been consolidated into a single modal. The Crop button is still the way in, but it now opens a dedicated media editor covering freeform and aspect ratio cropping, horizontal and vertical flipping, fine grained and snap rotation, and metadata editing in one place, replacing the older inline crop tool. The admin bar also now persists across every editor rather than disappearing when you move from the dashboard into the site editor, which removes a long standing inconsistency in how you navigate back out.

Notes, the in editor review feature, becomes considerably more usable. Notes now support rich text and links, accept @mentions that notify the person named, and can be attached to a specific run of text rather than only to a whole block. Multiple conversations can run on the same block, and longer notes collapse so the margin stays readable. Two new blocks ship as well: Playlist, which groups multiple audio tracks with an optional waveform, and Tabs, which organises content into tabbed panels.

Examples and use cases

Consider a client site where the hero heading works at desktop width but wraps awkwardly on a phone. The old fix was a theme child stylesheet, a plugin that injects CSS, or a custom class plus a media query maintained somewhere the client will never find. In 7.1 that is a font size set at the mobile breakpoint from the block's own settings panel, visible to whoever edits the page next. The maintenance burden of a site drops every time a fix moves out of a stylesheet and into content.

Bulk image uploads are the second obvious case. A property or e-commerce client dropping forty photographs straight off a phone into the Media Library has historically been the fastest way to discover that a shared hosting plan has a 256MB PHP memory limit. With resizing and thumbnail generation happening in the browser, the server receives files that are already processed, so the failure mode largely disappears and the origin does noticeably less work during a content push.

The Notes changes matter for anyone running content approval with a client. Being able to highlight a specific claim in a paragraph, leave a note on that phrase with a link to the source, and @mention the person who needs to confirm it is the difference between a review thread that resolves and one that turns into an email chain. For agencies that currently run approvals through Google Docs and then rekey the approved copy into WordPress, this removes some of the reason for the detour.

What this means for UK agencies and site owners

For agencies maintaining a portfolio of WordPress sites, 7.1 is a planning exercise rather than an emergency. There is no security fix driving it, so nothing here forces a same week update, but the iframed post editor change means the update carries more compatibility risk than a routine patch. The sensible order is to update a staging copy, open the post editor on the templates the client actually uses, and confirm that any plugin adding editor styles still behaves before touching production. This is the sort of pass that belongs in a scheduled WordPress maintenance cycle rather than in a rushed afternoon.

For site owners running a single business site, the practical gain is that a handful of things that used to require a developer no longer do. Responsive adjustments, image cropping and rotation, and audio playlists are all now editor level tasks. That does not remove the need for a developer on structural work, but it does shift the boundary, and it is worth knowing where the new boundary sits before paying for a change you could make yourself.

The developer facing additions point at where WordPress is heading. The SVG Icon API is now public, with wp_register_icon_collection(), wp_register_icon() and wp_get_icon() available for registering custom icon sets that then appear throughout the editor. The Abilities API introduced in 6.9 gains a filterable execution lifecycle, custom validation and shared discovery, which is the groundwork for automation and AI tooling built on top of WordPress. A new admin Design System provides semantic design tokens and a ThemeProvider React component so custom admin screens can match core styling. Anyone commissioning WordPress development over the next year will see these surfaces used, and they are documented in the WordPress 7.1 Field Guide.

Practical considerations

The iframed post editor is the change most likely to cause a support ticket. In 7.1 the post editor runs fully iframed for all themes, matching the site editor, so the editing canvas is a separate document from the admin interface. That is the correct architecture and it makes viewport units and media queries behave predictably inside the canvas, but any plugin or theme that assumed the editor shared the admin document, or that enqueued admin styles expecting them to apply to content, can render differently after the update. Page builders, custom block plugins and older editor styling are the usual suspects. Test rather than assume.

Moving image processing into the browser also moves the cost. The server does less, but the visitor's machine does more, so a content editor on an ageing laptop may find a bulk upload feels slower than it did even though the site is now doing the right thing. It also changes what your server logs show, which is worth remembering before concluding from a quiet log that nobody is uploading anything. Finally, the new blocks are worth a moment's thought before they are rolled out across a client site: content authored inside a Tabs or Playlist block is tied to that block, so it is a decision about structure and not only about presentation.

FAQ