Bulk AVIF Compressor — Local WebAssembly Optimizer
Re-encode AVIF images locally using a genuine WebAssembly AVIF encoder with quality controls and Smart Size Guard.
- No server uploadsImages are processed in your browser.
- Free to use
- No sign-up required
Bulk AVIF Compressor — Local WebAssembly Optimizer workspace
Good images. Less baggage.
Drop your images here, or choose a batch from your device.
Your next batch starts here.
Preview, rename and download. All in one place.
AVIF delivers state-of-the-art compression for high-impact hero photography and modern web apps, and our Bulk AVIF Compressor runs 100% locally on your device using a dedicated WebAssembly AVIF encoder and decoder fallback. Output is locked to .avif at 75% starting quality and Original dimensions so you can test tighter delivery sizes without uploading proprietary visuals to a cloud server. When an already efficient AVIF source does not shrink at your chosen quality and original dimensions, Smart Size Guard automatically retains your original .avif bytes. Use this tool when tuning AVIF asset weight; avoid repeated re-encoding of archival masters.
How local WebAssembly AVIF decoding and encoding work
Many browser-based tools rely solely on standard HTML5 canvas export calls, which often lack native AVIF encoding support and silently fall back to larger PNG or JPEG files. This compressor loads a genuine local WebAssembly AVIF encoder inside a background web worker so your downloads are always real .avif files.
Because AVIF compression analyzes complex coding blocks, the first file in a batch takes a moment to initialize the WebAssembly module, and high-resolution 4K photos require noticeably more CPU time than JPEG or WebP. Subsequent images in the same queue reuse the warm worker automatically.
Balancing AVIF quality settings and Smart Size Guard
AVIF is already highly compact, so an AVIF image saved at moderate quality may not get smaller if re-encoded at 75%. With Original dimensions selected, Smart Size Guard compares the newly encoded .avif byte size against your input file and keeps the original whenever the re-encode offers no byte reduction.
To achieve smaller files on already compact AVIF photography, either lower the quality slider into the 55–68% range and check fine textures in the 100% split preview, or pair compression with a Maximum width limit (such as 1600px or 1200px) so the encoder processes fewer total pixels.
How it works: compress AVIF images in bulk
- Add your .avif files to the browser queue—output stays locked to AVIF at 75% quality and original pixel dimensions.
- Wait briefly while the local WebAssembly AVIF worker processes each image, then inspect byte savings and 100% zoom detail.
- Lower the quality slider or set a maximum width if you need further reduction, click Apply & re-compress, and download your AVIF ZIP.
Local WebAssembly AVIF compression settings and tradeoffs
| Feature | Original AVIF | Compressed AVIF |
|---|---|---|
| Encoding engine | Source .avif image file | Dedicated local WebAssembly AVIF encoder in a web worker |
| Transparency & color | 8-bit or HDR/alpha AVIF source | 8-bit web-pixel AVIF export with alpha transparency preserved |
| Processing speed | Instant file read | CPU-intensive block encoding; worker is reused across the batch |
| Size protection | Already compact AVIF bytes | Smart Size Guard retains original AVIF when same-size encode is no smaller |
Frequently asked questions about bulk AVIF compression
Why does AVIF compression take longer than JPG or WebP compression?
AVIF uses advanced AV1-based intra-frame coding that requires significantly more CPU calculation per megapixel than JPEG or WebP. Because all encoding runs privately inside your browser's WebAssembly worker rather than on a remote server, large batches take a few extra seconds.
Are the compressed downloads verified to be real .avif files?
Yes. Every re-encoded file is produced by our bundled WebAssembly AVIF encoder with the image/avif MIME type—never a renamed PNG or JPEG fallback.
Does compressing an AVIF preserve HDR color data or animation?
When an AVIF is re-encoded through the browser pixel pipeline, it exports an 8-bit still AVIF image (with alpha transparency preserved) and does not retain HDR10/gain-map data, camera EXIF metadata or multi-frame animation sequences.
Why did my AVIF file show 'Kept original' after processing?
Many AVIF files found on the web are already encoded aggressively. When format and dimensions are unchanged and the 75% re-encode is no smaller than the input .avif, Smart Size Guard keeps your original file so you never end up with a larger download.