Add up to 30 JPG images (up to 50 MB each) and convert them to AVIF with libavif at the quality you choose (10 to 100, default 85). You can pick WebP as the output instead. The conversion runs in your browser, AVIF encoding takes longer than other formats, and the files are saved without the original EXIF data.
Convert JPG to AVIF for small files
AVIF (AV1 Image File Format) usually gives the smallest files of the formats browsers support. JPG photos converted to AVIF are typically much smaller than the original and smaller than WebP at similar visual quality, which makes AVIF a good choice for performance-focused websites.
Why AVIF compresses better than WebP and JPG
AVIF uses the intra-frame coding tools of the AV1 video codec. Compared with JPG's fixed 8 × 8 blocks, AV1 uses flexible block sizes up to 64 × 64 for its transforms, many more prediction modes and more efficient entropy coding. On a site with many photos, the smaller files mean noticeably less bandwidth.
Browser support
Current versions of Chrome, Firefox, Safari (16.4 and later) and Edge display AVIF. A common setup is to serve AVIF first, WebP as a fallback for older browsers, and JPG as the last resort, all from one <picture> element.
Encoding time
AVIF takes much more computation to encode than JPG or WebP, so a batch takes noticeably longer, especially on slower devices. It's a one-time cost: every visitor then downloads the smaller file. For images that must be converted on the spot, WebP encodes faster.
Quality settings
At 80 to 85, AVIF output looks the same as the JPG to the eye while being much smaller. For thumbnails and background images, 60 to 70 saves more with little visible loss. Compare the preview with the original before downloading. The output is a standard 8-bit image, the same color depth as a JPG.
When AVIF is the right choice
Choose AVIF when file size matters most and your visitors use current browsers: product galleries, image-heavy landing pages, photography portfolios and large hero images. High-resolution photos benefit the most, because they have the most bytes to save. On slow mobile connections that can make a clear difference in how fast the page appears.
Frequently Asked Questions
Is AVIF better than WebP?
For compression, usually yes: AVIF files are typically smaller than WebP at similar quality. WebP encodes faster and is supported by more older software.
Is AVIF better than JPG?
For file size, clearly: AVIF files are typically much smaller at the same visual quality. JPG still opens everywhere, while AVIF needs a current browser or a fallback.
Does AVIF support transparency?
Yes. AVIF has an alpha channel, like WebP and PNG, which JPG lacks. A converted JPG has no transparent areas, though, because the original didn't have any.
Why does AVIF encoding take longer?
The AV1 codec searches many ways to compress each part of the image, which takes far more computation than JPG or WebP. The time is spent once for smaller files on every download.
Is AVIF ready for production use?
Yes. All current major browsers support it. Serve it with WebP and JPG fallbacks for older browsers.
Can I use AVIF for printing?
It's not a good fit. Print services usually expect JPG, TIFF, PDF or PSD, and many don't accept AVIF. Use AVIF for the web and keep the JPG for printing.