AVIF to WebP Converter

AVIF to WebP Converter keeps the picture on this device. The download is offered only when the encoded bytes are WebP. WebP can keep partial transparency. Nothing is uploaded for the conversion.

Use this tool

Drop a file here, or use the picker. The file type is checked from its contents.

Result

The result appears in this panel after you run the tool.

About this tool

The selected AVIF appears under the file control. The result panel stays empty until Convert finishes, then it shows the WebP.

The file signature decides the format. A mismatched filename is ignored.

The download is offered only when the encoded bytes are WebP. WebP can keep partial transparency.

Files larger than 250 MB are refused. Images above 40 million pixels are refused from the header when it states the dimensions. After a successful conversion, suggested tools follow the file that was just written.

How to use it

  1. Choose a AVIF file with the picker, or drop it on the tool.
  2. Convert it. The browser decodes the AVIF and encodes WebP.
  3. Download the WebP, or continue with a suggested edit. The image stays in this browser.

Limitations

A fallback delivery when AVIF was the compatibility problem

Readers who skipped AVIF often still accept WebP

The docs site shipped AVIF and watched older browsers request the fallback. WebP is that fallback, and it can keep partial alpha, so a knockout in the AVIF need not be painted shut. This page therefore has no Background control. Both formats are typically lossy, and WebP quality will spend again whatever the AVIF still held. The source is admitted by sniffing an AVIF signature, never by the filename. A webp suffix on AVIF bytes does not select this destination by itself; you are choosing the destination by using this page.

WebP quality defaults to 0.92 and is forwarded

The range is labeled WebP quality. Its initial value is 0.92, and unlike AVIF’s conditional slider this number is passed when you encode WebP. Lower it only after you look at edges that were already quantized once. Raising it toward the top spends bytes restating AVIF artifacts. There is no probe that disables this particular range. The output must come back as WebP under a sniff. If it does not, you do not get a consolation file of another type.

AVIF stays the primary until the fallback is measured

Keep the AVIF for browsers that use it. The WebP is the alternate, and it should be generated from the AVIF you intend to ship, not from a chain of earlier fallbacks. If the AVIF and the WebP would be the same audience, you are doubling loss for no route. If alpha is the design, confirm the WebP preview still composites on both light and dark canvases. WebP quality is the number that changes the fallback’s cost. The AVIF file remains the one you can still point at as the original delivery. Name the fallback in the markup as an alternate, not as a replacement that lets you delete the AVIF. Measure both files at the display size. If the WebP is not smaller, or the knockout frays, the alternate is not earning its second generation. Older browsers are the audience; everyone else should keep receiving the AVIF you sniffed on the way in.

Privacy

Your file is processed in your browser and is not uploaded to UtilChain for conversion. The file name is not sent to analytics.