Skip to main content

AVIF to JPG converter

Convert AVIF images to JPG format

No watermarkFree & unlimited
All processing happens in your browser. No data is sent to any server.

This is a lossy format decoded and then re-encoded with a second lossy codec, which changes how you should set the quality slider. Whatever the AVIF encoder already discarded is gone; the JPEG encoder now makes its own decisions on top of that, and setting quality too low compounds the two. The upside is compatibility, and it is total: JPEG opens in every camera, printer, ID photo uploader and decade-old photo editor in existence.

Key facts about AVIF to JPG converter

Key facts about AVIF to JPG converter
Generation lossTwo lossy passes stack. The AVIF was already quantised, and the JPEG encoder quantises the decoded result again with a different transform.
Recommended qualityStay at 90 or above. Because the source is already lossy, aggressive settings degrade the picture faster than they would from an untouched original.
Transparency becomes whiteJPEG has no alpha channel, so the canvas is filled with white before the image is drawn and a transparent cut-out lands on a white rectangle.
Size deltaTwo to five times larger at comparable visual quality. A 120 KB full HD AVIF typically becomes a 300 to 600 KB JPG at quality 90.
Decoding requirementChrome 85, Firefox 93 or Safari 16 and later. An older browser reports a load failure rather than writing a broken JPG.
Bit depthBaseline JPEG is 8 bits per channel and so is the canvas, so a 10 or 12-bit AVIF is reduced and gradients can band.
HDR handlingAn AVIF with a PQ or HLG transfer curve is tone-mapped by the browser during decode, and the JPG carries no profile, so it is treated as ordinary sRGB.
Opens the resultEvery operating system, camera, printer, office suite and web form ever built. It is the one raster format you never check support for.

What happens to your file

There is no server in this picture. Your AVIF becomes an object URL, the browser's AV1 still-image decoder produces pixels inside an Image element, and those pixels are composited onto a canvas this page has already filled with white. The JPEG bytes are produced by canvas.toBlob, which calls the browser's own encoder on your machine. Nothing is transmitted, so there is no upload queue and no temporary remote file.

About this tool

  1. 1

    Load your AVIF files

    Drop up to twenty .avif files, each as large as 500 MB, or click to open the file picker.

  2. 2

    Check the preview appears

    A blank preview means your browser cannot decode AVIF. Update it or switch browsers before going further.

  3. 3

    Set a high quality

    The slider starts at 90 and that is a sensible floor for a re-encode. The estimated output size updates as you move it.

  4. 4

    Convert and compare

    Use the side-by-side view to check skies, skin tones and shadows, then save the JPG or take converted-jpg-files.zip.

Specs & compatibility
Input and outputTakes .avif only (image/avif) and returns .jpg with the image/jpeg type; any other extension is refused before decoding.
Conversion pathAVIF to JPG runs in three steps: an <img> element decodes the AVIF, which the browser itself must be new enough to read; the pixels land on a 2D canvas in this tab; then canvas.toBlob with the image/jpeg type returns the finished file.
Browser supportThe AVIF side needs Chrome 85, Firefox 93 or Safari 16.4 to decode, while writing the JPG is just as universal, since every canvas implementation encodes JPEG.
Controls for this pairA 30 to 100 quality slider (steps of five, default 90) drives the JPG encode, max-dimension presets from 3840 down to 200 px resize the AVIF first, and the strip-metadata toggle is moot on this pair.
Batch, caps and namingTwenty AVIF files per run at 500 MB each; one result downloads as a single JPG, several as converted-jpg-files.zip, zipped by JSZip 3.10 in page memory.
Device ceilingThe canvas caps it: past roughly 16,384 px a side Chromium refuses the bitmap and iPhone Safari gives up sooner, so an oversized AVIF fails before any JPG bytes exist.
  • Do not go below quality 80 unless size is a hard constraint; you are already working from a compressed source.
  • If the AVIF has a transparent background and white is wrong, composite it over your colour in an editor first.
  • Keep the AVIF as your master and treat the JPG as an export, so a re-export does not add a third generation.
  • For web delivery, serving the AVIF with a JPG fallback in a picture element beats replacing the AVIF entirely.
  • Browser AV1 decode, browser JPEG encode
  • White matte applied under transparency
  • Quality slider with an estimated file size
  • Twenty photos exported in one go
  • Getting an AVIF download into a photo editor or print service that rejects the format.
  • Meeting an upload requirement on a portal whose accepted list stops at JPEG and PNG.
  • Sending an image to someone on an older computer who cannot open it.
Yes, some. The AVIF already discarded information during its own encode; decoding gives you that reduced picture, and JPEG quantises it again with a different transform. Quality 90 or above keeps the second pass close to invisible; below 70 the compounding shows in skies and shadows.
AVIF is a far more modern codec. AV1 intra coding uses more flexible block partitions and a much richer prediction set than the transform JPEG relies on, typically reaching the same perceived quality in a third to a fifth of the bytes. A two to five times increase is expected.
It becomes white. AVIF stores alpha as a separate auxiliary image item, but JPEG has no alpha channel, so something has to replace it. This page paints the canvas white before drawing, which is why cut-outs land on white rather than the black they would otherwise produce.
Your browser has no AVIF decoder. Support arrived in Chrome 85, Firefox 93 and Safari 16 and is missing from older versions and some in-app browser views. Since the browser does the decoding, the page cannot work around it; update or switch browsers.
No. An AVIF can carry EXIF and XMP boxes with camera model, exposure and GPS data, but that never reaches the canvas, which receives only pixels, and the JPEG is written with no EXIF segment. Read the metadata out with exiftool first if you need it.

Related tools

View all

Need the opposite? Try JPG to AVIF

Updated

We use anonymous analytics to improve ToolChamp. No personal data is stored or sold. Privacy Policy