AVIF to WebP Converter

AVIF to WebP, compatible everywhere. Nothing ever uploads.

Drop AVIF files below — get WebP images back, accepted almost everywhere, with transparency kept. Converted entirely on your device.

  • Your file data never leaves the device
  • Lossless or lossy — your choice
  • Batch up to 20 files
  • Works offline after load

Convert AVIF to WebP

Add your AVIF files

Drag & drop AVIF files here

or browse your files · you can also paste from clipboard (Ctrl+V)

Loading the WebP encoder…

    No files yet. Everything stays on this device. Downloads start instantly.

    Privacy you can verify, not just trust

    Most online AVIF converters upload your images to their servers first — and some keep a download link live for 30 days. This one can't: your browser decodes AVIF natively and the WebP encoder (libwebp, compiled to WebAssembly) runs entirely in your browser. Your file data never leaves the device — the only third-party requests are the site's own analytics, which count page views — and it uploads nothing, ever. The encoder file is served from this site, not fetched from anywhere else, and there is no file fetched after load for the conversion itself. Don't take our word for it:

    New cross-origin requests during use: 0
    1. Press F12 to open developer tools, then the Network tab.
    2. Convert any AVIF above. Watch: apart from the site's analytics, nothing new is requested — no uploads, and no file data ever leaves your device.
    3. Extra credit: disconnect your internet after this page loads — conversion still works.

    How to convert AVIF to WebP without uploading it

    Every "free" online AVIF converter you've used uploads your images to a company server, converts them there, and — in several documented cases — keeps a copy or a live download link for days. For personal photos, screenshots, logos, and anything you wouldn't post publicly, that's an unnecessary risk. The safer approach is to convert the file where it already is: on your own device.

    This tool does exactly that. When you drop an AVIF here, your browser:

    1. Decodes the AVIF natively — every modern browser includes an AVIF decoder, so there is no decoder file to download and no waiting for a library to load. Animated AVIF files decode to their first frame only.
    2. Reads the image's orientation data and stores the output upright, so a portrait image doesn't come back sideways.
    3. Resizes it to the width you picked (800 px by default), keeping the aspect ratio and the alpha channel — transparency is never flattened onto a background.
    4. Encodes it as WebP with libwebp, the reference WebP encoder, running as WebAssembly in your browser — lossy at the quality you pick, or truly lossless with the Lossless toggle on. Your original file is never modified.

    Lossy or lossless — which should you pick?

    Pick lossy (the default, quality 85) when the image is going on a website, into a blog post, or onto Discord or a forum: it is the small file that loads fast, and at quality 85 it looks identical to the original for almost every image. Pick lossless when every pixel has to survive exactly — a logo master, a screenshot you will edit further, or an icon with razor-sharp edges. Lossless files are bigger, sometimes bigger than the AVIF for photos, because lossless cannot throw detail away. Either way, keep the AVIF as your master copy and publish the WebP.

    Why is WebP bigger than AVIF?

    AVIF is built on the AV1 video codec, a newer and much stronger compressor than WebP's VP8-era design, so for the same quality AVIF files are usually noticeably smaller. WebP at quality 85 is typically 25–35% smaller than the same image saved as PNG — but that saving is measured against PNG, not against AVIF, and it is typical, never a guarantee. Converting AVIF to WebP is a compatibility trade, not a size win: you accept a larger file so the image opens where AVIF does not. If the destination accepts AVIF, keep the AVIF.

    Why convert at all if AVIF is smaller?

    Because not everything accepts AVIF yet. Some older browsers, image editors, content management systems and upload forms still reject AVIF files outright, while WebP is accepted almost everywhere a modern image format is expected. Converting the copies you publish or share — and keeping the AVIF as the master — gets the image seen without re-shooting or re-exporting it. If the destination has a size limit, pick a destination preset and the converter will aim for it: website heroes aim for under 300 KB, blog images under 150 KB, Discord or forum uploads under 256 KB.

    Honest limitations

    Lossy by default

    Unless Lossless is on, the output discards some detail. Quality 85 is visually identical to the original for most images, but quality 100 is near-lossless, not pixel-perfect. Keep the AVIF as your master copy.

    WebP is usually larger than the AVIF

    AVIF is the better compressor, so the WebP usually comes out bigger than the AVIF it came from — even at quality 85. That is expected, not a defect: you converted for compatibility. The card shows both sizes honestly.

    Animated AVIF is first frame only

    Browsers decode only the first frame of an animated AVIF for web pages. This tool converts that frame and says so plainly on the file card. WebP itself can animate, but this tool converts still images only.

    10/12-bit AVIF is tone-mapped to 8-bit

    AVIF can store 10-bit or 12-bit colour, but the browser canvas that feeds the encoder stores 8 bits per channel, so deep-colour AVIFs are tone-mapped down to 8-bit. For most photos the difference is invisible; for smooth gradients it can show banding.

    Metadata is stripped

    Camera metadata (EXIF, including location) is dropped on re-encode, and 10-bit and 12-bit AVIF files are tone-mapped down to 8-bit. Orientation is preserved — the output is stored upright.

    Very large images depend on your device

    The encoder runs entirely on your device, so a 50-megapixel AVIF needs hundreds of megabytes of memory while it converts. A desktop handles that; a low-memory phone may not. Files over 25 MB are refused outright.

    Frequently asked questions

    Is WebP smaller than AVIF?

    No — usually the opposite. AVIF is the better compressor, so the same image as WebP is typically larger than the AVIF it came from, even at quality 85. You convert AVIF to WebP for compatibility, not for size: some older browsers, apps and upload forms still do not accept AVIF, while WebP works almost everywhere. At quality 85, WebP is typically 25–35% smaller than the same image saved as PNG, but that saving is against PNG, not against AVIF — and it is typical, never a guarantee. This tool shows the before and after size honestly for every file, so you can see the real result instead of taking our word for it.

    Is the WebP output lossless?

    Only when the Lossless toggle is on. With it on, the encoder is libwebp's true lossless mode, which stores every pixel exactly — a lossless WebP decodes back to the identical image. With it off (the default), the output is lossy WebP at the quality you pick: quality 85 looks identical to the original for most images, and quality 100 is visually near-lossless but not pixel-perfect. Keep your AVIF as the master copy and use WebP as the published version.

    Will my AVIF's transparency survive as WebP?

    Yes. WebP 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. Transparency is preserved in both lossy and lossless mode, though lossy mode can soften very fine semi-transparent detail at low quality.

    Will the animation in my AVIF survive as a WebP?

    No. An animated AVIF 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. WebP itself can animate, but this tool converts still images only. If you need an animated WebP, convert each frame separately and combine them with an animation tool.

    What happens to transparency and metadata?

    Transparency is preserved — WebP has a full alpha channel, so see-through areas stay see-through. EXIF metadata, including location, is dropped on re-encode. 10-bit and 12-bit AVIF files are tone-mapped down to 8-bit, because the browser canvas that feeds the encoder stores 8 bits per channel. Orientation is preserved — the output is stored upright.

    Why convert AVIF to WebP instead of keeping the AVIF?

    AVIF compresses better than WebP, so on size alone you should keep the AVIF. The reason to convert is compatibility: AVIF is still not accepted by some older browsers, image editors, content management systems and upload forms, while WebP is accepted almost everywhere a modern image format is expected. Convert the copies you need to share or publish, and keep the AVIF as your master copy. If the destination accepts AVIF, do not convert at all.

    Can I share the WebP on Discord, a forum or by email?

    Usually, yes. Discord, most forums, Slack, WhatsApp and every modern browser display WebP inline, and email clients are catching up — 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.

    Is there a file size or daily limit?

    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. Most AVIFs saved from 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 AVIF where a desktop will not.