WordPress 7.1 shipped on August 19, 2026, and its headline change is a real architecture shift: image resizing, format conversion, and thumbnail generation now happen in your visitor’s browser instead of on your server. It also adds two new blocks, lets you style hover and focus states without writing CSS, and improves collaboration through richer Notes. Most sites can update without issue, but the media-processing change is worth understanding before you do.
The Big One: Client-Side Media Processing
Until now, every image you uploaded to WordPress was resized, rotated, and converted into multiple thumbnail sizes entirely on your server — real CPU and memory cost on every single upload. WordPress 7.1 moves that work into the browser using wasm-vips, a WebAssembly build of the libvips image library, running in a background Web Worker so it doesn’t freeze the upload screen.
The catch: full support currently requires Chrome 137+ or Edge 137+. Safari and Firefox don’t yet support the WebAssembly features this needs, so WordPress automatically falls back to the old server-side processing for those browsers — nothing breaks, you just don’t get the performance benefit yet on non-Chromium browsers.
A related addition: animated GIFs are now automatically converted to MP4/WebM video on upload (via a new @wordpress/video-conversion package), which is typically a fraction of the file size of the equivalent GIF.
What Else Shipped in 7.1
| Feature | What it does |
|---|---|
| Interactive state styling | Style :hover, :focus, and :active directly from the block interface — no custom CSS needed |
| Tabs block | A native tabbed-content block, core-built rather than plugin-dependent |
| Playlist block | An audio playlist block with waveform visualization |
| Richer Notes | Expanded commenting/notes for team collaboration on drafts |
| Editor polish | Reorganized command palette, a persistent admin bar across editors, shareable links to specific revisions |
Should You Update Now?
- Take a full backup first — database and files, not just a plugin snapshot, as with any major core update.
- Test the upload flow on staging before production, especially if your team uploads a lot of large images or animated GIFs — confirm the new client-side processing behaves correctly in your team’s actual browsers.
- Don’t worry about Safari/Firefox users — the automatic server-side fallback means visitors and editors on those browsers see no difference in functionality, just no speed-up yet.
- Check any custom code that hooks into image upload/resize functions — a plugin or custom function that assumes server-side processing happens on every upload should be tested against the new client-side path.
We covered a general safe-update process (not specific to any one release) in WordPress Staging Sites: How to Test Changes Safely Before You Publish — the same staging-first approach applies here. If you’re catching up, our rundown of the previous release is in WordPress 7.0 “Armstrong” Is Here.
Frequently Asked Questions
Do I need Chrome to use WordPress 7.1?
No. Every browser can use WordPress 7.1 normally — Chrome and Edge 137+ just get the new faster client-side image processing, while other browsers automatically use the previous server-side method with no loss of functionality.
Will my existing images be affected by the update?
No, client-side processing only applies to new uploads going forward. Images already on your site and already processed into their thumbnail sizes are untouched.
Is WordPress 7.1 safe to update to right away?
For most sites, yes — take a backup and test on staging first if you run custom code touching the media upload process, which is the one area with a real behavior change in this release.
Featured image: original illustration.