ByOfficial Integration of JPEG XL into the Chromium Browser Engine
Today marks a significant turning point in the world of technology, as Google has officially reintroduced native support for the JPEG XL format into the Chromium browser engine. This move is not just a simple image format update, but a step that redefines the future of image compression, performance, and security on the web.
This new support is based on the Rust-based, memory-safe decoder `jxl-rs`, which completely addresses the security and maintenance concerns that led to the previous removal of JPEG XL from Chrome.
How to Activate JPEG XL in Chrome
Although JPEG XL support is natively available in Chromium, it is not enabled by default. To use it, you need to enable a flag manually:
Open `chrome://flags` in your Chrome browser
Search for `enable-jxl-image-format`
Enable it
Restart your browser
This is the first time since 2022 (after version 110) that JPEG XL is natively returning to Chrome.
Status of JPEG XL Support in Other Browsers
Looking at the browser ecosystem, JPEG XL support is still uneven:
Firefox: Support is available, but users have to enable it manually
Safari: Only partial support, and only in limited use cases
Chrome: Now native support at the Chromium level, which is a major change
This clearly shows that Chrome’s return has brought JPEG XL back into the mainstream.
What is JPEG XL and Why is it Better than JPEG?
JPEG XL is a next-generation image format designed to replace the older and more limited JPEG format. JPEG XL’s Key Capabilities
Up to 60% better compression without quality loss
Extremely fast decoding, reducing page load times
Progressive decoding, allowing images to load gradually and improving user experience
Animation support, which is not possible with JPEG
High Dynamic Range (HDR) support
Compared to modern web standards, JPEG is now quite outdated, while JPEG XL redefines both performance and visual quality.
Why Google Removed JPEG XL Support in 2022
When Google removed experimental support for JPEG XL from Chrome in 2022, several reasons were given:
Low website adoption rate
Limited interest in the developer community
Google’s intention to promote its own format, AVIF
Google believed that continuing to work on JPEG XL was a waste of resources due to its low usage.
The Real Reasons Behind JPEG XL’s Return
Now, the circumstances have completely changed. Several strong factors forced Google to make this decision:
1. Support from Apple and Mozilla
Apple and Mozilla recently started supporting JPEG XL on their platforms, making Chrome the only major browser that didn’t support it.
2. The PDF Association’s Major Decision
At the end of 2025, the PDF Association declared JPEG XL the preferred format for HDR content.
This directly impacted Chrome, as its PDF viewer became dependent on JPEG XL support to correctly render HDR PDFs.
3. Strong Demand from the Developer Community
Developer surveys identified JPEG XL as a top pain point. Advanced features such as:
Progressive Rendering
Lossless Recompression
Animation
made it essential for developers.
Rust-based `jxl-rs`: Guaranteeing Security and Stability
This time, Google has chosen the `jxl-rs` decoder written in the Rust language instead of a C/C++ based implementation.
Advantages of Rust
Memory Safety by Design
Protection against vulnerabilities like buffer overflows
Fewer bugs and less maintenance
With this change, Google no longer has any basis to claim that maintaining JPEG XL is difficult. The Impact of JPEG XL on the Web
The return of JPEG XL will bring several positive changes to the web ecosystem:
Faster website loading
Reduced data usage, especially for mobile users
Improved SEO scores due to better Core Web Vitals
Better visual quality without large file sizes
This represents a strategic opportunity for website owners, bloggers, and media platforms.
AVIF vs. JPEG XL: A Comparison
While AVIF is also a modern format, JPEG XL surpasses it in several aspects:
Direct lossless conversion from JPEG
Better backward compatibility
Easier adoption
Faster encoding/decoding
This is why developers consider JPEG XL a more practical solution.
The Future Direction: Will JPEG XL Become the New Standard?
With native support in Chromium, it’s clear that JPEG XL is no longer an experimental technology.
In the coming months, we expect to see:
Native support in CMS platforms
Adoption by CDNs and image optimization tools
Widespread use in PDFs, web, and mobile apps
This comeback is a decisive step towards making JPEG XL the next image standard for the web.
Conclusion
Google’s reintegration of JPEG XL into Chromium is not just a technical update, but a foundational step for the future of the web.
The secure Rust-based implementation, support from the browser ecosystem, acceptance in PDF standards, and developer demand – all have contributed to giving JPEG XL the position it deserves.
This change will propel the web forward on all three fronts: performance, security, and quality.
Are you searching for the best hosting plan? Click now and get 20% off
Frequently Asked Questions (FAQ)
Question 1: What is JPEG XL?
JPEG XL is a modern and advanced image format developed as an alternative to the older JPEG format. It supports better compression, higher image quality, faster loading, and modern features such as HDR, animation, and progressive decoding.
Question 2: Why is JPEG XL support in Google Chrome important?
Google Chrome is the world’s most widely used browser. Native support for JPEG XL in the Chromium engine brings this format into the mainstream, resulting in faster image loading on websites and an improved user experience.
Question 3: Why is JPEG XL not enabled by default in Chrome?
Currently, JPEG XL is available as an experimental feature. To use it, you need to enable the `enable-jxl-image-format` flag in `chrome://flags`.
Question 4: How much better is JPEG XL than JPEG?
JPEG XL offers approximately 60% smaller file sizes compared to traditional JPEG, without sacrificing quality. In addition, it provides faster decoding and better visual output.
Question 5: Is JPEG XL beneficial for SEO?
Yes, JPEG XL improves website speed, which leads to better Core Web Vitals. Faster page loading directly impacts SEO rankings and user engagement positively.
Question 6: What is the support for JPEG XL in Firefox and Safari?
Firefox has JPEG XL support, but it needs to be enabled manually.
Safari currently only has partial support.
The situation has improved significantly with native support in Chrome.
Question 7: Why did Google remove JPEG XL support previously?
In 2022, Google removed JPEG XL support due to low usage, limited website adoption, and to promote its own AVIF format.
Question 8: Why did Google bring back JPEG XL support now?
There are several reasons for this, including:
Support from Apple and Mozilla
Recognition of JPEG XL for HDR PDFs by the PDF Association
Growing demand from developers
Secure Rust-based implementation
Question 9: What is jxl-rs, the Rust-based implementation?
jxl-rs is a JPEG XL decoder written in the Rust programming language, which is memory-safe. This reduces security risks and makes maintenance easier in the long run.
Question 10: Which is better, JPEG XL or AVIF?
Both are modern formats, but JPEG XL’s advantages include direct lossless conversion from JPEG, faster processing, and better compatibility, which many developers find more practical.
Question 11: Could JPEG XL become a web standard in the future?
Given the native support in Chromium, its acceptance in the PDF standard, and growing browser support, it’s clear that JPEG XL has a strong possibility of becoming the next major image standard for the web.
Question 12: When should website owners adopt JPEG XL?
As soon as browser support stabilizes, website owners and bloggers should start adopting JPEG XL to benefit from improved speed, reduced bandwidth, and higher image quality.
