Support for JPEG XL file type

[Mr-W-H-X]

Would Seer support .jxl in the future?

The JPEG XL Image Coding System (ISO/IEC 18181) has a rich feature set and is particularly optimised for responsive web environments, so that content renders well on a wide range of devices. Moreover, it includes several features that help transition from the legacy JPEG format.

Migrating to JPEG XL reduces storage costs because servers can store a single JPEG XL file to serve both JPEG and JPEG XL clients. Existing JPEG files can be losslessly transcoded to JPEG XL, significantly reducing their size. These can be restored into the exact same JPEG file, ensuring backward compatibility with existing JPEG-based applications. This provides a smooth transition from legacy JPEG platforms to the modern JPEG XL. Both the transcoding and restoration are computationally efficient.

JPEG XL is designed to meet the needs of image delivery on the web and professional photography. It supports wide colour gamut as well as high dynamic range and high bit depth images. JPEG XL further includes features such as animation, alpha channels, layers, thumbnails, lossless and progressive coding to support a wide range of use cases including but not limited to photo galleries, e-commerce, social media, user interfaces and cloud storage.

JPEG XL offers significantly better image quality and compression ratios than legacy JPEG. It is designed for computationally efficient encoding and decoding using software implementations without the need for additional hardware acceleration, even on mobile devices.

The codec is designed to allow users to balance three primary criteria for their application:

high fidelity to the source image,
encoding and/or decoding speed,
compression ratio (typically 20:1 to 50:1).

[ccseer]

already implemented in 4.0.0.

…

On Mon, Jan 20, 2025, 5:36 PM Orodio ***@***.***> wrote: Would Seer support .jxl sooner or later? The JPEG XL Image Coding System (ISO/IEC 18181) has a rich feature set <https://ds.jpeg.org/documents/wg1n83043-REQ-JPEG_XL_Use_Cases_and_Requirements.pdf> and is particularly optimised for responsive web environments, so that content renders well on a wide range of devices. Moreover, it includes several features that help transition from the legacy JPEG format. Migrating to JPEG XL reduces storage costs because servers can store a single JPEG XL file to serve both JPEG and JPEG XL clients. Existing JPEG files can be losslessly transcoded to JPEG XL, significantly reducing their size. These can be restored into the exact same JPEG file, ensuring backward compatibility with existing JPEG-based applications. This provides a smooth transition from legacy JPEG platforms to the modern JPEG XL. Both the transcoding and restoration are computationally efficient. JPEG XL is designed to meet the needs of image delivery on the web and professional photography. It supports wide colour gamut as well as high dynamic range and high bit depth images. JPEG XL further includes features such as animation, alpha channels, layers, thumbnails, lossless and progressive coding to support a wide range of use cases <https://ds.jpeg.org/documents/wg1n83043-REQ-JPEG_XL_Use_Cases_and_Requirements.pdf> including but not limited to photo galleries, e-commerce, social media, user interfaces and cloud storage. JPEG XL offers significantly better image quality and compression ratios than legacy JPEG. It is designed for computationally efficient encoding and decoding using software implementations without the need for additional hardware acceleration, even on mobile devices. The codec is designed to allow users to balance three primary criteria for their application: high fidelity to the source image, encoding and/or decoding speed, compression ratio (typically 20:1 to 50:1). — Reply to this email directly, view it on GitHub <#448>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADZZIHUIFMYA62QU6VQ3DKL2LS7RPAVCNFSM6AAAAABVP5OKJ6VHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZXHA2DQNJSGU> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[ccseer]

[Mr-W-H-X]

OK

[ccseer]

added in 4.0.0 #452