JPG is the compatibility exit from AVIF
- Reading AVIF
- native — Chromium decodes it with no extra library
- Writing AVIF
- not possible in a browser canvas: ask for image/avif and you get a PNG back
- Extra download on this page
- none
This is the conversion you make when something simply refuses to open an AVIF — an older phone, a print shop, a CMS uploader, a desktop app that has not been updated in years. JPG opens everywhere, and that is the entire reason to pick it. Two costs come with it: any transparency is flattened to white, and the file will almost certainly be larger than the AVIF you started from, because AVIF is the more efficient codec. If the destination can read WebP, that page is the better trade.
We measured it: real file sizes
Settings: page defaults
What the numbers sayThe +2942% on the middle row deserves a careful reading: it is not a statement about JPG being bad, it is a statement about how small the AVIF was. That 1200 × 800 UI capture fits in 1,472 bytes as AVIF. As JPG it costs 43.7 KB — which is almost exactly the 43.5 KB the same image costs when converted from PNG. JPG lands where JPG lands, whatever you feed it. The photo is the one row where JPG looks good (231.6 KB against 288.4 KB from the PNG original), and even that is only because the AVIF had already thrown away detail the JPG encoder no longer has to pay for. Pick this page for maximum compatibility, never for size.
Measured on 2026-07-28 by running these files through this very page in Chromium 151.0.7922.34. Every page uses the same published test files, so the numbers are comparable across converters.Method, and download the test images →
What is AVIF to JPG conversion?
This tool converts AVIF images into the JPG format, entirely in your browser with no upload. AVIF is a modern, highly efficient image format based on the AV1 codec. It offers excellent compression with transparency and HDR support, but is only opened by newer browsers and apps. JPG (JPEG) is a lossy format without transparency that compresses photographs to a small size. It is the most universal format for camera and web photos, at the cost of losing a little quality each time it is saved.
How to use it
- Select or drop in your AVIF image.
- The tool converts it to JPG locally, instantly.
- Click Download to save the JPG file.
When should you convert AVIF to JPG?
AVIF compresses extremely well, but support is still limited outside the newest browsers, so you may need a more compatible format.
Converting AVIF to JPG is worthwhile when you want to shrink the file a lot and do not need transparency — especially for photos, where it saves significant space and is easy to upload or email. Note that JPG drops transparency and can add compression artifacts around sharp text or edges.
AVIF vs JPG: key differences
| Property | AVIF | JPG |
|---|
| Compression | Lossy | Lossy |
| Transparency | Yes | No |
| Best for | Modern web images needing maximum compression | Photographs, camera images, web photos |
Why won't my downloaded .avif file open — convert it to JPG
When you save an image from a newer website, you often end up with an .avif file. AVIF compresses extremely well, but plenty of image viewers, older phones, and many editors or upload forms simply don't recognise it, so a double-click just gives you a "can't open this file" error. Converting to JPG fixes that instantly — almost any device or app can open a JPG. One thing to keep in mind: AVIF is already a lossy format, so converting won't recover any detail or improve quality. Because JPG compresses less efficiently, the resulting file can even end up larger than the original AVIF, which is perfectly normal.
One tool: one row not even doubles, another grows thirtyfold
The photo row runs 122.3 KB → 231.6 KB (+89%) — the only result across every AVIF exit that amounts to roughly a doubling. The reason holds up: JPEG’s discrete cosine transform was designed for continuous-tone photographs, that is its home ground, and it keeps pace. The UI screenshot row is a different world: 1.4 KB → 43.7 KB (+2942%). The number on the left is what matters — that 1200 × 800 screenshot takes just 1,472 bytes as AVIF, smaller than many sites’ favicon. JPEG has no route anywhere near that figure; it has to pay for every flat region. The illustration sits between them: 3.2 KB → 23.5 KB (+626%). So the decision follows content, not format: convert photographs, leave screenshots and flat graphics alone. Worth noting too: JPG has no alpha, so a transparent source arrives on a white fill.
Frequently Asked Questions
Why did my tiny AVIF turn into a file thirty times bigger?
Because the AVIF was extraordinarily small, not because JPG is broken. Our 1200 × 800 UI capture fits into 1,472 bytes as AVIF and costs 43.7 KB as JPG — and notice that the same image costs 43.5 KB when converted from PNG. JPG lands where JPG lands regardless of the source. The photo is the one case where it looks good: 231.6 KB against 288.4 KB from the PNG original.
Are my images uploaded?
No. The conversion runs entirely in your browser using the Canvas API. Your images are never sent to a server or stored, so it is safe for private photos.
Does converting AVIF to JPG reduce quality?
JPG is a lossy format, so the image is compressed based on the quality setting and may lose a little detail. In practice the difference is usually invisible, and you get a much smaller file.
Is transparency preserved?
No. JPG does not support transparency, so transparent areas are filled with white. If you need to keep transparency, convert to PNG or WebP instead.
Can I convert many images at once?
You can convert images one at a time; everything runs locally, so speed depends on your device. For large batches, a desktop browser works best.
