Why Chromium Ends JPEG XL Prematurely

Table of Contents

1. Introduction
2. What is JPEG XL?
3. The Initial Support and Excitement
4. Industry Support for JPEG XL
5. The Unexpected Removal Decision
6. Potential Benefits of JPEG XL
7. Backwards Compatibility and Royalty-Free Standard
8. Google's Backing of WebP and AV1
9. The Impact of Chromium's Decision
10. Conclusion

Introduction

In this article, we will discuss the rise and fall of JPEG XL, a highly anticipated image format that promised to revolutionize image sharing on the internet. We will explore the initial support and excitement surrounding JPEG XL, the industry's backing for this format, the unexpected decision to remove support for it, the potential benefits it offered, and the impact of Chromium's decision. Additionally, we will Delve into Google's preference for WebP and AV1, and the implications this has on the future of image formats. Let's dive in and discover what led to the demise of JPEG XL and what it means for the future of image compression.

The Rise and Fall of JPEG XL

JPEG XL, a relatively unknown format, gained massive Attention in the tech community due to its promise of superior image quality and smaller file sizes compared to traditional JPEGs. However, before it could gain traction, Google and Chromium decided to remove support for JPEG XL, leading to its untimely demise.

What is JPEG XL?

JPEG XL, short for Joint Photographic Experts Group Extra Large, was developed by the Joint Photographic Experts Group (JPEG) as a successor to the widely used JPEG image format. It aimed to address the limitations of traditional JPEGs, such as loss in image quality and larger file sizes. JPEG XL incorporated improved compression algorithms and supported features like an alpha layer for transparency.

The Initial Support and Excitement

When JPEG XL was introduced, it received widespread support and praise from developers, contributors, and the general public. Notably, companies like Facebook and Adobe expressed eagerness for full JPEG XL support in Chrome. Facebook saw the potential for smaller file sizes and higher quality images on their platform, while Adobe recognized the benefits of JPEG XL for image processing in Photoshop, Camera Raw, and Lightroom.

Industry Support for JPEG XL

JPEG XL garnered significant adoption from major industry players like Intel, Shopify, and Critter. Intel advocated for JPEG XL to be enabled by default in Chrome, emphasizing its preference for the format. Critter, a leading illustration and drawing app, implemented HDR support with JPEG XL, while Adobe and Serif also followed suit with their respective software updates.

The Unexpected Removal Decision

Despite the overwhelming positive feedback, Chromium surprisingly decided to remove support for JPEG XL without providing a clear explanation. While the exact reasons remain unknown, speculations suggest that Google's focus on promoting its established formats, like WebP and AV1, played a role in the decision. Regardless, the lack of response from the Chromium team left many puzzled and disappointed.

Potential Benefits of JPEG XL

JPEG XL offered several advantages over existing image formats, including:

1. Improved image quality with smaller file sizes.
2. Lossless recompression of JPEGs.
3. Progressive decoding for reduced visual latency.
4. Support for HDR animations.
5. Ecosystem interest and adoption by industry leaders.

However, Chromium's decision hindered the realization of these benefits and prevented JPEG XL from becoming the standard image format on the web.

Backwards Compatibility and Royalty-Free Standard

One of JPEG XL's notable features was its compatibility with existing formats. It allowed lossless recompression of JPEGs and facilitated seamless conversion to JPEG XL when the browser didn't support the format. Moreover, JPEG XL was an open standard, free from royalty fees, making it an attractive choice for developers.

Google's Backing of WebP and AV1

Google has been actively promoting its favored image formats, WebP and AV1, within the Chromium ecosystem. While WebP has seen limited adoption beyond Google's services, AV1 has gained traction as a future-proof video codec. Google's preference for these formats likely influenced its decision to remove support for JPEG XL.

The Impact of Chromium's Decision

Chromium's removal of JPEG XL support had a profound impact on the format's future prospects. Despite industry support and interest, without Chrome's backing, widespread adoption became unlikely. JPEG XL may find support in smaller browsers and Chromium forks, but its potential impact is significantly diminished without support from the widely used Chrome browser.

Conclusion

The rise and fall of JPEG XL highlight the complexities and challenges in establishing a new image format. Despite its promising features and industry-wide support, Chromium's unexpected decision to remove support for JPEG XL significantly hindered its adoption. As the industry continues to evolve, the battle between different image formats remains ongoing, with significant implications for developers, users, and the future of internet image sharing.