WordPress 7.1, codenamed "Mary Lou," shipped on August 19, 2026, closing out WordCamp US with the project’s biggest editing update in over a year. The headline changes are responsive styling controls built into the Site Editor, a rebuilt media editor that crops and flips images in the browser instead of on the server, and two new blocks for Playlist and Tabs content, according to the official announcement on WordPress.org.
If you run or maintain WordPress sites, the practical question isn’t whether to eventually update. It’s whether to do it this week or wait a patch cycle, and that depends more on your plugin stack than on the release itself.
What Actually Changed in 7.1
The Site Editor now lets you set how a block looks at different screen sizes directly through block settings or Global Styles, without writing custom CSS or reaching for a third-party plugin to handle breakpoints. That’s been a real gap for anyone building client sites in the block editor, where “make this stack differently on mobile” usually meant a snippet or an add-on.
Media handling gets the bigger structural change. Image cropping, flipping, and metadata editing now happen client-side through WebAssembly before the file ever reaches your server, with support for freeform and aspect-ratio cropping. For hosts and agencies dealing with upload-processing load on shared hosting, that’s a meaningful shift in where the work happens.
The two new blocks are narrower but useful: a Playlist block for grouping audio files with an optional waveform view, and a Tabs block for organizing content into clickable panels without a plugin. The admin bar is also persistent now across every screen in wp-admin, and the Notes feature picked up rich text and @mentions for teams reviewing drafts together.
For Plugin and Theme Developers
Two developer-facing changes are worth flagging separately. The SVG Icon API is now public, so plugins and themes can register their own icon collections instead of shipping icon fonts or inline SVG sprites. The Abilities API also expanded, adding a filterable execution lifecycle and shared discovery aimed at AI and automation tooling that needs to call into WordPress predictably. If you’re building or maintaining custom WordPress plugins, both are worth a look before your next release cycle.
Should You Update Now
Core releases rarely break sites on their own, but 7.1 touches the editor and media pipeline directly, which is exactly where third-party page builders and gallery plugins tend to step on core’s toes. The more responsible move on a production or client site is to update staging first, click through the editor screens you actually use, and confirm your media library and any custom cropping or gallery plugins still behave before pushing to production. WordPress core itself patches fast when something slips through, as it did twice already this month with 7.0.3 and 7.0.4, so there’s little upside in rushing a major feature release onto a live site the same day it ships.
If your team is still running an older 6.x branch, this is also a reasonable point to plan a proper WordPress upgrade and compatibility pass rather than clicking update and hoping, especially if the site carries page builders or older commercial plugins that haven’t been tested against 7.1 yet.
