JPG to AVIF Converter — Convert JPG to AVIF Online
Halve the size of a JPG photograph at a quality you cannot see the difference in. Drop your file below, pick AVIF as the output format, and move the quality slider down to 75% — at the default 92% an already-compressed JPG barely shrinks at all. Free, private, and entirely in your browser with no upload required.
Drop images here or click to browse
Supports HEIC, WEBP, AVIF, BMP, TIFF, SVG, GIF, ICO, PDF, JPG, PNG
100% Private — Your files never leave your device
All conversion happens directly in your browser using JavaScript. Nothing is uploaded to any server. Your images stay on your computer the entire time.
Why Convert JPG to AVIF?
Because JPEG is a compression scheme from 1992 and AVIF is one from 2019. Both throw away detail the eye is unlikely to miss; AVIF, built on the AV1 video codec, is simply far better at choosing what to throw. Give the two formats the same photograph and the same instruction — make this look about this good — and AVIF does it in a fraction of the bytes.
Taking the 1600 × 2000 photograph from this site's own homepage, decoding it, and re-encoding those exact pixels through the converter above:
- As a fresh JPG at 50% quality: 108.6 KB, measuring 39.5 dB PSNR
- As AVIF at 50% quality: 41.5 KB, measuring 40.1 dB
That is 62% fewer bytes at slightly better measured quality. Repeat that across a page of images and it is the difference between a site that loads instantly on a phone and one that does not.
There is one thing this conversion cannot do, and it is worth being blunt about. Your JPG has already been compressed once. Whatever detail it discarded is gone, and AVIF cannot invent it back — converting a bad JPG gives you a smaller bad image, not a better one. AVIF re-compresses what survives, more efficiently than JPEG could. Keep the JPG if it is the only copy you have.
Quality vs File Size Tradeoffs
This is the section that matters, because the default setting is the wrong one for this conversion. Every number below is the same source photograph — a 259.3 KB JPG, 1600 × 2000 pixels — pushed through the converter on this page and measured, not estimated. PSNR is against the JPG's own decoded pixels, so it measures what the AVIF step costs you, not what the original JPEG compression already did.
| Quality setting | AVIF size | vs the 259.3 KB JPG | PSNR |
|---|---|---|---|
| 50% | 41.5 KB | 84.0% smaller | 40.1 dB |
| 60% | 75.9 KB | 70.7% smaller | 42.8 dB |
| 75% (recommended) | 124.2 KB | 52.1% smaller | 45.5 dB |
| 85% | 189.6 KB | 26.9% smaller | 49.2 dB |
| 92% (default) | 250.9 KB | 3.2% smaller | 52.8 dB |
| 100% | 786.1 KB | 3.0× the size | 67.6 dB |
Read the bottom of that table carefully. At the converter's default 92% you save 3.2%, and at 100% you produce a file three times the size of the JPG you started with. Neither is a bug. AVIF at a high quality target is faithfully reproducing your JPG's pixels including the compression artifacts JPEG baked into them, and coding someone else's blocking and ringing artifacts exactly is expensive. The image is not getting better. The file is just getting bigger.
The saving arrives when you let AVIF discard something. At 75% it halves the file and still measures 45.5 dB against the source — a difference you will not find without flicking between the two at 200% zoom. At 50% it removes 84% of the bytes, which is the right trade for a thumbnail and the wrong one for a hero image.
How much you save depends on how compressed your JPG already was, and the spread is wide. Running the same test over this site's three stock photographs at 75% quality gave savings of 29.2%, 52.1%, and 67.1%. The photo that saved least was the one whose JPG was already squeezed hardest — there was less fat left to trim. At 92%, that same already-squeezed photo came out 10.3% larger as an AVIF than it went in as a JPG. Your own images will land somewhere on that range, so watch the size readout the converter prints next to each file rather than trusting a number from a table.
One row is missing on purpose: there is no lossless AVIF. This converter encodes with 4:2:0 chroma subsampling at every setting, so even the 100% slider position discards colour resolution. If you need every pixel preserved exactly, AVIF is not the format and your JPG was not lossless either — see how to convert images without quality loss.
AVIF Browser Compatibility (2026)
Every current browser displays AVIF. The format took five years to get there — Edge was the last holdout, and only enabled it by default in January 2024 — which is why AVIF still carries a reputation for patchy support that the numbers no longer justify.
| Browser | AVIF since | Released |
|---|---|---|
| Chrome | 85 | August 2020 |
| Opera | 71 | 2020 |
| Firefox | 93 | October 2021 |
| Samsung Internet | 14 | 2021 |
| Safari (macOS and iOS) | 16.4 | March 2023 |
| Edge | 121 | January 2024 |
That adds up to roughly 93% of global browser traffic, according to caniuse.com. Safari 16.1 and 16.2 could open some AVIF files but not all of them, which is why the table dates Safari from the 16.4 release that finished the job. The remaining slice of traffic is mostly old installs that will never update, so serve AVIF from a <picture> element with a JPG fallback and no visitor sees a broken image:
<picture>
<source srcset="photo.avif" type="image/avif">
<img src="photo.jpg" alt="…">
</picture>Browsers are the easy part. Outside them support thins out quickly: Windows needs the AV1 Video Extension installed before Photos will open an AVIF, and plenty of desktop editors still refuse the format outright. If the file has to open on someone else's machine rather than in their browser — a client, a printer, an email attachment — send the JPG. That is the one job JPG still does better than anything else.
How to Convert JPG to AVIF
- Drag your JPG file into the drop zone, or click to browse and select it.
- Choose AVIF from the Output Format menu.
- Drag the Quality slider down to 75%. Leaving it at the default 92% will barely shrink a file that is already a JPG.
- Check the size readout next to the file — it shows exactly how much you saved.
- Download the AVIF — it's saved straight to your device.
You can drop several JPGs at once and take them away together as a ZIP. Nothing is uploaded: the AVIF encoder is compiled to WebAssembly and runs on your own machine, so even confidential photographs never leave your computer. Expect a large image to take a few seconds — our 3.2-megapixel test photo needed between three and eight seconds, because AV1 compression is doing real work.
When to Use AVIF vs WebP vs JPG
All three have a job. Picking by file size alone is how you end up emailing a client a photo they cannot open.
- AVIF — photographs on a website, where the bandwidth saving is largest and the losses are invisible. Best in class when you compress aggressively: 23% smaller than WebP at 50% quality on our test photo, at slightly better measured quality.
- WebP — the same job when you want faster encoding, a few more years of browser support, and a real lossless mode. Encodes in a fraction of AVIF's time. Start at JPG to WebP.
- JPG — anything that leaves the web. Cameras, printers, email, old phones, and desktop software all read it without a plugin. It is the format you send other people.
Treat the AVIF as a derivative, not a replacement: keep the JPG, regenerate the AVIF whenever you need it. For a closer look at how the two modern codecs differ, see WebP vs AVIF — and if you are choosing a format for print, email, or archival rather than the web, our image format by use case guide walks through each of them.
Already have AVIF files that a desktop editor refuses to open? AVIF to JPG handles the return trip.
Frequently Asked Questions
How much smaller is AVIF than JPG?
About half, if you lower the quality slider to 75%. This matters more than the usual answer admits: your JPG is already compressed, so the saving depends entirely on where you set the slider. This site's 1600×2000 test photo is a 259.3 KB JPG. Converting it here produced a 124.2 KB AVIF at 75% quality — 52.1% smaller — but only a 250.9 KB AVIF at the default 92%, which is a saving of just 3.2%. At the default setting you have done a lot of work for almost nothing. Drop the slider to 75%.
Why is my AVIF bigger than the original JPG?
Because you left the quality slider too high. AVIF at 92% is trying to preserve your JPG's pixels almost exactly, including the compression artifacts the JPG already baked in — and reproducing artifacts faithfully is expensive. On one of our test photos the 92% AVIF came out 10.3% larger than the source JPG, and at 100% the AVIF was three times the size of it. AVIF only beats JPG when you let it throw something away. Set the slider to 75% or below.
Does converting JPG to AVIF lose quality?
Yes, twice over. JPG is already lossy, and this converter's AVIF is lossy too, so you are compressing an image that was compressed once before — what the JPG discarded is gone and AVIF cannot bring it back. The good news is that the second step is nearly free at sensible settings: the 75% AVIF of our test photo measured 45.5 dB PSNR against the JPG's own pixels, and the 92% AVIF measured 52.8 dB, both comfortably in the range normally called visually lossless. There is no lossless setting here — even at 100% the encoder subsamples chroma at 4:2:0.
What quality setting should I use for JPG to AVIF?
75% is the sweet spot for a photograph that is already a JPG. It roughly halves the file while measuring 45.5 dB PSNR against the source, which almost nobody can distinguish from the original at normal viewing size. Go down to 50% if the image is a thumbnail or the bandwidth matters more than the detail — that was 84% smaller on our test photo. Going above 85% is usually wasted: you are spending bytes to preserve JPEG artifacts rather than picture.
Is AVIF better than JPG?
For compression, decisively. Re-encoding our test photo's pixels as a fresh JPG at 50% quality gave a 108.6 KB file at 39.5 dB. AVIF at 50% gave 41.5 KB at 40.1 dB — 62% smaller and marginally better measured quality. That gap is the whole reason AVIF exists. JPG still wins on universality: every camera, editor, printer, and 20-year-old device reads it, and AVIF is a web format that plenty of desktop software still refuses to open.
Can I convert JPG to AVIF for free?
Yes. This JPG to AVIF compressor is completely free with no sign-up, watermarks, or file limits. The AVIF encoder is libavif compiled to WebAssembly and it runs inside your browser, so your images are never uploaded to a server.
Which browsers support AVIF in 2026?
All of the current ones. Chrome has supported AVIF since version 85 (August 2020), Opera since 71, Firefox since 93 (October 2021), Samsung Internet since 14, Safari since 16.4 (March 2023), and Edge since 121 (January 2024) — Edge was the last major holdout. Per caniuse.com that works out to roughly 93% of global browser traffic. Desktop software is patchier: Windows needs the AV1 Video Extension before Photos will open an AVIF, and some image editors still cannot.
Should I use AVIF or WebP for my JPGs?
AVIF when you are compressing hard, WebP when you want speed and the widest reach. On our test photo AVIF at 50% quality was 23% smaller than WebP at the same setting, and scored slightly better on PSNR while doing it. But WebP encoded in a fraction of the time and has a few more years of browser support behind it. The safe answer for a website is to serve AVIF with a WebP or JPG fallback in a picture element, so neither choice has to be final.
Why is the first conversion slower than the others?
The AVIF encoder is a 3.3 MB WebAssembly module that downloads the first time you pick AVIF, then stays in memory for the rest of the session. Encoding itself is also genuinely slow work: AVIF uses the AV1 codec's intra-frame compression, which searches much harder for redundancy than JPG does. Our 3.2-megapixel test photo took between three and eight seconds depending on the quality setting. That search is exactly what buys you the small file.