Chrome Just Shipped JPEG XL. What That Actually Means

By Siam Sukkhee Trading Co., Ltd — 2026-10-07 — Hacker News

Chrome 155 dropped JPEG XL. Not behind a flag. Not as an experiment. Live, for everyone.

The reversal is interesting. More interesting is why they came back and how.

The compression numbers first

JPEG XL delivers 30–50% better compression than standard JPEG. That's not marketing speak. On a 2 MB photograph, you're looking at cuts to maybe 1 MB or less, with no visible quality loss. The format also handles lossless compression, built-in HDR, and can convert JPEG files with perfect reversibility—useful if you need to preserve originals but shrink the working copy.

For high-fidelity photos and professional imaging, this is the thing you want.

The question is always: compression or compatibility? The answer, as it usually goes, is both or neither. JPEG XL had compression. It had no users.

What changed

Other browsers moved. Developers kept asking. That continuous pressure—not from tech blogs, from actual people building things—shifted the calculus.

But the real story isn't why Chrome shipped it again. It's how.

Safety, written in Rust

Image decoders are attack surface. They sit in the renderer, pulling untrusted binary data from the network, and a single buffer overflow gets you remote code execution. For years that meant C++ and the usual class of memory bugs: out-of-bounds reads, heap overflows, use-after-free.

Chrome reimplemented the decoder in Rust. Specifically, jxl-rs—a pure Rust version of the JPEG XL decoder.

Rust doesn't solve security. What it does is eliminate entire categories of bugs at compile time. No buffer overflows. No use-after-free. The unsafe parts? Restricted to a small number of highly-scrutinised locations. The implementation has survived fuzzing and AI code review without finding memory safety bugs.

This is not new thinking.

Speed without compromise

A memory-safe decoder that's also slow is a hard sell. Modern image decoding leans on SIMD—vector instructions that crunch data in parallel. Writing SIMD code safely in Rust used to require unsafe blocks everywhere, which defeats the purpose.

That problem got solved through a Rust feature called target_feature_11, which stabilised SIMD use without requiring unsafe code. Chrome layered a SIMD abstraction on top, inspired by the C++ Highway library. You get the performance without the risk.

Actually, that's not quite right. You get similar performance. Not identical. The trade-off is smaller than people expected, but it's there.

Why this matters for you

If you serve images—product photography, editorial, anything that depends on fidelity—you should test JPEG XL alongside AVIF. The format is most helpful for high-resolution work and cases where progressive loading matters.

It's not a JPEG replacement yet. But the surface is growing. Chrome pushed the button. Others will follow.

The lesson here isn't really about JPEG XL. It's that when a format solves a real problem, developers will use it. And when Google gets the security model right—memory safety first, then speed—the browser becomes genuinely safer for it.

Source: "JPEG XL can offer 30-50% better compression than JPEG along with HDR support and other improvements." — Frontend Focus

Tags: ESG metals mining industry