Free, in your browser — your image never leaves you. Alpha channel preserved.
or drop the image here
Converting…
RoundCut converts AVIF to WebP entirely in your browser using the platform's native decoder and encoder. The file is never uploaded. Alpha transparency is preserved in the output. Expect the WebP file to be roughly 20 to 25 percent larger than your AVIF source — you convert for compatibility, not for smaller files.
Drop an AVIF file on the upload area (or click to pick one). The conversion runs the moment the file lands — there is no "Convert" button to chase. The browser decodes the AVIF natively, then the platform's WebP encoder produces the result. When it is ready, the stats line shows the input and output size, and the Download button saves the WebP to your device. The whole loop typically takes under a second for most photos on a desktop browser.
WebP at our near-lossless setting is visually indistinguishable from the AVIF source for photographs — PSNR around 44 dB on a typical photo. There is one re-encode step, so the result is technically lossy, but the artifacts are not visible to the naked eye. Graphics with sharp edges, fine text, or hard color transitions may show subtle differences at any quality setting; for those, keep the AVIF. There is no quality slider — the chosen setting is what every conversion uses.
WebP wins on compatibility. WordPress, Shopify, older CMS plugins, social media upload pipelines, and legacy CDN configs all accept WebP today but still reject AVIF in many places. Keep AVIF when you control the delivery end-to-end and want the smallest possible file at a given quality. Switch to WebP when you have to hand the image to a system that does not yet read AVIF. You are not upgrading — you are trading a sliver of file size for the ability to ship the image at all.
Yes. WebP supports an alpha channel, and so does AVIF, so the conversion keeps every transparent pixel intact. This is the key difference from converting AVIF to JPG, where transparency would be flattened to white. PNG-like cutouts, logos with soft edges, UI assets with rounded corners — they all survive the round trip unchanged. The encoder writes a single near-lossless setting for both the RGB and the alpha planes, so the edges of the cutout stay clean and the transparency does not turn muddy.
The conversion runs in the browser's native image engine plus the platform WebP encoder. Nothing is uploaded, nothing is logged, nothing is queued on a server. If you open DevTools and watch the Network panel while you convert, you will see zero outbound image requests. The same code path runs on every browser — there is no server fallback. No account, no signup, no email — you arrive, drop the file, take the WebP, and leave. The file lives only on your device, before and after.
WebP is accepted by older browsers, content management systems like WordPress and Shopify, social media upload pipelines, and legacy CDN configs that still reject AVIF. You already have AVIF for best compression; you need WebP when the system on the other end does not read AVIF yet. The reason is compatibility, not file size.
No — AVIF is typically 20 to 25 percent smaller than WebP at the same visual quality. Converting AVIF to WebP produces a slightly larger file, not a smaller one. If file size is what you are optimizing for and your destination supports AVIF, keep the AVIF. Convert to WebP only when the destination does not accept AVIF.
Yes. Both AVIF and WebP support alpha channels, so transparent pixels in your AVIF are written into the WebP intact. This is different from converting to JPG, where transparency would be flattened to a solid color. Logos, cutouts, and UI assets keep their soft edges and rounded corners after the conversion.
Your file never leaves your browser. The conversion runs entirely on your device using the platform image engine — no upload, no server, no data collection. You can verify it with DevTools open: there are zero outbound image requests during conversion. There is no account and no signup either, so nothing about you is logged.
Minimally. The WebP encoder runs at a near-lossless setting tuned for photographs — PSNR around 44 dB on a typical photo, which is visually indistinguishable from the AVIF source. The re-encode is one lossy step, not double-lossy. Graphics with sharp edges, fine text, or hard color transitions may show subtle differences; for those, keep the AVIF.
Not yet — the current version converts one file at a time. Batch conversion is planned for a later release. For now, run them one after the other — each conversion is fast enough that it is barely a wait, since WebP encode is the quick path on every modern browser.