AVIF Compressor

How to Compress AVIF Images Online

1. Upload Your AVIF Files: Drag and drop or click "Add Files" to add one or more .avif images. Static and animated AVIF are both accepted, and batch compression is supported in a single session.
2. Pick a Quality Preset or Target Size: Choose Quality Preset (Highest, Very High, High, Medium, Low, Very Low, Lowest) for a one-click setting, set Target file size (%) to shrink to a fraction of the original (e.g., 60% turns a 4 MB photo into roughly 2.4 MB), enter a Specific file size in KB or MB, or move the Image Quality (%) slider for fine control between 1 and 100.
3. Adjust Resolution (Optional): Pick a resolution preset (4320p, 2160p, 1440p, 1080p, 720p, 576p, 480p, 360p, 240p, 144p), scale by File resolution percentage, or enter exact width × height in pixels. Auto Scale keeps the aspect ratio when you change one dimension.
4. Compress and Download: Click Compress. Files are processed in your browser session — no sign-up, no watermark, originals are not retained on the server after the session ends.

Why Compress AVIF?

AVIF (AV1 Image File Format) was published by the Alliance for Open Media in February 2019 and uses the AV1 intra-frame codec inside a HEIF container. At equivalent perceived quality it produces files roughly 50% smaller than JPEG and 20–30% smaller than WebP, but high-resolution AVIFs straight from a camera or design tool can still run several megabytes — large enough to slow page loads or bump against upload caps. Compression is the difference between an AVIF that ships and one that sits in a folder.

• Web performance — Core Web Vitals (LCP in particular) penalize multi-megabyte hero images. Trimming an AVIF from 1.8 MB to 350 KB at Quality 70 typically shaves a full second off LCP on a 4G connection.
• CDN and storage costs — Image CDNs bill on egress bytes; halving the average image weight halves the bill. A 100k-image catalog at 80 KB instead of 200 KB saves ~12 GB of monthly transfer per 1k pageviews.
• Email and messaging caps — Gmail caps single attachments at 25 MB and Outlook.com at 20 MB; compressing a batch of HDR AVIFs from 8 MB each to under 2 MB lets a dozen fit in one message.
• Photography portfolios — AVIF preserves 10- and 12-bit color and HDR (PQ and HLG transfer with BT.2020 primaries), so even at quality 60 a landscape keeps its sky gradient where a JPEG of the same size would band.
• E-commerce product shots — Batch-compress hundreds of product photos to a consistent 100 KB target so the grid loads instantly without per-image manual tuning.
• Stock photo licensing — Buyers download large source files; serving a compressed AVIF preview at 1080p keeps bandwidth low while protecting the full-resolution master.

AVIF vs WebP vs JPEG vs PNG

AVIF Quality Preset Quick Guide

Frequently Asked Questions

Why is my AVIF file already small — is there anything left to compress?

AVIF saved by Photoshop, Affinity, or a phone export often uses a quality preset of 85–90 to be safe, which still leaves headroom. Re-encoding at 70–75 typically removes another 30–50% of the bytes with no visible difference at normal viewing distance. The savings come from coarser quantization on areas the eye doesn't notice (smooth skies, out-of-focus backgrounds), not from cropping or resizing.

Will compressing AVIF lose transparency or HDR data?

No. The compressor preserves the alpha channel and the HDR transfer characteristics (PQ or HLG) embedded in the source. Only the chroma and luma sample precision change with quality — bit depth, color primaries, and alpha stay intact unless you explicitly downsample resolution.

How does AVIF compare to WebP for the same target file size?

AVIF typically wins on photographic content by 20–30% — i.e. the same visual quality fits in 70–80% of the WebP byte count. WebP can edge ahead on lossless graphics with large flat-color regions and on very small icons under 5 KB where AVIF's overhead matters more. For everything in between, AVIF is smaller. See WebP to AVIF if you need to convert direction first, or AVIF to WebP for the reverse fallback.

Why does encoding AVIF take longer than JPEG or WebP?

AVIF uses the AV1 codec's intra-frame mode, which evaluates many more block partitions and prediction modes per pixel than the older DCT in JPEG or VP8 in WebP. A 12-megapixel photo can take 5–30 seconds on a laptop depending on the speed setting, versus tenths of a second for JPEG. The trade-off is one-time cost on encode for permanent savings on every download.

Will every browser display the compressed AVIF?

As of May 2026, AVIF is supported in Chrome 85+, Firefox 93+, Safari 16.4+ (macOS Ventura / iOS 16.4+), and Edge 121+, covering roughly 94% of global users per caniuse. The remaining gap is mostly older iOS, in-app browsers, and locked-down corporate Windows builds. Standard practice is a <picture> element with AVIF first and a WebP or JPEG fallback for those clients — see JPG to AVIF or PNG to AVIF to build the AVIF half of the pair.

Can I batch compress hundreds of AVIFs at once?

Yes. Drop a folder's worth onto the upload area and apply a single Quality Preset or Target file size (%) to all of them. Each file is processed in turn within the same browser session, and you can download them individually or as a zip when finished. There's no per-file sign-up step.

What's the smallest size I can compress an AVIF to without it looking broken?

For a 1080p photograph, ~80–120 KB at Quality 60–65 is usually the floor before banding appears in skies and shadows. Pure graphics (logos, illustrations) can compress to 10–20 KB at the same dimensions because flat color regions encode efficiently. Going below 25% quality on photos tends to produce visible block artifacts that no amount of resolution reduction will hide.

Should I compress, resize, or both?

Both tools work together. If your image is already at display resolution, compress only — quality changes do most of the work. If the source is much larger than where it will be displayed (e.g., a 6000-pixel-wide camera original headed for a 1200-pixel article), resize first using Resize AVIF or set a resolution preset here, then compress. The combined savings are larger than either alone.

Are my files uploaded to a server?

Files are uploaded over HTTPS for processing because AVIF re-encoding requires libavif, which can't run reliably in every browser yet. After your session ends, originals and outputs are deleted — there is no public link, no account requirement, and no watermark added to the output.