Convert AVIF to JPEG XL
Drop a AVIF file below and get a JPEG XL 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 AVIF
Lower means a smaller file. 75 is a good default for photos.
100% in your browser Files are never uploaded.
Why convert AVIF to JPEG XL?
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.
These are the two most capable image formats currently in existence, and converting between them is rarely about capability. AVIF won the deployment race; JPEG XL is generally considered the better engineering. Moving in this direction means preferring the format that is technically ahead over the one you can actually publish.
Before you convert
You are converting away from the one browsers support
AVIF is enabled by default in every major browser. JXL, as of August 2026, is not — Safari alone opens it without user intervention, Chrome 145 keeps its decoder behind a flag, Firefox behind a preference. For anything going onto a web page this direction is backwards. It only makes sense for storage, or in anticipation of Chrome's default-on, expected in the second half of 2026.
Encoding is much faster in this direction
One genuine practical advantage: JXL encodes considerably faster than AVIF. AV1's compression comes from an expensive search, and a large image can take seconds. If you are processing a large batch and encoding time is the bottleneck rather than file size, this difference is noticeable and real.
Little is lost, but little is gained either
Transparency, high bit depth and HDR are supported on both sides, so the conversion is feature-preserving. But it is still a re-encode: a lossy AVIF decoded and re-encoded as lossy JXL goes through a second generation of loss for a compression gain that, from an already-compressed source, is modest. Unless you specifically need JXL, this often is not worth the pass.
What carries over
- Transparency
- High bit depth and HDR
- Faster encoding than AVIF
What does not
- Default browser support
- A little detail — a second lossy pass
- Animation, if the source had any
AVIF vs JPEG XL at a glance
| Property | AVIF | JPEG XL |
|---|---|---|
| Compression | Lossy | Lossy |
| Transparency | Yes | Yes |
| Typical file size | 40-55% of an equivalent JPEG | 45-60% of an equivalent JPEG |
| Compatibility | All current browsers; some older desktop apps lag behind | Safari and recent Chrome; still uncommon elsewhere |
| Usually comes from | Websites optimising page weight | Long-term archives and photography workflows |
Frequently asked questions
Are my AVIF 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 JPEG XL lose quality?
JPEG XL 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.
Where do AVIF files come from?
Almost always from a website. AVIF compresses better than anything else in wide use, so sites that care about page weight serve it. Cameras and phones do not produce it, which is why most people only meet AVIF when saving an image from the web.
Is JPEG XL ready to use?
Partly. Safari has supported it for some time and Chrome shipped stable support in early 2026, but overall coverage still sits around 15%. It is a sound choice for archiving, where compression quality matters more than universal support, and a poor one for images going onto a public website today.