
许多我们熟悉的图像格式已经存在数十年。我们对 JPEG 和 PNG 再熟悉不过,GIF 甚至在社交媒体上再度走红,因为那些小巧又有些烦人的循环动画又一次成了潮流。与此同时,更新的格式也不断涌现,比如 WEBP 和 AVIF,各种平台和软件公司纷纷采用它们,以获得更高的效率、性能和图像质量。
在新一轮竞相争夺关注度的格式中,JPEG XL 尤为引人注目。它被誉为在有损压缩领域超越 JPEG 的格式,同时还增加了无损模式。人们曾寄望它能全面取代 Web 上所有现有的栅格图像格式。然而,一个主要问题在于 Google 起初似乎并不支持,后来又态度反转——在这家搜索巨头的重新支持下,该格式如今有望大展宏图。那么,这背后到底发生了什么?
JPEG XL 标准虽然现代化,却并非全新产物。它于 2021 年 10 月 13 日首次发布,由联合图像专家组(Joint Photographic Experts Group)、Google 和 Cloudinary 组成的联盟共同开发。该标准源自 Jon Sneyers 关于 Free Universal Image Format(FUIF)的早期工作,以及 Google 在 PIK 格式方面的研究。
最终决定该格式采用 *.jxl 文件扩展名。规范定义了一种功能丰富的格式,远超传统 JPEG 的能力。它不仅支持包括 Alpha 通道在内的无损压缩,还提供多种有损压缩模式,以适配照片类和合成类图像。
其解码速度依旧飞快——几乎与 JPEG 相当,且远快于基于 x265 的 HEIC。它的一项关键未来适应性特性是支持 32 位采样精度,以及每边超过十亿像素的图像——如果你跟着算的话,这就是所谓的兆像素级图像。
自发布以来,众多科技巨头相继支持这一标准,包括 Meta、Adobe、Intel 和 Flickr。尽管从表面看,Google 似乎从一开始就全力支持——毕竟它参与了该标准的研发——但据 TT Lab 报道,事情的发展并非如此简单。
早在 2021 年,Chromium 就实现了基于 libjxl 的解码器,似乎预示着 JPEG-XL 即将在 Chrome 及其他产品中获得支持。然而,不久之后方向发生转变。2022 年底,它被标记为将移除,理由是生态系统的支持力度不足以证明继续将 JPEG-XL 纳入产品的必要性。
Chrome 110 发布时,已看不到 JPEG-XL 的身影——它不会成为产品的一部分。此后数年,关于这种新兴格式是否应被纳入的争论在 Chrome 问题跟踪器上持续发酵。与此同时,JPEG-XL 在其他地方也在艰难立足。Apple 于 2023 年将其支持引入 Safari,而 Mozilla 则持续观望,指出出于内存安全的考虑,不愿再引入另一个 C++ 图像解码器。
直到 2025 年 11 月,Google Chrome 区域技术负责人 Rick Byers 表示,局面已发生变化。他发文指出,鉴于 JPEG-XL 支持已被加入 PDF 格式和 Safari,以及生态系统中出现的其他支持信号,开发团队愿“在 Chromium 中集成一个高性能且内存安全的 JPEG XL 解码器”。
Chrome 在浏览器市场的占有率超过 65%,因此这一决定有望彻底改变该格式的命运,并使其在网络上的采用率迅速飙升。不过,前提是它必须真正得到实施。Byers 同时谨慎指出,新格式的引入将取决于对解码器长期维护的承诺。
进展迅速:今年 2 月 Chrome 145 发布时,JPEG-XL 已被列入议程。这得益于 jxl-rs 解码器的开发——它使用 Rust 实现。出于安全考虑,这是一个有意为之的决定,Google 依据 Rule of 2 来保障浏览器安全。不过,该解码器起初并未默认启用。又过了大约半年,新格式才真正成为 Chrome 的主流功能,而不再隐藏在实验性标志之后。而到了 Chrome 155,JPEG-XL 将在浏览器中获得全面支持。
不要指望广域网上立即涌现大量 *.jxl 文件。不过,鉴于新格式相比 JPEG 能带来 30-50% 的压缩率提升,它几乎会吸引所有希望缩减数据预算并加快页面加载速度的内容提供商。一旦性能提升开始显著增加流量,足以弥补因旧版不兼容浏览器而流失的用户,其普及速度就会加快。
对于作为终端用户的你而言,这可能意味着一些小小的烦恼。下载 *.jxl 文件后,当你尝试用旧版不支持的软件打开时,会遇到困难;你也可能拿到一台支持 JPEG-XL 拍摄的设备,却发现无法将照片上传到使用过时图像提交表单的网站。
这与 HEIC、AVIF 和 WEBP 开始在网络上流行时我们所经历的问题如出一辙,而这一次我们也得再次挺过去。好在,最终我们会得到稍微更美观、占用空间更小的图片。毫无疑问,这一切是值得的。
本文来源:https://hackaday.com/2026/10/28/jpeg-xl-is-back-on-the-menu/
若有版权问题,请来信告知:13951431913#139.com 或在右方提交评论。
Many of the image formats we’re familiar with have been around for decades. We all know JPEG and PNG like the back of our hands, and GIF even had a bit of a resurgence when tiny annoying looping animations became cool again on social media. There has been a growth in newer formats, though, like WEBP, and AVIF, with various platforms and software companies adopting them for greater efficiency, performance, and image quality.
Amongst the new crop of formats vying for relevance is JPEG XL . It was touted as a format that improved on what JPEG could do in the lossy compression space, while also adding on a lossless mode. There were grand hopes that it would become a universal replacement for all existing raster formats on the Web. A major problem was that Google was seemingly against it, only to backflip—with the format now slated to hit the big time with renewed backing from the search giant. So what’s going on?
The JPEG XL standard is modern, but by no means brand new. It was initially released on 13 October 2021, having been developed by a consortium of the Joint Photographic Experts Group, Google, and Cloudinary. It was deveoped from earlier work from Jon Sneyers on the Free Universal Image Format (FUIF) , and work from Google on the PIK format.
It was decided the resulting format would use the *.jxl file extension. The spec defined a format with a wide range of features well beyond what classic JPEG ever offered. It has lossless compression, including for the alpha channel, but also lossy compression available in different modes to suit both photographic and synthetic imagery.
It remains fast to decode—almost as fast as JPEG and much quicker than HEIC with x265. A key future proofing feature is that it can also handle 32-bit sample precision, and images with over a billion pixels per side—that’s a terapixel, if you’re playing along at home.
A wide range of major tech companies have backed the standard in the years since it dropped, from Meta, to Adobe, Intel, and Flickr. While it might seem like Google was fully onboard from the get-go, having literally been involved in development of the standard, the history is more complicated, as reported by TT Lab .
Chromium implemented a libjxl-based decoder all the way back in 2021, which seemed to signal JPEG-XL support would soon be a thing in Chrome and other products besides. However, soon enough, there was a change in direction. In late 2022, it was slated for removal, with a notice that ecosystem support wasn’t great enough to justify continued efforts to bring JPEG-XL into the fold.
In Chrome 110, there was no trace left—JPEG-XL was not going to be a part of things. And yet, in the years that followed, debate raged on the Chrome issue tracker as to whether the nascent format would earn its inclusion. Elsewhere, JPEG-XL was struggling to find a footing. Apple rolled it into Safari in 2023, while Mozilla continued to hedge, noting that including another C++ image decoder was undesirable for reasons around memory safety.

