Home/AVIF to JPG
100% local · nothing is ever uploadedConvert AVIF to JPG
AVIF being the most efficient format doesn't mean every upload form or tool accepts it yet. Drop your AVIF files below and get back a JPG that opens anywhere, converted entirely in your browser — one file or a whole batch.
Drop your images here
or browse files
JPG, PNG, WebP, AVIF, or HEIC (Safari only) · processed locally · never uploaded · paste with Ctrl+V also works
No images yet. Drop some above to get started.
Why convert AVIF back to JPG?
AVIF displays fine in any modern browser, but accepting an AVIF upload is a separate story — plenty of CMS media libraries, print services, and older tools still only recognize JPG or PNG, the same gap that pushes people to convert WebP back to JPG too. Converting to JPG is the safe fallback whenever the receiving end hasn't caught up.
Transparency is the one thing this conversion can't carry over — JPG has no alpha channel, so any transparent area in the AVIF gets replaced with a flat color. If the source is an icon or graphic rather than a photo, the AVIF to PNG converter is the one that actually preserves it.
AVIF vs WebP: Why AVIF Compresses Better →What you give up going back
Some of what AVIF can hold has no equivalent in JPG at all. AVIF stores 10 or 12 bits per colour channel and can describe HDR and wide-gamut colour; JPG is 8-bit and, in practice, sRGB. If the source came from a modern phone or a photo pipeline that preserved that range, the conversion flattens it, and no quality setting brings it back.
For the overwhelming majority of images that costs you nothing visible, because most photos on the web were never wide-gamut to begin with. It's worth knowing if you're archiving rather than publishing — in that case keep the AVIF as the master and treat the JPG as a copy for whoever needs it.
Why do it anyway
Because acceptance and display are different problems. Every browser still receiving updates shows AVIF, so nothing on the web needs this conversion. What needs it is everything else: government portals and job application forms validating against a fixed list of JPG and PNG, print services, older desktop software, and internal corporate tools that have never heard of the format.
It's also a second lossy pass, so convert from the original if you still have one. Where you can't, keep the quality at 80 or above — the AVIF already discarded detail, and stacking an aggressive JPG encode on top of that is where visible artifacts start.
FAQ
Why would I downgrade a modern format?
Because something on the receiving end refuses AVIF. That's almost always an upload form, a print service or older software rather than a browser — browsers handle AVIF fine. If it's only ever going on a web page, you don't need this conversion.
Will it look worse?
Marginally, since it's a second lossy encode. At quality 80 or above it isn't visible at normal viewing size on a photograph. What does get lost regardless is HDR and wide-gamut colour, which JPG has no way to represent.
What about a transparent background?
It gets filled with solid white — JPG has no alpha channel. If the image needs transparency, convert to PNG or WebP instead.