How to Convert AV1 IMAGE FILE FORMAT to JPG Online Free

AVIF is one of the newest image formats around. It is built on the AV1 video codec developed by the Alliance for Open Media, and it packs remarkable detail into very small files, often noticeably smaller than the same picture saved as JPG.^[1] The problem is reach. Plenty of older browsers, image editors, and operating systems still cannot open an AVIF, so the file that looked great on your machine can show up as a broken thumbnail on someone else's.

Converting AVIF to JPG solves that instantly. JPG has been the default photo format for decades, so it opens in essentially every program, on every device, without a plugin. The trade is honest: you get maximum compatibility, and in return the file grows larger and gets re-encoded from an already-compressed source. This guide explains what each format is doing under the hood, why the size grows, and how to set quality so you do not stack fresh artifacts on top of the ones AVIF already introduced.

Why convert AVIF to JPG at all

The single reason to make this conversion is compatibility, not quality or size. AVIF is technically the more advanced format: it compresses better, supports transparency, and can hold high dynamic range and a wide color gamut. JPG does none of those things. So this is one of the rare conversions where you are deliberately moving to the older, less capable format because that is exactly what makes it work everywhere.

If you are emailing a photo to someone on an older phone, uploading to a site that rejects AVIF, or opening the image in an editor that has never heard of AV1, JPG is the safe common ground. Think of it as translating into the language every device already speaks.

AVIF and JPG: modern codec versus legacy standard

These two formats are separated by nearly thirty years of compression research. JPG, defined by the Joint Photographic Experts Group and standardized as ISO/IEC 10918 in 1992, compresses images by splitting them into 8-by-8 pixel blocks, transforming each block with a discrete cosine transform, and discarding the high-frequency detail the eye is least sensitive to.^[3] It was a landmark for its time and remains extraordinarily well supported, but its block-based approach shows visible artifacts at low quality and it caps out at 8 bits per channel with no transparency.^[4]

AVIF wraps a still image encoded with the intra-frame tools of the AV1 video codec inside the ISO base media file container.^[2] Instead of fixed 8-by-8 blocks it uses variable-sized partitions, far more sophisticated spatial prediction, and a modern entropy coder, which is why it can reproduce the same picture in a fraction of the bytes. It also supports transparency, 10- and 12-bit color depth, high dynamic range, and wide gamut, none of which JPG can carry. Converting from AVIF to JPG therefore means projecting a richer, more efficient representation down onto an older, simpler one, keeping the visible picture but shedding the capabilities JPG never had.

How the conversion works under the hood

The converter cannot translate AVIF's compressed data directly into JPG's, because the two use entirely different math. Instead it works in two stages. First it fully decodes the AVIF, running the AV1 intra decoder to reconstruct the complete image as a grid of raw pixels in memory. At this moment the picture exists with no compression at all, exactly as AVIF intended it to look.

Then it re-encodes those raw pixels as JPG, applying the block transform and quantization at whatever quality you chose. Because JPG cannot represent transparency, any transparent areas are flattened against a solid background color first, and because JPG is limited to standard 8-bit color, any high dynamic range or wide-gamut information is tone-mapped down to fit. The key consequence is that this is a lossy-to-lossy re-encode: you start from an image AVIF already compressed and compress it again with a different, less efficient method, so a small amount of extra detail is always lost even at high quality.

Convert AVIF to JPG, step by step

1. Open the converter and add your AVIF

   Open the FileFormer image converter and drop your AVIF file in. The conversion runs on your own device, so the image is never uploaded anywhere.

2. Set JPG as the output format

   Choose JPG. This is what gives you the file that opens in any browser, editor, or operating system with no special support.

3. Pick a quality level

   A JPG quality around 85 keeps a photo looking crisp while holding the file size down. Since you are re-encoding an already-compressed image, avoid going very low, or you will stack visible artifacts on top of the ones AVIF already introduced.

4. Export and download

   Convert, check the preview, and download. If the result looks soft, bump the quality up and export again.

What you give up in the swap

Because JPG is simpler than AVIF, a few things do not survive the trip. Knowing them up front saves surprises.

Color, gamut, and dynamic range

The most under-appreciated part of this conversion is what happens to color. AVIF can store 10 or 12 bits per channel, describe colors in a wide gamut such as Display P3 or Rec. 2020, and carry high dynamic range signaling that tells a capable screen to render bright highlights well beyond ordinary white.^[2] A modern phone photo saved as AVIF may quietly contain all three of these. JPG, by contrast, is a standard-dynamic-range, 8-bit-per-channel format that almost everyone treats as plain sRGB.

When the converter projects an HDR, wide-gamut AVIF into JPG, it must tone-map the extended brightness range and gamut-map the wider colors back into what sRGB can express. Done well, the result still looks natural on an ordinary screen; done carelessly, highlights can clip to flat white and saturated colors can shift. This is a real, if usually subtle, loss that has nothing to do with the quality slider, and it is one more reason to keep the original AVIF whenever the destination can actually display its richer color. For an everyday photo viewed on a standard screen, the difference is often invisible, but for deliberately graded or HDR imagery it is worth being aware of.

Quality: avoiding stacked artifacts

The trap in this conversion is compounding compression. Your AVIF has already discarded some detail to reach its small size; encoding the decoded result as a low-quality JPG discards more, and because the two formats introduce different kinds of artifacts, the second pass can make the first pass's flaws more visible rather than hiding them. That is why the quality setting matters more here than when starting from a lossless source.

The practical rule is to stay at 85 or above unless a size limit forces otherwise, and to convert once from the original AVIF rather than repeatedly re-saving the JPG, since every additional JPG save is another lossy generation.

Real-world scenarios and the right approach

Whether JPG is the right target, and which quality to pick, depends on why the AVIF is a problem in the first place:

The theme is that JPG is a compatibility fallback, not an upgrade. Reach for it only where AVIF genuinely does not work, and choose PNG or WebP instead whenever transparency or crisp text is involved.

When to keep the AVIF instead

You are re-encoding a lossy image into another lossy format, so a little sharpness is always lost, and the file gets bigger. If the destination already understands AVIF, such as a modern website, a current browser, or an up-to-date phone, there is no reason to convert. Keep the AVIF and enjoy the smaller file and richer color.

Only reach for JPG when you actually hit a wall: a program that will not open the file, an upload form that rejects it, or a recipient on older hardware. If you find yourself doing the reverse often, saving small modern files for the web, the JPG to AVIF guide covers going the other direction.