Convert JPEG XL to JPEG
Drop a JPEG XL file below and get a JPEG 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 JPEG?
Plenty of websites, content management systems and older desktop programs reject JPEG XL uploads outright. JPEG is accepted just about everywhere, and that alone accounts for most of these conversions.
Expect the JPEG file to come out larger than the JPEG XL you started with. That is the price of the broader compatibility and simpler decoding JPEG gives you.
JPEG XL can carry transparency; JPEG cannot. Transparent pixels are composited onto white during conversion, so a logo with a see-through background will come out sitting on a white rectangle.
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.
You have a .jxl and you need something that opens everywhere. JPEG is the safest destination there is. What that costs you depends entirely on where the JXL came from — and in one specific case, it costs nothing at all.
Before you convert
If the JXL was made from a JPEG, the original is still in there
JXL's lossless JPEG repacking is reversible by design: a JXL created that way can be turned back into the exact original JPEG, byte for byte. Nothing is re-encoded and nothing is lost, because the JPEG data was never altered, only stored more efficiently. If your file came out of an archive-shrinking workflow, this conversion is simply unpacking it.
If it was authored as JXL, this is a normal lossy conversion
A JXL encoded from a camera file or an editor is not carrying a JPEG inside it, so the conversion re-encodes the picture and the usual rules apply: expect a larger file, because JPEG is far less efficient, and expect some detail to go. Quality around 85 to 90 is the sensible range; pushing to 100 inflates the file without a visible return.
Depth, transparency and animation all stop here
JXL supports high bit depth, wide colour, an alpha channel and animation. Baseline JPEG supports none of those. HDR material comes out flattened to standard range, transparency gets filled with white, and anything moving arrives as a single frame. If any of those matter, PNG or WebP will carry more of the file across.
What carries over
- Universal compatibility
- The exact original, if the JXL repacked a JPEG
What does not
- High bit depth and HDR
- Transparency and animation
- Compression efficiency
JPEG XL vs JPEG at a glance
| Property | JPEG XL | JPEG |
|---|---|---|
| Compression | Lossy | Lossy |
| Transparency | Yes | No |
| Typical file size | 45-60% of an equivalent JPEG | 100% of an equivalent JPEG |
| Compatibility | Safari and recent Chrome; still uncommon elsewhere | Opens everywhere, including decades-old software |
| Usually comes from | Long-term archives and photography workflows | Digital cameras and photo sharing |
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 JPEG lose quality?
JPEG 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.
What quality setting should I use?
For photographs, 75 to 85 is the range where most people cannot tell the result from the original at normal viewing size. Below about 60 you start seeing blocky artefacts around sharp edges. Above 90 the file grows quickly in exchange for very little visible gain.