Hacker ApprovedDepartments

JPEG XL

Hacker Approved

Image format in Developer tools

Recommended as a versatile image format that can replace JPEG, PNG and GIF, convert old JPEGs losslessly, compress better and decode progressively; critics cite security risk and format fatigue.

Recommended as a versatile image format that can replace JPEG, PNG and GIF, convert old JPEGs losslessly, compress better and decode progressively; critics cite security risk and format fatigue.

240 people gave an opinion

recommend it
172
criticize it
68
approval share
72%
Each figure is 2 people. RecommendsCriticizes

Recommended in 11 of 13 months

  1. November 2025: recommended
  2. December 2025: recommended
  3. January 2026: recommended
  4. February 2026: recommended
  5. March 2026: recommended
  6. April 2026: not recommended
  7. May 2026: recommended
  8. June 2026: recommended
  9. July 2026: recommended
  10. August 2026: recommended
  11. September 2026: recommended
  12. October 2026: recommended
  13. November 2026: not recommended (month in progress)

Why it carries the badge

  • 172 people recommend itNeeds 10 or more, met.
  • 2.5 recommenders for every criticNeeds 2 to 1 or better, met.
  • Recommended in 11 of 13 monthsNeeds 4 or more, met.

The same three rules apply to every product, and the badge can’t be bought. How the badge works

What people say about it

The reasons people give, with the number of comments that give each one. Open a reason to read what they said.

Why people recommend it

Each mark is one comment

  • Lossless transcoding of existing JPEGs

    “it is possible to do a transcode of all of your existing ('classic') JPEG files with zero (visual) losses in quality”

    Comment from 16 Oct 2026 in “JPEG XL vs. AVIF for web use-cases”

    “you can losslessly convert back and forth between the two for smaller filesize in JPEG XL with no quality loss”

    Comment from 14 Sep 2026 in “The case against JPEG XL”

    “JXL gives you progressive rendering, easy upgradability on JPEGs, and better lossless and high bitrate images.”

    Comment from 16 Oct 2026 in “JPEG XL vs. AVIF for web use-cases”
  • One format for every use

    “The format is designed to be as general as possible, potentially replacing many common (JPEG, GIF, PNG) and professional image formats.”

    Comment from 7 Oct 2026 in “Shipping JPEG XL in Chrome”

    “JPEG XL is probably the first format which actually achieves this, covering all kinds of pictures you can think of”

    Comment from 7 Oct 2026 in “Shipping JPEG XL in Chrome”

    “a single format that works both for 10000x10000 lossless scientific images, and for 256x256 lossy web photos”

    Comment from 14 Sep 2026 in “The case against JPEG XL”
  • Better compression than AVIF

    “JPEG XL easily beats AVIF on the not-so-long tail of use cases and having compatible viewers everywhere is quite useful.”

    Comment from 14 Sep 2026 in “The case against JPEG XL”

    “At around 98KB, the JXL looks significantly better, and at around 240KB already looks really close to the final image”

    Comment from 14 Sep 2026 in “The case against JPEG XL”

    “it often handles clean edges and smooth surfaces (the likes of which you might see in digital art) better”

    Comment from 17 Oct 2026 in “JPEG XL vs. AVIF for web use-cases”
  • Progressive decoding

    “JPEG XL supports progressive decoding, so you can see the picture in lower quality long before the download has finished”

    Comment from 1 Dec 2025 in “Google unkills JPEG XL?”

    “It is, however, a very useful image format feature, giving you most information from the spinner/sticker/emoji/sprite”

    Comment from 13 Jan 2026 in “Chromium Has Merged JpegXL”

    “the JPEG XL ability to truncate the bitstream anywhere, or send the progressive updates for salient regions first”

    Comment from 14 Sep 2026 in “The case against JPEG XL”

What people warn about

