How to Convert and Compress Images to AVIF (2026)
Last updated:
Quick Answer
AVIF (AV1 Image File Format) compresses images 40–60% smaller than JPG and 25–35% smaller than WebP at the same visual quality. To compress to AVIF: upload your image to FileCurve, select AVIF as output format, set quality to 60 (equivalent to JPG quality 85). Chrome, Firefox, Safari 16+, and Edge all support AVIF — representing over 90% of browser market share as of 2026.
Step-by-step
- 1
Upload your image (JPG, PNG, WebP, HEIC) to FileCurve Image Compressor.
- 2
Select "AVIF" as the output format.
- 3
Set quality to 60 (AVIF quality scale is 0–100; 60 = JPG quality ~85 equivalent).
- 4
Check the output size vs. your original JPG — expect 40–60% smaller.
- 5
Download the .avif file.
- 6
In your HTML/CSS, use the <picture> element with AVIF as the primary source and JPG as fallback for unsupported browsers.
Expected output
Format
AVIF
Quality setting
AVIF quality 60 (equivalent to JPG quality 85)
Estimated size
40–60% smaller than JPG, 25–35% smaller than WebP at same quality
Why you might need this
- →Next.js/Nuxt websites — use next/image with AVIF format for automatic LCP gains
- →Shopify stores — AVIF product images load 50% faster, improving Core Web Vitals
- →WordPress sites with WP 6.5+ — native AVIF support, huge page speed wins
- →CDN-served image libraries where bandwidth cost reduction matters
- →Web app thumbnails and preview images — AVIF makes thumbnail grids load near-instantly
Troubleshooting
Safari shows a broken image for my AVIF
AVIF requires Safari 16+ (released Sep 2022). Safari 15 does not support AVIF. Add a JPG fallback using the <picture> element.
WordPress does not accept AVIF uploads
WordPress added AVIF support in WP 6.5 (April 2024). Older installs need the "Enable AVIF" plugin or manual mime type registration in functions.php.
AVIF conversion is slow in FileCurve
AVIF encoding is computationally intensive — 3–10× slower than JPG. This is normal. Processing happens in your browser.
My CDN does not serve AVIF with correct content-type
Add "image/avif" MIME type to your CDN or server config. Cloudflare CDN handles this automatically if Polish is enabled.
CMS auto-converts my AVIF back to JPG on upload
Some CMSs convert on upload. Use the CMS's AVIF support settings, or serve AVIF directly via CDN and bypass CMS image handling.
Frequently asked questions
How does AVIF compare to WebP?
AVIF is 25–35% smaller than WebP at the same quality. AVIF also handles HDR images better. WebP has slightly wider browser support (Chrome 23+ vs Chrome 85+ for AVIF) — but as of 2026 both have 90%+ support.
What is AVIF browser support in 2026?
Chrome 85+, Firefox 113+, Safari 16+, Edge 121+. Together these cover ~93% of global browser traffic. Only Internet Explorer (dead) and very old mobile browsers lack support.
When should I use AVIF vs WebP vs JPG?
AVIF: new web projects where you control the stack and need maximum compression. WebP: when you need broader backward compatibility or faster encoding. JPG: when sharing outside the web (email, printing, government portals).
Does AVIF support transparency?
Yes — AVIF supports alpha transparency, making it a viable replacement for PNG as well as JPG.
What quality setting should I use for AVIF?
Quality 50–65 is the sweet spot. Quality 60 gives near-lossless results. Quality 40 is visibly compressed. Quality 80+ gives minimal file size savings over WebP.