JPG to AVIF Converter

This tool converts JPG photos to AVIF right in your browser, and AVIF usually lands at about half the size of the JPG with no difference your eye can catch. Free, no sign-up, one photo or a whole batch of them.

So why use this one over the dozens of other JPG-to-AVIF sites? Almost all of them upload your photo to a server, convert it there, and send it back. To make a file smaller, you end up handing a private image to a stranger's computer. That has always bugged me. Here the entire conversion runs on your own device, so nothing is uploaded, nothing is stored, and there is no queue to wait in. As a bonus it strips the GPS location and camera metadata out of the file on the way through, so the AVIF you download is not quietly broadcasting where you were standing when you took the shot.

1. Drop your JPGs onto the box, or click to browse, or paste an image straight from your clipboard. One file or a couple hundred, it does not care.
2. Leave the quality slider where it is unless you have a reason not to. The default is tuned to keep the photo looking untouched while still shrinking it hard. Push it up toward 100 for a fussy, detailed shot, or drop it lower when you want the smallest possible file and can live with a hair less fidelity.
3. Need to fix orientation while you are here? The rotate and flip buttons straighten or mirror the image in the same pass.
4. Click Convert. Every file shows its old size next to its new one, so you can see exactly what you saved.
5. Download each AVIF on its own, or grab the whole set as one ZIP when you converted a stack.

Uploading a photo just to shrink it is backwards, and it is worth being clear about why. When you drop a JPG on a typical online converter, that file travels across the internet to a machine you do not control, sits in some company's storage for a length of time you cannot verify, and comes back. For a holiday snap you might shrug. For a screenshot of a document, a photo of your kid, or a picture with your house in the frame, that is a handoff you never needed to make.

This converter never makes it. The JPG is read and re-encoded inside the browser tab, on your own processor. Pull the network cable before your first conversion, though, and you get an error rather than an AVIF, so it does not work offline, and on this tool that first fetch is a heavier ask than on any other page here. The AVIF encoder is the reason: it ships as two builds of 3,534,665 and 3,485,872 bytes, by a wide margin the heaviest thing on this site, and no page loads that up front. It comes down on your first press of Convert, along with a 166,470-byte JPEG reader, and the built export confirms neither one arrives with the page. Your photo still never enters the loop, because what gets fetched is a piece of this page.

The metadata piece is the part most converters skip, and it is the one I would actually check for. Your camera and phone bake a lot into a JPG that has nothing to do with the picture: the exact GPS coordinates where you stood, the date and time, the phone or camera model, sometimes a serial number. Post that JPG straight to the web and anyone who downloads it can read your location out of it. Converting to AVIF here clears all of that automatically. What you get back is the pixels and nothing else, which is exactly the state you want a photo in before it goes anywhere public.

AVIF is the newest widely-supported image format on the web, built on the AV1 video codec, and it compresses hard. For a typical photo, expect it to come out 30 to 50 percent smaller than the JPG, and on images with big smooth areas like skies or skin it can go past 80 percent, all while looking the same at a normal viewing size. If your site is heavy with photos, swapping JPG for AVIF is one of the biggest single wins you can get on load time, and it feeds straight into your Core Web Vitals.

Now the honest part, because you should know what this does and what it does not. Your JPG was already compressed once when it was first saved, and it threw away some detail then that is gone for good, and no amount of AVIF will bring it back. What it does is store whatever is left far more efficiently, so you get the same-looking photo in a much smaller file. It will not look better than the JPG did, it will match it. So feed it the best original you have. Convert an already-tiny, already-mangled thumbnail hoping for magic and you just get a small blurry AVIF instead of a small blurry JPG.

One more thing AVIF can do that JPG never could: it holds transparency, and that half carries straight through here. The wider color range and the higher bit depth are real features of the format and this converter does not reach them. It works in 8 bits per channel and writes no color profile, so a wide-gamut or HDR master should be encoded by whatever produced it. Drop one in anyway and the tool names the profile it had to leave behind.

A few things worth knowing. If you have a stack of JPGs, drop them all in at once and take the ZIP at the end, it is far quicker than doing them one at a time. AVIF encoding leans on your processor more than saving a JPG does, so a big batch runs a few seconds per image rather than being instant. That is what the smaller files cost you, and for most work it is a price worth paying.

On browser support, AVIF works in every current browser, Chrome, Firefox, Edge, and Safari 16 and up, which is nearly everyone online. If you are publishing to the public web and a slice of your visitors might be on some ancient setup, keep a JPG copy around to serve as a fallback. For a modern site, an app, or your own storage, AVIF on its own is fine. And hold onto your JPG originals if they matter, use the AVIF as the lightweight copy you actually ship or store.