Convert AVIF to JPG
Convert AVIF to JPG locally, even if your browser cannot display AVIF. Quality slider, batch input and an instant ZIP download.
- Runs in your browser
- Files are never uploaded
- Free, no account
JPG has no alpha channel, so transparent pixels are painted with the colour below.
Metadata is stripped. Re-encoding rebuilds the file from raw pixels, so EXIF — GPS coordinates, camera model, serial number, capture time — and any XMP or IPTC block are dropped. Pixels are written in sRGB.
Nothing leaves this tab. The encoders are WebAssembly builds of libjpeg-turbo (MozJPEG), libpng/oxipng, libwebp and libavif running inside a worker on your machine.
How to convert AVIF to JPG
- Drop your .avif files onto the box above, or click to browse.
- Choose a background colour if any of the images have transparent areas — JPEG cannot store them, so they have to be painted with something.
- Leave quality at 88, or adjust it. The default is set high on purpose: the source is already lossy, and a high-quality second pass keeps the two sets of artefacts from stacking up.
- Save each JPG, or download the batch as a ZIP.
It works even if your browser cannot show AVIF
This page tries the browser's built-in AVIF decoder first because it is fast. If the browser does not have one — Safari before version 16, older Firefox builds, some embedded browsers — the tool falls back to a WebAssembly build of libavif that is bundled with the page. Either way, the decoding happens on your device and no file is uploaded.
That also means the tool works offline. Once the page has loaded, you can disconnect entirely and keep converting.
What you gain and what you give up
| AVIF | JPEG | |
|---|---|---|
| Opened by old software | Rarely | Essentially always |
| File size for the same photo | Baseline | 1.5–2.5× larger |
| Transparency | Yes | No — flattened on conversion |
| Colour depth | Up to 12-bit, HDR capable | 8-bit sRGB |
| Decode speed | Slower | Very fast |
| Editing support | Limited plug-ins | Universal |
Keeping the second encode invisible
Any lossy-to-lossy conversion risks compounding artefacts. Three things keep that under control here:
- A high default quality. At 88, MozJPEG spends enough bits to reproduce the AVIF's own output faithfully rather than re-quantising it coarsely.
- Progressive, trellis-optimised encoding. The encoder used here is MozJPEG, which produces measurably smaller files than a plain libjpeg at the same quality — so a high quality setting costs less than you would expect.
- No resizing. The image comes out at exactly its original pixel dimensions, so nothing is resampled.
If the image has transparency you need to keep, or you want a lossless result, use AVIF to PNG instead. To go back the other way, see image to AVIF, and for mixed batches the universal image converter.
Questions
My software says it cannot open .avif — will this help?
Yes. AVIF is decoded here with a WebAssembly build of libavif and re-saved as a JPEG, which every operating system, editor, printer and upload form has understood for thirty years.
Does it work if my browser has no AVIF support?
Yes. The tool tries the browser’s native decoder first for speed, and falls back to the bundled libavif decoder when the browser cannot read the file. Either way the work happens on your device.
Will the JPG look worse than the AVIF?
Slightly, because two lossy codecs are applied in sequence. Keeping quality at 88 or above — the default here — makes the second pass essentially invisible at normal viewing sizes.
What about transparent AVIF images?
JPEG has no alpha channel, so transparent regions are flattened onto the background colour you select. Convert to PNG instead if you need the transparency preserved.
Why convert away from AVIF at all?
Because plenty of software still cannot read it: older phones, most desktop image viewers, many CMS uploaders and almost every print shop. JPEG is the format that is accepted everywhere, at the cost of a larger file.