Can WordPress 7.1 Optimize Images Without a Plugin?
Mostly, yes. WordPress 7.1 image optimization without a plugin is now real: the release (August 19, 2026) moves image compression, resizing, and thumbnail generation into your browser, converts iPhone HEIC photos to JPEG on upload, decodes AVIF natively, and preserves HDR gain maps. For routine upload-time optimization, most sites no longer need a dedicated plugin. The trade-off is control: WordPress optimizes to its own defaults, only in supported browsers, and it never touches the full-size original you upload.
Quick answer: Yes, largely. WordPress 7.1's browser-based pipeline (released August 19, 2026) handles upload-time compression, resizing, thumbnails, HEIC-to-JPEG conversion, and native AVIF decoding without a plugin. It uses fixed defaults, works fully only in Chrome and Edge 137+, and leaves your original file's metadata untouched.
Published August 21, 2026 by the Mochify Engineering Team. This quick answer separates what WordPress 7.1's new browser-based pipeline automates from what still requires a dedicated tool.
What WordPress 7.1 does natively
The new pipeline runs in the browser through a WebAssembly build of the libvips image library, so processing no longer hits PHP memory limits or upload timeouts on shared hosting. According to the WordPress 7.1 dev notes, libvips produces JPEGs around 15% smaller than the old server-side pipeline, and the release announcement confirms native handling for AVIF, HEIC, and HDR gain maps.
In practice: HEIC photos are decoded in the browser and uploaded as web-ready JPEG (the HEIC original is kept as a companion file), 10-bit and 12-bit AVIF sources keep their bit depth in generated sizes, and HDR gain-map data survives across every thumbnail.
One important limit: client-side processing currently works in Chrome and Edge 137+ only. Firefox, Safari, and low-memory devices silently fall back to the old server-side processing, so results are not identical for every user who uploads.
What it still leaves to you
WordPress applies its own defaults, not your decisions. JPEG quality stays fixed at 82 unless a developer adds code-level filters, there is no per-image choice of output format or quality in the admin, and the release notes describe nothing for re-optimizing images already in your media library. Scaling still caps large uploads at 2560px rather than the exact dimensions your theme needs.
The original file is also untouched by design. WordPress has never stripped metadata from the full-size original, so an uploaded photo's EXIF data, including GPS location, stays in that file on your server. If that matters for privacy, it needs handling before upload; our EXIF and WordPress SEO Quick Answer covers why.
Where pre-upload optimization still fits
Optimizing before upload gives you what 7.1 does not: exact dimensions, your chosen format and quality, and clean metadata, identical in every browser. Files are streamed into memory on Mochify's servers for processing and wiped immediately, with nothing retained. If your library is full of iPhone photos, start with the HEIC to JPEG converter, and see our guide to fixing next-gen image formats in WordPress for the delivery side that 7.1 still does not solve.
Optimize before you upload
With Mochify you can describe the whole job in plain English, for example: "resize these to 1600px wide, convert to WebP, and strip GPS data."
Open mochify.app →