WebP and JPEG XL in one sentence each
WebP is Google’s image format from 2010, with lossy (VP8-based) and lossless modes and support in virtually every current browser (caniuse: WebP). JPEG XL is the newer ISO/IEC 18181 standard from the JPEG committee, with lossless and lossy modes, high bit depth, progressive decoding and lossless JPEG recompression (jpeg.org).
Two kinds of WebP, two defaults
The converter looks inside each WebP file before deciding what to do:
- Lossless WebP (a
VP8Limage) is converted to lossless JPEG XL. The pixels, including transparency, stay exactly the same. - Lossy WebP (a
VP8image) is converted with the visually lossless setting. The result should look the same as the WebP, but it is a new lossy encoding of already-lossy pixels.
You can override this in Settings. Choosing Lossless for a lossy WebP preserves the decoded pixels exactly, but the file will often be much larger than the WebP — the compression artefacts become part of what is preserved.
An honest warning about lossy sources
Re-encoding an already-lossy image cannot improve its quality and may not reduce its size. The tool shows this warning once per session, and for every file it displays the original size, the new size and the change in percent. When the JXL is larger, it is marked in red, the original is highlighted as the smallest file, and you can choose Keep original. Nothing is hidden.
When WebP to JXL makes sense
- Archiving lossless WebP exports (from design tools or screenshot apps) in an ISO standard format.
- Moving away from WebP in a workflow where every other image is already JPEG XL.
- Testing: tick WebP and AVIF as extra outputs to see how all three formats compare on your own image.
When it does not
- Images already served on a website as WebP. WebP has the widest support of the modern formats, and a second lossy conversion will not improve quality.
- Animated WebP: not supported in this version.
- When the recipient cannot open JXL — see browser support.
What happens to metadata
WebP can contain EXIF and XMP chunks. They are copied into the JPEG XL file unless you choose to remove them, and GPS coordinates can be removed on their own. If the WebP has an embedded colour profile (ICCP chunk), it is decoded by the browser and converted to sRGB; the metadata report tells you when that happened.
For a broader look at the trade-offs, read JXL vs WebP vs AVIF.
Last updated:
Frequently asked questions
Will converting WebP to JXL make my images smaller?
Not necessarily. A lossy WebP has already discarded detail, and re-encoding it to any lossy format adds a second generation of compression. Sometimes the JXL is smaller, sometimes larger. The tool shows the real numbers and recommends keeping the WebP when it is smaller.
Are animated WebP files supported?
Not in this version. Animated WebP files are detected and skipped with a notice. Static WebP images, lossy or lossless, are supported.
Is transparency kept?
Yes. WebP alpha channels are carried over to the JPEG XL file.
Why would I convert WebP to JXL at all?
Mainly for lossless WebP files you want to archive in a newer standard format, or to compare formats for your own images. For lossy WebP used on websites, converting rarely makes sense unless you have a specific reason.