Convert AVIF to JPG

• Decodes the .avif with the browser's own decoder and writes those pixels as JPEG at quality 80.
• Flattens any see-through area onto white, or onto the colour set beside the button, before the JPEG is written.
• Hands back 8-bit sRGB samples, so a 10- or 12-bit source arrives at the depth every JPEG has.

• Nothing is resampled: the JPG carries the width and height the AVIF recorded.
• Nothing stored around the picture travels — no capture fields, no colour profile, no print resolution.
• An animated AVIF is turned away before any decoding starts, so no single frame is quietly kept.

1. Add the .avif file. Drop it on the panel above or press Browse files. The pair is fixed, so the panel takes AVIF and turns away anything else at the moment it is chosen.
2. Pick what sits behind the see-through parts. JPEG has no alpha channel, so anything transparent has to land on something. White is the default; black and a colour picker sit beside it for the files where white is wrong.
3. Press Convert to JPEG. Your browser decodes the picture and the JPEG encoder the page downloaded writes it at quality 80. Both halves run here, in this tab, on the machine in front of you.
4. Download the .jpg and read the weight. It will almost certainly be heavier than the file that went in. The panel prints both figures side by side so the jump is not a surprise later.

When a site offers AVIF to a browser that says it can read AVIF, and you right-click a picture and save it, what lands in your downloads folder is whatever was served. Image delivery networks do this per visitor, from a single URL, so the format you end up with was decided by a negotiation between two machines rather than by anyone who published the page.

Other routes lead to the same place: a content system that rewrites everything on ingest will hand one back to the person who supplied a JPEG. However it got there, the file is not broken: it is an ordinary picture at ordinary dimensions that displays perfectly in the browser it arrived through.

• Desktop photo editors. Support is arriving, but a copy more than a couple of years old will not have it, and several of the smaller editors have none at all.
• Print. Photo labs, kiosk machines and the counter at a print shop accept a short, conservative list of formats, and this one is rarely on it.
• Upload forms — job applications, marketplaces, government portals. Most name JPG and PNG and stop there, and the error they give is usually no help.
• Documents and slide decks that somebody else will open on an older machine, where the picture turns into an empty placeholder rather than an error.
• Older operating systems and their file managers. A folder full of files with no thumbnails is normally the first sign of what you are holding.

The browser hands its decoder's output over as plain 8-bit sRGB samples and the JPEG encoder writes those. That is the whole transaction, and it settles every question below before the button is even pressed.

• Depth. AVIF can hold 10 or 12 bits a channel. The decode returns 8, which is all a JPEG could have stored in any case, so nothing is lost twice.
• Colour. A wide-gamut or HDR picture is normalised to ordinary sRGB by the browser before this page sees a pixel, so the .jpg matches the picture on an ordinary screen rather than what the master held. On a wide-colour or HDR screen, the original may have looked richer than the download.
• Metadata. Nothing that sat around the picture survives: no capture date, no camera, no coordinates, no XMP packet, no embedded profile, no print resolution.
• Transparency. JPEG has no alpha channel, so see-through pixels are filled in first. When that is the part you needed, take AVIF to PNG instead.

This conversion runs against the grain. AVIF exists because it beats JPEG at the same visible quality, so undoing it spends bytes rather than saving them, and a file arriving several times heavier than the one that went in is the ordinary outcome rather than a fault. The gap widens with the size of the picture.

What you are buying with those bytes is somewhere to use the file. If the destination caps the weight as well as naming the format, convert here first and then take the .jpg through the compressor, so the size search is run against the file you are actually going to hand over rather than against the one before it.

No AVIF decoder ships in this site's code, and that is a decision rather than an omission: a WebAssembly one is a heavy download that does a worse job than the decoder already installed a few millimetres away. The conversion therefore works exactly where your browser does, and nowhere else.

This site supports Chrome 111, Firefox 111 and Safari 16.4 and later. Where Resizo cannot open an AVIF in the browser at hand, the panel says so the moment the file is added, rather than leaving the conversion to fail halfway through.

• One file per run, up to 20 MB. For a folder, the bulk converter takes AVIF files too and writes them as JPEG, PNG or WebP.
• Quality is fixed at 80 and no byte target can be set here, so a .jpg that has to fit a size ceiling needs a pass through the compressor afterwards.
• An animated AVIF is refused outright. Nothing on this site exports its frames, and taking the first one without being asked would be a substitution rather than a conversion.
• A browser with no AVIF support of its own cannot be helped from here, because the decoder belongs to the browser rather than to this page.