Why convert AVIF to JPG?
AVIF is built on the AV1 video codec and it is genuinely excellent — around twice as compact as JPEG at the same visual quality, with proper support for transparency and high dynamic range. The catch is everything else. Modern CDNs now serve AVIF to your browser automatically without telling you, so files land in your downloads folder in a format that older Photoshop, many Windows tools, most office suites, print pipelines and a long list of upload forms simply will not open.
JPG is the opposite trade: mediocre compression, universal acceptance. That makes this conversion the standard rescue move — you are not converting to get a better image, you are converting to get an image that everything can read.
Opens on anything
JPG is accepted by every editor, printer, browser and upload form made in the last thirty years. That is the whole point of converting.
10-bit and HDR files
AVIF is often 10-bit while JPG is 8-bit. Files are read correctly here, but see the note below on what that means for HDR.
Files never leave your device
Decoding happens in your browser tab. Most converters upload your files to a server you know nothing about — this one cannot.
What output size should you expect?
AVIF and HEIC are close cousins in efficiency — both beat JPEG by roughly a factor of two on the same picture. So a faithful JPG is normally larger than the AVIF you started from. Measured on a 1600×1068 AVIF of 168.3 KB:
| Output setting | File size | vs original |
|---|
| PNG (lossless) | 2.26 MB | +1273% |
| JPG quality 95 | 442.8 KB | +163% |
| JPG quality 85 | 258.7 KB | +54% |
| JPG quality 80 | 219.6 KB | +31% |
| JPG quality 75 | 191.2 KB | +14% |
| JPG quality 70 ← default | 173.2 KB | +3% |
| JPG quality 65 | 157.5 KB | −6% |
| WebP quality 80 | 161.2 KB | −4% |
That is why the default here is quality 70 rather than the 85 or 90 most converters ship: it lands within a few percent of the original file size, so the first thing you see is not a file that tripled. You can always push it up, and Match original size will search per file for the setting that lands closest to what you started with.
Two honest limitations
10-bit and HDR AVIF
AVIF commonly stores 10 bits per channel; JPG stores 8. Conversion here goes through an 8-bit canvas, so a high dynamic range AVIF will be tone-mapped down and may look flatter or differently graded than it did in an HDR-aware viewer. For ordinary photos shot in SDR you will not notice. If you specifically need to preserve HDR, keep the AVIF or convert with a desktop tool that supports it.
Transparency
AVIF supports an alpha channel and JPG does not. If your file has transparency and you convert to JPG, those areas become a solid colour. This page checks for transparency as soon as a file is decoded and warns you before you download, rather than letting you discover it later. Switch the output to PNG or WebP to keep it.
FAQ
Why is my JPG bigger than the AVIF I started with?
Because AVIF compresses roughly twice as efficiently as JPEG for the same visual quality, and that is exactly why CDNs serve it. Any faithful JPG has to spend more bytes to store the same picture. Quality 70 brings it back to around +3%; the WebP option actually comes out slightly smaller than the original AVIF.
Is AVIF better than JPG?
For compression, yes — substantially better. For compatibility, no, and it is not close. AVIF needs a recent browser and a recent image editor; JPG needs nothing. The right answer depends on which of those two problems you have.
Does it handle 10-bit AVIF files?
Yes, they decode correctly, including the 10-bit test file used to build this page. What it cannot do is keep the extra bit depth — the output is 8-bit JPG, so HDR files lose their extended range. See the limitations section above.
Will I lose transparency?
Only if you choose JPG, which has no alpha channel at all. This page detects transparency after decoding and warns you with a one-click switch to PNG or WebP, which both preserve it.
Are my files uploaded anywhere?
No. The panel on this page counts the number of outbound requests and the total outbound byte size; converting a file keeps both at zero apart from the one-time decoder download.
Why is the first conversion slower?
On any recent Chrome, Firefox, Edge or Safari your browser decodes AVIF itself and the first conversion is instant. On an older browser this page loads a WebAssembly build of libavif (about 1.2 MB, then cached) so that the file still converts instead of failing.
Is this really free? What's the catch?
Free and unlimited, no account, no email, no watermark. There is no server doing the work, so there is no per-conversion cost to pass on to you.
Is there a file size or count limit?
No artificial limit. Everything is processed on your machine, so the only ceiling is your own memory. Very large batches of full-resolution images will use a lot of RAM.