Convert WebP to AVIF

Already down to WebP and want to know if AVIF can shrink it further? Drop your files below and find out — the conversion happens entirely on your device, batch or single file.

Drop your images here

or browse files

JPG, PNG, WebP, AVIF, or HEIC (Safari only) · processed locally · never uploaded · paste with Ctrl+V also works

Quality80

Lower quality means a smaller file.

Output format

Convert between JPG, PNG, WebP, and AVIF, or keep the original format.

No images yet. Drop some above to get started.

Why go from WebP to AVIF?

Starting from WebP instead of JPG or PNG means there's less low-hanging fruit left, since WebP already compressed the image once — but AVIF's newer codec typically still finds another 10-20% on top, thanks to more efficient tools for the same job. Transparency carries over either way, since both formats handle it the same way.

How much it's worth doing depends on how hard the original WebP was already compressed: one saved at a moderate quality setting still has real room to shrink further, while one already pushed close to its practical limit won't gain much no matter what you convert it to. It's a quick thing to check either way, since nothing leaves your device to find out.

AVIF vs WebP: Why AVIF Compresses Better →

You're compressing something already compressed

This conversion is different from starting at JPG or PNG, and the difference matters. A WebP has already been through a lossy encoder once: detail was discarded and won't come back. Re-encoding it as AVIF discards a little more, on an image that has less to spare than the original did.

That's not a reason to avoid it, but it does change the question. The gain has to be worth a second generation of loss — and unlike the first conversion, where the savings were dramatic, here you're working on a file that has already given up most of its easy weight.

How much you actually gain

Less than the headline figures suggest, and it depends heavily on the source. Published comparisons using perceptually matched quality commonly put AVIF 20-30% below WebP. On our own test image — deliberately grain-heavy, which is the hardest case — the gap came out closer to 12%. Both numbers are honest; they describe different pictures. Large, smooth, detailed photographs sit at the top of that range and noisy ones at the bottom.

What decides it for you is how hard the WebP was squeezed already. One saved at a moderate quality still has real room to shrink further. One already pushed near its limit has very little, and converting it buys you a few percent in exchange for another lossy pass — which is a bad trade. If you still have the original JPG, PNG or camera file, converting that directly to AVIF beats going through WebP every time.

FAQ

Is this conversion worth doing at all?

It depends on how compressed the WebP already is. If it was saved at a moderate quality there is real room left and AVIF will take a useful bite out of it. If it was already pushed hard, you may gain only a few percent while paying for a second lossy encode. Check the size difference the tool reports before converting a whole batch.

Will the image degrade?

Slightly, and unavoidably — it's a second lossy pass. At a sensible quality setting you won't see it at normal viewing size. What you should avoid is doing this repeatedly, or after the WebP was already compressed aggressively, since each pass works on a thinner image than the last.

Can I convert back to WebP later?

Yes, the AVIF to WebP converter handles that — but understand it's another lossy pass, not an undo. Nothing recovers what was discarded. If you might need the WebP again, keep it rather than planning to reconstruct it.