New movement happened in November 2025, when Rick Byers, Area Tech Lead on Google Chrome, noted that the landscape had shifted. He posted that in light of JPEG-XL support being added to things like the PDF format and Safari, amidst other signals of support in the wider ecosystem, that the development team would be open to “integrate a performant and memory-safe JPEG XL decoder in Chromium.”
With Chrome having over 65% of the browser market, this would be a game changer for the format and likely see its adoption skyrocket across the web. It just needed to actually be implemented. However, Byers was careful to note that the inclusion of the new format would be contingent on a commitment to long-term maintenance of the decoder.
Things moved fast, and when Chrome 145 dropped in February this year, JPEG-XL was on the docket. This was thanks to the development of the jxl-rs decoder, which was implemented in Rust. This was an intentional decision for security reasons, with Google relying on the Rule of 2 to keep its browser safe. However, the new decoder was not activated by default. It would take another half a year or so before the new format would become a mainstream part of Chrome, rather than being hidden behind an experimental flag or anything like that. As of Chrome 155, though, JPEG-XL will be fully supported in the browser.
Don’t expect to see a ton of *.jxl files out on the wider web immediately. However, with the new format offering 30-50% better compression than JPEG, it will be appealing to just about any content provider looking to slimline data budgets and improve page loading times. When the performance gains start boosting traffic to a degree that makes up for the loss of users from older non-compliant browsers, expect to see things changing more quickly.
What does it mean for you, the end user? Probably little more than some minor headaches. You’ll struggle here and there when you download a *.jxl and try and load it into older software that doesn’t support it. You might get a device that shoots pictures in JPEG-XL and then find you can’t upload them to an older website with an out-of-date image submission form.
It’s the same problem we’ve all dealt with as HEIC, AVIF, and WEBP have started bouncing around the web, and we’ll have to weather it again. At least, at the end of the day, we’ll have slightly prettier images that take up a little less space. It’ll all be worth it, to be sure.