Convert AVIF to WebP — Free, Fast & Private
Converting AVIF to WebP is a deliberate step backwards, and a sensible one. AVIF compresses better, but WebP has been supported by every major browser for years longer, and it is accepted by a great many tools and platforms that still reject AVIF outright — CMS uploaders, older WordPress installations, image libraries, some email clients, and a good deal of desktop software.
You give up perhaps 20–30% in file size relative to AVIF. You keep most of the advantage over JPEG, which is where the real saving was in the first place. For most practical purposes this is the better trade.
What carries over, and what is quietly dropped
Transparency carries over intact. Both formats use a full 8-bit alpha channel, so cut-outs, logos and soft shadows survive without a matte colour being flattened in.
Colour depth is reduced, and this one matters. AVIF can store 10- or 12-bit colour and HDR metadata. WebP is 8-bit SDR only. If your AVIF came from an HDR source — a modern phone screenshot, a graded photograph, an export from a wide-gamut workflow — converting to WebP tone-maps it down to 8 bits per channel. Most images are unaffected because most images were 8-bit to begin with, but a wide, smooth gradient in a high-bit-depth source can develop visible banding once it is squeezed into 256 levels per channel.
Animation is not carried over. Both formats can technically hold animation, but this converter works frame by frame, so an animated AVIF becomes a single still image.
Where AVIF files come from
Increasingly, from websites. Many sites now serve AVIF to browsers that accept it, so an image saved with “Save image as…” can land on your disk as .avif even though you never asked for it. Newer Android devices can capture in AVIF, and design tools including Squoosh and Figma export it. The usual symptom is an image that will not open in an older desktop application — converting it to WebP, or to JPG for maximum compatibility, resolves it.
Choosing between WebP, JPG and PNG
If the image has transparency, WebP or PNG — JPEG cannot hold an alpha channel and will flatten it onto white. If it is a photograph destined for the web, WebP. If you need it to open in absolutely anything, including a decade-old application or a print service, JPG. If it is line art, a screenshot or a diagram where every pixel should stay exactly as it is, PNG.
Everything runs in your browser through the Canvas API, so your images are never uploaded. There is no server, which is why nothing leaves your device and also why your own hardware does the work. To be exact about the limits rather than vague: the free tier converts 5 files per batch and Pro removes that cap, and each file can be up to 200 MB. There is no daily quota or monthly credit on either tier — drop a batch of AVIFs and take back a ZIP of WebPs.