Convert AVIF to JPG in your browser

AVIF is the newest image format on the web, which is why so little outside a browser will open one. This gives you the format everything opens.

AVIF
No AVIF selected
Drop a file to start
Drop AVIF files here

or browse your device. Everything is processed on this device

No AVIF to hand?

How to convert AVIF to JPG

01
Drop the AVIF files

One or a hundred. They are decoded in this tab by the same code your browser uses to display them, and never uploaded.

02
Check the quality

82 is a safe default for a file that has already been compressed once. Drag the divider to compare before and after.

03
Save the JPG

The download is a .jpg, which every editor, phone, print shop and upload form accepts without argument.

What is an AVIF, and why can nothing open it?

AVIF is an image format built on the AV1 video codec, published in 2019. It compresses photographs harder than anything else in common use, typically well below JPEG and meaningfully below WebP at matching quality, which is why sites have started serving it and why you have ended up with one.

Support outside the browser is another matter. Browsers have all read AVIF for a few years, but a great deal of desktop software, most print workflows, plenty of upload forms and a lot of internal tooling still refuse it. That gap is the whole reason this page exists, and it is closing, slowly.

JPG is the format on the other side of that gap. It is thirty years old, universally supported, and for a photograph the quality difference at sensible settings is invisible. The cost is size: expect the JPG to be noticeably bigger than the AVIF was, because you are trading a very modern codec for a very old one. That is the trade you came here to make.

AVIF to JPG FAQ

Why is the JPG bigger than the AVIF?

Because AVIF is a much better compressor. It is built on a modern video codec and stores a photograph in well under what JPEG needs for the same visual quality. Converting to JPG buys compatibility and pays for it in bytes, usually somewhere between fifty per cent and double. If size matters more than compatibility, keep the AVIF.

Does converting lose quality?

A little. Your AVIF is already lossy, so this is a second lossy pass over an image that has been through one, and the two compound. That is why quality defaults to 82 here rather than the 78 the JPG compressor uses. At that setting the difference is invisible at normal viewing size.

What about transparency?

AVIF supports an alpha channel and JPG does not, so a transparent background comes out white. If the image has transparency you want to keep, convert it to PNG instead, which holds alpha the way AVIF does.

Can my browser even read AVIF?

Almost certainly, since decoding happens with the same code that displays the format, and every current browser supports it. If yours does not, the page will tell you rather than hand back something broken.

Are my AVIF files uploaded to convert them?

No. The AVIF is decoded and the JPG is written by your own browser, in this tab. There is no upload endpoint in the site for a file to go to, which you can check in your network tools: convert something and watch that no request carries it. Disconnect from the network after the page loads and it still works.

Does this remove EXIF, GPS and AI metadata?

Yes, every time, and there is no way to turn it off. The image is decoded to pixels and encoded again from those pixels alone, so EXIF and GPS, the XMP packet, embedded colour profiles, and any Content Credentials or AI-generation tags the file arrived with do not survive. There is no switch for this, because there is no way to keep them. What no compressor can remove is a watermark written into the pixels themselves, such as the invisible marks some image generators add: those survive re-encoding here and everywhere else.

Drop more files

Same format joins the queue. Anything else re-routes to its own tool.