Why AVIF files are hard to open
AVIF is built on the same codec as AV1 video and is the most efficient image format in wide use: the same picture is typically about half the size of a JPG, and still smaller than WebP. Browsers have handled it for years, but the rest of the software world has not caught up — desktop photo editors, office documents, chat apps and upload fields routinely refuse an .avif file.
This converter works in your browser, so the image is never sent anywhere. Everything runs on the device you are already using, which is also why it is instant: no upload, no queue, and no second download of a processed copy.
AVIF or JPG: what you gain and lose
Where AVIF files come from
AVIF is turning up in the same accidental way WebP did a few years ago: saved from a site that switched to it for performance, exported by an image pipeline, downloaded from a service that now ships AVIF by default, or captured by a phone set to the most efficient format. The file is an ordinary photograph — only the container is unfamiliar.
The mismatch sits on the other side of the wire. Browsers gained AVIF decoding years ago, so the picture displays perfectly on a website and then refuses to open the moment it lands on a desktop. That is why a file which was visible a second ago suddenly appears to be broken, and why the fix is a format change rather than a repair.
How to convert AVIF to JPG
- 1
Add the AVIF files
Up to 20 at a time, each up to 50 MB. Your browser decodes them on your own device, so nothing is uploaded and nothing waits in a queue.
- 2
Set the quality
The slider defaults to 90%, where the second encoding pass is invisible at normal size. Raise it for fine detail — and expect the JPG to be larger than the AVIF regardless.
- 3
Download the JPGs
Each file comes back at its original pixel dimensions, with a white background wherever the AVIF was transparent.
Other things you can do with the image
Frequently asked questions
Which browsers can decode the AVIF files I drop in?
Chrome 85+, Edge 85+, Firefox 93+ and Safari 16.4+. Older browsers cannot decode AVIF at all — if yours is one of them, the tool says so plainly instead of producing a broken file.
Does the quality change?
AVIF is already lossy, so the picture is re-encoded a second time. At the default 90% the difference is not visible at normal viewing size; use 100% for images with fine detail or small text.
What happens to transparent AVIF images?
AVIF supports transparency and JPG does not, so transparent areas are filled with white before the file is written. A cut-out subject therefore gets a white backdrop. Use a PNG if the alpha channel has to survive.
Will the JPG be bigger than the AVIF was?
Almost always, often two to four times bigger. AVIF compresses far more efficiently than JPG. The reason to convert is compatibility, not file size.
Are my images uploaded to a server?
No. Your browser decodes the AVIF and re-encodes it as JPG inside a Web Worker on your own device. There is no upload step, so no copy of the image exists on our side.
Can I convert several AVIF files at once?
Yes — up to 20 files per run, each up to 50 MB, processed one after another on your device.
Is AVIF better than WebP or JPG?
On file size it is the best of the three. AVIF is built on the same codec as AV1 video, lands typically 20–30% smaller than WebP and around half the size of a JPG at matched quality, and it supports transparency. Where it loses is support and speed: encoding takes noticeably longer, and desktop software has been slow to catch up. AVIF is the right format for images you deliver yourself; JPG is the right format for images somebody else has to accept.
Does converting to JPG bring back the detail AVIF discarded?
No. Both formats are lossy, and once AVIF has thrown information away it cannot be recovered — converting only re-describes what is left in a less efficient container. Treat the JPG as a compatibility copy, keep the AVIF if it is the original, and avoid converting back and forth, because every pass adds another generation of loss.
What if my browser cannot open the AVIF at all?
Then the tool says so instead of producing a broken file. AVIF decoding needs Chrome 85+, Edge 85+, Firefox 93+ or Safari 16.4+; on anything older the file is refused with a message rather than converted into something misleading. Doing the conversion in a current browser is the way round it — nothing about the image itself needs to change.