AVIF to JPG Converter
Turn .avif images into JPGs that every site, form, and print shop accepts — decoded by your browser's own AVIF codec, converted and verified right here, nothing uploaded.
Convert AVIF files to JPG
Drop .avif files, pick a quality and background, and download verified JPGs with real before/after sizes.
Nothing to download: your browser is the decoder
Unlike the HEIC converter on this site — which must ship a WebAssembly decoder because browsers refuse to license HEVC — AVIF decoding is already built into every current browser: Chrome and Edge, Firefox since version 93, Safari since 16.4. This page leans on that: your file is decoded by the browser's own codec, drawn to a canvas, and re-encoded as JPEG. No module to fetch, nothing added to the page weight, and one less thing to trust. If your browser is old enough to lack AVIF support, the tool says so plainly when the page loads instead of failing with a cryptic error.
What the conversion costs, honestly
JPG buys universal acceptance and pays in three ways. Size: the JPG will almost always be larger than the AVIF — the row shows the measured change for your file. Quality: JPEG re-encodes the decoded pixels with its own lossy pass, faint at the default quality 92 but real. Transparency: JPEG has none, so transparent regions flatten onto your chosen background color, with a note on the row when it happens. Need the alpha kept? UseAVIF to PNG instead.
The honest details
- Decoded natively: your browser's own AVIF codec does the decoding — this page ships no decoder and fetches nothing extra.
- Feature-checked up front: the page probes AVIF decoding with a tiny test image at load time and shows a plain-language notice if your browser cannot do it.
- Animated AVIFs: image sequences keep their first frame, and the row says so.
- Metadata is stripped: EXIF — including GPS location — does not survive the re-encode. A privacy win for sharing; keep your originals.
- Content over filename: a
.avifthat is secretly something else is detected and handled as what it really is, with a notice. - Verified output: every JPG is re-decoded and dimension-checked before its download button appears.
Related tools
Keeping transparency or planning further edits? AVIF to PNG is the lossless landing place. Going the other direction,JPG to AVIF makes files smaller instead of more compatible. If the JPG then needs to hit a size limit, Compress JPEG squeezes it with MozJPEG.
Frequently asked questions
Why would I convert AVIF back to JPG?
Compatibility. AVIF is smaller and every current browser displays it, but plenty of upload forms, older tools, office software, and print services still only accept JPG. Converting hands you the thirty-year default that everything opens — at the cost of a larger file, which the row shows honestly.
How does this page decode AVIF without downloading a decoder?
Your browser already has one. Chrome and Edge, Firefox 93+, and Safari 16.4+ ship native AVIF decoding, so this page simply asks the browser to decode — no WebAssembly module, nothing extra fetched. The page checks this capability when it loads and tells you plainly if your browser is too old, rather than failing mysteriously.
What happens to transparency?
JPEG has no alpha channel, so any transparent areas are composited onto the background color you pick above (white by default), and the file row says when that happened. To keep transparency, use AVIF to PNG instead.
Will the JPG be bigger than the AVIF?
Almost always yes — you are trading AVIF’s modern compression for JPEG’s universal compatibility. The result row shows the measured change from real bytes, including "larger" when it grows, so the trade is visible rather than hidden.
What about animated AVIFs?
An AVIF can be an image sequence (the avis brand). Browser decoding keeps the first frame, and the file row tells you when that happened instead of silently dropping frames.
Is my file uploaded anywhere?
No. Decoding, converting, and verification all run in your browser tab, and the site’s security policy blocks requests to any other origin — verifiable in your network inspector.
Local processing: your images are decoded, converted, and verified inside your browser and never transmitted — see the methodology page for how to verify the no-upload claim yourself.