You attach a AVIF file, hit send, and the reply comes back: "can you resend this as JPEG?" It happens with print shops, CMS uploads and government portals alike. Here is the clean way to convert, what it does to your file, and the numbers to expect.
The two formats, side by side
| 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 |
Read the support column first; in most conversions that row alone is the entire motivation.
Why AVIF files end up needing to be JPEG
AVIF (AV1 Image File Format) is a lossy and lossless format made for next-generation web images, high-quality compression. Its weak spots — slower encoding, limited browser support in older versions — are exactly where JPEG steps in.
JPEG (Joint Photographic Experts Group) handles photographs, social media, web images, and in 2026 its support looks like this: every browser and device made in the last 25 years. On size, the practical picture: a 12-megapixel photo lands around 3-4 MB at quality 85.
In practice the push comes from three places: platform requirements, collaboration with people on other tools, and plain file-size pressure.
Converting AVIF to JPEG in the browser
Open the JPEG converter and drop your AVIF file onto the upload area. Multi-select works, so a whole folder of files goes in at once — useful when a shoot or an export produced dozens of them.
Start the conversion and watch the size readout: the page shows the output weight before you commit to downloading. That single number answers most of the questions people bring to guides like this one.
When the batch finishes, grab the ZIP rather than clicking files one by one — it preserves the original filenames with the new extension.
If a file fails — it happens with corrupted exports — re-saving it once from any viewer and retrying usually clears it. Genuinely broken files fail everywhere, including in Photoshop.
Before you convert: a 30-second checklist
Keep the original. Conversions into lossy formats are one-way; the AVIF you started from is your archive copy, so it never gets deleted or overwritten.
Check the destination's rules. If a platform or print shop asked for JPEG, it often also has size or resolution limits — knowing them now saves a second round trip.
Group the batch. Converting fifty files in one upload beats fifty single conversions, and the ZIP you get back keeps the set together with its filenames intact.
Quality: the honest version
AVIF uses lossy and lossless compression; JPEG uses lossy. Re-saving a lossy file repeatedly is what visibly degrades images — a single conversion at good settings is not the problem.
For scale: roughly half the size of a comparable JPEG, and about 20% under WebP. After conversion to JPEG, expect the relationship to shift — a 12-megapixel photo lands around 3-4 MB at quality 85.
Canva and Adobe Express can export JPEG too, but both push you through an editor first — fine for one file, slow for forty.
If the converted file will be edited again later, convert once and edit that copy — chaining conversions through three formats is how artifacts creep in.
Platform quirks worth knowing
Messaging apps and social platforms recompress whatever you send — WhatsApp and most social feeds will re-encode your carefully converted JPEG anyway, so don't chase perfection for those destinations. Email clients are stricter: attachments survive untouched, which makes format choice matter more there.
CMS uploaders are the third trap: many enforce size limits or a format whitelist. If an upload bounces, the platform's allowed-formats list — not your file — is usually the explanation.
The metadata question nobody asks
Every photo from a camera or phone carries hidden baggage: capture date, device model, exposure settings and — on phones — often GPS coordinates. Conversion is one of the moments where that baggage can be kept or dropped.
For files headed to the public web, dropped metadata is a privacy feature: nobody needs your home coordinates embedded in a product photo.
The practical rule: treat the original as the metadata archive and the converted copy as the public version. That division of labour answers most privacy and copyright questions before they come up.
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.
The compounding is what surprises people: 200 KB saved per image across a forty-image page is eight megabytes a visitor never downloads.
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.
Where JPEG files go next
Once your files are JPEG, they slot into workflows AVIF could not reach: photographs, social media, web images. If you handle this pair often, the AVIF vs JPEG comparison covers the deeper trade-offs.
Three pitfalls to skip
Don't upscale before converting — extra pixels invent nothing and inflate the file. Don't convert a screenshot with text into a heavily lossy format if crisp edges matter. And keep the AVIF originals archived; storage is cheaper than regret.
The pattern behind all three: conversion is cheap and reversible only when the original survives. Protect the source and every mistake becomes a do-over.
How the compression actually works
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.
Once you see the mechanism, every size difference in this article stops being magic and starts being arithmetic.
Converting at scale
Past a certain volume the bottleneck moves from conversion speed to organization. Name files before converting, not after — the converter preserves names, so a clean naming scheme going in is a clean archive coming out.
Teams that hit this weekly keep two folders per project: masters in AVIF, delivery in JPEG, regenerated from masters whenever specs change.
What the numbers look like
Take a typical case: roughly half the size of a comparable JPEG, and about 20% under WebP. Convert that to JPEG and the format's profile takes over: a 12-megapixel photo lands around 3-4 MB at quality 85. The percentages vary with image content — flat-color graphics and detailed photos compress very differently — so trust the size readout on your own files over any blog's average.
Frequently Asked Questions
Does converting AVIF to JPEG reduce quality?
Only if JPEG is lossy, and even then a single conversion at default settings is rarely visible. The damage people associate with conversion comes from re-saving lossy files over and over, not from one clean pass. Keep the original AVIF and you can always go back.
Can I convert several AVIF files at once?
Yes — drop the whole selection into the JPEG converter and you get the results back as one ZIP. Batch jobs of 30-50 files are routine; the per-file time stays in the seconds.
Is the converted file bigger or smaller than the AVIF?
It depends on content, but the baselines are: roughly half the size of a comparable JPEG, and about 20% under WebP, while for JPEG: a 12-megapixel photo lands around 3-4 MB at quality 85. Flat graphics and photographs sit at opposite ends of every compression curve, so check the size shown before downloading.
Do I need Photoshop for this?
No. Photoshop, Canva and Adobe Express can all export JPEG, but for a pure format change a browser converter does the identical job without the subscription or the wait.
Does converting change the image dimensions?
No. Width and height in pixels stay exactly the same; only the encoding changes. If you also need resizing, do it as a separate, deliberate step — and always downscale, never upscale.
Why did my converted file come out larger?
Content sits on different compression curves: a file that AVIF encodes efficiently can genuinely grow as JPEG. It is normal for some images, which is why the size readout before download matters more than any rule of thumb.
Next step: open the JPEG converter, feed it one real AVIF from your project, and judge the size readout with your own eyes. That number settles the debate faster than any guide.
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.