Convert WebP to AVIF
One step further in web image compression.
- Private by defaultDeleted within an hour
- Super FastProcess in seconds
- No Sign-upStart instantly
How it works
Add your images
Drag and drop, paste, or pick files. They upload over an encrypted connection.
Pick a quality or a target size
Use the quality slider, or tell it exactly how many KB or MB you need.
Download
Save each file, or grab them all at once as a ZIP.
WebP was the first widely adopted successor to JPEG and PNG; AVIF is the next generation and usually compresses the same picture further. If a site already serves WebP, moving its largest images to AVIF is one of the few remaining ways to cut image weight without changing how the pages look.
There is a catch worth knowing about. A WebP that was saved with lossy compression has already lost detail, and encoding it again as AVIF applies a second round of loss on top of the first. Where the original JPEG, PNG or camera file is still available, convert from that instead; use this page when the WebP is the only copy you have.
Transparency carries over unchanged. Animated WebP files do not: AVIF output here holds a single frame, so only the first frame is kept and the editor tells you when that happens. Gains are also smaller than when starting from JPEG, since WebP is already efficient, and some images barely shrink at all. Files travel over an encrypted connection, are converted on our own servers and are deleted within one hour.
Deciding which images are worth converting
Going from JPEG to WebP is an obvious win. Going from WebP to AVIF is a smaller one, and it pays to be selective. Sort your images by size and look at the top of the list. A banner photo of 250 KB as WebP may come down to 170 or 180 KB as AVIF, and that image is downloaded by every visitor. A 12 KB thumbnail might save 2 KB, which nobody will ever notice.
As a working rule, convert photographs above 50 KB and leave the small stuff. Icons, logos and line graphics in lossless WebP are already near their minimum and are better left alone.
How to limit the damage of a second lossy pass
When the WebP is all you have, three choices keep the result clean. Do not chase the smallest file: this page starts at 55, and going up to 60 or 65 lets the AVIF encoder reproduce the WebP faithfully instead of smoothing it further. Do not resize up, only down or not at all. And compare at full size in the editor before you replace anything on a live site, paying attention to gradients such as skies, where two rounds of compression are most likely to produce visible bands.
What to do with animated WebP
Animations are the one case where this conversion goes backwards, because the AVIF made here holds a single frame. Keep animated files as WebP. If their size is the problem, the WebP compressor on this site re-encodes all frames at a lower quality or a smaller size and keeps the motion. For clips longer than a few seconds, a short muted video file is smaller than either format and plays in every browser.
Frequently asked questions
Is AVIF always smaller than WebP?
Usually, but not always. The gain varies by image and is smaller than when converting from JPEG.
Does converting twice hurt quality?
It can. Re-encoding a lossy WebP adds a second round of loss, so convert from the original file when you have it.
What happens to an animated WebP?
Only the first frame is kept, and the editor shows a notice. Keep animations as WebP or GIF.
Is transparency preserved?
Yes. Transparent and semi-transparent areas are kept.
The AVIF came out larger than my WebP. Why?
The WebP was probably saved at a low quality already. The AVIF then has to spend bytes on describing its artefacts exactly. Lower the quality a little, or keep the WebP; the editor shows both sizes so you can decide.
Can I serve both WebP and AVIF?
Yes, and it is the usual arrangement. List the AVIF first and the WebP second in a picture element. Browsers that read AVIF take it, and the others fall back to WebP.