{"id":3262,"date":"2026-08-08T02:04:42","date_gmt":"2026-08-07T23:04:42","guid":{"rendered":"https:\/\/picajet.com\/articles\/formats\/jpeg-xl\/"},"modified":"2026-08-08T09:01:38","modified_gmt":"2026-08-08T06:01:38","slug":"jpeg-xl","status":"publish","type":"format","link":"https:\/\/picajet.com\/articles\/formats\/jpeg-xl\/","title":{"rendered":"JPEG XL"},"content":{"rendered":"

JPEG XL grew out of two independent research efforts \u2014 Google’s Pik codec and Cloudinary<\/a>‘s FUIF \u2014 which the JPEG committee merged into a single project in January 2019. The goal was to fix JPEG’s aging limitations (8-bit-only color, no alpha channel, poor efficiency at high resolution) while also unifying the fragmented landscape of lossy, lossless, and animated formats competing to replace it: WebP, AVIF, and HEIC. The bitstream froze in October 2021, with the ISO\/IEC 18181 standard published across several parts through 2022.<\/p>

JPEG XL’s adoption story has been unusually turbulent for a format this technically capable. Google shipped it experimentally in Chrome from version 91 through 109, then removed it in Chrome 110 (February 2023), citing insufficient ecosystem interest \u2014 a decision that stalled web-facing adoption for years even as Apple added default support in Safari 17 later that same year. As of 2026 only Safari renders JPEG XL out of the box; Chrome and Firefox both have working decoders sitting behind experimental flags, with Google signaling a possible default-on shift in the second half of the year.<\/p>

For a DAM, JPEG XL is currently a format to track rather than rely on. Its ability to losslessly re-encode an existing JPEG into a meaningfully smaller file \u2014 and reconstruct the exact original bytes on demand \u2014 is genuinely useful for shrinking storage on JPEG-heavy archives without any quality loss, and its native EXIF\/XMP\/ICC support means metadata survives the round-trip. But because most browsers still can’t render it without a user manually flipping a flag, it is not yet safe as a delivery\/preview format in a DAM’s public-facing pipeline; treat it as an efficiency layer under the hood, not a replacement for JPEG or TIFF in day-to-day workflows.<\/p>","protected":false},"excerpt":{"rendered":"

A royalty-free codec (ISO\/IEC 18181) offering both lossy and lossless modes, high bit depth, and lossless JPEG transcoding, built as a unified successor to JPEG, PNG and GIF.<\/p>\n","protected":false},"author":0,"featured_media":0,"template":"","meta":{"footnotes":"","faq":[{"question":"Is JPEG XL ready to serve as a DAM archival master in 2026?","answer":"Not yet. While its lossless mode and lossless-JPEG-transcode capability are technically strong, Chrome and Firefox still ship JPEG XL disabled by default, and archival-scale tooling and long-term format stability aren't proven. Keep TIFF, JPEG 2000, or RAW as the durable master for now."},{"question":"Which browsers support JPEG XL natively?","answer":"Only Safari, since version 17 in 2023. Chrome and Firefox both have working decoders, but as of 2026 they remain gated behind experimental flags rather than enabled by default."},{"question":"Can JPEG XL losslessly repackage an existing JPEG file?","answer":"Yes \u2014 JPEG XL can losslessly re-encode an existing JPEG into a meaningfully smaller .jxl file that reconstructs the exact original bytes on demand, which is useful for shrinking storage on JPEG-heavy archives without any quality loss."},{"question":"What metadata does the JPEG XL container support?","answer":"JPEG XL natively supports EXIF, XMP, JUMBF boxes, and full ICC profile embedding, giving it the richest metadata model of any format in this comparison on paper."},{"question":"Why did JPEG XL adoption stall on the web?","answer":"Google shipped it experimentally in Chrome from version 91 through 109, then removed it in Chrome 110 (February 2023), citing insufficient ecosystem interest \u2014 a decision that stalled adoption even as Safari added default support later that same year."},{"question":"What can JPEG XL do that JPEG cannot?","answer":"JPEG XL adds a lossless Modular mode, up to 32-bit float samples for HDR, and support for up to 4,099 channels (CMYK, alpha, spot colors) \u2014 all beyond what baseline JPEG's 8-bit design allows."},{"question":"Is JPEG XL safe to use in a DAM's public-facing delivery pipeline?","answer":"Not yet. Because most browsers can't render it without a user manually enabling a flag, JPEG XL isn't currently safe as a delivery or preview format for a general audience."},{"question":"What's a practical DAM use for JPEG XL today?","answer":"Treat it as an efficiency layer under the hood \u2014 for example losslessly repackaging JPEG-derived assets to save storage \u2014 rather than as a replacement for JPEG or TIFF in day-to-day ingest and delivery workflows."}],"checked_date":"2026-08-07","sources":[{"statement":"JPEG XL's bitstream was frozen in October 2021, with ISO\/IEC 18181 parts published through 2022.","source_name":"ISO\/IEC 18181-2 (File format)","url":"https:\/\/www.iso.org\/standard\/80617.html","checked":"2026-08-07"},{"statement":"JPEG XL originated from Google's Pik codec and Cloudinary's FUIF, merged by the JPEG committee in January 2019.","source_name":"Google Open Source Blog: Journey to JPEG XL","url":"https:\/\/opensource.googleblog.com\/2026\/06\/journey-to-jpeg-xl-how-open-source-experiments-shaped-the-future-of-image-coding.html","checked":"2026-08-07"},{"statement":"Chrome removed JPEG XL support in Chrome 110 (Feb 2023); Safari 17 added full support later that year.","source_name":"Phoronix: JPEG XL Possible Chrome Return","url":"https:\/\/www.phoronix.com\/news\/JPEG-XL-Possible-Chrome-Back","checked":"2026-08-07"},{"statement":"JPEG XL supports native EXIF and XMP boxes plus lossless transcoding of existing JPEG files.","source_name":"libjxl format_overview.md","url":"https:\/\/github.com\/libjxl\/libjxl\/blob\/main\/doc\/format_overview.md","checked":"2026-08-07"}],"kicker":"","fact_checker":0,"reading_time":0,"revisions":[],"seo_title":"","seo_description":"","noindex":false,"ext":"jxl","full_name":"JPEG XL Image Coding System","vendor_name":"JPEG committee (ISO\/IEC JTC 1), from technology developed by Google and Cloudinary","introduced":"Bitstream frozen October 2021; ISO\/IEC 18181 published in parts across 2021\u20132022","container_notes":"JPEG XL combines a lossy VarDCT mode for photographic content with a lossless Modular mode, supports up to 32-bit float samples for HDR and up to 4,099 channels (CMYK, alpha, spot colors), and can losslessly repackage an existing JPEG into a smaller .jxl file that reconstructs byte-for-byte. The container natively supports EXIF, XMP, JUMBF boxes and full ICC profile embedding, giving it the richest metadata model of any format in this list on paper.","open_with":[{"platform":"macOS","how":"Native support in Preview and Finder Quick Look since macOS 14 Sonoma \/ iOS 17"},{"platform":"Safari","how":"Full support since Safari 17 (2023) \u2014 the only major browser enabling it by default"},{"platform":"Windows","how":"Free 'JPEG XL Image Extension' from the Microsoft Store adds Photos app and Explorer preview support"},{"platform":"Chrome \/ Firefox","how":"Decoders exist but are gated behind experimental flags (chrome:\/\/flags, Firefox Labs) as of 2026, not enabled by default"}],"archive_advice":"Too young for DAM master duty as of 2026: while its lossless mode and lossless-JPEG-transcode capability are technically strong, Chrome and Firefox still ship it disabled by default, and archival-scale tooling and long-term format stability aren't proven yet. Use it selectively for space-efficient lossless repackaging of JPEG-derived assets, but keep TIFF, JPEG 2000, or RAW as the durable master until browser and ecosystem support solidify.","related":[],"tool_link":""},"silo":[23],"class_list":["post-3262","format","type-format","status-publish","hentry","silo-formats"],"_links":{"self":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/3262","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format"}],"about":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/types\/format"}],"version-history":[{"count":3,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/3262\/revisions"}],"predecessor-version":[{"id":3786,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/3262\/revisions\/3786"}],"wp:attachment":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/media?parent=3262"}],"wp:term":[{"taxonomy":"silo","embeddable":true,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/silo?post=3262"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}