Convert AVIF to JPG — what it is, why sites serve it, and the legacy-tool problem

The short version

1. Drop the .avif on the converter. Single file or folder. Runs in-browser; the file doesn't upload.
2. Leave quality at 92. AVIF sources are typically saved at a higher-quality equivalent than JPEG's 82 default — re-encoding at 82 would be visibly lossy.
3. Download the .jpg. Single file → JPEG. Batch → ZIP with original names re-suffixed.
4. Use the JPG in whatever wouldn't open AVIF. Photoshop CS6, Windows Photos on older builds, most print kiosks, legacy email clients.

Ninety-five percent of the time that's all you need. The rest of this post is useful if you're hitting AVIF a lot (designers, e-commerce, journalists scraping reference imagery), or if you want to understand why the format exists and where JPG actually costs you quality vs filesize.

What AVIF is, in one paragraph

AVIF is "AV1 Image File Format" — a still-image codec that borrows AV1's video-compression machinery and applies it to photographs. AV1 is the royalty-free video codec built by Google, Apple, Mozilla, Microsoft, Intel, and Netflix between 2015 and 2018. Taking a single frame of AV1 and wrapping it in an HEIF-style container gives you AVIF — dramatically better compression than JPEG (30-50% smaller at equivalent visual quality), full alpha support, HDR, wide colour gamut, and 10-bit depth. It's the obvious "what replaces JPEG" answer on paper.

On the web, Chrome 85+ (2020), Firefox 93+ (2021), and Safari 16+ (2022) decode AVIF natively. Cloudflare, Shopify, and most CDNs auto-serve AVIF to browsers that advertise support viaAccept: image/avif. Your browser shows the image; the URL still says .jpg; the bytes downloaded are AVIF. When you right-click "Save Image As," most browsers save the actual bytes — which means you end up with an AVIF file on disk, regardless of what the URL looked like. That's "the Save Image As AVIF problem."

Why your apps can't open it

AVIF decoding requires the AV1 codec. AV1 is young — standard finalised 2018, reference decoder (libaom) usable 2019, hardware decode arrived in consumer chips starting late 2020. Anything older than that effectively cannot open AVIF without a plugin. The rough lay of the land:

• Opens AVIF natively: Chrome 85+, Firefox 93+, Edge 121+, Safari 16+, Windows 11 (Photos + File Explorer thumbnails if the AV1 Extension is installed, which it usually is by default), macOS 13+, iOS 16+, Android 12+, Photoshop 2023+ (24.0).
• Needs a plugin or conversion: Windows 10 (needs AV1 Video Extension — free from Microsoft Store), older Photoshop (Substance 3D plugin or convert), older Illustrator, Affinity Photo pre-v2, older XnView, GIMP pre-2.10.22.
• Can't open it at all, period: Windows Photo Viewer (classic), most print-kiosk firmware, many commercial lab CMSes, legacy email clients, anything built on pre-2020 image libraries, a surprising amount of enterprise software.

The short version: anything shiny and current handles AVIF. The long tail of "everything else your life actually touches" doesn't. Until 2026-ish that's going to keep being true. JPEG remains the universal destination format; AVIF is the delivery format.

AVIF vs JPG vs WebP vs PNG — real file sizes

Here's a representative set — a single 3000×2000 photograph (landscape scene, mixed sky and foliage, typical web hero image) encoded across the four formats at visually equivalent quality. Numbers are averages from a 20-image test set we maintain for this kind of comparison.

The short reading of that chart: AVIF is roughly half the bytes of JPEG at equivalent visual quality, WebP sits between them closer to JPEG, and PNG is ~10× the cost because it's lossless. That's why sites serve AVIF — every KB is faster page load on mobile. The tradeoff is tooling compatibility, as above. When you need the file to work in Photoshop CS6 or Windows 10 Mail, you're paying those extra bytes for the JPG knowingly.

Quality settings — why 92 not 82

We default the JPG output at q=92 rather than the q=82 default we use in our compression guide. Reason: AVIF at its normal web-delivery quality (roughly AV1 CRF 30) is visually equivalent to JPEG around q=90-93. If we re-encoded at q=82 you'd lose perceptible detail in the transcode — compounding the loss the AVIF encoder already applied. Better to stay at q=92 and take the slightly larger file; if you need smaller, run the output through our JPEG compressor after you've confirmed the content is what you need.

Rule of thumb for AVIF-to-JPG transcodes:

• q=95 — archival / reference quality. Some AVIF sources (especially 10-bit) justify this.
• q=92 (our default) — visually lossless vs the AVIF source on any monitor you'll encounter.
• q=85 — if filesize matters more than perceptual transparency. Detectable softening on close inspection of foliage, skin, gradients.
• q=75 — only for thumbnails or if re-compression is expected downstream.

We expose the slider in advanced settings. Leave it at 92 for anything you care about.

Transparency — AVIF has alpha, JPG doesn't

AVIF supports full alpha channels. If the source has transparency (logos with transparent backgrounds, product cut-outs, UI assets), converting to JPG silently fills the transparent areas with a background colour. Default white; we expose a picker.

• If the source is transparent and you need transparency: pick PNG instead via our format converter, not JPG. PNG is 5-10× the file size but keeps the alpha.
• If the source is transparent but the destination is on a known background: pick a matching fill colour in the cropper's advanced settings. A logo destined for a white document looks right as a white-filled JPG.
• If you're not sure: our converter detects alpha in the AVIF and warns before dropping it to white.

HDR, 10-bit, and colour gamut gotchas

