Convert AVIF to JPG online, free

Where AVIF refuses to open

Operating systems were slow to add support. Windows does not preview AVIF out of the box without an add-on from the Microsoft Store, and File Explorer often shows a blank thumbnail. macOS only learned to read AVIF in Ventura, so anyone on an older Mac is stuck.

Desktop applications lag further behind. Plenty of photo editors, layout tools, and older versions of Photoshop and office suites simply do not list AVIF as a format they can import. You double-click the file and nothing happens, or the app throws an unsupported-format error.

Upload forms are the most common wall people hit. Job portals, bank verification pages, school admission sites, and marketplaces frequently accept only JPG, JPEG, or PNG. They were built before AVIF existed and have never been updated, so a perfectly good AVIF is rejected at the door.

Phones and messaging apps are uneven too. Some Android galleries open AVIF, some do not. Print kiosks, older e-readers, and many TVs cannot display it. The pattern is consistent: anything more than a couple of years old, or anything that prizes broad compatibility over modern features, is a risk.

JPG has the opposite reputation. It is thirty years old and there is essentially no device, app, or form on earth that cannot read it. Converting AVIF to JPG trades the new format's efficiency for that universal reach.

What you trade away in the conversion

The first trade is size, and it goes the wrong way. Because AVIF is more efficient than JPG, the JPG you get out is usually larger than the AVIF you put in, often by two to three times. A 150 KB AVIF might become a 350 KB JPG. That is not a bug; it is the price of a format that more software understands.

The second trade is transparency. JPG cannot store a transparent pixel, so any see-through areas in your AVIF are flattened onto white. For a normal photo there is nothing to lose. For a graphic meant to float over a coloured background, the transparency disappears and you get a white box, so keep those as PNG or WebP.

The third trade is colour depth. AVIF can hold high dynamic range and a wide colour gamut, letting bright highlights and saturated colours look more vivid on capable screens. JPG is standard dynamic range and eight bits per channel. Converting a true HDR AVIF to JPG tone-maps it down, and a very vivid image can look a touch flatter as a result.

For the vast majority of files, none of these trades matters. Most AVIFs in the wild are ordinary photos with no transparency and no HDR, and the only practical change is a larger, universally readable JPG. The honest summary is simple: you give up some bytes and a few advanced features to gain a file that opens anywhere.

When converting to JPG is the right call

An upload form that rejects AVIF is the clearest case. If a portal demands JPG or JPEG and you only have AVIF, conversion is the only way through. Run the file through here, get a JPG, and submit it. If the form also caps the size, the sibling compress-to-size tool can land the JPG under a specific KB limit afterwards.

Sharing with someone on older software is the next. You download an AVIF from a website to email to a colleague, but they are on an older Mac or a locked-down work laptop that cannot open it. A JPG sidesteps the whole problem because their machine already reads it.

Editing in an app that will not import AVIF rounds it out. If your photo editor, slide tool, or document app refuses the format, convert to JPG first and bring that in instead. You lose the alpha channel if there was one, but you gain a file the editor actually accepts.

The common thread is destination, not preference. AVIF is the better format to keep for the web. JPG is the format you reach for the moment a real piece of software or a real form has to read the file and cannot handle anything newer.

When you should keep the AVIF instead

If the file is bound for a modern website you control, keep it as AVIF. Current browsers decode it, it loads faster than JPG, and converting to JPG would only make your pages heavier for no benefit. Serving AVIF with a JPG fallback is the standard modern pattern.

If the image needs its transparency, do not flatten it into JPG. Convert the AVIF to PNG for a lossless transparent copy, or to WebP for a smaller transparent copy. Both keep the alpha channel that JPG throws away.

If the picture is a flat graphic, logo, or screenshot full of crisp text, JPG is a poor fit because its lossy compression softens hard edges. PNG or WebP keep those edges clean. AVIF itself also handles flat graphics well, so often the best move is to leave it alone.

The rule of thumb: convert to JPG for compatibility, and only for compatibility. If nothing is forcing your hand, the newer format is usually the one worth keeping.

Quality settings and how the conversion works

Because JPG is lossy, the quality slider controls how much detail survives the re-encode. imgkilo defaults to quality 90 for AVIF to JPG, which keeps the result visually identical to the source for photos while holding the file reasonably small.

Push quality to 92 or higher if the image is destined for print or a high-resolution display, where every bit of detail counts. Drop it to 80 to 85 only if you need extra compression for a slow connection or a tight upload limit and can accept faint softening on hard edges.

Under the hood, your browser decodes the AVIF into raw pixels, those pixels are drawn onto an HTML canvas at full resolution, and the canvas is encoded as JPG. Transparent pixels are painted onto white first, since JPG needs a colour for every pixel. The whole pipeline runs locally, so the original AVIF and the new JPG both stay on your device.

One habit worth keeping: convert from the original AVIF once, at the quality you want, and keep that JPG. Re-encoding a JPG to JPG repeatedly degrades it a little each pass, so going straight from the source avoids stacking up losses.

Converting a folder of AVIF files at once

Image CDNs and modern cameras now hand out AVIF in bulk, so you rarely have just one. Drop a whole folder onto imgkilo and every file is converted in parallel using a worker pool in your browser, then bundled into a single ZIP of JPGs with the original names preserved.

Up to 100 files at 50 MB each go in one batch. A set of twenty web-sized AVIFs converts in a few seconds; larger photographic files take a little longer because each one is fully decoded and re-encoded, but the work is spread across your machine's cores rather than queued one at a time.

Because nothing uploads, batch size is limited only by your device's memory, not by a server quota or a paid plan. There is no per-file fee, no watermark, and no cap on how many batches you run. When the first ZIP finishes downloading, the queue is ready for the next folder.

If you need the JPGs at a specific size for a form, convert here first, then send the results through the compress-to-size tool, which iterates quality to hit an exact target like 100 KB or 200 KB per file.