Skip to content
ImageConverter

Secure server conversion

WebP to AVIF Converter

Convert WebP images to AVIF for a further reduction in file size, with transparency preserved. Before you do, it is worth knowing that this is the least compelling conversion in the AVIF set: both formats are already modern and efficient, and the gain is real but modest.

Deleted automatically Uploads removed within 30 minutes

Drag and drop your WEBP images here

Add several at once. Each file is processed and then deleted from our server.

Up to 20 MB per file Batch ready

70
Smaller file More detail
Presets:

Higher keeps more detail; lower makes a smaller file. Applies to images you add after changing it.

Step by step

How to convert WEBP to AVIF in 4 steps

  1. Add your WebP files

    Drag them in or click to browse.

  2. Set the quality

    70 by default. Raise it for graphics and logos.

  3. Wait a moment

    AVIF encoding is noticeably slower than WebP.

  4. Compare the sizes

    Compare the sizes reported next to each file, including any that got larger — a useful signal that the original was already efficient.

Format comparison

WEBP vs AVIF

WebP

Lossy or lossless

A web format from Google that can work like JPG or like PNG, usually producing a smaller file than either.

  • Smaller files than JPG or PNG for most images
  • Supported by every current browser
  • Some older desktop software and upload forms still reject it

AVIF (AV1 Image File Format)

Lossy or lossless

The newest widely supported web format, built on the AV1 video codec and designed for the smallest files.

  • Usually the smallest file at a given visual quality
  • Supported by current Chrome, Edge, Firefox and Safari
  • Slow to encode, and unsupported by much older software

Unusually for this site, the most useful thing this page can tell you is that you may not need it.

Most conversions here solve a real problem: a file will not open, a platform rejects a format, a photo is too large to email. This one does not. WebP and AVIF are both modern, both royalty-free, both support transparency and animation, and both are displayed by every current browser. You are not fixing anything — you are trading one good format for a slightly better one.

What you gain: typically 20–30% smaller files. Real, and worth having at scale, but a fraction of what converting from JPG or PNG achieves.

What it costs:

  • A generation of loss. Your WebP is almost certainly already lossy. Re-encoding removes more detail on top of what has already gone.
  • Encoding time. AV1 evaluates far more possibilities than WebP does. Several seconds per large image rather than a fraction of one.
  • Some compatibility. Both are patchy outside the browser, but WebP has a few years' head start and is accepted in more places.

So when is it worth it? When you are serving a lot of images and bandwidth genuinely costs you something; when a specific large image dominates a page's load time; or when you are building an AVIF-with-WebP-fallback setup and need both. For a handful of images on a small site, the honest answer is that the WebP was fine.

Quality

Quality and file size

Because both formats are lossy, this is a second compression pass on an image that has already lost detail. That makes restraint more valuable than aggression here.

  • 85–100 — Preserves the WebP closely, but the file may be no smaller. You are spending space preserving WebP's own artefacts.
  • 60–84 — The useful band. 70 is the default and is where AVIF's advantage actually shows.
  • Below 60 — Two generations of loss start compounding visibly, especially in skies, skin and other smooth gradients.

Convert from the best source you have. If the WebP was itself produced from a JPG or a PNG, converting that original straight to AVIF gives a better result than going through the WebP — one compression pass instead of two.

If your WebP is lossless — common for logos and icons exported from design tools — the saving here can be very large, but so is the risk to edge quality. Use 90 or above, and check the result at full zoom.

If a file comes back larger, the WebP was already compressed harder than the setting you chose. Keep the original; nothing has been gained.

Serving both formats instead of choosing

If this is for a website, you probably do not have to pick. The <picture> element lets each browser take the best format it understands:

<picture>
  <source srcset="photo.avif" type="image/avif">
  <source srcset="photo.webp" type="image/webp">
  <img src="photo.jpg" alt="…">
</picture>

Browsers take the first type they support, so newer ones get the AVIF and everything else falls back cleanly. That is usually a better answer than replacing your WebP files outright, because you keep the broader compatibility as a safety net.

Transparency and animation

Transparency is preserved exactly, including partial transparency. Both formats carry a full alpha channel.

Animation is not. Both formats support animated images, but this tool converts a single frame — an animated WebP becomes a still. To keep motion, leave it as WebP or convert to GIF.

The other direction

If you have AVIF files that something will not open, converting to JPG is the usual fix, or to PNG when transparency matters.

Privacy

What happens to your file

This tool runs on our server, so it works the same on every phone and computer. Your file is uploaded, and this is exactly what happens to it:

  • Stored outside the public web root under a random name, never under your file's name.
  • Processed, with the original upload deleted immediately — whether it succeeded or failed.
  • The result sits behind a signed link that only you receive, which stops working after 20 minutes, and the file is deleted the moment you download it.
  • Anything never collected is deleted automatically within 30 minutes.
  • The image itself is never logged or kept. If a conversion fails, we record the formats involved and the error — not the file.
  • Camera metadata, including any GPS coordinates recording where a photo was taken, is removed from the result. Only the rotation needed to show the image the right way up is kept.

Questions & answers

WebP to AVIF: frequently asked questions

Is converting WebP to AVIF actually worth it?

Sometimes. You gain around 20–30% in file size, which matters at scale or for a large image dominating a page load. But you pay a generation of quality loss and much slower encoding, and both formats already work in every current browser. For a handful of images on a small site, the WebP was fine.

How much smaller will the AVIF be?

Typically 20–30%, which is far less than converting from JPG or PNG because WebP is already efficient. A lossless WebP can shrink much more, though you should use a high quality setting to protect edge detail.

Is transparency preserved?

Yes, exactly, including partial transparency such as soft shadows. Both formats carry a full alpha channel.

What about animated WebP?

The animation is not kept — you get a single frame. Both formats support animation, but this tool converts one frame. Leave the file as WebP, or convert to GIF, if the motion matters.

Should I replace my WebP files with AVIF?

Usually not outright. Serving both with a <picture> element gives modern browsers the smaller AVIF while keeping WebP as a fallback, so you get the saving without losing the broader compatibility.

Why did my file get bigger?

The WebP was compressed harder than the quality you selected, so re-encoding could not remove the same detail twice. Keep the original — that result means it was already efficient.

Keep going

View all tools