Convert JPEG XL to AVIF
Drop a JPEG XL file below and get a AVIF back. The conversion happens on your own machine, so nothing is uploaded and there is no size or quantity limit beyond what your browser can hold in memory.
Drop images here
Ctrl/⌘ VPaste a screenshot or copied image
Accepts JPEG XL
Lower means a smaller file. 75 is a good default for photos.
100% in your browser Files are never uploaded.
Why convert JPEG XL to AVIF?
Plenty of websites, content management systems and older desktop programs reject JPEG XL uploads outright. AVIF is accepted just about everywhere, and that alone accounts for most of these conversions.
Both formats are lossy. Every re-encode discards a little more detail, so it is worth starting from the original rather than from a copy that has already been through this a few times.
Both of these are current-generation formats with comparable ambitions, and on pure compression they are close enough that the choice rarely comes down to efficiency. What separates them today is deployment: AVIF is in every major browser by default, and JPEG XL is not. That single fact is usually the whole reason for this conversion.
Before you convert
Deployment, not quality, is what you are buying
AVIF got into browsers because AV1 was built royalty-free by an industry alliance that included the browser vendors themselves. JPEG XL had no such backing and has spent years waiting — Chrome only shipped a decoder in early 2026 and still keeps it behind a flag. The formats are technically peers; their fortunes differ for reasons that have nothing to do with image quality.
This is still a re-encode
Despite both being modern, there is no shortcut between them: the image is decoded and encoded again. If the source was lossy JXL, this is a second lossy pass and some detail goes. If the source was a lossless JPEG repack, converting to lossy AVIF discards both the losslessness and the ability to reconstruct that original JPEG — worth pausing on if the file came out of an archive.
Most features survive the trip
Unlike a step down to JPEG, this conversion keeps nearly everything: transparency, high bit depth and HDR are all supported on both sides. What you lose is encoding speed — AV1 searches hard and takes noticeably longer than JXL — and, if the source animated, everything after the first frame, since this is a still image converter.
What carries over
- Transparency
- High bit depth and HDR
- Default support in every major browser
What does not
- Encoding speed
- A little detail, if the source was lossy
- Reversibility, if the JXL repacked a JPEG
JPEG XL vs AVIF at a glance
| Property | JPEG XL | AVIF |
|---|---|---|
| Compression | Lossy | Lossy |
| Transparency | Yes | Yes |
| Typical file size | 45-60% of an equivalent JPEG | 40-55% of an equivalent JPEG |
| Compatibility | Safari and recent Chrome; still uncommon elsewhere | All current browsers; some older desktop apps lag behind |
| Usually comes from | Long-term archives and photography workflows | Websites optimising page weight |
Frequently asked questions
Are my JPEG XL files uploaded anywhere?
No. The decoder and encoder are WebAssembly modules that run inside this page. The network tab may show a codec downloading the first time you use a format, but no request contains your file. On supported browsers, a codec that has already been used is cached so the same conversion can work offline.
Is there a file size or quantity limit?
There is no limit imposed by us. The practical ceiling is your device’s memory, since the image has to be held uncompressed while converting. On a typical laptop, images up to around 100 megapixels convert without trouble.
Will converting to AVIF lose quality?
AVIF is a lossy format, so some data is discarded. At the default quality setting the difference is not visible at normal viewing sizes. If you need an exact copy of the pixels, choose PNG instead.
Does it work on a phone?
Yes. The same WebAssembly modules run on mobile browsers. Conversion is slower than on a desktop because phone CPUs are weaker, and very large images are more likely to hit memory limits.
What produces JPEG XL files?
Mostly archiving workflows and photography software that adopted it early. It is not something a camera or phone hands you. If you have one, it most likely came from someone deliberately choosing it for storage quality.
Where does AVIF actually work?
Every major browser decodes AVIF natively, so it is safe for use on the web. Desktop applications lag further behind — plenty of image viewers and editors still cannot open it. Encoding is also noticeably slower than the other formats here, so expect a large image to take a few seconds.