Convert WebP to AVIF
The editor above is set to export AVIF at quality 70. Open a WebP and it is re-encoded on your device with libavif; nothing is uploaded. Expect a smaller saving than from a JPG or a PNG — WebP is already a modern format — and read the table below before choosing a higher setting, because above a certain point the AVIF comes out bigger than the file you started with.
The first AVIF export downloads the encoder from this site, about 840 KB, which your browser then keeps.
Is it worth converting? What we measured
Most WebP files you meet were made by a website or an image CDN, at a lossy setting around 75 to 80. To stand in for one, we saved our sample landscape (1920 × 1280) as WebP at quality 80, which made a 423 KB file, then put that file through the editor. For each setting, the table shows the AVIF next to simply re-saving it as WebP:
| Quality | Re-saved as WebP | AVIF | AVIF vs the 423 KB WebP |
|---|---|---|---|
| 60 | 309 KB | 259 KB | 38% smaller |
| 70 | 343 KB | 272 KB | 35% smaller |
| 80 | 405 KB | 331 KB | 21% smaller |
| 90 | 487 KB | 497 KB | 17% larger |
| 100 | 2,297 KB | 1,431 KB | 238% larger |
Three things stand out. Re-saving as WebP at the setting it already had barely changes the size; there is nothing left for the same encoder to find. AVIF, a newer and more thorough encoder, does find more: a third off at quality 70, a fifth at 80. And from 90 upwards the conversion backfires, because the encoder is being asked to preserve the first encoder’s blur and blocking faithfully, and that detail is expensive to store.
So this page starts at 70. Compare the result with the divider, and if you can see a difference in the areas that matter, go to 80 — but not beyond it.
If your WebP is lossless
WebP has a second, lossless mode, used for screenshots, logos and interface graphics; CropShrink writes it when you export WebP at quality 100. Converting one of those is a different decision. We made our 1600 × 922 sample screenshot into a lossless WebP of 1,040 KB; as AVIF at quality 90 it became 213 KB, about a fifth.
That is a large saving, but it changes what the file is. The lossless WebP was a pixel-exact copy, and the AVIF is not: AVIF export here is always lossy for colour, and fine coloured text picks up a faint tint. For a screenshot on a web page that is a good trade. For a file whose pixels must stay exact — a design asset, a diagram someone will zoom into — keep the lossless WebP.
Start from the original if you have it
A lossy WebP has already had detail removed. Converting it to AVIF removes a little more: each encoder discards what it judges you will not notice, and the second one works from the first one’s leftovers rather than the real scene. One round of that is invisible at sensible settings; it is still a loss you do not need to take if a better source exists.
If you have the JPEG or PNG the WebP was made from, convert that instead, using JPG to AVIF or PNG to AVIF. Converting WebP to AVIF is for the times when the WebP is all you have — an image saved from a web page, or a media library that only kept the optimised copies.
Transparency, animation and metadata
- Transparency carries over exactly. WebP and AVIF both have a full alpha channel, and CropShrink stores AVIF’s losslessly, so cut-outs and soft shadows come through unchanged.
- Animated WebP is not supported. The editor works on a single frame, so the AVIF is a still picture, not an animation.
- Metadata is not copied. Any EXIF or XMP inside the WebP, such as camera details or a location, is left behind, which you can confirm with the EXIF tool.
Who can open each format
WebP reached every major browser a couple of years before AVIF did. Safari added WebP in version 14 and AVIF in version 16, so an iPhone still on iOS 14 or 15 shows a WebP but not an AVIF. Edge was last to AVIF, in version 121 at the start of 2024. On an up-to-date browser, both work.
The AVIF vs WebP guide compares the two formats in full. If an older audience matters, serve both: a <picture> element can list the AVIF first and the WebP as the fallback, and each browser takes the first one it understands. Outside browsers, WebP has had a few more years to be adopted, but for image editors, social platforms and upload forms JPEG is still the safe choice.
Questions about converting WebP to AVIF
Is AVIF better than WebP?
It compresses better. From our 423 KB WebP sample, AVIF at quality 70 was 272 KB, where re-saving as WebP gave 343 KB. WebP opens in more places, especially on older Apple devices, and encodes much faster.
Why is my AVIF bigger than the WebP?
The quality is set too high for a file that was already compressed. At 90 our sample grew from 423 KB to 497 KB, and at 100 to 1,431 KB. Stay at 80 or below.
Does converting WebP to AVIF lose quality?
Slightly, because a lossy image is being compressed again. At quality 70 to 80 the difference is very hard to see; check it with the comparison divider. A lossless WebP becomes lossy when converted.
Is my file uploaded to convert it?
No. The AVIF encoder is downloaded to your browser and runs there; the image never leaves your device. The privacy policy shows how to check.
More image tools
Every one of these is the same editor, opened for a different job — and all of them run on your device.
- JPG to AVIFRoughly halve a photo, converted on your device.
- PNG to AVIFShrink screenshots and graphics, transparency intact.
- AVIF vs WebPSize, lossless, speed and support, measured, and when to use which.
- Compress an imageShrink a photo for the web, an email or an upload form.
- Resize an imageChange the pixel dimensions with Lanczos3, Catmull-Rom or Mitchell.
Or start from the full editor, which does all of it at once.