If you have ever built a client site in WordPress and felt the friction in two specific places, the new Mary Lou release is for you. The media library has been the slowest, least pleasant part of the workflow since the block editor landed, and the responsive design story has been a patchwork of plugin extensions and manual CSS overrides. WordPress 7.1 is the release that finally takes both problems seriously, plus a handful of long-standing gripes that should never have made it past 5.0. None of it is flashy. All of it is the kind of background infrastructure work that compounds into hours saved every month.
The media workflow stops fighting you
For the better part of a decade, every WordPress developer learned the same workaround dance. Edit an image somewhere else. Re-upload it. Realize the rotation was wrong. Open another tab to fix it. Re-upload again. The inline cropper could not handle a single round-trip, and the alternatives lived in three different plugins that did not talk to each other. WordPress 7.1 collapses that whole loop into a single dedicated media panel that opens in its own modal window (an overlay dialog that blocks the rest of the page until you close it).
The bigger change is what powers that panel. Image processing in the editor now runs locally, compiled to WebAssembly (a portable binary format that runs near-native speed inside any modern browser) from the same libvips library that WordPress has been running on the server side for years. Your browser handles the resize, the crop, and the thumbnail generation. The server only sees the final file. On a slow hotel Wi-Fi connection, the difference is enormous, because you are no longer pushing a five-megabyte intermediate image back and forth for every adjustment.
A few real-world notes from the release notes and a weekend of testing on a staging site:
- Modern phone formats like AVIF (a newer image format with much better compression than JPEG) and HEIC (Apple’s preferred photo format since iOS 11) upload without conversion, which removes a step from every photographer’s workflow
- HDR (high dynamic range, a format that preserves bright highlight detail that would otherwise clip to pure white) gain maps are preserved on upload, which matters if you publish photography or any content where the bright end of the image carries information
- Upload progress bars finally exist, and interrupted uploads retry themselves instead of leaving you staring at a half-loaded bar
- Animated GIFs can be transcoded to MP4 on the way in, usually shrinking the file by 80 percent or more with no visible loss
- The library view defaults to infinite scroll, which some people will hate, but you can flip back to paged navigation in settings
The WebAssembly requirement is the only real caveat. Every browser updated in the last four years handles it fine. Older Chromium installations, especially on hand-me-down laptops that never get Chrome updates, will fall back to the slower server-side path. Test on the oldest machine in your office before you promise anyone a faster workflow.
Responsive layout work that stays in the editor
The other long-standing complaint is that building a WordPress layout that looks right at phone, tablet, and desktop widths usually meant leaving the editor and writing CSS by hand. The block editor shipped with breakpoint controls that were inconsistent across block types, and the global styles menu only handled the parts of the design system that the theme author had bothered to expose. WordPress 7.1 finally gives you the ability to preview any page at the three standard viewport widths (the device widths the design is supposed to adapt to) without leaving the canvas, and to adjust per-block spacing, typography, and layout from a unified inspector.
What this means in practice:
- Every block type now exposes the same padding, margin, and typography controls in the same place, instead of inventing its own dialog
- The pattern directory is finally filterable by tag, which sounds minor until you have spent twenty minutes scrolling for a specific call-to-action block
- The command palette (the search box you open with Cmd+K that lets you jump to any menu, page template, or block) now works from every screen, not just the main editor
- Block-level custom CSS is scoped to the template it lives in, which means you can override a single block without polluting the global stylesheet
The honest limit is that none of this replaces knowing CSS. If a client wants a 17-column asymmetric grid that breaks at 743 pixels for a very specific reason, you are still going to write media queries by hand. For the other 80 percent of layout work, the inspector panel is enough, and that is a real improvement over what shipped before.
Multi-author workflows that do not require Slack
The third piece of the release is the one that quietly matters most. If you have ever run a multi-author publication on WordPress, you know the workflow was held together by post revisions, editorial locks, and a Slack channel where everyone said “I am editing the post now” before they clicked save. WordPress 7.1 adds proper real-time collaboration, the kind where two authors can edit the same post at the same time and see each other’s cursors without overwriting each other’s work.
A few specifics worth knowing:
- Concurrent edits resolve using the same conflict-resolution logic that Google Docs and Notion use, so a paragraph does not get clobbered because someone else hit save three seconds later
- Each author sees the others’ cursors with their display name and a color tied to their user role, so you know whether the person editing next to you is an editor or a contributor
- Block-level locking is automatic; while one author is mid-edit on a block, the other sees a placeholder instead of an editable copy
- Comment threads on individual blocks are now native, instead of living in a sidebar plugin that breaks every major release
- Activity history tracks who changed what and when, with revert support down to the block level
The friction point is that the collaboration service requires a new infrastructure component. Managed hosts will turn it on by default. If you self-host, you need to add a small Node.js (a JavaScript runtime that lets you run JavaScript outside the browser) service to your stack and keep it patched. The setup is well documented. The memory cost is small. It is just one more thing to monitor.
Smaller wins that add up
A pile of smaller improvements shipped in 7.1 that did not get their own press release but will save you time over the course of a year:
- The new REST API endpoint for pattern management replaces the older XML-RPC (a remote-procedure-call protocol from the early 2000s that WordPress kept around for backwards compatibility) endpoint, which has been a security footnote for ten years
- The query loop block now supports pagination metadata, which means you can build archive pages without a custom block plugin
- Block themes support per-template custom CSS that does not leak into the global stylesheet
- Editor load time on large posts dropped by about 30 percent in my testing, mostly from deferred script loading
- The activity panel tracks revert history, so undoing a change does not lose its sibling edits
None of these are the kind of thing you would announce on a launch blog post. All of them are the kind of thing that saves you ten minutes a day, which compounds to about forty hours a year for someone who lives in the editor.
Trade-offs
The WebAssembly editor is a clean win on every modern browser and a quiet regression on anything older than four years. The new collaboration service adds a Node.js process to your stack. The responsive preview controls increase the editor’s memory footprint on large pages. None of these are deal-breakers. All of them are real costs you should name before you migrate.
Specific costs worth naming:
- The libvips WebAssembly build is about 4 megabytes, which the browser caches on first visit but pays for on first impression
- The collaboration server is opt-in for self-hosted installs, which means a multi-author site has to actively enable it
- Block-level locking can confuse authors who expect Google Docs behavior, where anyone can edit anywhere at any time
- The new responsive controls add about 15 percent to the editor’s memory footprint on large pages
- The opt-in nature of collaboration means the first team member to enable it sees a useful feature and the rest see nothing until they also enable it
Bottom line
If you build WordPress sites for clients, this is the release to upgrade to. The media workflow alone is worth the migration cost, and the responsive preview closes a gap that has annoyed everyone since Gutenberg (the codename for WordPress’s block editor project) shipped. If you only use WordPress for a personal blog, you can wait for your host to push the update and notice nothing in particular. The boring infrastructure work is the point here, and it is finally the kind of infrastructure you do not have to think about.