Image · 55 tools · nothing uploads

AVIF to JPG

Open an AVIF as a JPG. The same picture costs several times more bytes here, because JPEG needs them to look the way the AVIF looked.

Input

Options

AVIF to JPG is the conversion where the file gets bigger. AV1 spends few bits on a photograph and JPEG needs a great many more to look the same, so the byte count climbs. The quality box is the only lever on that, and it works on the JPEG, not on what the AVIF dropped.

Questions

Why does the JPG end up bigger?

Because AV1, the codec inside AVIF, compresses more efficiently per pixel than JPEG, so representing the same picture at a comparable visual quality costs JPEG more bytes.

Is any detail lost?

Some, depending on the quality option, default 80. The AVIF is decoded to full pixels and JPEG compression is applied fresh, so this is not a byte-for-byte repack; block-based JPEG encoding adds its own generation of loss.

Which engine handles this?

jSquash decodes the AVIF and encodes the JPEG through mozjpeg, both WebAssembly, running in Node, on the command line, through MCP and in the browser, with no separate download.

What size should I expect?

Several times larger than the source AVIF is common, since AVIF is one of the more efficient widely supported image codecs and JPEG is one of the less efficient ones at the same visual quality.

What is the reverse page?

There is no dedicated page. Convert image, the general hub, can write AVIF from a JPG source, without a jpg-to-avif page of its own.

Related Image tools