Convert JPEG to JPEG XL
Drop a JPEG 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 JPEG
Lower means a smaller file. 75 is a good default for photos.
100% in your browser Files are never uploaded.
Why convert JPEG to JPEG XL?
For the same picture, JPEG XL usually lands well under the size of the JPEG original. That matters when you are trimming page weight or squeezing under an upload limit.
JPEG XL supports an alpha channel, so you can cut out a background after converting. The conversion itself will not invent transparency that the JPEG file never had.
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.
This conversion is unlike every other one on this site, and it is worth understanding why before you judge it by the usual standards. JPEG XL can take an existing JPEG and repack it losslessly — not re-encode it, repack it — coming out around 20 percent smaller with the original JPEG recoverable byte for byte, metadata and all. There is no quality decision to make and nothing is thrown away.
Before you convert
Why this is possible at all
JPEG XL's coding tools are a superset of JPEG's. That means it can express everything a JPEG contains and then apply better entropy coding on top — asymmetric numeral systems in place of Huffman, smarter prediction of DC coefficients. The picture is not touched; only the way it is written down changes. This is the one case in image conversion where "smaller" and "identical" are both true at the same time.
You cannot ship the result yet
As of August 2026, Safari is the only browser that opens a JXL out of the box. Chrome 145 shipped a decoder in February but keeps it behind a flag, with default-on expected in the second half of the year; Firefox 152 is in the same position behind image.jxl.enabled. Browsers that decode JXL without the user doing anything cover roughly 14 percent of visitors — which becomes 85 to 90 percent the day Chrome flips the switch. Until then, JXL is a storage format, not a delivery format.
Where it genuinely pays off today
A photo archive. If you are holding tens of thousands of JPEGs on a disk or in object storage, this takes a fifth off the bill with no quality decision, no one-way risk and full reversibility — you can turn any of them back into the exact original JPEG whenever you need to. That is a genuinely rare proposition, and it does not depend on any browser shipping anything.
What carries over
- Every pixel, bit for bit
- All metadata, including encoder quirks
- The ability to reconstruct the exact original
What does not
- About 20 percent of the file size
- Nothing else — this is the point of it
JPEG vs JPEG XL at a glance
| Property | JPEG | JPEG XL |
|---|---|---|
| Compression | Lossy | Lossy |
| Transparency | No | Yes |
| Typical file size | 100% of an equivalent JPEG | 45-60% of an equivalent JPEG |
| Compatibility | Opens everywhere, including decades-old software | Safari and recent Chrome; still uncommon elsewhere |
| Usually comes from | Digital cameras and photo sharing | Long-term archives and photography workflows |
Frequently asked questions
Are my JPEG 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.
Will converting from JPEG lose more quality?
A little, if the target is also lossy. The JPEG you start with has already discarded data, and a second lossy encode discards a bit more. At quality 80 or above that second loss is hard to spot, but it is exactly why you should keep the original rather than converting the same file back and forth.
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.