Jump to content

JPEG XL: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
m →Codec implementations: The licenses are not dueling, they are dual. Aka spelling edit
→Official software support: More comprehensive
Line 166: Line 166:


===Official software support===
===Official software support===
* [[Apple Inc.]]<ref>{{cite web |title=JPEG XL: How It Started, How It’s Going |url=https://cloudinary.com/blog/jpeg-xl-how-it-started-how-its-going |publisher=Cloudinary |access-date=3 November 2023 |date=12 July 2023}}</ref>
** [[iOS]]/[[iPadOS]] 17 and later – system-wide reading including [[Files (Apple)|Files]] and [[Photos (Apple)|Photos]]
⚫
** [[macOS]] [[macOS Sonoma|Sonoma]] (version 14) and later – reading on [[Finder (software)|Finder]] and [[Preview (macOS)|Preview]]<ref>{{Cite web |date=2023-10-29 |title=macOS 14 Sonoma: The Ars Technica review |url=https://arstechnica.com/gadgets/2023/09/macos-14-sonoma-the-ars-technica-review/11/ |access-date=2023-10-29 |website=ArsTechnica |language=en}}</ref>
** [[visionOS]] (presumed)
** [[watchOS]] 10 and later
⚫
** [[Safari (web browser)|Safari 17]] and later<ref>{{Cite web |title=Explore media formats for the web - WWDC23 - Videos |url=https://developer.apple.com/videos/play/wwdc2023/10122/ |access-date=2023-06-06 |website=Apple Developer |language=en}}</ref><ref>{{Cite web |title=Safari 17 Beta Release Notes |url=https://docs.developer.apple.com/documentation/safari-release-notes/safari-17-release-notes |access-date=2023-06-06 |website=Apple Developer Documentation |language=en-US}}</ref> via the [[WebKit]] engine<ref>{{Cite web |title=208235 – Support JPEG XL images |url=https://bugs.webkit.org/show_bug.cgi?id=208235 |access-date=2023-07-28 |website=bugs.webkit.org}}</ref>
* [[GNOME Web|Epiphany]] 45<ref>{{Cite web |date=2023-04-12 |title=Support for JPEG-XL (#2040) · Issues · GNOME / Epiphany · GitLab |url=https://gitlab.gnome.org/GNOME/epiphany/-/issues/2040 |access-date=2023-07-28 |website=GitLab |language=en}}</ref> via the WebKitGTK engine<ref>{{Cite web |title=257871 – [CMake] Enable JPEG XL by default, no longer experimental |url=https://bugs.webkit.org/show_bug.cgi?id=257871 |access-date=2023-07-28 |website=bugs.webkit.org}}</ref>
* [[GNOME Web|Epiphany]] 45<ref>{{Cite web |date=2023-04-12 |title=Support for JPEG-XL (#2040) · Issues · GNOME / Epiphany · GitLab |url=https://gitlab.gnome.org/GNOME/epiphany/-/issues/2040 |access-date=2023-07-28 |website=GitLab |language=en}}</ref> via the WebKitGTK engine<ref>{{Cite web |title=257871 – [CMake] Enable JPEG XL by default, no longer experimental |url=https://bugs.webkit.org/show_bug.cgi?id=257871 |access-date=2023-07-28 |website=bugs.webkit.org}}</ref>
* [[iOS]] V17+ has full support and works in default photos app
* [[ImageMagick]] – reading and writing of JPEG XL images
⚫
* [[KDE]] applications can be built with KImageFormats plugin with native JPEG XL support. <ref>{{cite web |url=https://invent.kde.org/frameworks/kimageformats |title=KImageFormats |website=[[KDE Invent]] |access-date=29 October 2023}}</ref> This gives most KDE apps native support for both read and writing and works with all apps from the Dolphin file manager including Gwenview image viewer, [[Krita]] digital painting tool and [[Digikam photo manager]].
* [[ImageMagick]] supports reading and writing of Jpeg XL images.
⚫
* [[KDE]] applications can be built with KImageFormats plugin with native JPEG XL support. <ref>{{cite web |url=https://invent.kde.org/frameworks/kimageformats |title=KImageFormats |website=[[KDE Invent]] |access-date=29 October 2023}}</ref> This gives most KDE apps native support for both read and writing and works with all apps from the Dolphin file manager including Gwenview image viewer, [[Krita]] digital painting tool and [[Digikam photo manager]].
⚫
* [[Safari (web browser)|Safari 17]]<ref>{{Cite web |title=Explore media formats for the web - WWDC23 - Videos |url=https://developer.apple.com/videos/play/wwdc2023/10122/ |access-date=2023-06-06 |website=Apple Developer |language=en}}</ref><ref>{{Cite web |title=Safari 17 Beta Release Notes |url=https://docs.developer.apple.com/documentation/safari-release-notes/safari-17-release-notes |access-date=2023-06-06 |website=Apple Developer Documentation |language=en-US}}</ref> via the [[WebKit]] engine<ref>{{Cite web |title=208235 – Support JPEG XL images |url=https://bugs.webkit.org/show_bug.cgi?id=208235 |access-date=2023-07-28 |website=bugs.webkit.org}}</ref>
⚫
* [[MacOS]] v14.0+ supports limited native JPEG XL support including thumbnail support in the finder. <ref>{{Cite web |date=2023-10-29 |title=macOS 14 Sonoma: The Ars Technica review |url=https://arstechnica.com/gadgets/2023/09/macos-14-sonoma-the-ars-technica-review/11/ |access-date=2023-10-29 |website=ArsTechnica |language=en}}</ref>


===Unofficial or indirect support===
===Unofficial or indirect support===

Revision as of 05:21, 3 November 2023

JPEG XL
Filename extension
.jxl
Internet media type
image/jxl[a]
Magic numberFF 0A or 00 00 00 0C 4A 58 4C 20 0D 0A 87 0A[2]
Developed by
Type of formatLossy/lossless bitmap image format
Extended from
StandardISO/IEC 18181[4]
Open format?Yes (royalty-free[5])
Website

JPEG XL is a royalty-free raster-graphics file format that supports both lossy and lossless compression. It is designed to outperform existing raster formats and thus become their universal replacement.[5]

Name

The name consists of JPEG (for the Joint Photographic Experts Group, which is the committee which designed the format), X (part of the name of several JPEG standards since 2000: JPEG XT, JPEG XR, JPEG XS), and L (for long-term). The L was included because the authors' intention is for the format to replace the legacy JPEG and last just as long, too.[6]

Authors

The main authors of the specification are Jyrki Alakuijala, Jon Sneyers, and Luca Versari. Other collaborators are Sami Boukortt, Alex Deymo, Moritz Firsching, Thomas Fischbacher, Eugene Kliuchnikov, Robert Obryk, Alexander Rhatushnyak, Zoltan Szabadka, Lode Vandevenne, and Jan Wassenberg.

History

In August 2017, JTC1 / SC29 / WG1 (JPEG) published a call for proposals for JPEG XL, the next generation image encoding standard.[7] The proposals were submitted by September 2018, leading to a committee draft in July 2019.[8] It was mainly based on a combination of a proposal called PIK,[9] submitted by Google, and a proposal called FUIF[10] — itself based on FLIF — submitted by Cloudinary.

The bitstream was informally frozen on 24 December 2020 with the release of version 0.2 of the libjxl reference software.[11] The file format and core coding system were formally standardized on 13 October 2021 and 30 March 2022 respectively.[4][12]

Description

The JPEG XL call for proposals[7] talks about the requirement of a next generation image compression standard with substantially better compression efficiency (60% improvement) comparing to JPEG. The standard is expected to outperform the still image compression performance shown by HEIC, AVIF, WebP, and JPEG 2000. It also provides efficient lossless recompression options for images in the traditional/legacy JPEG format.

JPEG XL supports lossy compression and lossless compression of ultra-high-resolution images (up to 1 terapixel), up to 32 bits per component, up to 4099 components (including alpha transparency), animated images, and embedded previews. It has features aimed at web delivery such as advanced progressive decoding[13] and minimal header overhead, as well as features aimed at image editing and digital printing, such as support for multiple layers, CMYK, and spot colors. It is specifically designed to seamlessly handle wide color gamut color spaces with high dynamic range such as Rec. 2100 with the PQ or HLG transfer function.

Features

The main features are:[14][15][16]

  • Image dimensions of over a billion (230−1) pixels on each side.[17]
  • Up to 4099 channels. Main channels: either one channel for grayscale, three channels for RGB, or four channels for CMYK. The rest of the channels are optional and can be used to store alpha (either "straight" or "premultiplied"), depth, or thermal data.[17]
  • There can be multiple frames, with non-zero duration (for animation) or with zero duration (making them work more like layers in graphics software). Frames can be smaller or larger than the image canvas and can be blended in various ways. However, regular video codecs are still preferred for encoding realistic content.
  • Independent tiles: Decoding of sections of a large image by allowing images to be stored in tiles.
  • Progressive decoding: Mode specifically designed for responsive loading of large images depending on the viewing device's resolution.
  • Reversible JPEG transcoding: ~20% size reduction can be achieved.
  • Lossless encoding for any channel, including alpha.
  • Support for both photographic and synthetic imagery: The format features two complementary modes that can be used depending on the image contents.
  • Graceful quality degradation across a large range of bitrates: Quality loss isn't as abrupt as with older formats.
  • Perceptually optimized reference encoder which uses a perceptual color space, adaptive quantization, and conservative default settings.
  • Support for wide color gamut and HDR: JPEG XL has built-in support for various color spaces, transfer curves, and high screen brightness.
  • Efficient encoding and decoding without requiring specialized hardware: JPEG XL is about as fast to encode and decode as old JPEG using libjpeg-turbo and an order of magnitude faster to encode and decode compared to HEIC with x265.[17] It is also parallelizable.
  • Royalty-free format with an open-source reference implementation available on GitHub under a 3-clause BSD license.[18]

Technical details

refer to caption
JPEG XL codec architecture diagram

JPEG XL is based on ideas from Google's PIK format and Cloudinary's FUIF format (which was in turn based on FLIF).[19]

The format is mainly based on two encoding modes:

  • VarDCT mode (variable-blocksize DCT) – it is based from the same DCT algorithm as legacy JPEG, but blocks, instead of being restricted to 8×8, come in various sizes (2×2 up to 256×256), non-square shapes (e.g. 16×8, 8×32, 32×64), or can use another transforms (AFV, Hornuss). It is only used for the 3 color channels, which typically use the XYB color space (although YCbCr is also supported in order to recompress legacy JPEG). The VarDCT mode is based on (lossy) PIK. Lossy modes typically use the XYB color space derived from LMS.[20]
  • Modular mode is responsible, among other things, for efficient lossless content encoding and also for lossy and near-lossless purposes. Modular can also be used internally in VarDCT to save 2D data, i.e. everything except the AC (high-frequency) DCT coefficients, including the DC image (which is always a 1:8 subsampled image so also includes low-frequency AC coefficients in case block sizes larger than 8×8 are used), the weights of adaptive quantization and filter strengths.

Any additional/extra channels (e.g. alpha, depth, thermal, spot colors, etc.) are always encoded in the modular mode. It was based on FUIF, combined with elements of lossless PIK, lossless WebP, and new ideas that have been developed during the collaborative phase of the standardization process.[21] Modular mode allows lossy compression with the help of the modified Haar transform called "squeeze" which has progressive properties, quality of the image increases with the amount of data loaded.

One of the ways VarDCT-based images can be loaded more progressively is by saving the DC coefficients in a separate "DC frame" that uses modular squeeze: allowing previews corresponding to 1:16, 1:32 etc subsampled images. A squeeze transform can also be used to encode the alpha channel progressively together with VarDCT-encoded color channels, making both modes work in tandem.

JPEG XL defaults to a visually near-lossless setting that still provides good compression.[17]

These modes can be assisted by separate modeling of specific image features called:

  • Splines for coding e.g. hairs (not yet used by the reference encoder).
  • Repeating "patches" like text, dots, or sprites.
  • Noise synthesis: since noise is hard to compress, it is better to separate it out and then regenerate it in the decoder. This is similar to film grain synthesis in modern video codecs like AV1, although JPEG XL's noise synthesis is not aiming to mimick the granularity of analog photographic film, but rather to model the photon noise at the pixel level like what you get on a digital camera at high ISO settings.

JPEG XL codec can losslessly transcode a widely-supported subset of JPEG files, by directly copying JPEG's DCT block coefficients to 8×8 VarDCT blocks, making smaller file sizes possible due to JPEG XL's superior entropy coding. This process is reversible and it allows for the original JPEG file to be reconstructed bit-for-bit, although constraints limit support for some files.[22]

Prediction is run using a pixel-by-pixel decorrelator without side information, including a parameterized self-correcting weighted ensemble of predictors. Context modeling includes specialized static models and powerful meta-adaptive models that take local error into account, with a signaled tree structure and predictor selection per context. Entropy coding is LZ77-enabled and can use either asymmetric numeral systems or Prefix codes (useful for low-complexity encoders, or reducing the overhead of short streams).[15]

Animated (multi-frame) images do not perform advanced inter-frame prediction, though some rudimentary inter-frame coding tools are available:

  • Frames can be smaller than the full canvas size, leaving other pixels untouched.
  • Frames support several blending modes in addition to replacing previous frames, such as addition or multiplication.[23]
  • Up to four frames can be remembered and referenced by later frames, using the "patches" coding tool.

Industry support and adoption

Besides Cloudinary and Google (originally[clarification needed]), throughout JPEG XL's preliminary implementation in web browsers, various representatives of well-known industry brand names have publicly voiced support for JPEG XL as their preferred choice, including Facebook,[24][25] Adobe,[26][27] Intel and the Video Electronics Standards Association,[28][29] The Guardian,[30][31] Flickr and SmugMug,[32] Shopify,[33] the Krita Foundation,[34] and Serif Ltd.[35]

Software

Codec implementations

JPEG XL Reference Software (libjxl)
Initial releaseDecember 27, 2019; 4 years ago (2019-12-27)[36]
Stable release
0.8.2 / June 14, 2023; 16 months ago (2023-06-14)
Repositoryhttps://github.com/libjxl/libjxl[37] Edit this on Wikidata
Written inC++
Operating system
LicenseNew BSD License (previously Apache License 2.0)
Websitejpeg.org/jpegxl Edit this on Wikidata
  • JPEG XL Reference Software (libjxl)
    • license: New BSD License (previously Apache License 2.0)
    • contains (among others):
      • encode/decode library libjxl
      • encoder cjxl
      • decoder djxl
      • fast lossless-only encoder fjxl
      • tool for benchmarking speed and quality of image codecs benchmark_xl
      • GIMP and Gtk pixbuf plugin file-jxl
  • J40: Independent, self-contained JPEG XL decoder[38]
  • libjxl-tiny: a simpler encoder implementation of JPEG XL, aimed at photographic images without an alpha channel.[39]
  • jxlatte: Java JPEG XL decoder [40]
  • jxl_decode: A Python JPEG XL decoder.[41]
  • jpeg-xl-encode: a PHP JPEG XL wrapper for an encoder.[42]
  • hydrium: Fast, ultra-low-memory, streaming JPEG XL encoder written in portable C.[43]
  • jxl-oxide: Small JPEG XL decoder written completely in Rust. [44]

Official software support

Unofficial or indirect support

Preliminary web browser support

Support for JPEG XL in Chromium and Chrome web browsers was introduced for testing April 1, 2021[59] and removed on December 9, 2022 - with support removed in version 110.[60][61] The Chrome team cited a lack of interest from the ecosystem, insufficient improvements, and a wish to focus on improving existing formats as reasons for removing JPEG XL support.[59][62][60] The decision was met with opposition from the community, with many voicing support for JPEG XL on Chromium's bug tracker.[59][63][62] Jon Sneyers, co-author of the JPEG XL spec, has questioned the conclusions drawn by the Chrome team, saying: "I think there has been an unfortunate misinterpretation of the data ... which has unfortunately lead [sic] to an incorrect decision."[64] The decision was also criticized by Greg Farough from the Free Software Foundation, who said it demonstrated Google's "disturbing amount of control" over the web and web browsers.[65]

Standardization status

Common Name Part First public release date (First edition) ISO/IEC Number Formal Title
JPEG XL Part 1 30 March 2022 ISO/IEC 18181-1 JPEG XL Image Coding System — Part 1: Core coding system[4]
Part 2 13 October 2021 ISO/IEC 18181-2 JPEG XL Image Coding System — Part 2: File format[12]
Part 3 3 October 2022 ISO/IEC 18181-3 JPEG XL Image Coding System — Part 3: Conformance testing
Part 4 5 August 2022 ISO/IEC 18181-4 JPEG XL Image Coding System — Part 4: Reference software

Rivals

Notes

  1. ^ This is unofficial, but de facto. See the official list of media types.[1]

References

  1. ^ "Media Types". IANA. Archived from the original on 2022-10-21. Retrieved 2022-10-21.
  2. ^ "JPEG XL Format Overview". GitHub. Archived from the original on 2022-10-20. Retrieved 2022-10-20.
  3. ^ a b "fuif/README.md". GitHub. 2019-04-04. Archived from the original on 2021-04-24.
  4. ^ a b c ISO/IEC 18181-1:2022 Information technology — JPEG XL image coding system — Part 1: Core coding system.
  5. ^ a b "Can JPEG XL Become the Next Free and Open Image Format? - Slashdot". 2021-02-20. Archived from the original on 2021-12-30.
  6. ^ "Support for reading/Writing JPEG XL images (#4681) · Issues · GNOME / GIMP". 2021-02-26. Archived from the original on 2021-12-30.
  7. ^ a b "N79010 Final Call for Proposals for a Next-Generation Image Coding Standard (JPEG XL)" (PDF). ISO/IEC JTC 1/SC 29/WG 1 (ITU-T SG16). 15 April 2018.
  8. ^ Rhatushnyak, Alexander; Wassenberg, Jan; Sneyers, Jon; Alakuijala, Jyrki; Vandevenne, Lode; Versari, Luca; Obryk, Robert; Szabadka, Zoltan; Kliuchnikov, Evgenii; Comsa, Iulia-Maria; Potempa, Krzysztof; Bruse, Martin; Firsching, Moritz; Khasanova, Renata; Ruud van Asseldonk; Boukortt, Sami; Gomez, Sebastian; Fischbacher, Thomas (2019). "Committee Draft of JPEG XL Image Coding System". arXiv:1908.03565 [eess.IV].
  9. ^ "PIK, A new lossy/lossless image format for photos and the internet". GitHub. Retrieved 2022-10-17.
  10. ^ "FUIF, Free Universal Image Format". GitHub. Retrieved 2022-10-17.
  11. ^ "v0.2 JPEG XL Reference Software". GitLab. 2021-02-19. Archived from the original on 2021-10-20.
  12. ^ a b ISO/IEC 18181-2:2021 Information technology — JPEG XL image coding system — Part 2: File format.
  13. ^ "Using Saliency in progressive JPEG XL images". Retrieved 2022-10-17.
  14. ^ "JPEG XL reaches Committee Draft". JPEG.org. 2019-08-03. Archived from the original on 2019-08-03. Retrieved 2019-08-03. The current contributors have committed to releasing it publicly under a royalty-free and open source license.
  15. ^ a b "JPEG XL White Paper" (PDF). JPEG.org. 2021-01-29. Archived (PDF) from the original on 2 May 2021. Retrieved 2021-03-17.
  16. ^ "JPEG XL vs. AVIF - Page 6". encode.su. Retrieved 2022-10-22.
  17. ^ a b c d Sneyers, Jon (26 May 2020). "How JPEG XL Compares to Other Image Codecs". Cloudinary. Archived from the original on 2021-12-30. Retrieved 2021-02-19.
  18. ^ "libjxl/libjxl: JPEG XL image format reference implementation". GitHub. Archived from the original on 2022-05-22. Retrieved 2022-06-05.
  19. ^ "FLIF - Free Lossless Image Format". Archived from the original on 2021-12-21. Retrieved 2021-04-06.
  20. ^ Alakuijala, Jyrki; van Asseldonk, Ruud; Boukortt, Sami; Szabadka, Zoltan; Bruse, Martin; Comsa, Iulia-Maria; Firsching, Moritz; Fischbacher, Thomas; Kliuchnikov, Evgenii; Gomez, Sebastian; Obryk, Robert; Potempa, Krzysztof; Rhatushnyak, Alexander; Sneyers, Jon; Szabadka, Zoltan; Vandervenne, Lode; Versari, Luca; Wassenberg, Jan (6 September 2019). "JPEG XL next-generation image compression architecture and coding tools". In Tescher, Andrew G; Ebrahimi, Touradj (eds.). Applications of Digital Image Processing XLII. Vol. 11137. p. 20. Bibcode:2019SPIE11137E..0KA. doi:10.1117/12.2529237. ISBN 9781510629677.
  21. ^ "FLIF, 3 Sep 2021, jonsneyers comment". GitHub.
  22. ^ Sneyers, Jon (2021-12-10). "Feature request: allow jbrd to reconstruct a part of the file when it's not possible for the whole file". GitHub.
  23. ^ "JPEG XL reference implementation". GitHub. 3 December 2021. Archived from the original on 30 December 2021. Retrieved 24 June 2021.
  24. ^ Andre, Erik (2021-04-20). "Statement of support by Facebook on Chromium's issue #1178058". bugs.chromium.org. Retrieved 2022-11-03.
  25. ^ Andre, Erik (2021-05-24). "Statement of support by Facebook on Firefox's issue #1539075". bugzilla.mozilla.org. Retrieved 2022-11-03.
  26. ^ Rosenthol, Leonard (2021-06-07). "Statement of support by Adobe on Firefox's issue #1539075". bugzilla.mozilla.org. Retrieved 2022-11-03.
  27. ^ Chan, Eric (2022-08-23). "Statement of support by Adobe on Chromium's issue #1178058". bugs.chromium.org. Retrieved 2022-11-03.
  28. ^ Wooster, Roland (2022-08-24). "Statement of support on Chromium's issue #1178058 by VESA's DisplayHDR Chairman and Principal Engineer at Intel's Client Computing Group". bugs.chromium.org. Retrieved 2022-11-03.
  29. ^ Wooster, Roland (2022-11-11). "Reinforced statement of support on Chromium's issue #1178058 by VESA's DisplayHDR Chairman and Principal Engineer at Intel's Client Computing Group". bugs.chromium.org. Retrieved 2022-11-11.
  30. ^ Chauvin, Mariot (2022-08-26). "Statement of support by The Guardian on Chromium's issue #1178058". bugs.chromium.org. Retrieved 2022-11-03.
  31. ^ Chauvin, Mariot (2022-01-13). "Statement of support by The Guardian on Firefox's issue #1539075". bugzilla.mozilla.org. Retrieved 2022-11-03.
  32. ^ MacAskill, Don (2022-01-04). "Statement of support by Flickr and SmugMug on Firefox's issue #1539075". bugzilla.mozilla.org. Retrieved 2022-11-03.
  33. ^ Bendell, Colin (2022-10-17). "Statement of support by Shopify on Chromium's issue #1178058". bugs.chromium.org. Retrieved 2022-11-03.
  34. ^ Rempt, Rempt (2022-11-10). "Statement of support by the Krita Foundation on Chromium's issue #1178058". bugs.chromium.org. Retrieved 2022-11-11.
  35. ^ Brightman, Tony (2022-11-11). "Statement of support by Serif Ltd.'s SerifLabs on Chromium's issue #1178058". bugs.chromium.org. Retrieved 2022-11-11.
  36. ^ "Update JPEG-XL with latest changes". GitHub. 2019-12-27. Retrieved 10 October 2022.
  37. ^ "PLEASE DO NOT OPEN NEW ISSUES HERE". Retrieved 27 May 2021.
  38. ^ J40: Independent, self-contained JPEG XL decoder
  39. ^ "libjxl-tiny". GitHub. 4 November 2022.
  40. ^ "jxlatte". GitHub. 23 December 2022.
  41. ^ "jxl_decode". GitHub. 8 June 2023.
  42. ^ Siipola, Johannes (2022-10-31), JPEG XL Encode, retrieved 2022-11-29
  43. ^ Leo Izen (6 March 2023). "hydrium". GitHub. Retrieved 2023-04-02.
  44. ^ Wonwoo Choi (29 October 2023). "jxl-oxide". GitHub. Retrieved 2023-09-29.
  45. ^ "JPEG XL: How It Started, How It's Going". Cloudinary. 12 July 2023. Retrieved 3 November 2023.
  46. ^ "macOS 14 Sonoma: The Ars Technica review". ArsTechnica. 2023-10-29. Retrieved 2023-10-29.
  47. ^ "Explore media formats for the web - WWDC23 - Videos". Apple Developer. Retrieved 2023-06-06.
  48. ^ "Safari 17 Beta Release Notes". Apple Developer Documentation. Retrieved 2023-06-06.
  49. ^ "208235 – Support JPEG XL images". bugs.webkit.org. Retrieved 2023-07-28.
  50. ^ "Support for JPEG-XL (#2040) · Issues · GNOME / Epiphany · GitLab". GitLab. 2023-04-12. Retrieved 2023-07-28.
  51. ^ "257871 – [CMake] Enable JPEG XL by default, no longer experimental". bugs.webkit.org. Retrieved 2023-07-28.
  52. ^ "KImageFormats". KDE Invent. Retrieved 29 October 2023.
  53. ^ "Jpeg Xl Wic". GitHub. 27 November 2021. Archived from the original on 30 December 2021. Retrieved 23 March 2021.
  54. ^ "JXL WIN Thumb". GitHub. 11 June 2022. Retrieved 27 December 2022.
  55. ^ "JXLook". GitHub. December 2021. Archived from the original on 2021-12-30. Retrieved 2021-03-01.
  56. ^ "libjxl gdk-pixbuf plugin". GitHub. Retrieved 2022-11-26.
  57. ^ "Qt jpegxl image plugin". GitHub. Retrieved 29 October 2023.
  58. ^ "1539075 - (JPEG-XL) Implement support for JPEG XL (Image/JXL)". Archived from the original on 2022-01-04. Retrieved 2021-03-01.
  59. ^ a b c "Issue 1178058: JPEG XL decoding support (image/jxl) in blink (tracking bug)". bugs.chromium.org. Retrieved 2022-12-16.
  60. ^ a b Proven, Liam. "Google drops forthcoming version of JPEG from Chromium". www.theregister.com. Retrieved 2023-06-06.
  61. ^ JPEG XL support
  62. ^ a b Sneyers, Jon (2022-11-02). "The Case for JPEG-XL". Cloudinary Blog. Retrieved 2022-12-30.
  63. ^ Shankland, Stephen (2022-11-03). "Chrome Banishes JPEG XL Photo Format That Could Save Phone Space". CNET. Retrieved 2022-11-03.
  64. ^ Sneyers, Jon (2022-12-14). "Re: Intent to Prototype: JPEG XL decoding support (image/jxl) in blink". blink-dev (Mailing list). Retrieved 2022-12-30.
  65. ^ Purdy, Kevin (2023-04-17). "FSF: Chrome's JPEG XL killing shows how the web works under browser hegemony". Ars Technica. Retrieved 2023-06-06.
Wikimedia Commons has media related to JPEG XL.
Retrieved from "https://en.wikipedia.org/w/index.php?title=JPEG_XL&oldid=1183261589"