home.social

#jpegxl — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #jpegxl, aggregated by home.social.

fetched live
  1. FYI, if you use #Firefox you can now enable #JPEGXL support to try it out (without having to fiddle around with any tricky settings):

    Just go to Settings > Firefox Labs > and enable the “Media: JPEG XL” checkbox.

    It’s good to see that it’s another step closer to being enabled by default!

    #Safari / #WebKit has had support for about three years (but doesn’t yet implement progressive loading), and #Chrome has it behind a feature flag, but not much has happened recently. Getting there, slowly!

  2. FYI, if you use #Firefox you can now enable #JPEGXL support to try it out (without having to fiddle around with any tricky settings):

    Just go to Settings > Firefox Labs > and enable the “Media: JPEG XL” checkbox.

    It’s good to see that it’s another step closer to being enabled by default!

    #Safari / #WebKit has had support for about three years (but doesn’t yet implement progressive loading), and #Chrome has it behind a feature flag, but not much has happened recently. Getting there, slowly!

  3. The benefit of JXL not being recognized as an image format by signal is that you can just send JXLs via signal without it brutally compressing them in a lossy manner and stripping out all the exif data. 😊

    #Signal #JXL #JPEGXL

  4. The benefit of JXL not being recognized as an image format by signal is that you can just send JXLs via signal without it brutally compressing them in a lossy manner and stripping out all the exif data. 😊

    #Signal #JXL #JPEGXL

  5. #TIL about #jxl art: Hand-writing #JpegXL bitstreams to get a given image as small as possible.

    This can apparently result in >90% reduction over the already chart-topping performance of the generic JXL encoder in some cases.

    Insane stuff!

  6. If you are using #Firefox 150 or higher remember to go into Settings and Block slopware interface in the “AI controls” tab, and to enable #JPEGXL in the Firefox Labs tab.

  7. If you are using #Firefox 150 or higher remember to go into Settings and Block slopware interface in the “AI controls” tab, and to enable #JPEGXL in the Firefox Labs tab.

  8. I happened to stumble across an article that JpegXL is now available in Chrome on Android (after a flag flip), and Firefox too. And indeed it is: jpegxl.info/resources/jpeg-xl-

    What changed? When?

    #JpegXL #jxl

  9. I happened to stumble across an article that JpegXL is now available in Chrome on Android (after a flag flip), and Firefox too. And indeed it is: jpegxl.info/resources/jpeg-xl-

    What changed? When?

    #JpegXL #jxl

  10. Dass es eine neue CSS-Eigenschaft (field-sizing) gibt, ist total an mir vorbei gegangen. Das muss ich dann einmal testen.

    #Firefox152 :firefox: : #Mozilla räumt in den Einstellungen auf | iX Magazin heise.de/news/Firefox-152-Mozi #Firefox :firefox: #MozillaFirefox :firefox: #Browser #Webbrowser #Datenschutz #privacy #Tracking #JPEGXL

  11. Dass es eine neue CSS-Eigenschaft (field-sizing) gibt, ist total an mir vorbei gegangen. Das muss ich dann einmal testen.

    #Firefox152 :firefox: : #Mozilla räumt in den Einstellungen auf | iX Magazin heise.de/news/Firefox-152-Mozi #Firefox :firefox: #MozillaFirefox :firefox: #Browser #Webbrowser #Datenschutz #privacy #Tracking #JPEGXL

  12. »With #Firefox 152 there is now the #JPEGXL support code being compiled by default for the release albeit still disabled at run-time by default behind a preference for now.«

    phoronix.com/news/Firefox-152-

  13. »With #Firefox 152 there is now the #JPEGXL support code being compiled by default for the release albeit still disabled at run-time by default behind a preference for now.«

    phoronix.com/news/Firefox-152-

  14. Maybe someone can correct me, but wasn't #JPEGXL half deprecated because the browsers didn't want to support it just a year or two ago? This article makes it sound like #Google was pushing towards it and fully supporting it. Excited to see some love for it though.

    opensource.googleblog.com/2026

  15. Maybe someone can correct me, but wasn't #JPEGXL half deprecated because the browsers didn't want to support it just a year or two ago? This article makes it sound like #Google was pushing towards it and fully supporting it. Excited to see some love for it though.

    opensource.googleblog.com/2026

  16. RE: chaos.social/@chrysn/116634862

    @jonsneyers Could you help me figure out whether this JXL trick is realistic or I'm trying to catch a ghost?

    I'm serving image thumbnails on file shares and later on the web; some use cases just use 64x64px, some want 2k. Pre-JXL I'd have stored binary steps and told the browser in a srcmap. Can a progressive encoder drop hints like "for 128px, you'll be reasonably done by 4015 bytes"? (And then there's the question of how to tell the browser so it can request ranges.)

    #jxl #jpegxl

  17. RE: chaos.social/@chrysn/116634862

    @jonsneyers Could you help me figure out whether this JXL trick is realistic or I'm trying to catch a ghost?

    I'm serving image thumbnails on file shares and later on the web; some use cases just use 64x64px, some want 2k. Pre-JXL I'd have stored binary steps and told the browser in a srcmap. Can a progressive encoder drop hints like "for 128px, you'll be reasonably done by 4015 bytes"? (And then there's the question of how to tell the browser so it can request ranges.)

    #jxl #jpegxl

  18. I guess I can finally hope to use #jpegxl in my projects!

  19. "so basically AVIF is the new JPEG, and JPEG XL is the new PNG."

    #avif #jpegXl #jxl

  20. "so basically AVIF is the new JPEG, and JPEG XL is the new PNG."

    #avif #jpegXl #jxl

  21. Hey @gianni I was just chatting with @yawnbox about a wild range of tech things, and, since I am starting to host an Immich instance in my home, I am considering to convert all my emails to JPEG XL, and I was wondering if there is a way to do so without risking to lose any metadata.

    I am happy to read any links you might have but I need them to be as simple as possible because encoding/decoding stuff confuses me a lot. Not my thing… This is why I found your article explaining how AV1 works in simple words absolutely illuminating! Anyway, I just want to save storage space.

    Also, I am a big big fan of Aviator, and I have been following your work for a while. Thanks so much for all of it!

    #JXL #JPEGXL #JPEG #encoding #decoding #image #metadata #compression

  22. Hey @gianni I was just chatting with @yawnbox about a wild range of tech things, and, since I am starting to host an Immich instance in my home, I am considering to convert all my emails to JPEG XL, and I was wondering if there is a way to do so without risking to lose any metadata.

    I am happy to read any links you might have but I need them to be as simple as possible because encoding/decoding stuff confuses me a lot. Not my thing… This is why I found your article explaining how AV1 works in simple words absolutely illuminating! Anyway, I just want to save storage space.

    Also, I am a big big fan of Aviator, and I have been following your work for a while. Thanks so much for all of it!

    #JXL #JPEGXL #JPEG #encoding #decoding #image #metadata #compression

  23. With the speed around #JpegXL picking up (now in #Firefox and #Chrome nightlies), I'm wondering what good use of an #HTML srcset would be there.

    As JXL's progressive compression is good, we don't need different files in the srcset (so there's no need to load the first few KiB again when zooming in), but how can or should the HTML somehow tell the browser that for (say) up to 800px width it can request the Range: bytes=0-12345, and the next usable zoom level of 1600px needs the first 42KiB?

  24. With the speed around #JpegXL picking up (now in #Firefox and #Chrome nightlies), I'm wondering what good use of an #HTML srcset would be there.

    As JXL's progressive compression is good, we don't need different files in the srcset (so there's no need to load the first few KiB again when zooming in), but how can or should the HTML somehow tell the browser that for (say) up to 800px width it can request the Range: bytes=0-12345, and the next usable zoom level of 1600px needs the first 42KiB?

  25. Laut Kommentaren leider noch immer nicht standardmäßig eingeschaltet. Aber kann nicht mehr lang dauern.

    #Firefox 149 Now Available With XDG Portal File Picker, Rust-Based #JPEGXL Decoder

    phoronix.com/news/Mozilla-Fire

  26. Laut Kommentaren leider noch immer nicht standardmäßig eingeschaltet. Aber kann nicht mehr lang dauern.

    #Firefox 149 Now Available With XDG Portal File Picker, Rust-Based #JPEGXL Decoder

    phoronix.com/news/Mozilla-Fire

  27. Progress in #Firefox for #JpegXL: While the latest nightly for Android still needs image.jxl.enabled=true in about:config, it now renders
    jpegxl.info/resources/jpeg-xl- without any visible errors.
    One day…

  28. Progress in #Firefox for #JpegXL: While the latest nightly for Android still needs image.jxl.enabled=true in about:config, it now renders
    jpegxl.info/resources/jpeg-xl- without any visible errors.
    One day…

  29. The truth is, #WebP is only a stopgap. The real deal is #AVIF and ultimately #JPEGXL (.jxl).

    JPEG-XL is superior in almost everything. In the very few cases that it is not, that's where AVIF comes in.

    We can get rid of WebP, old JPEG, GIF, later on. Maybe even PNG and APNG.

    😜🖖🏽

  30. The truth is, #WebP is only a stopgap. The real deal is #AVIF and ultimately #JPEGXL (.jxl).

    JPEG-XL is superior in almost everything. In the very few cases that it is not, that's where AVIF comes in.

    We can get rid of WebP, old JPEG, GIF, later on. Maybe even PNG and APNG.

    😜🖖🏽

  31. The truth is, #WebP is only a stopgap. The real deal is #AVIF and ultimately #JPEGXL (.jxl). JPEG-XL is superior in almost everything. In the very few cases that it is not, that's where AVIF comes in. We can get rid of WebP, old JPEG, GIF, later on. Maybe even PNG and APNG. 😜🖖🏽

  32. The truth is, #WebP is only a stopgap. The real deal is #AVIF and ultimately #JPEGXL (.jxl). JPEG-XL is superior in almost everything. In the very few cases that it is not, that's where AVIF comes in. We can get rid of WebP, old JPEG, GIF, later on. Maybe even PNG and APNG. 😜🖖🏽

  33. I hope the F-Stop Gallery app for Android gets updated with WebP and JPEG XL support.

    For now, I switched to Fossify Gallery.

    fossify.org/apps/

    #Android #WebP #JPEGXL

  34. I hope the F-Stop Gallery app for Android gets updated with WebP and JPEG XL support.

    For now, I switched to Fossify Gallery.

    fossify.org/apps/

    #Android #WebP #JPEGXL

  35. I hope the F-Stop Gallery app for Android gets updated with WebP and JPEG XL support. For now, I switched to Fossify Gallery. www.fossify.org/apps/ #Android #WebP #JPEGXL

    Our apps

  36. Unfortunately, as of today, mainstream browsers still offer very limited support for JPEG XL. If you're as curious about it as I am — wanting to understand its origins and how to enable it in your browser to save bandwidth, or convert your existing JPEG images to JPEG XL format without loss of quality while freeing up at least 20% of your hard drive space — then I invite you to read my new blog post:
    zaku.eu.org/blog/2026-03-05-th
    Please feel free to leave a comment😄

    #JPEGXL

  37. A reminder; if you use Chrome and have version 145 and higher, enable JPEG XL:

    chrome://flags/#enable-jxl-image-format

    #JPEGXL #Chrome