JPEG XL: Why Better Compression Alone Isn't Enough


JPEG XL represents a significant technical improvement over existing image formats, but its path to adoption illustrates how technical merit alone doesn’t guarantee success in established ecosystems. The format delivers better compression ratios than JPEG, supports both lossy and lossless encoding, handles high bit depths, and includes progressive decoding—yet it faces an uphill battle for browser and platform support.

The Technical Case

JPEG XL achieves roughly 60% better compression than legacy JPEG at equivalent quality levels. It supports features modern applications need: wide color gamuts, alpha transparency, animation, and lossless recompression of existing JPEGs without generation loss. The format handles both photographic and synthetic content efficiently, something that typically requires choosing between JPEG and PNG today.

The codec is also designed with performance constraints in mind. Decoding complexity remains comparable to existing formats, avoiding the CPU overhead that has limited HEIF adoption despite its compression advantages. Reference implementations achieve real-time decode speeds on modern hardware without specialized acceleration.

Infrastructure Inertia

The challenge isn’t the format itself but the infrastructure built around existing formats. Content delivery networks have optimized their caching, transformation, and delivery pipelines for JPEG, PNG, and WebP. Adding JPEG XL support means updating CDN edge nodes, image processing services, thumbnail generators, and format negotiation logic across millions of servers.

Browser support determines what formats websites can safely deploy. Chrome added then removed JPEG XL support, citing insufficient interest and the maintenance burden of supporting another codec. Without Chrome, which represents the majority of browser traffic, websites can’t rely on JPEG XL as a primary format. This creates a chicken-and-egg problem: browsers want to see demand before investing in support, but developers can’t create demand without browser support.

Competing Interests

The format landscape includes players with different incentives. Google controls both Chrome and WebP, an existing modern image format. Apple develops HEIF/HEIC, which ships as the default camera format on iOS. Both companies have invested significantly in their respective formats and the infrastructure to support them.

AVIF, based on the AV1 video codec, entered the scene more recently with backing from the Alliance for Open Media, which includes Google, Apple, Mozilla, and others. AVIF achieves compression ratios competitive with JPEG XL while leveraging decoder hardware already being deployed for video. The shared infrastructure between image and video encoding provides an economic advantage that standalone image formats lack.

Fallback Complexity

Supporting a new image format in production requires robust fallback chains. A typical implementation might check for JPEG XL support, fall back to AVIF, then WebP, then traditional JPEG. Each format in the chain requires encoding, storage, cache management, and testing. The operational complexity grows with each additional format.

Content negotiation happens through Accept headers or separate URL schemes, both of which complicate caching strategies. Edge caches must either store multiple versions of each image or perform real-time transcoding, each with its own performance and cost implications. For large-scale deployments serving billions of images, this complexity translates directly to infrastructure costs.

Progressive Enhancement Limits

Progressive enhancement works well for features that degrade gracefully, but image formats are binary: either the browser decodes the format or it doesn’t. JavaScript polyfills for image decoding exist but impose significant CPU overhead and defeat much of the performance benefit of better compression. Users on slower connections, who would benefit most from reduced file sizes, pay the highest penalty for client-side decoding.

Adoption Patterns

New formats typically gain traction through platform adoption or clear economic incentives. WebP succeeded partly because Google could deploy it across YouTube and other properties, demonstrating real-world benefits at scale. HEIF spread through smartphone cameras where Apple could control both capture and display.

JPEG XL lacks a single large platform champion pushing adoption. It exists as an open standard with multiple implementations, which provides long-term sustainability but doesn’t create the immediate deployment momentum that platform-backed formats achieve.

The Long View

Format transitions take years or decades. JPEG itself, introduced in 1992, coexisted with GIF and other formats for years before becoming dominant. PNG reached stable browser support in the early 2000s but didn’t see widespread adoption until the 2010s. WebP launched in 2010 but only achieved broad browser support by 2020.

JPEG XL may follow a similar trajectory, gaining adoption first in specialized applications where its specific advantages matter most—medical imaging, professional photography, archival systems—before potentially expanding to general web use. Or it may remain a technically superior format that never achieves mainstream adoption, superseded by video-codec-derived formats with better hardware support and platform backing.

The outcome depends less on technical merit than on economics, platform politics, and infrastructure momentum.