Image Tools
AVIF Compressor
Tune the most efficient format there is — AVIF re-encoded at your chosen quality, entirely in-browser.
In short
Compress AVIF images online: re-encode the smallest modern format at lower quality presets, with exact savings per file. Client-side and private.
By NaveenKumar T · Updated
Learn: How to Compress Images for the Web (Without Ruining Them)
- Per-image savings shown
- 3 quality presets or a KB target
- Batch compression
Runs entirely in your browser — nothing you paste or open here is uploaded, logged, or stored.How we handle data →
Learn more
Compressing AVIF images, explained
AVIF already sits at the efficient end of image compression, so this tool's job is quality tuning: dropping an archival-quality AVIF to delivery quality, or batch-normalizing a folder to one preset. As everywhere on this site, every card reports its exact before/after sizes — no claimed averages, just your files' numbers.
Encoding runs on libaom — the AV1 reference encoder — compiled to WebAssembly, so it works in every modern browser rather than only the few whose canvas can write AVIF. AV1 compression is computationally heavy by design: expect each image to take noticeably longer than a JPEG or WebP would, with the per-card progress bar showing the work as it happens.
What re-encoding does to AVIF sources
AVIF files arrive from build pipelines, Squoosh-style exporters, image CDNs and newer Android cameras, and increasingly carry 10-bit color, wide gamut or HDR. This compressor decodes to 8-bit sRGB pixels before re-encoding, so an HDR or Display P3 AVIF comes back as a standard-dynamic-range sRGB file — smaller, but flattened. Transparency survives; metadata does not. Size-wise, a quality-90 export typically drops 35–50% at Balanced, while a file already encoded at quality 60 will usually be kept as 'already optimized' at High Quality and gain only modestly at Max. Because AV1 degrades gracefully, Max Compression (50) still looks acceptable for thumbnails where JPG at 50 would not.
Speed is the real constraint. Encoding runs at libaom speed 6 for images up to 2 megapixels and speed 8 above that, single-threaded, so a 24-megapixel file can occupy the tab for a minute or more and the page may stutter until it finishes. Queue a handful of files at a time, or resize delivery images to their display size before compressing — a 1600-pixel-wide AVIF encodes in a few seconds and is what a web page needs anyway. Outputs are named name-compressed.avif. If a file only needs to be a different format rather than smaller, PNG to AVIF and JPG to AVIF handle the conversion; this page is for AVIFs you already have.
Help
Frequently asked questions
Everything you need to know about the AVIF Compressor.
01Will an HDR or 10-bit AVIF survive compression?
An HDR or 10-bit AVIF does not keep that range through compression: the file is decoded to 8-bit sRGB pixels before libaom re-encodes it, so an HDR or Display P3 source comes back as a standard-dynamic-range sRGB file — smaller, but flattened. Transparency survives; metadata does not. Images over 2 megapixels encode at libaom speed 8 instead of 6 to keep the run to seconds rather than minutes.
02Why does AVIF take longer to compress than other formats?
AV1 — the video codec AVIF is built on — spends far more computation searching for savings than JPEG or WebP do; that's exactly where its superior compression comes from. The encoder runs as WebAssembly in your browser, so large images can take a while. The result is worth the wait: AVIF at the same visual quality is usually the smallest file any format can produce.
03Why do large images use a faster encoding mode, and how long should I expect?
Expect seconds per image rather than milliseconds: libaom runs single-threaded in WebAssembly here, and a 12-megapixel photo can take tens of seconds. To keep that manageable, images over 2 megapixels encode at libaom speed 8 instead of 6, trading a few percent of compression for a run that finishes several times faster. The browser tab may feel sluggish while a large image encodes; that's normal. For big batches, downsize first — fewer pixels helps AVIF more than any preset.
Keep working
Related tools
Learn the format
Related guides
How to Compress Images for the Web (Without Ruining Them)
Practical image compression guide: lossy vs lossless, picking the right quality level, why some files won't shrink, and how to compress in your browser.
4 min readGuide · ImagesJPG vs WebP vs AVIF: Which Image Format Should You Use?
JPG, WebP and AVIF compared honestly: file size at equal quality, browser support, transparency and encode speed — plus a simple rule for choosing.
3 min read