Turn modern AVIF images into JPG or PNG that every app, printer and older device can open.
Convert JPG to AVIF
Convert JPG photos to AVIF — the most space-efficient mainstream image format — for dramatically smaller files.
Loading tool…
How to use JPG to AVIF
- Choose JPG, PNG or WebP files.
- Check that AVIF is offered in the output list; if it is not, your browser cannot encode it.
- Set the quality — AVIF holds up far lower than JPG, so 50–65 is a normal range.
- Batch several files and download them together as a ZIP.
About this tool
AVIF is the most space-efficient image format in mainstream use, and on photographic content it generally produces a smaller file than JPG at a comparable 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. The quality number is encoder-specific, so an AVIF at 60 is not the same setting as a JPG at 60 — judge it on the preview, not the number.
- 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: JPG, PNG, WebP. Output: AVIF, WebP, JPG.
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 “optimization”.
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 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, so the limits protect your own browser rather than a server: 25 MB per file, 20 files per batch, and 40 megapixels per image.
Frequently asked questions
How much smaller is AVIF than JPG?
AVIF generally produces the smallest file of the three at a comparable quality, and the gap is widest on photographic content with smooth gradients. We do not publish a percentage for it, because we have not run a documented test suite that would justify one — compare the before and after sizes the tool shows for your own image.
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
Guides that explain this
Longer reads on choosing a format and a quality setting, written around the same trade-offs this tool exposes.