JPEG XL: The Image Format That Could Replace Everything

Every few years, a new image format shows up promising to fix everything. Usually it fixes one thing and breaks two others. JPEG XL is different — it actually delivers on most of its promises. The problem? Almost nobody supports it yet.

Here's the deal: JPEG XL (file extension .jxl) was finalized in 2021 as a royalty-free, open-standard image codec designed to replace JPEG, PNG, GIF, and WebP. One format to rule them all. It offers better compression than all of them, supports transparency, animation, HDR, wide color gamuts, and can even losslessly transcode existing JPEGs into smaller files.

Sounds perfect, right? So why isn't it everywhere?

The Browser Support Mess

Safari supports JPEG XL natively (as of macOS Ventura and iOS 16). That's great if you're in the Apple ecosystem. Chrome added support, then removed it in 2022, citing "not enough interest." Firefox has experimental support behind flags. Edge follows Chrome's lead.

So as of April 2026, you can use JPEG XL on Apple devices and... that's about it for casual web browsing. You can enable flags in other browsers, but your average user isn't doing that.

For web developers, this means JPEG XL is stuck in the same chicken-and-egg problem that every new format faces: browsers won't support it until sites use it, and sites won't use it until browsers support it.

But the Tech is Actually Good

Let's talk about what makes JPEG XL compelling when you can use it (professional workflows, archival, controlled environments):

• Better compression: 20-30% smaller files than JPEG at the same perceptual quality. For photos with fine detail or transparency, you can hit 40-60% savings.
• Lossless JPEG recompression: You can take an existing JPEG, convert it to JPEG XL losslessly (mathematically identical pixels), and get a 20% size reduction. No quality loss. This is huge for archival.
• Progressive decoding: Like progressive JPEGs, but better. You can render a usable preview from the first few kilobytes, then refine as more data arrives.
• Everything in one format: Transparency? Check. Animation? Check. HDR and wide color? Check. Depth maps, layers, multiple exposures? All supported.
• Fast encoding and decoding: Unlike AVIF (which can be painfully slow to encode), JPEG XL is reasonably quick. Real-time encoding is feasible on modern hardware.

It's not theoretical either. Tools like image compressors that support JPEG XL show measurable file size wins with no visible quality loss.

Where You Can (and Should) Use JPEG XL Today

If you control the entire pipeline — the software creating the images and the software displaying them — JPEG XL makes sense right now.

Photography workflows: If you're shooting RAW and exporting for print or archival, JPEG XL beats TIFF for size and beats JPEG for quality. You get 16-bit depth, wide color, and reversible compression. Store your masters in JPEG XL and export to other formats as needed.

Design and creative tools: Photoshop and GIMP (with plugins) can handle JPEG XL. If you're working locally and just need a high-quality intermediate format, it's great. Smaller files than PSD or XCF, better fidelity than PNG.

Archival and storage: Got thousands of old family photos as JPEGs? Convert them to JPEG XL losslessly and save 20% disk space. You can always convert back if needed. This is genuinely useful if you're tight on storage or managing large photo libraries.

Controlled web environments: If you're building an iOS/macOS-only app or website where you know users are on Safari, go for it. Serve JPEG XL images and enjoy the bandwidth savings. Just remember to test on actual devices first.

The AVIF Comparison Everyone Asks About

AVIF is the other "next-gen" image format that actually has decent browser support (Chrome, Firefox, Safari all support it). So how does JPEG XL compare?

File size: Roughly tied. AVIF wins slightly on photographic content at very low bitrates. JPEG XL wins on high-fidelity images and anything with fine detail or text. In practice, the difference is marginal — both are better than JPEG.

Encoding speed: JPEG XL is much faster. AVIF encoding can take seconds per image even on fast hardware. JPEG XL is closer to JPEG encoding times. This matters if you're processing hundreds of images.

Feature set: JPEG XL supports more stuff out of the box (progressive decoding, lossless JPEG transcoding, better HDR handling). AVIF is more focused on lossy compression for web delivery.

Browser support: AVIF wins here. It's in all major browsers (though Safari was late to the party). JPEG XL is still waiting for Chrome and Firefox to care.

For web use in 2026, AVIF is the safer bet. For professional workflows and archival, JPEG XL is arguably better. And you can convert between formats easily enough that it's not a permanent commitment.

What Needs to Happen for Broader Adoption

Look, the tech is solid. What JPEG XL needs is momentum. Here's what would actually move the needle:

1. Chrome needs to reverse course and add native support. Google killed it once citing low usage (of course usage was low — they barely promoted it). If Chrome adds it back, Edge follows automatically, and suddenly 70%+ of browsers support it.

2. More cameras and phones need to shoot JPEG XL natively. Imagine if your iPhone or Pixel saved photos as .jxl instead of .heic or .jpg. Instant mass adoption. Apple has the codec support in Safari already; they just need to flip the switch on the camera side.

3. Social media and hosting platforms need to accept and serve JPEG XL. If you could upload a JPEG XL to Instagram or Twitter and it stayed JPEG XL (instead of being recompressed to JPEG), people would start caring. Bandwidth costs matter at scale.

None of this is technically hard. It's politics, priorities, and inertia.

Should You Care Right Now?

If you're building a general-audience website, no. Stick with JPEG, WebP, or AVIF (with JPEG fallbacks). JPEG XL isn't reliable enough yet for public-facing web content unless you're specifically targeting Safari users.

If you're a photographer, designer, or anyone managing large image libraries, yes. JPEG XL is a legitimately better archival format than anything else out there right now. The lossless JPEG transcoding alone is worth experimenting with. Tools like online image converters make it easy to test without installing software.

And if you're in a position to influence browser vendors (developer relations, standards bodies, loud on Twitter), push for JPEG XL support. The format is good. It deserves a real shot.

The frustrating thing about JPEG XL is that it's one of those rare cases where the tech is ahead of the adoption curve, not behind it. We have a format that solves real problems — file size, quality, versatility — and it's being held back by browser politics and ecosystem inertia.

Will JPEG XL eventually win? Hard to say. AVIF has momentum, JPEG refuses to die, and WebP is "good enough" for a lot of use cases. But JPEG XL has one thing going for it: when people actually use it, they tend to like it. That's not nothing.

So try it out in contexts where you control the pipeline. Use it for archival. Convert some test images and compare the results. And maybe, just maybe, if enough people start caring, the browsers will follow.