Converting WebP to AVIF gives you the same content in a different container. It runs in your browser: nothing is uploaded, there is no queue and no size limit.
What changes when you convert WebP to AVIF
- Both WebP and AVIF are lossy. Every re-encode discards a little more detail, so convert from the original when you can and keep the quality setting at 85 or above.
When to convert, and when not to
Convert to AVIF for hero images where every kilobyte counts. The best compression available today, with HDR and transparency. Slower to encode.
Keep WebP for images on websites. Smaller than JPG and PNG, keeps transparency and animation. Supported by every current browser.
How to convert WebP to AVIF
- Drop your WebP file on the converter above, or click to choose. Several at once is fine.
- Check the options if you need them: quality, resize, width (px), height (px), with both set, scale (%), never enlarge beyond the original.
- Click Convert, then Download. Nothing was sent anywhere, your browser did the work.
Questions
Is my WebP file uploaded?
No. The conversion runs in your browser with WebAssembly. There is no upload endpoint on this site. You can open your browser's Network tab, or go offline after the page loads, and it still works.
Is there a file size limit?
No fixed one. The limit is your device's memory: a large images file on a phone is slower than on a laptop, but nothing is rejected for being big.
Is it free?
Yes, without an account, without a daily cap and without a watermark. Your device does the computing, so there is no server bill to pass on.
Will the quality drop?
AVIF is lossy, so a little detail is traded for a smaller file. At quality 85 the difference is invisible on photos. For graphics with sharp edges, prefer a lossless format such as PNG.
Can I convert several files at once?
Yes. Drop them all; each is converted in turn and you can download them one by one or as a single ZIP.
Which engine does the conversion?
Image engine (jSquash: mozjpeg, oxipng, libwebp, libavif, libjxl), compiled to WebAssembly and running in your browser, on all your CPU cores when the browser allows it. First use downloads about 1.5 MB, cached afterwards.