AVIF to JPG: the picture your software refuses to open
You saved an image from a website and nothing on your computer will open it. That is AVIF. Chrome, Edge, Firefox and Safari all display it, and most image CDNs now serve it by default, which is why you ended up with one without asking for it. Older Photoshop versions, Windows Photo Viewer, print shops and a lot of upload forms still reject the extension. Nothing is wrong with your file. It just arrived in a format your tools were written before.
JPG is the one raster format with effectively universal support, so converting is the shortest path back to a picture you can email, print, or push through a form you do not control. What follows is what this converter does with your file, including the part most converter pages leave out.
Your JPG will probably be bigger than your AVIF
Every other converter promises a smaller file. On this conversion that promise is false, and it is easy to check. AVIF is a much more efficient codec than JPEG, so the same picture needs more bytes once it becomes a JPG. Here is a 2000 by 1500 photograph that arrived as a 138 KB AVIF, run through all three settings on our own server:
| Setting | JPG size | Against the AVIF |
|---|---|---|
| Best quality | 426 KB | +207% |
| Recommended | 184 KB | +33% |
| Smallest | 87 KB | -37% |
A second file, a 1200 by 900 AVIF of only 21 KB, went the same way but harder: +285%, +55%, and still +4% at Smallest. The better your AVIF was encoded in the first place, the less chance any JPG beats it. You are converting for compatibility, not to save space. If shrinking the file is the actual goal, compress the JPG afterwards, or keep the AVIF for the web and use the JPG only where AVIF is refused.
Photos come out upright
Phones store almost every picture in landscape and attach a tag saying which way to turn it. A converter that ignores that tag hands back every portrait shot on its side. Here the tag is read and applied before anything is encoded, then cleared from the output. Both halves matter: a tag left behind makes Chrome, Safari, iOS and Windows Photos rotate the already corrected photo a second time, which is how people end up with an upside down picture and no idea why.
Colours do not come back electric
Modern phones shoot in Display P3, a wider range of colour than sRGB. Dropping that profile does not convert anything. It leaves the same numbers to be read against the wrong ruler, and every saturated colour arrives oversaturated: skin goes red, skies go neon. The profile is carried into the JPG by default. If your destination ignores profiles altogether, the Colour profile setting converts the picture properly to sRGB instead of discarding the tag.
Transparent areas take the colour you choose
JPEG has no alpha channel, so a transparent background has to be filled with something. Hand a logo with clear corners to a careless converter and it often comes back with a black box behind it, which looks exactly like a broken file. White is the default here, and the colour picker next to the settings lets you set any colour you want, by swatch or by hex code. The result tells you the transparency was flattened, so a changed background is never a surprise. If you need the transparency kept rather than filled, use AVIF to PNG instead.
Which setting to pick
Best quality is for an archive copy or something heading to print, where you do not care that the file is several times larger. Recommended is the right answer for anything going on a screen, and the loss is not visible on a photograph at normal viewing size. Smallest is for email, messaging apps and anywhere a size limit is the real constraint. You can change your mind and convert again at no cost.
The file is read by its contents, not its name
Renaming a file does not change what is inside it, and people rename files constantly. An AVIF wearing a .jpg extension, or an .avif that someone saved from a browser under a different name, is identified from its own bytes and converted correctly. A greyscale AVIF converts as greyscale. An animated AVIF gives you its first frame as a still, and the result says so.
Batches keep your filenames
Convert a folder of images in one go and they come back as a single ZIP, every file under the name you sent it: photo.avif becomes photo.jpg, including Arabic, Chinese and accented filenames. One unreadable file does not ruin the run. It is skipped, named in the result with the reason, and everything else converts. The result also breaks down the before and after size of each file individually rather than giving you one total.
What you get
- A JPG that opens in software written before AVIF existed
- Photos the right way up, with the orientation tag cleared so nothing rotates them again
- Wide gamut colour kept, or converted properly to sRGB when you ask for it
- Transparent areas filled with the colour you choose, never black by accident
- The same pixel dimensions you started with, every time
- Batches returned as one ZIP under your original filenames
What's next?
Need the transparent background kept instead of filled? AVIF to PNG has a real alpha channel and keeps even partial opacity intact.
Already have the JPG and now it is too heavy for email? Compress JPEG brings the size down without changing the dimensions.
Same problem, different format? HEIC to JPG handles the iPhone version of exactly this situation.