Skip to content
ImageConverter

Secure server conversion

AVIF to WebP Converter

Convert an AVIF image into WebP. This is one of the few conversions people make knowing the file will get bigger — about 44% for a photograph in testing — because WebP opens in far more places. If you are wondering whether that trade is worth it, the answer depends on where the image is going, and it is covered below.

Deleted automatically Uploads removed within 30 minutes

Drag and drop your AVIF images here

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

Up to 20 MB per file Batch ready

85
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 AVIF to WEBP in 3 steps

  1. Add your AVIF file

  2. Keep quality at 85 or so — the AVIF is already compressed once

  3. Download your WebP

Format comparison

AVIF vs WEBP

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

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

Why the file gets bigger

AVIF, based on the AV1 video codec, is simply more efficient than WebP, which is based on the older VP8. Describing the same picture at similar quality takes WebP more bytes. Measured at this page's default setting:

  • A photograph: 24 KB as AVIF → 34 KB as WebP, 44% larger.
  • A simple transparent graphic: 1.7 KB → 3.4 KB, nearly double.

Both are still small files. The growth matters on a page with many images and very little on a single image you are sending somewhere.

Why convert anyway: reach

Every current major browser displays both formats. The difference is history and everything outside the browser:

  • Older devices and browsers. WebP support arrived years earlier, so older phones, tablets and browser versions that cannot display AVIF often can display WebP.
  • Software outside browsers. Image viewers, editors, content management systems, messaging apps and upload forms accept WebP far more often than AVIF.
  • Speed of creating files. WebP encodes much faster than AVIF, which matters to some publishing systems and batch workflows.

A second round of compression

AVIF is lossy and so is WebP here, so converting compresses an already-compressed image again, and some further detail is lost. At the default setting it is hard to see, which is why the default is set fairly high. Keep the AVIF, or better, the original the AVIF was made from.

Quality

Quality and file size

  • 85, the default — keeps the second generation of compression hard to see.
  • 90–100 — for images that will be edited again or viewed closely.
  • Below 70 — shows compression sooner than usual, because the image has already been through AVIF.

What carries across

  • Transparency — kept. WebP has a full alpha channel.
  • Colour depth — reduced. AVIF can hold 10 or 12 bits per channel; WebP holds 8, so a high-bit-depth AVIF is rounded down. Standard images look the same.
  • Animation — not kept. An animated AVIF becomes a single still WebP image.
  • Metadata — removed. Camera and location data are not carried into the WebP.

Several files at once

Add as many AVIF files as you like. Each is converted separately and can be downloaded as soon as it is ready, so you can start on the first while the rest are still converting. Each file can be up to the size shown on the upload area.

When AVIF to WebP makes sense

  • A CMS or platform that accepts WebP uploads but not AVIF.
  • Supporting older devices where WebP displays and AVIF does not.
  • Messaging and social apps with patchy AVIF support.
  • Editing in software that opens WebP but not AVIF.

When not to

If your website already serves AVIF to browsers that support it — often with a JPG or WebP fallback — there is nothing to gain by converting the AVIF itself: you would be making every visitor download a larger file. Converting makes sense when a specific destination rejects AVIF.

Location and camera data

AVIF files can carry the same metadata as camera photos, including where a picture was taken. None of it is carried into the WebP: an AVIF with fifteen metadata fields, including GPS coordinates, was converted to a WebP containing none. That makes this conversion a reasonable last step before publishing an image. Keep the AVIF if you need those details yourself.

Other options

  • AVIF to JPG — the most compatible choice of all for photographs.
  • AVIF to PNG — lossless, keeps transparency, much larger.
  • WebP to AVIF — the reverse, for shrinking WebP images.

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

AVIF to WebP: frequently asked questions

Why is the WebP bigger than my AVIF?

AVIF, based on the AV1 codec, is more efficient than WebP, based on the older VP8. At similar quality WebP needs more bytes: a photograph grew from 24 KB to 34 KB in testing, and a simple graphic nearly doubled.

Then why convert AVIF to WebP?

Reach. WebP support arrived years earlier, so it works on more older devices, and far more software outside browsers — viewers, editors, CMSs, apps and upload forms — accepts WebP than AVIF.

Does it lose quality?

A little. Both formats are lossy here, so the image is compressed a second time. At the default of 85 it is hard to see; keep the AVIF or the original it came from.

Is transparency kept?

Yes. WebP has a full alpha channel, so transparent areas come across exactly.

What happens to an animated AVIF?

It becomes a single still WebP image — the animation is not kept.

What about 10-bit or HDR AVIF images?

WebP stores 8 bits per channel, so higher bit depth is rounded down. Standard images look the same; the extra precision for HDR and very smooth gradients does not survive.

Keep going

View all tools