JPG to JPEG XL Converter
Convert JPG to JPEG XL online, free
Encode JPG to JPEG XL in your browser, far smaller at the same quality. Heads up: most apps still cannot open a .jxl yet.
Drop images here or click to upload
JPG only — up to 50MB each
- Files never leave your device
- Runs in your browser
- Free, no signup
How it works
- 1
Drop your JPG files
Drop a single JPG or up to 100 files together. For the best, most reliable savings, start from high-quality originals rather than already-small JPGs.
- 2
Pick a quality level
The default looks identical to the source for photos. Raise it for portfolio or print work; lower it for the smallest archive. JPEG XL holds quality well even when pushed.
- 3
Download JPEG XL files
Single files download immediately, batches arrive as a ZIP. Names are preserved with the new .jxl extension. Open them in Safari 17+, Photoshop, Lightroom, Affinity, GIMP or Krita.
Why move JPGs to JPEG XL, and when not to
Up to 55% smaller than JPG
JPEG XL compresses far harder than JPG at the same visual quality, so a photo library shrinks substantially. It also adds lossless, transparency, HDR and high bit depth that JPG cannot store.
Encoded in your browser, no upload
A WebAssembly build of the libjxl encoder runs entirely on your device. Your JPGs never leave the tab, and you get a real .jxl file, not a renamed JPG.
Honest about support
Chrome and Firefox cannot open .jxl yet, though Safari 17+ and editors like Photoshop and Affinity can. Best for archival, Apple, and pro workflows. Convert back to JPG anytime for universal reach.
Where this helps
Long-term photo archives
Storing a large library for years? JPEG XL keeps the same quality in far less space, and its lossless mode can preserve masters exactly, so backups cost less and nothing is lost over time.
Apple-centric workflows
If your devices or audience are on Safari 17+, macOS Sonoma+, or iOS 17+, JPEG XL already displays natively, so you get its efficiency now instead of waiting for the rest of the web to catch up.
Professional photo pipelines
Lightroom, Camera Raw, Affinity and Krita read JPEG XL, so studios can adopt it internally to cut storage while keeping HDR and high bit depth that a JPG would discard.
Future-proofing your originals
Convert from high-quality originals now and you have a modern, royalty-free file ready for when support widens, with JPGs always one conversion away whenever you need them.
Tips that help
- 1
Check that your destination can open .jxl first
Before converting in bulk, confirm the software or people receiving the files can read JPEG XL. Chrome and Firefox cannot yet; Safari 17+, Photoshop, Lightroom, Affinity, GIMP and Krita can.
- 2
Encode from high-quality originals
Re-encoding an already-small JPG may not shrink it much, because the detail is gone. Start from the best version you have to get JPEG XL's full size advantage.
- 3
This is a re-encode, not the lossless JPEG transcode
The reversible, ~20% lossless JPEG-to-JXL recompression needs the cjxl command-line tool. This browser tool does a normal quality-based encode, which is what most people actually want.
- 4
Keep your JPGs as a fallback
Until JPEG XL opens everywhere you need, hold on to the original JPGs. You then have the efficient archive and a universally readable copy side by side.
- 5
Need it to open anywhere? Convert back
If a .jxl needs to go somewhere that cannot read it, run it through the JPEG XL to JPG or PNG tools, which decode it in your browser and hand back a universal file.
JPG to JPEG XL: a smaller, more capable, future-proof file
JPEG XL is the format JPEG was meant to grow into. Standardised by the same committee as ISO/IEC 18181, it stores the same photo in far fewer bytes than JPG, adds a true lossless mode, transparency, HDR and high bit depth, and is completely royalty-free. The one honest catch is adoption: most software, including Chrome and Firefox, cannot open a .jxl file yet, so this is a format for archival, Apple and professional photo workflows, and future-proofing rather than for everyday sharing. This guide explains what you gain, who can actually open the result, exactly what this converter does and does not do, and how to choose a quality setting. imgkilo encodes JPEG XL in your browser, with no upload and no signup, on batches of up to 100 files.
What JPEG XL gives you over JPG
JPEG XL was designed decades after JPG, with all the compression research that happened in between. At the same visual quality it is typically much smaller, the project cites up to 55 percent smaller than JPG, so the same library of photos takes far less space.

