0+
June 3, 2026
June 1, 2026
Harvify Image Optimizer helps WordPress administrators convert Media Library images to modern WebP and AVIF formats without running heavy compression work inside PHP.
The plugin scans lightweight attachment metadata first, then your browser converts selected images in a small queue. Images are processed with Web Workers and OffscreenCanvas where available, uploaded back through authenticated WordPress REST API requests, and released from browser memory as each item finishes.
This client-side approach is designed for shared hosting environments where PHP memory limits and execution timeouts can interrupt large image optimization jobs.
Harvify Image Optimizer does not send images to a third-party compression service, load scripts from external CDNs, or track usage. Images are fetched by your browser from your own WordPress site and uploaded back to your own WordPress REST API.
AVIF encoding uses bundled WebAssembly encoder files. The current AVIF path uses the Apache-2.0 licensed @jsquash/avif single-thread encoder, with the earlier bundled wasm-avif encoder retained as a local fallback.
If you want to experiment with AVIF conversion outside your WordPress Media Library first, you can use this browser-based test tool:
/wp-content/plugins/.The source selector can scan JPEG, PNG, WebP, or AVIF attachments. The target selector can write WebP or AVIF, depending on browser, WordPress, and server image metadata support.
Yes. Scan a source format, select only the queue rows you want to process, adjust quality, and start the selected queue. This is recommended before processing a large live media library.
No. This version only replaces Media Library attachment files inside the uploads directory. Theme and plugin asset rewriting is intentionally excluded because it can break updates, checksums, and third-party package expectations.
No. Images are fetched by your browser from your own WordPress site and uploaded back to your WordPress REST API.
AVIF compression is more CPU intensive, especially when using a WebAssembly encoder in the browser. For large batches, start with a small test selection and keep concurrency low.
AVIF output depends on browser WebAssembly support and WordPress/server support for AVIF media metadata. WordPress added AVIF support in version 6.5, but the hosting image library must also support it.
The queue is saved in IndexedDB in the same browser. Open Harvify Image Optimizer again and choose Start Selected / Resume.
No, not by default. The admin must explicitly enable the delete originals option before starting the queue.