Convert WebP to JPEG XL
Drop a WebP 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 WebP
Lower means a smaller file. 75 is a good default for photos.
100% in your browser Files are never uploaded.
Why convert WebP to JPEG XL?
For the same picture, JPEG XL usually lands well under the size of the WebP original. That matters when you are trimming page weight or squeezing under an upload limit.
Both formats are lossy. Every re-encode discards a little more detail, so it is worth starting from the original rather than from a copy that has already been through this a few times.
It is worth being blunt about this one: for most people it is not worth doing yet. JPEG XL is the better format on paper, but you are starting from an already-compressed WebP and ending at a format almost nothing can display. The cases where it pays off are real but specific.
Before you convert
A second lossy pass eats most of the theoretical gain
JXL's efficiency advantage over WebP is measured by encoding both from the same untouched original. Encoding from a WebP means the detail WebP discarded is already gone, and JXL now spends bytes reproducing WebP's artefacts faithfully. Whatever margin remains is a fraction of the number you may have read. If the original file exists, encode from that.
You are trading universal support for almost none
WebP works in every browser people use. JXL, as of August 2026, opens out of the box only in Safari — roughly 14 percent of visitors — with Chrome's decoder still behind a flag pending a default-on expected later in the year. As a swap for a delivery format this is straightforwardly a downgrade until that changes.
Where it does make sense
Two situations. If the WebP was lossless to begin with, JXL lossless will store the same pixels in less space with nothing given up. And if you are building an archive rather than serving a page, betting on JXL is defensible — it is an open standard, it is arriving in browsers, and storage savings compound over years.
What carries over
- Transparency
- Pixel dimensions
- Every pixel, if both ends are lossless
What does not
- Practical viewability, for now
- A little detail, on a lossy source
- Animation, if the source had any
WebP vs JPEG XL at a glance
| Property | WebP | JPEG XL |
|---|---|---|
| Compression | Lossy | Lossy |
| Transparency | Yes | Yes |
| Typical file size | 65-75% of an equivalent JPEG | 45-60% of an equivalent JPEG |
| Compatibility | Supported by all current browsers and most apps | Safari and recent Chrome; still uncommon elsewhere |
| Usually comes from | Websites optimising page weight | Long-term archives and photography workflows |
Frequently asked questions
Are my WebP 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.
Why did I end up with a WebP file?
Most websites now serve WebP because it is smaller than JPEG, so saving an image from a web page usually hands you one. Browsers support it well, desktop software noticeably less so — which is why converting it away is such a common need.
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.