Designers argue about AVIF vs JPEG the way mechanics argue about engine oil — loudly, and usually without numbers. Here are the numbers.
The facts in one table
| Format | Compression | Transparency | Animation | Support (2026) |
|---|---|---|---|---|
| AVIF | Lossy and lossless | Yes | Yes | over 93% of browsers in 2026, including Chrome, Firefox, Safari and Edge |
| JPEG | Lossy | No | No | every browser and device made in the last 25 years |
Two rows, but they hide the biggest practical gap: file size on real images, covered next.
The kilobyte question
For AVIF, the working reality: roughly half the size of a comparable JPEG, and about 20% under WebP. For JPEG: a 12-megapixel photo lands around 3-4 MB at quality 85.
Averages mislead here — a logo and a sunset photo will rank these two formats in opposite order. Convert one of each and look at the readouts.
And if the destination is a web page, keep the modern baseline in view: WebP runs 25-34% under JPEG and AVIF roughly halves it — sometimes the right answer to "AVIF or JPEG" is a third format entirely.
Whichever way the kilobytes fall, remember they compound: a saving of 200 KB per image across a forty-image page is eight megabytes a visitor never downloads.
Quality and features
AVIF is lossy and lossless, strongest at next-generation web images, high-quality compression; its known costs are slower encoding, limited browser support in older versions.
JPEG is lossy, aimed at photographs, social media, web images; the trade-off there: lossy compression, no transparency, quality degrades on re-saving.
Neither list is a flaw — formats are tools, and a hammer is not a bad screwdriver. The question is only which job sits on your desk.
The verdict
Choose AVIF when your job looks like next-generation web images, high-quality compression and the priority is 50% smaller than JPEG, HDR support, excellent quality.
Choose JPEG when you are in photographs, social media, web images territory and need small file size, universal support, great for photos.
When in doubt, run the same image through the AVIF converter and the JPEG converter and let the size readouts vote.
The history that explains the gap
AVIF comes from 2019, built by the Alliance for Open Media; JPEG from 1992, by the Joint Photographic Experts Group. Every difference in the table above traces back to what problems were worth solving in those two moments.
The general law of image formats: the older one opens in more places, the newer one wastes fewer bytes. AVIF and JPEG follow it exactly.
Thirty seconds of compression theory
Dual-mode formats carry both toolboxes: a lossy mode for photographs and a lossless one for graphics. That flexibility is exactly why the modern web formats displaced single-mode ancestors.
Lossy compression throws away detail the eye is bad at noticing — fine texture, subtle color steps — and keeps what perception cares about. That is how a photo drops 80% of its weight while looking identical at arm's length; it is also why each re-save discards a little more.
Every recommendation here is downstream of those mechanics — formats do not have personalities, only algorithms.
Who picks what, in practice
The photographer delivering a wedding gallery cares about quality first and upload time second — the format whose profile reads "50% smaller than JPEG, HDR support, excellent quality" or "small file size, universal support, great for photos" closer to that wins the job.
The web developer chasing Core Web Vitals weighs file size above everything: between roughly half the size of a comparable JPEG, and about 20% under WebP and a 12-megapixel photo lands around 3-4 MB at quality 85, the smaller real-world output gets shipped.
The office user attaching a file for an unknown recipient optimizes for one thing — that it opens. Whichever of the two enjoys broader support is the safe envelope.
The print shop reverses every web instinct: resolution and lossless data outrank file size completely, because a 60 MB master is cheaper than a reprint.
The Core Web Vitals angle
Images are usually the heaviest asset class on a page, so format choice flows straight into Largest Contentful Paint — the Core Web Vitals metric Google weighs for ranking. Lighter images, earlier paint, better scores: the chain is that direct.
Pair the format change with loading="lazy" on below-the-fold images and correct display dimensions, and the speed gain typically doubles.
Measure before and after with PageSpeed Insights — the image-weight line item makes the improvement concrete instead of theoretical.
Troubleshooting the usual suspects
Colors shifted. Usually a color-profile story: the source carried a wide-gamut profile and the viewer assumes sRGB. Convert from an sRGB master when the destination is the web, and the shift disappears.
The file will not open. Nine times out of ten the viewer is the limitation, not the file. Try a second viewer before blaming the conversion, or convert to JPEG — if that copy opens, the original was fine all along.
Transparent areas turned white. The target format has no alpha channel; flattening is the documented behaviour, not a bug. Re-convert to PNG or WebP if transparency must survive.
The file got bigger. Some content genuinely compresses worse in the new format — flat graphics in photo-oriented codecs, photos in graphics-oriented ones. The size readout before download is the early warning.
Common Questions
Which is smaller, AVIF or JPEG?
Depends on the image. The anchors: for AVIF, roughly half the size of a comparable JPEG, and about 20% under WebP; for JPEG, a 12-megapixel photo lands around 3-4 MB at quality 85. Photographs and flat graphics compress on opposite curves, so test one of your own files rather than trusting an average.
Which is better for a website in 2026?
Browser support is the deciding spec: AVIF — over 93% of browsers in 2026, including Chrome, Firefox, Safari and Edge; JPEG — every browser and device made in the last 25 years. For pure web delivery, also weigh WebP and AVIF, which usually undercut both on size.
Can I serve both formats on the same website?
Yes — the HTML picture element exists for exactly this: list the efficient format first and the compatible one as fallback, and each browser takes the best it understands. It is the standard pattern on image-heavy sites.
Which one is safer for long-term archiving?
Archives want lossless data and broad software support, because the format must still open in twenty years. Between these two, lean toward the one whose compression does not discard information, and keep checksums either way.
Can I batch convert a mixed folder of AVIF and JPEG?
Yes — converters key on each file's actual type, not the folder. Drop the mixed set, pick one target format, and the output comes back uniform in a single ZIP.
Written by Giovanni Picaro, a web developer who has been building image tools and optimizing sites since 2019. Sources: MDN image format reference and Google web.dev. Last reviewed: 2026.