Convert PNG to JPEG XL
Drop a PNG 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 PNG
Lower means a smaller file. 75 is a good default for photos.
100% in your browser Files are never uploaded.
Why convert PNG to JPEG XL?
For the same picture, JPEG XL usually lands well under the size of the PNG original. That matters when you are trimming page weight or squeezing under an upload limit.
PNG has been the default lossless format for thirty years and it is showing its age — its compression was designed in an era of much smaller images and much slower machines. JPEG XL's lossless mode is the direct modern replacement, and on the same picture it typically produces a substantially smaller file with every pixel preserved exactly.
Before you convert
Lossless here means genuinely lossless
Unlike most conversions on this site, there is no quality slider and no judgement call. Every pixel and the full alpha channel arrive exactly as they left. The only thing that changes is how many bytes it takes to write them down. If the result ever needs to go back to PNG, it can, with nothing lost along the way.
The gain depends heavily on the content
On photographic material — where PNG has always been weakest — the saving is large. On flat-colour icons, screenshots and line art, PNG is already close to as good as lossless gets on that kind of data, and the margin narrows considerably. Do not expect one headline number to hold across a mixed library.
Storage yes, delivery not yet
As of August 2026 only Safari opens JXL without the user enabling anything; Chrome 145 has the decoder behind a flag with default-on expected later in the year, and Firefox is in the same holding pattern. That puts out-of-the-box coverage near 14 percent. As an archive format this is already a good trade. As the image you put in a page, it is premature — keep serving PNG or WebP for now.
What carries over
- Every pixel, exactly
- The full alpha channel
- The ability to go back to PNG unchanged
What does not
- A useful share of the file size
- Broad browser support, for now
PNG vs JPEG XL at a glance
| Property | PNG | JPEG XL |
|---|---|---|
| Compression | Lossless | Lossy |
| Transparency | Yes | Yes |
| Typical file size | 300-500% 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 | Screenshots, logos and graphics | Long-term archives and photography workflows |
Frequently asked questions
Are my PNG 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.
My PNG is a screenshot — anything to watch for?
Screenshots are mostly flat colour and sharp text, which is what lossy formats handle worst. If the target is lossy, text edges can pick up faint halos. Use a high quality setting, or stay with PNG if the text has to remain crisp.
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.