AVIF to WebP: help & limits

Make a WebP copy of a still AVIF when a website or editor accepts WebP but cannot use your AVIF. Your browser must be able to decode that AVIF variant and encode WebP. The preview lets you check the result before downloading, and unsupported files fail locally without being sent to another service.

How to use

1. Choose a still AVIF within the displayed limits.
2. Check the WebP preview for orientation, color and transparent edges.
3. Download the result and keep the AVIF original if you need its source encoding.

Supported files

Still AVIF · Up to 64 MiB · 64 megapixels. One image at a time. Maximum 16,384 pixels per edge and 128 MiB output.

How it works

A bounded container check rejects unsupported AVIF structures and sequences. The browser decodes accepted AVIF into a canvas and encodes lossy WebP at quality 92 out of 100. Output dimensions and format are verified before the download is offered.

Examples

Limitations

• Native AVIF decoding and WebP encoding vary by browser and file variant. An AVIF that another app opens may be rejected here.
• Still images only; AVIF sequences are rejected. HDR, high-bit-depth data, embedded metadata and exact color profiles are not preserved as a guarantee.
• WebP can be larger than an efficient AVIF source. Re-encoding is lossy, and low-memory devices can fail below the 64 MP / 16,384px limits.

Privacy

AVIF checking, decoding and WebP encoding take place on your device. An unsupported browser receives an error; Reqly does not fall back to a remote conversion service.

Common questions