Each mark is one comment

  • Large security attack surface

    “Google chose not to include JPEG XL in Chrome because vulnerabilities in the library could compromise the software”

    Comment from 25 Oct 2026 in “Broccoli2Shell: Brotli decoder RCE in Node.js, Python and more”

    “The C++ decoder was simply unsafe and they would not implement it until a memory-safe decoder was available.”

    Comment from 24 Aug 2026 in “Firefox intent to ship: JPEG XL”

    “JPEG XL carries a large security surface area which neither company was comfortable including in its current shape”

    Comment from 2 Dec 2025 in “Google unkills JPEG XL?”
  • Yet another format to support

    “I think they probably could have added those though, and then we wouldn't have yet another format to support for eternity.”

    Comment from 14 Sep 2026 in “The case against JPEG XL”

    “with only 20% improvement I can't say I'm super excited by this, compared to the pain of dealing with yet another new image format”

    Comment from 24 Nov 2025 in “Chrome Jpegxl Issue Reopened”

    “On the other side we introduce yet another format that has to be supported, that creates compatibility issues”

    Comment from 7 Oct 2026 in “Shipping JPEG XL in Chrome”
  • Gains too small to justify

    “with only 20% improvement I can't say I'm super excited by this, compared to the pain of dealing with yet another new image format”

    Comment from 24 Nov 2025 in “Chrome Jpegxl Issue Reopened”

    “Going from lossless WEBP to lossless JXL is marginal though, and is not worth the big decode performance loss.”

    Comment from 24 Nov 2025 in “Chrome Jpegxl Issue Reopened”

    “Seems like a very small advantage to warrant all the necessary work needed to make it mainstream.”

    Comment from 26 Nov 2025 in “Chrome Jpegxl Issue Reopened”
  • Overly complex design

    “Being an “everything” image format sounds awful and something that’s over engineered and no person understands it.”

    Comment from 7 Oct 2026 in “Shipping JPEG XL in Chrome”

    “Lots of complexity, it means a big library, which is high maintenance with a big attack surface.”

    Comment from 22 Jan 2026 in “JPEG XL Demo Page”

What people said

40 of the 383 comments that mention it, newest first. Each links to the original comment.

“JXL wins almost always. Not to mention you can losslessly, reversibly transcode lossy JPG files to JXL”

RecommendsComment from 29 Oct 2026 in “H.264 Is Magic (2016)”

“the case for JPEG XL is not that it's the best at everything, but that it is both quite good overall”

RecommendsComment from 29 Oct 2026 in “H.264 Is Magic (2016)”

“Google chose not to include JPEG XL in Chrome because vulnerabilities in the library could compromise the software”

MixedComment from 25 Oct 2026 in “Broccoli2Shell: Brotli decoder RCE in Node.js, Python and more”

“it often handles clean edges and smooth surfaces (the likes of which you might see in digital art) better”

RecommendsComment from 17 Oct 2026 in “JPEG XL vs. AVIF for web use-cases”

“JXL gives you progressive rendering, easy upgradability on JPEGs, and better lossless and high bitrate images.”

MixedComment from 16 Oct 2026 in “JPEG XL vs. AVIF for web use-cases”

“it is possible to do a transcode of all of your existing ('classic') JPEG files with zero (visual) losses in quality”

RecommendsComment from 16 Oct 2026 in “JPEG XL vs. AVIF for web use-cases”

“AVIF and JPEG XL actually have ability to mix-and-match blurry and sharp compression modes within a single image.”

RecommendsComment from 12 Oct 2026 in “I guess I'm using WebP now?”

“JPEG XL is probably the first format which actually achieves this, covering all kinds of pictures you can think of”

RecommendsComment from 7 Oct 2026 in “Shipping JPEG XL in Chrome”

“On the other side we introduce yet another format that has to be supported, that creates compatibility issues”

CriticizesComment from 7 Oct 2026 in “Shipping JPEG XL in Chrome”

“Being an “everything” image format sounds awful and something that’s over engineered and no person understands it.”

CriticizesComment from 7 Oct 2026 in “Shipping JPEG XL in Chrome”

“When literally every OS already comes with a form of libjxl pre-installed there is no good reason not to add support for it.”

RecommendsComment from 7 Oct 2026 in “Shipping JPEG XL in Chrome”

“The format is designed to be as general as possible, potentially replacing many common (JPEG, GIF, PNG) and professional image formats.”

RecommendsComment from 7 Oct 2026 in “Shipping JPEG XL in Chrome”

“JPEG XL has the right balance of features to become a true replacement of almost every relevant image format”

RecommendsComment from 7 Oct 2026 in “Shipping JPEG XL in Chrome”

“I think they probably could have added those though, and then we wouldn't have yet another format to support for eternity.”

MixedComment from 14 Sep 2026 in “The case against JPEG XL”

“re-compressing old JPEGs that they have no better sources for into JPEG XL with out decode-encode loss”

RecommendsComment from 14 Sep 2026 in “The case against JPEG XL”

“It's nice for peace of mind, you can bulk convert a large archive and you know you still have the same pixels everywhere”

