libjxl VS qt-jpegxl-image-plugin

https://github.com/libjxl/libjxl/blob/main/doc/format_overvi... is a pretty detailed but good overview. The highlights are variable size DCT (up to 128x128), ANS entropy prediction, and chroma from luminance prediction. https://github.com/libjxl/libjxl/blob/main/doc/encode_effort... also gives a good breakdown of features by effort level.

For JPEG XL, refer to its format overview [1]. In short its lossless mode uses a combination of multiple techniques: the rANS coding with an alias table, LZ77, reversible color transforms, a general vector quantization that subsumes palettes, a modified Haar transform and a learnable meta-adaptive decision tree for context modelling.

One good thing about JPEG XL is that its lossy mode also largely uses the same tool, with a major addition of specialized quantization and context modelling for low- and high-frequenty components.

[1] https://github.com/libjxl/libjxl/blob/main/doc/format_overvi...

The cjxl source is here. If you spot any reason why -x strip=exif may not work, tell me.

The problem is that the instructions for actually running the WASM file are not that clear... the docs the author mentions shows how to compile to WASM, which is easy enough, but then here's the instructions to make that actually work in the browser:

https://github.com/libjxl/libjxl/blob/main/tools/wasm_demo/R...

Yeah, you need some mysterious Python script, a JS service worker at runtime, choose whether you want the WASM or WASM_SIMD target, use a browser that supports Threads and SIMD if you chose that, make sure to serve everything with the appropriate custom HTTP headers... just reading that, I can see that to get this stuff working on non-browser WASM targets would likely require expertise in WASM, which is the point of the OP. WASM's UX is just not there yet.

https://github.com/libjxl/libjxl#usage

> Specifically for JPEG files, the default cjxl behavior is to apply lossless recompression and the default djxl behavior is to reconstruct the original JPEG file (when the extension of the output file is .jpg).

I mean compiling a bleeding edge kicad, inkscape or jpeg-xl is easy. But will probably trash your system if you already have an older version installed.

But you look at your image viewer that could have the lossless indicator? (and there is an issue open to add this indicator to the jxl files)

https://github.com/libjxl/libjxl/issues/432

You might want to use libjxl directly, e.g. for visually lossless images: cjxl --effort 9 --brotli_effort 11 --distance 1.0 --num_threads (nproc) --lossless_jpeg 0 input.png output.jxl on linux (if you're on windows/mac, just replace the (nproc) with the number of cpu threads you have, e.g. --num_threads 16).

Download qjpegxl.dll and qavif.dll and copy the DLL files into imageformats folder.

Found the solution! Download the jxl image plugin dll from here and put it in D:\Dropoff\XnViewMP-win-x64\XnViewMP\plugins\imageformats. Now XnView will properly decode JXL files with .jxl file extension and show thumbnails in the app. It decoded a 50 MP lossy JXL (4:4:4 I believe) in 2 seconds with my 9100F CPU.

KDE's KImageFormats plugin for Qt supports JXL, though this may not be enabled on your distro. If it is, Qt image viewers like Gwenview can be used to view JXL files. If not, there's another plugin available, which may be available in your distro or you can build it yourself, which also enables programs like Gwenview to use JXL.

Original PhotoQt v2.3 can be easily enhanced to display JXL images on Windows just by adding qjpegxl.dll plug-in.

digiKam is able to display JXL files when qt-jpegxl-image-plugin is installed.

For jxl look at https://github.com/novomesk/qt-jpegxl-image-plugin/