To the frustration of many developers and end-users, back in 2022 Google deprecated JPEG-XL support in Chrome/Chromium and proceeded to remove the support. That decision was widely slammed and ultimately Google said they may end up reconsidering it. In November there was renewed activity and interest in restoring JPEG-XL within Google’s image web browser and as of yesterday the code was merged.

  • The_Decryptor@aussie.zoneEnglish
    3·
    1 day ago

    And PNG is so old that it lacks basic modern features like HDR support.

    You can actually store HDR images in PNG (Even BMP, but that’s cursed), you just need to include the right metadata, and have a client that supports said metadata. Without it, the image looks a bit funky, but still legible.

    Now WebP on the other hand, is incapable of storing HDR images. The lossless mode is limited to 8bpc images, and Google killed off WebP2 in favour of AVIF (Which doesn’t have a dedicated lossless mode), which could have fixed those limitations.

      • The_Decryptor@aussie.zoneEnglish
        3·
        22 hours ago

        Yep, that’s the proper way (Since you can specify the metadata correctly)

        But there’s also an older rather cursed way, a specially crafted colour profile that a compatible viewer would see and then act as if the image data was in a specific HDR format. It worked too, a few viewers support it, but it’s a pretty terrible way to handle it so it’s been deprecated.

        I actually used it as part of a pipeline to turn Xbox HDR screenshots into HDR JXL images, the JXL encoder at the time would recognise it and apply the right metadata itself.