RecommendsComment from 14 Sep 2026 in “The case against JPEG XL”

“the JPEG XL ability to truncate the bitstream anywhere, or send the progressive updates for salient regions first”

RecommendsComment from 14 Sep 2026 in “The case against JPEG XL”

“JPEG XL easily beats AVIF on the not-so-long tail of use cases and having compatible viewers everywhere is quite useful.”

RecommendsComment from 14 Sep 2026 in “The case against JPEG XL”

“a single format that works both for 10000x10000 lossless scientific images, and for 256x256 lossy web photos”

MixedComment from 14 Sep 2026 in “The case against JPEG XL”

“Now that Rust library is available, they will continue adoption, as it should be.”

RecommendsComment from 14 Sep 2026 in “The case against JPEG XL”

“"We don't want to support another pile of security bug ridden C++ library" absolutely aren't "dubious grounds".”

CriticizesComment from 14 Sep 2026 in “The case against JPEG XL”

“you can losslessly convert back and forth between the two for smaller filesize in JPEG XL with no quality loss”

RecommendsComment from 14 Sep 2026 in “The case against JPEG XL”

“At around 98KB, the JXL looks significantly better, and at around 240KB already looks really close to the final image”

RecommendsComment from 14 Sep 2026 in “The case against JPEG XL”

“It's a format that combines and replaces the many different use cases that different formats are doing now.”

RecommendsComment from 26 Aug 2026 in “Firefox 157 will include JPEG XL by default on all platforms”

“The C++ decoder was simply unsafe and they would not implement it until a memory-safe decoder was available.”

RecommendsComment from 24 Aug 2026 in “Firefox intent to ship: JPEG XL”

“JXL is the best image format we have - supports lossy and lossless compression, HDR, and much more!”

RecommendsComment from 17 Jun 2026 in “Image Compression”

“Lots of complexity, it means a big library, which is high maintenance with a big attack surface.”

CriticizesComment from 22 Jan 2026 in “JPEG XL Demo Page”

“one of the really interesting things JPEG-XL adds is the ability to have an arbitrary number of non-color channels”

RecommendsComment from 14 Jan 2026 in “Chromium Has Merged JpegXL”

“It is, however, a very useful image format feature, giving you most information from the spinner/sticker/emoji/sprite”

RecommendsComment from 13 Jan 2026 in “Chromium Has Merged JpegXL”

“JPEG XL carries a large security surface area which neither company was comfortable including in its current shape”

CriticizesComment from 2 Dec 2025 in “Google unkills JPEG XL?”

“JPEG XL supports progressive decoding, so you can see the picture in lower quality long before the download has finished”

RecommendsComment from 1 Dec 2025 in “Google unkills JPEG XL?”

“Seems like a very small advantage to warrant all the necessary work needed to make it mainstream.”

CriticizesComment from 26 Nov 2025 in “Chrome Jpegxl Issue Reopened”

“JPEG XL was designed to support many uses cases like web delivery, medical imaging, raw camera sensor data”

RecommendsComment from 25 Nov 2025 in “Chrome Jpegxl Issue Reopened”

“The killer feature of JXL is that most websites already have a whole bunch of images in JPEG format”

RecommendsComment from 25 Nov 2025 in “Chrome Jpegxl Issue Reopened”

“JXL solves that issue for most websites since it is backwards-compatible and can be decoded into JPEG”

RecommendsComment from 24 Nov 2025 in “Chrome Jpegxl Issue Reopened”

“JPEG-XL is generally similar or better than AVIF at any reasonable compression ratios for web images”

RecommendsComment from 24 Nov 2025 in “Chrome Jpegxl Issue Reopened”

“Going from lossless WEBP to lossless JXL is marginal though, and is not worth the big decode performance loss.”

CriticizesComment from 24 Nov 2025 in “Chrome Jpegxl Issue Reopened”

“fast decoding options, and things like progressive decoding for its VarDCT mode are practical advantages too”

RecommendsComment from 24 Nov 2025 in “Chrome Jpegxl Issue Reopened”

“with only 20% improvement I can't say I'm super excited by this, compared to the pain of dealing with yet another new image format”

CriticizesComment from 24 Nov 2025 in “Chrome Jpegxl Issue Reopened”

“JPEG-XL is actually better as a lossless codec in terms of compression ratio and compression complexity.”

RecommendsComment from 23 Nov 2025 in “Google Revisits JPEG XL in Chromium After Earlier Removal”

Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.