Convert AVIF to JPG
Turn an AVIF into a JPEG that older software can actually open.
How it works
AVIF is a still image wrapped in video machinery. The file is an ISOBMFF container (the same box structure as an MP4) holding a single intra-coded AV1 frame, standardised by the Alliance for Open Media in February 2019.
Because it inherits a modern video codec's intra tooling it has far more to work with than JPEG's fixed 8×8 DCT: prediction blocks up to 128×128, directional intra modes at fine angular increments, chroma-from-luma prediction, several transform kernels, and in-loop deringing. In practice that is around half the bytes of a JPEG at matched quality and 20–30% below WEBP.
What AVIF stores and JPEG cannot
It also stores things JPEG has no room for. AVIF supports 10- and 12-bit sample depth, 4:2:0 through 4:4:4 chroma, an alpha channel as a separate auxiliary item, and HDR signalling via the PQ or HLG transfer functions with BT.2020 primaries. Baseline JPEG is 8 bits per channel and, for all practical purposes, standard dynamic range.
Converting flattens all of that: the pixels are decoded to 8-bit RGBA before encoding, so extra bit depth is quantised away and a wide-gamut HDR photo comes out looking flat and desaturated because its highlight range no longer has anywhere to go. Smooth gradients that were clean at 10 bits may show banding.
Slow to encode, cheap to decode
The asymmetry to know about is time. AV1 encoding is expensive: searching that many block partitions and prediction modes is orders of magnitude slower than a JPEG encode. Decoding is comparatively cheap, which is the tradeoff a website wants when a file is encoded once and served a million times. This tool only decodes AVIF, so it is quick; if you go the other direction, expect to wait.
The uneven AVIF rollout
Adoption arrived unevenly and that is why you are here. Chrome shipped AVIF in version 85 in August 2020, Firefox in 93 in late 2021, Safari in 16 in September 2022, and Edge only in 121 in January 2024, so the format became safely servable roughly a decade after JPEG-alternatives began appearing.
Desktop applications, older phones, printers, CMS upload validators and image libraries pinned to a working version are all still catching up. JPEG remains the format nothing rejects, which is the entire reason to convert.
Questions
Is my image uploaded to a server?
No. Open developer tools, watch the Network tab, and convert a file: you will see the code and WebAssembly modules being fetched, and no request that carries your image. The AV1 decode and the JPEG encode both run in a Web Worker on your own device.
Why does my HDR photo look washed out?
Because JPEG cannot describe it. An HDR AVIF encodes brightness with a PQ or HLG transfer curve over BT.2020 primaries; a JPEG is interpreted as standard-range sRGB. Converting reads those pixels as ordinary 8-bit values, which lowers apparent contrast and saturation. No setting recovers it. Keep the AVIF for anything you want to look right on an HDR display.
Can I keep the transparency?
Not in a JPEG. An AVIF stores its alpha as a second, separate image item inside the container, and the JPEG specification has no equivalent to put it in. This tool therefore blends every non-opaque pixel onto the colour you choose before encoding, and says so in the result line when it happened. If the transparency is the point, as with a logo or a cut-out product shot, convert to PNG or WEBP instead.
How much bigger will the JPEG be?
Commonly one and a half to three times the AVIF at a comparable appearance, since you are moving from a 2019 codec to a 1992 one. The result panel reports the exact byte delta after conversion. If the size matters more than compatibility, keep the original.