You’ve probably noticed the web has a weight problem. We’ve spent a decade optimizing JavaScript frameworks, shaving milliseconds off load times, and obsessing over Core Web Vitals—only to serve users a 3MB hero image that takes four seconds to paint on a screen. The endless bickering between WebP, AVIF, and legacy JPEG has felt less like innovation and more like a turf war.
But the tide just turned. Firefox 157 is shipping JPEG XL by default on all platforms. Chrome is following suit. The format wars aren’t just ending; they’re being settled in a way nobody expected.
We all thought the winning argument would be compression ratios. We were wrong. The real catalyst isn’t just better pixels—it’s memory safety.
Both Firefox and Chromium are adopting jxl-rs, a Rust-based implementation of the JPEG XL standard. This isn’t a coincidence. It’s a paradigm shift. Rust is quietly becoming the unifying substrate for browser image codecs, offering a rare alignment of technical merit and bulletproof memory safety.
Memory safety isn’t just a security feature anymore; it’s a competitive weapon.
When every major browser engine is parsing millions of untrusted images a second, the language you write your codec in matters. C++ is a liability. Rust is a moat. By standardizing on jxl-rs, the open web is effectively voting with its codebase, prioritizing safety and performance hand-in-hand.
But this creates a massive, uncomfortable tension in the ecosystem. Apple.
Apple already shipped libjxl—a C++ implementation—in their platforms. For years, they’ve played the isolationist game with Safari, lagging behind on features and forcing developers to beg for basic standards. But now, the ground is shifting. They aren’t just behind on a file format; they are on the wrong side of a fundamental architectural divide.
Apple is now standing on the C++ side of a divide, holding a ticking clock.
They can keep their Swift memory-safety experiments and C++ baggage, or they can embrace the reality that the rest of the browser world has moved on. If they don’t get on board with Rust, they risk falling behind on both security and rendering performance.
For developers, this is the breakthrough we’ve been waiting for. Faster loading, richer images, and a clearer path to future-proofing our apps. The web is finally getting its standard image format, but the real victory is watching Rust quietly take the crown.
FAQ
Q: If JPEG XL is technically superior, why did it take this long to adopt?
A: Because technical superiority doesn't win ecosystem wars—politics and security do. Browsers were hesitant to touch new C++ codecs due to memory safety risks, but the Rust-based jxl-rs implementation removed the final barrier.
Q: What does this mean for my web application right now?
A: You finally have a clear path to drop the WebP/AVIF fallback hacks. You can start serving JPEG XL to get smaller file sizes and better quality, knowing the two major browser engines are natively supporting it.
Q: Is this really a win for Rust, or just a coincidence of implementation?
A: It's a massive win for Rust. When both Chromium and Firefox independently choose a Rust-based implementation for a core web standard, it signals that memory safety is no longer optional—it's the baseline for new browser internals.