Convert JPEG XL to PNG online, free

To be honest, plenty of JPEG XL files in the wild are ordinary photos with no transparency at all. For those, PNG is overkill. The transparency argument only earns its keep when the alpha channel is actually doing something, which is exactly when JPG would quietly ruin the image.

Lossless: why PNG matches a lossless JPEG XL exactly

PNG is a lossless format. It does not throw away detail to save space the way JPG does, it records every pixel exactly. So when the decoder turns your JPEG XL into raw pixels and encodes those pixels as PNG, nothing is discarded in that step. The PNG is a perfect copy of whatever the .jxl decoded to.

This matters most when the original JPEG XL was itself saved losslessly, which is one of JPEG XL's signature modes. In that case the whole chain is lossless: the .jxl held every original pixel, and the PNG keeps every one of them. Convert that same file to JPG and you would bake in a permanent, if subtle, loss that PNG avoids entirely.

Because of this there is no quality slider for JPEG XL to PNG, and there should not be. There is no detail to trade away, so there is no knob to turn. If you have ever seen a converter ask you to pick a PNG quality, it was either compressing colours behind your back or secretly handing you a different format.

Lossless also means crisp edges survive. JPG smears the hard boundaries you find in logos, line art, and text on a screenshot into faint halos. PNG keeps every edge razor sharp. So if your .jxl is a diagram, an icon, or a UI capture full of small type, PNG is not just compatible, it is genuinely the higher-fidelity result.

The honest cost: PNG files are big

Here is the trade, stated plainly. PNG is one of the least space-efficient image formats, and JPEG XL is one of the most efficient. So the PNG you get out is usually a lot larger than the .jxl you put in. For a photograph the difference is often several times over. A small JPEG XL photo can balloon past a megabyte as PNG.

That is not a flaw in the tool, it is the nature of lossless. PNG stores every pixel, and photographs have millions of subtly different pixels, so there is little for PNG's compression to grip. Flat graphics are a different story: a logo with a handful of solid colours compresses very well as PNG, so the size penalty there is small. PNG was designed for exactly that kind of image.

This is the most important reason to think before you convert. If your .jxl is a normal photo with no transparency, PNG is the wrong target; you would pay a big size penalty for a lossless copy you do not need. In that case convert it to JPG instead, which is far smaller and opens just as widely.

If you do need PNG but the file comes out heavier than you would like, you can shrink it afterward. Compress the PNG to re-pack the pixels without any visible loss, or if you need to hit a hard upload limit, run it through the compress-to-size tool to land under a specific KB target.

Why your JPEG XL will not open

The browser story is the big one. Chrome added JPEG XL behind a flag and then removed support in 2023, so current Chrome cannot display a .jxl at all. Firefox only decodes it in Nightly builds behind a setting most people never enable. That covers most desktop browsers, none of which will show your file.

Apple is the exception. Safari has decoded JPEG XL since version 17 on recent macOS and iOS, so the file may open there while failing on the next device. That uneven support is part of why JPEG XL is so confusing in practice, and why a reliable converter is useful.

Operating systems and creative apps lag. Recent Windows 11 builds added JPEG XL support, but older Windows needs a codec add-on, and many image editors, layout tools, and office suites still do not list .jxl as a format they can import. You drag the file in and the app shrugs.

Upload forms are the most common wall, and here the transparency angle bites hardest. A design portal or asset library may demand PNG specifically because it needs the transparent background your .jxl has. Those forms accept PNG, JPG, or JPEG only, so a perfectly good transparent JPEG XL is rejected at the door. PNG, by contrast, has been a staple since the 1990s and opens essentially everywhere.

When PNG is the right call, and when JPG wins

Choose PNG when transparency matters. A logo, an icon, a product cut-out, a sticker, anything meant to float over a coloured background needs its alpha channel, and PNG is the lossless, universally-readable way to keep it. If a form or app explicitly asks for a PNG, that is also your answer with no further thought.

Choose PNG when the .jxl is lossless or has crisp edges. Screenshots, diagrams with text, line art, and UI mockups all have hard boundaries that JPG softens, and a lossless source deserves a lossless destination. PNG keeps them sharp, and because these images use limited colours, the file size stays reasonable.

Choose JPG when the image is an ordinary photo with no transparency. This is the honest counterweight to the whole page: photos have no alpha to protect, so the only thing PNG buys you there is a much bigger file. Convert that photo to JPG instead, which is far smaller and opens everywhere PNG does.

The rule of thumb: PNG for transparency, lossless files, logos, icons, screenshots, and anything a form names by extension. JPG for photographs. If you are not sure whether your .jxl has transparency, simply try the PNG output, the see-through areas will show on a checkered background.

How the conversion works

imgkilo carries its own JPEG XL decoder, a WebAssembly build of the reference libjxl decoder. It reads the .jxl bytes directly, so the conversion does not depend on your browser being able to display JPEG XL. This is what makes it work in Chrome and Firefox, which cannot open the format on their own.

Once decoded, the image lives as raw pixels. Those pixels, alpha channel and all, are drawn onto an HTML canvas with no white fill behind them, then encoded as a PNG. Because both the decode and the PNG encode are lossless, the result is an exact copy of whatever the JPEG XL contained.

Everything runs locally in the tab you already have open. The original .jxl and the new PNG both stay on your device; nothing is uploaded, nothing is stored online, and there is no account to create. You can confirm it in your browser's Network panel.

If the resulting PNG is heavier than you need, remember it is lossless by design. Send it through the compress-PNG tool to re-pack it, or the compress-to-size tool if a form imposes a hard KB limit.

Converting a folder of JPEG XL files to PNG at once

Asset exports and archives rarely come as a single file, so the tool is built for the batch. Drop a whole folder of .jxl files and every one is decoded and re-encoded to PNG in parallel using a worker pool in your browser, with the alpha channel preserved on each, then bundled into a single ZIP with the original names kept and the new .png extension applied.

Up to 100 files at 50 MB each go in one batch. A set of transparent icons converts quickly because flat graphics decode and encode fast. Photographic JPEG XL files take a little longer and produce much larger PNGs, but the work spreads across your machine's cores rather than queuing one file at a time.

Because nothing uploads, batch size is bounded only by your device's memory, not a server quota or a paid tier. There is no per-file fee, no watermark, and no cap on how many batches you run. Just bear in mind that PNGs are heavy, so a folder of large photos will produce a sizeable ZIP, one more reason to send true photos to JPG instead.

If you have a mixed folder of formats, not just JPEG XL, the bulk image converter handles the whole drop and lets you pick one output for everything. And if the resulting PNGs need to fit a specific limit, the compress-to-size tool iterates until each file lands under your target.