Convert JPG images to JPEG XL (JXL) locally - much smaller files at the same quality, no upload.
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
JPEG XL (JXL) often stores photos noticeably smaller than JPG at the same quality and even supports lossless storage. Keep in mind, though: JXL is still barely opened by any browser or program - it is mainly useful for archiving or when your target software explicitly supports JXL.
The JPG is decoded locally (including correct EXIF orientation) and encoded as JXL with a self-hosted codec. The quality slider controls the file size. Nothing is uploaded.
For the conversion your JPG is fully decoded and re-encoded from the pixels as JXL - an ordinary, fresh encoding step, not a bit-exact repackaging of the original JPEG data. At high quality the extra loss is practically unnoticeable, but a second compression step still happens. JXL is nonetheless useful for archiving large photo collections space-efficiently, if your backup or library software supports the format. For everyday sharing it stays impractical as long as recipients cannot open it; in that case the familiar JPG is the better choice.
| Input formats | JPG, JPEG |
|---|---|
| Output format | JXL |
| Batch processing | Yes |
| Processing | Locally in your browser (WebAssembly) |
| File upload | None |
Limitations: JXL cannot recover detail JPG already discarded, but it stores the image more compactly. Most browsers and programs do not open JXL yet - as JPG the image stays readable everywhere. Very large images need time and memory.
Depending on content and quality, often noticeably smaller than a comparable JPG.
No. JXL is still barely supported by browsers or programs; only use it if your target software can.
No, everything runs locally in the browser.
Yes, download individually or as a ZIP.