WebP to AVIF, smaller still. Transparency kept.

Usually, yes — but by less than from JPG or PNG. A WebP image re-encoded as lossy AVIF at quality 80 is typically 20–30% smaller with no visible difference, because AVIF's AV1 codec predicts neighbouring pixels better than WebP's VP8 does — and this tool shows the before and after size honestly for every file, so you can see the saving instead of taking our word for it. Flat graphics with few colours shrink the most, and at quality 100 the AVIF can be larger than the WebP for simple images. If a file comes out bigger, the card says so and you can keep the WebP.

No — this tool's AVIF output is always lossy. The quality slider (50 to 100, default 80) trades file size against detail, and at 80 the result is visually identical to the original for almost every image. Quality 100 is visually near-lossless but not pixel-perfect. There is deliberately no lossless toggle: the vendored encoder's lossless mode produces greyscale files — a colour image comes back without its colour — so offering it would silently destroy your images. If you need every pixel exactly, convert from the original JPG or PNG instead — this tool cannot recover detail the WebP already discarded. Keep your WebP as the master copy and use AVIF as the published version.

Yes. AVIF stores a real alpha channel, so transparent and semi-transparent pixels survive the conversion — smooth edges stay smooth, unlike GIF, which only allows fully opaque or fully gone. The preview shows transparency as a checkerboard so you can see it. Lossy compression can soften very fine semi-transparent detail at low quality, so check the preview for logos with hairline edges. There is no background picker and nothing is flattened onto a background.

Only its first frame converts. An animated WebP carries several frames, but browsers only expose its first frame to a web page, so this tool converts that first frame and says so on the file card instead of silently dropping the motion. AVIF itself can animate, but this tool converts still images only — the vendored encoder produces still images, so there is no animated-AVIF output. If you need the animation, keep the WebP or convert each frame separately.

From the original, when you still have it. WebP to AVIF is lossy-to-lossy: artefacts already baked into the WebP stay in the AVIF, and re-encoding cannot recover detail the first compression discarded. If the WebP is all you have, it still works — quality 80 looks identical to the WebP for almost every image — but never convert an AVIF back to WebP and forward again; every lossy generation loses a little more.

Because AVIF squeezes harder than any other web format. The AV1 encoder searches far more ways to pack each image into fewer bytes, and that search takes time — roughly 5–10 seconds for a large photo on a typical laptop, where the same image becomes a WebP almost instantly. The batch converts one file at a time so the page stays responsive, and each file card shows how long its encode took. The smaller file is the payoff: typically 20–30% smaller than the WebP at the same visual quality.

Conversion is disabled, and the page says so plainly — there is no fallback that produces a different format. Unlike WebP, AVIF cannot be encoded with the browser's built-in canvas encoder: canvas toBlob with image/avif is not reliably available, and Safari cannot encode AVIF at all. Some converters quietly fall back to WebP and hand you a WebP file with an .avif name; this tool never does that. If you see the unavailable banner, try a current version of Chrome, Edge, Firefox or Safari — or use our WebP to PNG converter instead, which works everywhere.

Metadata is dropped on re-encode — which is good for privacy, since a WebP can carry EXIF and XMP data, including location. Colour profiles are not carried over either; the output uses the browser's standard colour handling. WebP is an 8-bit-per-channel format, so there is no 10- or 12-bit colour to carry over — the AVIF output is 8-bit, matching the input. A WebP file can carry an EXIF chunk, but this tool does not read an orientation tag and the decode used here does not apply one, so the image is stored the way its pixels are.

Usually, yes. Every current browser displays AVIF, and Discord, most forums, Slack and WhatsApp accept it — though a few older upload forms and apps still only accept JPG or PNG, so check the destination first. Use the destination presets if the app has an upload size limit: website heroes aim for under 300 KB, blog images under 150 KB, and Discord or forum uploads under 256 KB. The presets aim for the target, they do not guarantee it — the tool reports the size it actually reached. Note the difference between viewing and encoding: the preview needs a browser that displays AVIF, so on a very old browser the preview may stay blank while the downloaded file is perfectly valid.

There is no daily limit and no account. A 25 MB safety cap applies per file and 20 files per batch, because decoding large images in the browser is memory-heavy and AVIF encoding takes a few seconds per image. Most WebPs saved from a phone or the web are well under 5 MB, far below the cap. Very large images also depend on your device's memory — the encoder runs entirely on your device, so a low-memory phone will struggle with a 50-megapixel WebP where a desktop will not.