Convert Images Browser processing Batch + ZIP

Convert JPG to AVIF

Convert JPG photos to AVIF — the most space-efficient mainstream image format — for dramatically smaller files.

Loading tool…

Your images are processed in your browser and are not uploaded to our servers.

How to use JPG to AVIF

  1. Upload JPG, PNG or WebP files.
  2. Check that AVIF is offered in the output list; if it is not, your browser cannot encode it.
  3. Set the quality — AVIF holds up far lower than JPG, so 50–65 is a normal range.
  4. Batch several files and download them together as a ZIP.

About this tool

AVIF is the most space-efficient image format in mainstream use, typically beating JPG by 40–60% at the same visual quality. This tool encodes AVIF locally using your browser’s own encoder, so the option appears only when your browser genuinely supports it — no silent fallback that hands you a mislabelled file.

Recommended settings

Settings we suggest

  • Start at quality 60 and compare; AVIF at 60 often matches JPG at 80.
  • Serve AVIF inside a <picture> element with a WebP or JPG fallback.
  • Encoding is CPU-heavy and runs on your device — expect large batches to take time.

Supported formats

Input: JPEG, PNG, WEBP. Output: AVIF, WEBP, JPEG.

Input formats

JPGPNGWebP

Output formats

AVIFWebPJPG

AVIF output appears only when your browser can encode it.

Quality & file size

Lossy formats (JPEG, WebP, AVIF) trade detail for smaller files as you lower the quality; PNG stays lossless regardless of the slider. The tool always shows the original and result sizes so you can judge the trade-off, and it never recommends a result that is larger than your original as an “optimisation”.

Privacy

Every image is decoded, transformed and re-encoded entirely in your browser using the Canvas API and a Web Worker. Files are never uploaded, are not stored in localStorage, and are cleared from memory when you remove them or close the page.

More detail: how we process images, security and our privacy policy.

Common issues & limitations

  • AVIF output is hidden entirely when the browser cannot encode it.
  • Encoding is much slower than JPG or WebP, particularly on mobile.
  • Converting an already-lossy JPG cannot restore detail it has already lost.
  • All processing happens on your device; nothing is uploaded, so very large batches are limited by your available memory.

Frequently asked questions

How much smaller is AVIF than JPG?

At matching visual quality AVIF is typically 40–60% smaller than JPG, and usually 20–30% smaller than WebP. Gains are largest on photographic content with smooth gradients.

The AVIF option is missing — why?

AVIF output only appears when your browser can actually encode it. Decoding AVIF is near-universal, but encoding is not; Chrome and Firefox on desktop are your best bet.

Should I serve AVIF on my website?

Serve it alongside a fallback rather than on its own. A <picture> element with AVIF first and WebP or JPG after gives modern browsers the small file and everyone else a working image — our website optimizer generates exactly that markup.

Is AVIF encoding slow?

Yes, noticeably slower than JPG or WebP, and it runs on your own device. Large batches take a while; that is the encoder working, not a stalled upload.

Related tools