Showing results for 
Show  only  | Search instead for 
Did you mean: 
Strollin' around
Status: Trending idea

I think it's a great opportunity for Firefox to stand out by supporting JPEG XL before any other browser.

Imagine images served by Cloudflare and Cloudinary load faster and look better only with Firefox. Firefox was a pioneer of web technologies and it should win the title back, if Firefox just keep following Chrome without any differentiation, why would people choose Firefox?

If the decoder memory safety is a concern, maybe Mozilla can start a crowd funding campaign to sponsor a Rust decoder, even the campaign itself will attract reports and attentions for Firefox.

Mozilla argued AVIF was already supported as a same generation but clearly JPEG XL has many advantages:

  • Much better encoding performance (AVIF is not suitable for realtime CDN optimization at all)
  • lossless and better high fidelity (video codec based image format)
  • HDR (there will be a billion of mobile devices with real good & bright screen in just a few years)
  • Little generation loss (important for web)

Supports from Facebook, Adobe (they're adding export support), Intel and VESA, Krita, The Guardian, libvips, Cloudinary, Shopify


Strollin' around

It has several advantages:

Being able to recompress JPEGs losslessly with a space saving

Large bit and image size limits which means no tile boundary effects, or much generational loss when re-encoding

New member

Seems to be pretty much a no-brainer. Mozilla should be taking every reasonable opportunity to differentiate Fx from Chrome and the chrome-a-clone brethren.

Familiar face

The implementation bug for this is here


Strollin' around

Great suggestion. It's a low-hanging fruit to surpass Chrome and make Firefox the preferred browser for some WebDevs as well.

New member

Hello, since yesterday Darktable can export to JXL and my first tests are fantastic:

  • quality
  • size
  • speed
  • format options

Please add JXL support!


New member

Please support jpegXL! Google should not be the ones to dictate what codecs are accepted or not, especially if they are rejecting something that is obviously superior.

Strollin' around

I literally made an account to vote for this. Google should not be allowed to change the standard in their favor of WEBP and AVIF for more personal control. This format is the best i know and I would instantly use this in personal web development if this gets stabilized. If not i still might do it. image.jxl.enabled stays on

Strollin' around

This needs more attention in my opinion. Stupid to allow Google to bully the internet into using "their" format instead of the actual better option

Strollin' around

Any potential updates about this getting enabled by default? 👀 

Like even enabled by default in beta builds first and then the final builds after. 


Strollin' around

Yes, Please! 🙏🏼 JPEG-XL has benefits from many other formats (and advantages over WebP/AVIF) including animation & lossless option, Filesizes can be scaled up and down according to use-case,

and it has an all-in-one approach that's backwards compatible with legacy formats, surely Firefox would seize this opportunity to show why other companies should seriously move towards more open-standards.

Also why they should consider moving away from their locked-down proprietary ones that they get an advantage in pushing due to their market position? I believe that this format would be in-line with Mozilla's stance on browsers in general and offers the users choice.