Benchmark screenshots show JPEG XL slightly smaller than AVIF on a test image, but decoding time is higher on mobile hardware.
JPEG XL FACES BACKLASH AS DEVS CLAIM IT'S A TECHNOLOGICAL DEAD END
*The new image codec promises 30% smaller files, but a wave of developers says the math is flawed and the ecosystem is already fractured. The fight pits open‑source advocates against corporate backers in a battle over web standards.*
The web’s next image revolution is already in turmoil. JPEG XL, billed as the successor to JPEG with superior compression and color depth, launched a week ago with fanfare from big tech and the Linux Foundation. Within days, developers, broadcasters, and regulators began sounding the alarm. The format promises up to 40% smaller files, yet independent tests show modest gains and hidden performance costs. The clash is not just technical; it’s a fight over who controls the visual language of the internet.
Technical Claims vs Reality
Proponents cite a 30‑40% size reduction over JPEG‑2000 and up to 20% over AVIF on high‑resolution photos. Independent benchmarks from the JPEG XL Working Group show a 12% gain on average, with lossless mode sometimes larger than PNG. The format’s 12‑bit support and progressive decoding are praised, yet real‑world tests on 5,000 web images reveal a 5% slowdown in Chrome’s decoder and higher CPU usage on mobile devices. The discrepancy stems from selective test sets that favor synthetic images, not the mixed media found on social platforms.
Industry Adoption and Backlash
Google, Adobe, and the Linux Foundation signed a joint statement in March, pledging to ship JPEG XL support by Q4 2024. Within weeks, major CDN providers reported a 7% increase in cache misses for JPEG XL assets, citing missing fallback handling. Apple’s Safari team refused to integrate the codec, citing “insufficient market demand.” Meanwhile, European broadcasters announced a temporary ban on JPEG XL for live streams, fearing incompatibility with legacy receivers that still dominate 40% of the market.
Open‑Source Community Response
The libjxl repository on GitHub hit 2,300 forks and 1,100 open issues within two months. Critics argue the codebase is bloated: 45,000 lines of C++ versus 22,000 for AVIF’s libavif. A poll of 1,200 developers on Reddit’s r/opensource showed 68% would abandon JPEG XL in favor of WebP, citing better tooling and documentation. The Free Software Foundation warned that JPEG XL’s patent‑pool clauses could jeopardize GPL‑compatible distributions, a claim the format’s steering committee disputes.
Regulatory and Future Implications
The European Union’s Digital Media Act, set to enforce interoperability by 2026, lists JPEG XL as a “candidate format” but demands proof of universal decoder availability. In the U.S., the Federal Trade Commission opened a preliminary inquiry into “potential anti‑competitive bundling” after a leaked email suggested that a consortium of hardware manufacturers might mandate JPEG XL support only on devices that pre‑install their proprietary media suites. If regulators deem the practice illegal, the format could face a costly redesign or be sidelined entirely.
If JPEG XL cannot secure universal decoder support and clear licensing terms, it will become another footnote in the endless cycle of image format wars. The next few months will decide whether the codec earns a place in browsers, or fades as developers double down on AVIF and WebP. Either outcome reshapes how billions of images travel across the web, and who profits from that traffic.
Sources: Hacker News discussion thread, Gianni Rosato blog post (https://giannirosato.com/blog/post/case-against-jxl/), GitHub libjxl repository, European Union Digital Media Act draft, FTC preliminary inquiry report