Convert AVIF to JPG

Where the .avif on your desktop came from

You almost certainly did not choose this format. AVIF is what a modern site hands your browser when it wants its pages to load quickly, and it is therefore what appears in your downloads folder after a right-click and Save Image As. The site never asked. It looked at what your browser advertised support for, picked the smallest thing on the list, and sent that.

The format itself is an achievement. AVIF is a still frame encoded with AV1, the video codec, wrapped in the same ISO container Apple uses for HEIC. It handles transparency, wide color, ten and twelve bits per channel, and it compresses harder than anything else in general use. That is the whole reason it spread. The trouble is that browsers adopted it years before everything else did, and the gap has not closed: plenty of desktop photo viewers, older Photoshop installs, print shop intake forms, marketplace listing tools and claim portals still refuse the file outright. You have an excellent picture in a wrapper the program in front of you has never heard of.

Renaming it to .jpg does not help, and it is the first thing nearly everyone tries. The extension is only a label. Anything that actually opens the file reads the box structure at the front, finds the brand avif sitting there, and stops. Some programs report that as a damaged file, which sends people hunting for a repair utility they do not need. Nothing is damaged. The bytes have to genuinely change, which is what this page does.

Converting AVIF to JPG costs a second round of compression

This is the part worth understanding before you press the button, because no other tool in this category will mention it. AVIF is lossy. Detail was already thrown away when the file was made. JPEG is also lossy, so writing one takes a further helping out of what survived the first pass. That is a second generation, and it cannot be reversed by converting back later.

In practice, at the default quality of 82, you will not see it on a photograph. The reason to state it anyway is that people convert the same picture repeatedly across weeks, each time from whatever file they happen to have to hand, and generations stack. Keep the AVIF if there is any chance you will need another format from it later. Convert from the original, never from the last conversion.

Raising the slider does not buy quality back. Measured on this tool's own test image — an 8.2 KB AVIF at 480 by 360 — quality 82 produces a 17.5 KB JPG and quality 100 produces a 127 KB one. That is fifteen times the original file, spent faithfully reproducing compression artifacts the AVIF encoder had already baked in. There is nothing in the picture worth that. The useful direction on the slider is downward: the same image at quality 45 lands at 9.3 KB, barely above where it started.

Expect the file to grow, and check by how much first

Almost every conversion here produces a bigger file, which surprises people who assume JPEG is the compact format. It was, twenty-five years ago. AV1 is roughly twice as efficient at matched visual quality, so handing that back has a price, and the multiplier varies far more than the direction does. On the test files above: the photograph roughly doubled, and a small transparent badge went from 1.1 KB to 7.5 KB, nearly seven times over.

That spread is why a measured number appears above the button instead of a reassurance. Rather than scaling your image down and weighing the result — which would change the very density being measured — the tool samples it: a grid of crops is lifted at one-to-one from corners, edges and middle so that both the busy regions and the calm ones are represented in something like their true proportion. That sample goes through the JPEG encoder at whichever quality the slider is set to, and the cost per pixel that comes back is scaled up to the dimensions your output will have. Move the slider and the figure is recalculated, because it was never a fraction applied to your file size in the first place. If the answer is uncomfortable, cap the longest side before converting, or convert and thencompress the JPG to a specific target size, which searches for the right quality instead of leaving you to guess and re-run.

Transparency has to become a color, and the default here is white

AVIF carries a full alpha channel. JPEG has none whatsoever, so every transparent pixel needs a solid color assigned to it on the way out. When a converter does not ask, the answer it silently uses is black, because an unpainted canvas is black — and that is where the black rectangle around a downloaded logo comes from.

The color picker on this page appears only for files that genuinely have transparent pixels, and genuinely is doing real work in that sentence. The container's own alpha flag cannot settle the question, and neither can anything else short of decoding: once an image is drawn, the surface holds four channels whether or not the picture ever used the fourth. So the decoded pixels are scanned, and the choice is offered when the scan finds something to fill. On a fully opaque photograph no picker appears, because a control that changes nothing is worse than one that is missing.

An AVIF that moves arrives as one still frame

AVIF can hold a sequence. Such files carry the brand avis instead ofavif, and they behave much like a short silent video. JPEG holds exactly one image, so there is no version of this conversion in which the motion survives and no setting that changes it.

The brand is read out of the container before anything is encoded, so a file that moves is labeled while you can still change your mind rather than explained afterwards on a receipt. If the motion is what you actually wanted, this is the wrong page and it is better to know now.

Why there is no JPG to AVIF tool on this site

Its absence is deliberate and the reason was measured rather than assumed. Browsers write images through a canvas, and asking a canvas for AVIF was tested in both engines this site is built against. Safari's engine returns a real AVIF. Chromium hands back a PNG instead, without an error, leaving you a file that has the right name and the wrong contents.

A converter that works properly in one browser and has to refuse in the rest is not worth publishing, and the alternative — shipping a megabyte-plus AV1 encoder as WebAssembly to every visitor — is a poor trade for a conversion most people do not need. Saying so is a better answer than a page that quietly disappoints. The same reasoning is why there is no JPG to HEIC page either.

The conversion happens on your own machine

Both halves of this job already exist inside your browser. AVIF decoding is why the file previews at all when you drop it, and JPEG writing has been part of the canvas API since long before any of this. Nothing needs to travel, so nothing does: your pictures stay on your device from the moment you choose them until you save the results. Open your browser's network panel and run a conversion — after the page itself loads, the panel stays empty. The practical benefits follow from that rather than from a promise: no queue, no account, no ceiling on file size beyond the memory your device is willing to give this tab, and forty files are no more sensitive than one.

There is a cost to naming rather than discovering later. Metadata does not survive the trip. The encoder receives a grid of pixels, and nothing rides alongside it — so any EXIF block, embedded color profile, copyright field or AI-generation marker present in the AVIF is absent from the JPG. For images saved off the web that is usually the outcome you would have chosen. When the source is your own camera roll and the capture data matters, keep the originals somewhere safe before you convert. If you would rather strip metadata deliberately and keep the format, that is a different job than this one.