Convert AVIF to WebP
Output is typically about 50% larger.
- Files stay on your device
- No upload, no waiting
- No sign-up, no watermark
How it works
Add your AVIF file
Drag a AVIF file onto the drop zone, or click to browse. You can select several at once.
Choose your settings
Adjust the quality slider if you want a smaller file or a sharper result. 80 suits most photographs.
Download the WebP
Conversion runs on your device as soon as each file is added — no upload, no queue. Download each result when it is ready.
Related tools
All image tools- AVIF to JPGOutput is typically roughly 2.3× larger.
- AVIF to PNGOutput is typically roughly 10× larger.
- JPG to WebPOutput is typically about 34% smaller.
- Compress ImageSmaller files, quality you control.
- Resize ImageExact pixel dimensions, aspect ratio kept.
- Crop ImageReframe without losing any sharpness.
Questions
Is it worth serving both AVIF and WebP?
Only if images are a real share of your page weight. A picture element with an AVIF source and a WebP fallback costs a little markup and saves genuine bandwidth on image-heavy pages. For a site with a handful of images, pick WebP alone and spend the effort somewhere that matters more.
Will converting AVIF to WebP make the file smaller?
Usually, yes. A 12-megapixel photo is around 1.4 MB as AVIF and around 2.1 MB as WebP — about 50% larger. Because WebP is lossless the result depends entirely on the image content — flat colour and text compress far better than photographic detail.
Does converting AVIF to WebP lose quality?
A little, by design. AVIF is lossless and WebP is lossy, so some detail is discarded in exchange for a much smaller file. At quality 80–90 the result is visually indistinguishable from the original for photographs. For screenshots, logos or anything with sharp text, stay with a lossless format instead — lossy compression creates visible halos around hard edges.
Is transparency preserved when converting AVIF to WebP?
Yes. Both AVIF and WebP support an alpha channel, so transparent and semi-transparent pixels carry across unchanged — a logo with a cut-out background stays cut out, and soft drop shadows keep their gradient rather than picking up a white halo. Because WebP can compress lossily, a very hard edge against transparency may pick up slight softness at high compression; keep quality at 85 or above for cut-out graphics.
What happens to an animated AVIF?
Only the first frame is converted. Every conversion here decodes one frame onto a canvas and re-encodes it, so the result is always a still image — that applies to WebP as much as to any other target. To shrink an animation while keeping the motion, a video file (MP4 or WebM) is usually around a tenth of the size of the equivalent AVIF, and needs an encoder we do not ship yet.
Is WebP safe to use on a live website?
Yes. Every browser in current use supports it — Chrome since 2014, Firefox since 2019, and Safari since version 14 in 2020. Coverage is above 97% of global traffic. The remaining gap is older desktop software and some print workflows, so keep a JPEG or PNG original if the image also has to leave the web.
About avif to webp
Why people convert AVIF to WebP
A middle ground: broader support than AVIF, much smaller than JPEG or PNG. Usually someone standardising a mixed asset library on a single format.
Reasonable as a fallback inside a picture element alongside the AVIF. If you still have the original the AVIF was made from, encode the WebP from that instead — one lossy generation is better than two.
Worth knowing: The WebP will be noticeably larger than the AVIF at the same visual quality. That is the price of the wider support you are buying.
AVIF and WebP side by side
| AVIF | WebP | |
|---|---|---|
| Full name | AV1 Image File Format | WebP |
| Compression | Lossy or lossless | Lossy or lossless |
| Transparency | Yes — alpha channel | Yes — alpha channel |
| Animation | Yes | Yes, in the format |
| Browser support | Chrome 85+, Firefox 93+, Safari 16.4+ (March 2023), Edge 121+ | All modern browsers — Chrome 32+, Firefox 65+, Safari 14+ (2020), Edge 18+ |
| Typical 12 MP photo | ~1.4 MB | ~2.1 MB |
| Usually used for | Performance-critical web images where every kilobyte counts | Web images where page weight matters and modern browsers are the audience |
On a typical 12-megapixel phone photo, the WebP output comes out about 50% larger than the AVIF original. These are order-of-magnitude figures for one kind of image — your own results will vary a great deal, because flat colour, text and line art behave nothing like photographic detail, and the quality slider moves the figure substantially.
What to watch out for
- Not accepted by some older desktop software and print workflows
- Slightly slower to encode than JPEG
- Larger than AVIF at the same quality
- Animation is lost. Only the first frame is converted — every conversion here decodes a single frame onto a canvas and re-encodes it, so the result is a still image whatever the target format. To shrink an animation and keep the motion, a video file is typically around a tenth of the size of the equivalent AVIF.
About the two formats
AVIF currently produces the smallest files of any widely supported format — commonly half the size of JPEG at the same perceived quality, with excellent handling of gradients and noise. The cost is encoding time, which can be seconds per image rather than milliseconds, and support that only became universal with Safari 16.4 in 2023.
WebP is the pragmatic modern choice for the web: roughly 25–35% smaller than JPEG at comparable quality, with transparency and animation that JPEG lacks, and — since Safari 14 in 2020 — support in every browser that matters. It is the format to reach for when you want smaller pages without worrying about fallbacks.
Other conversions
Everything runs on your device — nothing is uploaded, so there is no size limit, no queue and no copy left on a server afterwards. There is more on how browser-based conversion works if you want the detail. Otherwise, browse every image tool, or convert WebP back to AVIF.