It is also more capable. JPG is lossy-only, 8-bit, and cannot store transparency. JPEG XL adds a genuine lossless mode, an alpha channel, high dynamic range, wide colour, and up to 32 bits per channel. One format covers photographs, flat graphics, and archival masters where JPG needed several.
Crucially, it is royalty-free and open, built on the libjxl reference implementation under a permissive licence. That removed the patent worries that slowed earlier formats, which is a large part of why archives, photographers, and tooling have started adopting it despite slow browser support.
So converting a JPG to JPEG XL buys you a smaller, richer, future-proof file. The question that decides whether it is right for you is not quality, it is whether the place the file is going can open it yet.
Read moreRead less
Who can actually open a JPEG XL today
This is the honest centre of the page, so read it before you convert. On the open web, Apple is the exception that supports JPEG XL: Safari 17 and later, on macOS Sonoma and iOS 17 and newer, decodes it natively. Chrome, Edge, and Firefox do not decode it by default, so a .jxl you create may not even open in your own browser.
Desktop creative software is further ahead than browsers. Photoshop, Lightroom and Camera Raw, Affinity, GIMP, Krita, and Paint.NET can open JPEG XL, and ImageMagick, FFmpeg and the libjxl command-line tools handle it for developers. Recent Windows 11 builds added support, while older Windows needs a codec add-on.
What this means in practice is that JPEG XL is excellent for a workflow you control, an Apple-centric one, a professional photo pipeline, or a long-term archive, and poor for anything you hand to an unknown recipient. If you email a .jxl to a colleague on a Windows laptop with Chrome, there is a good chance it simply will not open.
If you need the picture to open everywhere, JPEG XL is the wrong target and JPG or PNG is the right one. The reverse tools on this site convert a .jxl back to JPG or PNG in your browser for exactly that reason.
What this converter does, and what it does not
This tool decodes your JPG into raw pixels and re-encodes those pixels as JPEG XL at the quality you choose. That is a normal lossy encode, the same kind every converter here does, and it produces a standard .jxl file that any JPEG XL reader can open.
It is not the specialised lossless JPEG transcode. JPEG XL can re-wrap an existing JPEG without decoding it, shrinking the file around 20 percent while keeping the ability to reconstruct the exact original JPEG byte for byte. That mode operates on the JPEG's internal coefficients and needs the cjxl command-line tool; a browser canvas only has access to decoded pixels, so it cannot do it.
For almost everyone this distinction does not matter. If you want a smaller, modern copy of a photo, the pixel re-encode here is exactly right and visually identical at sensible quality. If you specifically need reversible, archival-grade lossless recompression of original JPEGs, reach for cjxl directly.
Everything runs locally. The encoder is a WebAssembly build of libjxl that downloads once and then works entirely on your device, so your photos never leave the browser tab.
Choosing a quality setting
JPEG XL quality behaves much like other modern codecs: because the format is efficient, a moderate setting already looks excellent. The default is a strong starting point and keeps the file visually identical to the source for typical photos.
Raise the quality for images where someone will look closely, such as portfolio shots or anything destined for print through a JPEG-XL-aware editor. The file grows but detail is preserved more faithfully.
Lower the quality when you want the smallest possible archive and can accept the same gentle softening you would from any lossy format. JPEG XL degrades gracefully rather than breaking into the hard blocks JPG shows, so it stays usable at settings where JPG would look rough.
If pixel-perfect fidelity is the goal, remember that JPEG XL has a true lossless mode. This in-browser tool focuses on quality-based lossy encoding; for guaranteed lossless archival, the libjxl command-line encoder is the dedicated path.
Good reasons to convert to JPEG XL now
Archival is the strongest case. If you are storing a large photo library for the long term and your tools can read JPEG XL, the format saves significant space at the same quality, and its lossless mode can preserve masters exactly. Smaller archives cost less to store and back up.
Apple-centric workflows are another. If your audience or your own devices are on Safari 17+, macOS Sonoma+, or iOS 17+, JPEG XL is already viewable, so you get the efficiency now rather than waiting for the rest of the web.
Professional photo pipelines that run through Lightroom, Camera Raw, Affinity, or Krita can adopt JPEG XL internally to cut storage while keeping HDR and high bit depth that JPG would throw away.
And future-proofing is legitimate on its own. Converting from a high-quality original now gives you a file that is ready for the day support widens, and you can always convert a copy back to JPG whenever you need universal compatibility.
Converting a whole folder of JPGs at once
Archival and migration jobs are rarely one file, so the tool is built for the batch. Drop a folder of JPGs and every file is encoded to JPEG XL in parallel using a worker pool in your browser, then bundled into a single ZIP with the original names kept and the new .jxl extension applied.
Up to 100 files at 50 MB each go in one batch. JPEG XL encoding does more work than JPG, so large images take a moment each, but the work spreads across your CPU cores rather than queuing one 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.
Keep your original JPGs alongside the new JPEG XL files until support is everywhere you need it. That way you have the efficient archive and a universally readable copy, and you can always regenerate JPGs from the originals or by converting the .jxl files back.
Frequently asked questions
Honest answers to what people ask before using this tool.
Further reading
Independent references if you want to go deeper on the formats and tradeoffs.