AVIF can carry wide-gamut (Display P3, Rec. 2020) and HDR (HLG, PQ) content. JPEG can carry wide-gamut via ICC profile but practically everyone outputs sRGB, and JPEG has no HDR tone-mapping. Converting HDR AVIF to JPEG without tone-mapping produces an image that looks flat or clipped. Our converter auto-tone-maps HDR AVIF to SDR sRGB using the same algorithm macOS Preview uses — not perfect, but visually correct on SDR monitors.

If you need to preserve HDR or Display P3 gamut, JPEG is the wrong destination; keep the AVIF or convert to a wider-gamut format like 16-bit TIFF.

Animated AVIF — AVIS

AVIF supports animation (the multi-frame AVIS variant). JPEG doesn't. If your source is animated, converting to JPEG gives you the first frame only; the animation is lost. For animated AVIF, convert to GIF (universal but massive and 8-bit) or WebP (smaller, better colour, not universal). Our converter detects animated input and warns before dropping frames.

Batch workflow — a folder of AVIFs to a folder of JPGs

Designers pulling reference imagery, journalists scraping photo galleries, and e-commerce teams auditing supplier assets all hit the same pattern: a folder of .avif files, needs to be a folder of .jpg files, now.

1. Drop the folder on the converter. Up to 500 files at a time (browser memory permitting).
2. Leave quality at 92 unless you have a reason to lower it.
3. Pick the transparency fill if any of your AVIFs have alpha (default white).
4. Export ZIP. Original filenames preserved, .avif swapped for .jpg.

For recurring workflows (product-photo pipelines), a command-line tool like cavif paired with libavif is worth setting up. For ad-hoc folders the browser-based path is the shortest.

How our converter compares

AVIF-to-JPG is a smaller pool than JPEG compression — many generic converters still don't decode AVIF at all. Here's the landscape as of 2026:

Short summary: Photoshop if you're on it already and 2023+. CLI if you run pipelines. For everyone else — a folder of AVIFs and the JPGs back in a zip — our converter is the shortest path and doesn't upload your files.

Works well / doesn't work

Works well

• Static AVIF photographs from any web source (hero images, article photos, product shots)
• AVIF with transparency (alpha fill-picker, or route to PNG via our format converter)
• HDR and wide-gamut AVIF (auto tone-mapped to sRGB)
• Batches up to ~500 files per session
• Privacy-sensitive source imagery (runs in-browser)

Doesn't work (well) yet

• Animated AVIF (AVIS) — we extract the first frame and warn; use WebP or GIF for animated output
• Display P3 preservation — JPEG output is sRGB only (format limitation)
• 10-bit archival output — JPEG is 8-bit per channel
• AVIF files over ~100 MB (browser memory ceiling)

Tips for the best result

• Leave quality at 92. AVIF sources are usually encoded at a quality point where q=82 JPEG would be visibly worse.
• Convert to JPG only if you actually need JPG. If the destination accepts WebP (most modern software), convert to WebP instead — you keep the alpha channel and get a smaller file. Our format converter does AVIF→WebP too.
• For transparency, use PNG, not JPG. JPEG has no alpha — it silently fills to white.
• Keep the AVIF source. If you ever need higher quality or a different destination, the AVIF is a better master than the JPG transcode.
• Don't transcode twice. Every conversion costs quality. Convert once at delivery.
• Windows 10 + AVIF: install the free AV1 Video Extension from Microsoft Store, and Windows Photos handles AVIF natively — you may not need to transcode at all.

Common questions

Why won't my browser save the image as JPG?

Because the server is sending AVIF. Modern browsers save the bytes that were actually downloaded, not the URL extension. If the server served AVIF (because your browser advertised AVIF support in its Accept header), you get AVIF on disk regardless of the URL saying .jpg. The workaround is to transcode after the fact, which is what this tool does. Some browsers offer "Save image to Photos" that auto-transcodes — useful if you're only saving occasional single files.

Is AVIF lossy or lossless?

Both, configurable per-file. Web-delivered AVIF is almost always lossy (the point is smaller filesize than JPEG at equivalent quality). Lossless AVIF exists — it's typically 10-30% smaller than lossless PNG — but it's rarer in the wild. Our converter handles both transparently.

Will I lose quality converting AVIF to JPG?

Yes — by definition. JPEG is a lossy format, so re-encoding adds another generation of loss on top of whatever the AVIF already discarded. At q=92 the loss is below human perception on any normal monitor; at q=82 it's detectable but small; below q=75 it's visible. See the JPEG quality numbers for the size-vs-quality curve.

Can I convert AVIF to PNG instead?

Yes — and you should if the source has transparency or if you're editing further downstream. PNG is lossless, so the conversion doesn't add quality loss (though the file is 5-10× larger). Our format converter does AVIF→PNG in the same session.

Is AVIF replacing JPEG?

Slowly. AVIF adoption on the web is around 35-40% of mainstream image traffic as of 2026 and climbing. JPEG will remain the universal compatibility format for another 5-10 years minimum, because the long tail of software that can't decode AVIF is enormous. Most sites serve both, content-negotiated per browser.

Are my files uploaded?

No. Decoding and re-encoding both run in your browser tab via WebAssembly. This is a privacy win for confidential reference imagery — CloudConvert and Convertio both upload every file to their servers.

Does this handle HEIC too?

Not in this tool — HEIC (iPhone's Apple-flavoured HEIF) uses HEVC instead of AV1, different codec. Use our HEIC to JPG converter instead (same in-browser workflow, different decoder). See also our HEIC to JPG guide.

Ready?

AVIF to JPG converter →. Drop the files, leave quality at 92, download. Free, in your browser, no upload. If you were also going to compress the result, skip the second step and run our JPEG compressor on the output instead — it's designed for exactly that workflow. If the source has transparency you need to keep, route through our format converter to PNG or WebP instead.