WordPress 7.1 "Mary Lou": What Actually Changed (August 2026)

WordPress shipped version 7.1, nicknamed “Mary Lou,” on 19 August 2026. It is core WordPress rather than a WooCommerce-specific update, but since WooCommerce runs on top of WordPress, a core release changes the ground every WooCommerce store stands on. Here is what actually changed, dated and sourced from WordPress's own release announcement and independent hosting documentation, and what it means if you are running WooCommerce or weighing it against a hosted platform like Shopify.

A major release, and a well-documented one

7.1 shipped on schedule at WordCamp US, in Phoenix, and WordPress's own release post credits over 800 contributors globally, more than 170 of them first-time contributors, across upward of 1,500 enhancements and fixes. It launched with full translations already complete in more than 20 locales. Those numbers are a reasonable proxy for how active and well-resourced the open-source project remains, and they are worth naming plainly given how often “open source” gets treated as a synonym for under-maintained.

The part that matters most if you spend your day uploading product photos

The most practically useful change for a store owner is not a new block or a design tweak. WordPress 7.1 moves image compression, resizing and thumbnail generation into the browser, using a WebAssembly build of the libvips image library, before an image is ever sent to the server. WordPress's own announcement frames this as reducing the processing load and memory use on the server side, and it pairs with native support for newer image formats – AVIF, HEIC and HDR gain maps – without a plugin. For a WooCommerce catalogue with genuinely large numbers of product photos, faster, lighter uploads and fewer server timeouts during a bulk import is the kind of change that is felt directly rather than read about.

Treat the specific performance framing as WordPress's own description of the change rather than an independently benchmarked number, in the same way any vendor's stated improvement is worth confirming against your own server and your own image sizes before taking it as guaranteed. The direction of the change – work shifted from your server to the visitor's browser at upload time – is the more durable point regardless of the exact figure.

A new media editor, and two new blocks

Alongside the upload changes, 7.1 ships a reworked media editor modal with freeform and fixed-aspect-ratio cropping, flipping, rotation and metadata editing handled directly in the browser, plus an optional GIF-to-video conversion aimed at cutting file size. The Media Library now defaults to infinite scrolling rather than paginated results. Two new blocks arrive as well: a Playlist block for grouping audio with an optional waveform view, and a Tabs block for splitting content into switchable panels – both more relevant to a content-heavy site than to a typical product page, but worth knowing about if your store runs a blog or a guides section on the same WordPress install. Site identity settings – title, tagline, and site icon – also move into their own labelled section of the Site Editor rather than sitting scattered across older screens, a small housekeeping change that mostly matters to whoever set the site up in the first place and now has to find those settings again.

Developers get a couple of additions worth flagging even though they touch nothing a shopper sees directly: a custom icon registration API for extending the block editor's icon set without hacking around the existing one, and expanded styling controls that let blocks declare responsive behaviour and interactive states – hover, focus, active – without hand-written custom CSS. Accessibility work continues in this release too, with a new accessible tooltips API and more consistent screen-reader labelling across admin screens, which is incremental rather than headline news but is the kind of steady work that keeps a fifteen-year-old open-source project from accumulating accessibility debt as it grows.

Collaboration features aimed at teams, not solo shop owners

A meaningful share of 7.1 is aimed at people editing a site together rather than a single owner running a store alone: inline notes with rich text and @mentions, a suggestion mode, and emoji reactions for asynchronous feedback on a draft, plus a persistent admin bar carried across every editor view. None of this changes what a shopper sees on the storefront. If you are the only person who ever touches your WordPress admin, this part of the release is safe to ignore; if you run WooCommerce with a small team editing content and product listings together, it is a genuine, if incremental, improvement to how that work gets coordinated.

What this means if you run WooCommerce today

The standard advice for any WordPress core update applies here without exception: update a staging copy first, confirm your active theme and plugins still render correctly, and place particular attention on checkout and the product edit screen given how directly this release touches image handling. WordPress's own release notes do not flag 7.1 as a breaking change, but “not breaking” in a release announcement is a starting assumption to verify against your own specific combination of theme, page builder and plugins, not a guarantee that covers every installed setup.

If your product images are uploaded through a page builder or a custom import script rather than the standard WordPress media uploader, check specifically whether that path benefits from the new browser-side processing at all – a change implemented in the core media uploader does not automatically extend to every alternative upload route a theme or plugin might use instead. Bulk importers used for large catalogue migrations are the most likely to bypass it entirely, which is worth confirming before you count on faster imports that may not actually apply to your specific workflow.

The wider point: this is what “free” software still asks of you

None of this is a criticism of WordPress – a core release with this many contributors, this much testing, and full translations ready on day one is exactly the kind of maintenance a mature open-source project should be doing. But it is a useful, concrete reminder of something worth keeping in mind whenever WordPress and WooCommerce get described as the free alternative to a hosted platform: someone still has to track core releases, plan a staging update, and re-verify theme and plugin compatibility each time, on a schedule set by the project rather than by your own sales calendar. That work is real even when the software itself costs nothing, and it is exactly the trade-off we walk through in more detail in our Shopify vs WooCommerce cost comparison.

Where this leaves a Shopify-curious store owner

If tracking core releases and re-testing plugin compatibility is not how you want to spend a week in August, that is a fair reason to prefer a hosted platform that absorbs this layer of maintenance for you. Shopify folds platform updates into its subscription rather than handing them to you as a calendar entry, and on the theme side, Kiosk builds numbered Shopify editions with the features stores commonly reach for plugins or apps to get – wishlist, quick view, subscriptions, bundles – included in the theme rather than maintained separately. See the full range at Kiosk, including two free editions if you would rather look at the code first.