Convert images to AVIF
Convert JPG, PNG or WebP to AVIF in your browser with quality and effort controls. AVIF is often half the size of an equivalent JPEG.
- Runs in your browser
- Files are never uploaded
- Free, no account
Pixel-perfect output. Expect files several times larger than the quality slider produces.
Higher effort spends more CPU searching for a smaller file at the same quality. Above 7 the extra saving is usually under 3% but encoding takes several times longer.
Off keeps the alpha channel. Turn it on to paint a solid background behind transparent pixels.
Metadata is stripped. Re-encoding rebuilds the file from raw pixels, so EXIF — GPS coordinates, camera model, serial number, capture time — and any XMP or IPTC block are dropped. Pixels are written in sRGB.
Nothing leaves this tab. The encoders are WebAssembly builds of libjpeg-turbo (MozJPEG), libpng/oxipng, libwebp and libavif running inside a worker on your machine.
How to convert images to AVIF
- Drop JPG, PNG, WebP, GIF or BMP files onto the box above. The source format is detected from the file's contents, so a wrongly named extension does not matter.
- Set the quality slider. AVIF numbers do not map onto JPEG numbers — quality 50 in AVIF looks roughly like quality 80 in JPEG.
- Set the effort slider if you care about the last few percent. Higher effort means a longer search for a compact encoding at the same visual quality.
- Wait. AVIF is genuinely slow to encode; a large photograph at high effort can take several seconds. The progress bar shows which file is being worked on.
- Download each file, or take the whole batch as a ZIP.
The encoder is libavif with the AOM AV1 encoder, compiled to WebAssembly and run inside a worker thread so the page stays responsive while it grinds. Nothing is uploaded.
Quality and effort: two different dials
These are constantly confused, so it is worth being precise. Quality sets the target — how much detail the encoder is allowed to discard. Effort sets how hard the encoder searches for the cheapest way to hit that target. Raising effort makes the file smaller and the encode slower; it does not make the image look better.
| AVIF quality | Roughly equivalent JPEG | Use for |
|---|---|---|
| 75–85 | q95+ | Near-transparent quality, archival delivery |
| 60–70 | q88–92 | Hero images, photography portfolios |
| 50–60 | q78–85 | The general-purpose default |
| 35–45 | q65–75 | Thumbnails, list images, background textures |
| Below 30 | — | AVIF stays smooth rather than blocky, but detail is clearly gone |
On effort: going from 4 to 6 typically buys 3–6% smaller files for roughly double the time. Going from 6 to 9 buys another 2–3% for several times the time again. Effort 6 is a sensible default; drop to 2–3 when you are converting hundreds of files.
Where AVIF wins and where it does not
- Photographs: AVIF's biggest win. 40–60% smaller than JPEG at matched quality is routine, and it degrades into softness rather than the blocky mess JPEG produces at low bitrates.
- Gradients and flat colour: excellent. AV1's larger transform blocks and directional prediction avoid the banding that plagues 8-bit JPEG.
- Images with transparency: supported, with the alpha plane coded separately.
- Logos, icons and screenshots: often a loss. Lossless WebP or a well-optimised PNG will usually produce a smaller file, faster.
- Very small images: AVIF's container overhead can make a 32 × 32 icon larger as AVIF than as PNG.
Deploying AVIF safely
Chrome, Edge, Firefox, Safari 16+ and all current mobile browsers decode AVIF. Older browsers and a great deal of desktop software do not. The standard pattern is a picture element with AVIF first, WebP second and JPEG as the final source, letting the browser take the first format it understands. Keep your originals — AVIF is a delivery format, and if you ever need to go back, AVIF to JPG and AVIF to PNG will do it locally. For mixed conversions in one pass, use the universal image converter.
Questions
Why is AVIF encoding so slow?
AVIF uses the AV1 video codec’s intra-frame coder, which searches a huge space of block partitions and prediction modes. That search is what buys the file-size win. Lower the effort slider to trade some compression for speed.
What do the quality and effort sliders actually do?
Quality sets how much detail the encoder may discard — AVIF at 50 looks roughly like JPEG at 80. Effort controls how hard it searches for a compact encoding at that quality; it changes size and time, never the visual target.
How much smaller is AVIF than JPEG?
For photographs, 40–60% smaller at matched quality is typical, and AVIF degrades far more gracefully at very low bitrates. For flat graphics with few colours, lossless WebP or PNG can still win.
Can everyone view AVIF?
Chrome, Edge, Firefox, Safari 16+ and current mobile browsers all decode AVIF. Older desktop software often cannot, so serve AVIF through a picture element with a WebP or JPEG fallback rather than replacing the originals.
Why is AVIF encoding slower than JPEG or WebP?
AVIF searches a far larger space of block partitions and prediction modes, which is exactly why it compresses better. It runs on your own CPU here, so a large photo can take several seconds — progress is shown per image.