Add JXL support.

[FerrumMaster]

Enhancement

Hi,

Please add support JXL using libjxl when doing import.

I have converted my library to JXL as it takes 50-60% less space versus JPG and Adobe, Apple and ofc Linux has native support of this file format.

[FerrumMaster]

FF 152 added default JXL support. Please consider adding it, the storage cost these days is painful, not mentioning the reduced traffic as the files are really smaller.

[ildyria]

Hi,

JXL is barely supported anywhere, and by barely I am being very generous. See: https://caniuse.com/jpegxl

So to support jxl we would pretty much need to allow import on jxl format but immediately decode it to a usable format for wide range of web browser to generate the medium/small/thumbs. :/

[FerrumMaster]

Please add preferences to leave the medium/small/thums also in jxl, no conversion, otherwise that defeats the idea. Chrome, Safari and FF now supports it natively, what's with the barely supported statement(like AI trained on old sources?).

You can do exports in Adobe products, Windows has plugin in store, same applies to any Linux, MacOS has native support.

Try out it yourself, what is the data saving ratio doing it that way, remaining the same IQ. It is >50% + HDR support and it is totally free.

[ildyria]

what's with the barely supported statement(like AI trained on old sources?

I literally gave you the link of caniuse which is the authority with regard to what is supported where.
https://caniuse.com/jpegxl
See at the bottom all the * that it needs flags.

Literally more sources cites this issue:

• https://www.smallpics.io/blog/what-is-jpeg-xl/ March 26, 2026
• https://www.photoformatlab.com/blog/jpeg-xl-chrome-2026-image-format-guide April 6, 2026

[FerrumMaster]

what's with the barely supported statement(like AI trained on old sources?

I literally gave you the link of caniuse which is the authority with regard to what is supported where. https://caniuse.com/jpegxl See at the bottom all the * that it needs flags.

Literally more sources cites this issue:

* https://www.smallpics.io/blog/what-is-jpeg-xl/ March 26, 2026

* https://www.photoformatlab.com/blog/jpeg-xl-chrome-2026-image-format-guide April 6, 2026

That's outdated info. That's why replied that way.

As of FF 152 it it is enabled by default.

[d7415]

Firefox now offers experimental support for the new JPEG XL image format, which generally provides better compression than WebP, JPEG, PNG, and GIF and is designed to supersede them. You can enable it from the Firefox Labs panel in Settings.

https://www.firefox.com/en-US/firefox/152.0/releasenotes/

[Redsandro]

Hi @ildyria

I have been waiting for browser JPEG-XL/2021 adoption for a long time. A sigh of relief. Unbelievable quality for small files, a big leap from JPEG/1992 into this century. The day Chromium switched is the day I switched for my personal archives.

I didn't really think this through because just now I see all my Lychee uploads get rejected. And I have to convert files I want to host on the gallery back. I found this issue through search.

Consider this my +1, plus an FYI that this has been a pivotal month. A lot has changed since july:

Browser	Look mom, no flags	Release notes / announcement
Chrome	Chrome 155 stable, Oct 6, 2026	Chrome for Developers: JPEG XL in Chrome
Brave (desktop)	Brave 1.97, Oct 9, 2026	PiunikaWeb
Firefox	Firefox 158, Oct 13, 2026	Firefox 158 release notes
Chromium ESR	Chromium 156 ESR, Oct 20, 2026
Safari (macOS, iOS/iPadOS)	Safari 17, September 2023	WebKit: Features in Safari 17 beta

ESR-based browsers such as Vivaldi follow soon.

To be honest: No Edge. I wonder how long Edge will take this time to follow the leader. Although I'm not using Lychee as an outside facing gallery. It's just for the family and none of us is using Edge. It's a use case where we don't necessarily need to wait for the world to catch up, though it's beginning to. 😃

It would be sweet if Lychee would accept the uploads and transcode the thumbnails, small and medium variants to jpg or webp.

[Redsandro]

Wait a minute, I see the diagnostics of 7.12 now:

JPEG XL is not supported by this system: .jxl uploads will fail.
JPEG XL requires Imagick enabled and ImageMagick built with JXL support (check magick -list format).

This is new, right? 👍 So I guess the ball is in my court, and I need to figure out how to get a jxl-supported magick in Debian 13 trixie. 🙂

[ildyria]

Yep. That's why the docker image is a better approach. 😜

[FerrumMaster]

How time files since I opened up the ticket.

Are you saying now you can upload jxl, it just needs imagemagick =>7.0.10-54? Haven't tried Lychee for a while, as FileBrowser Quantum replaced it in functionality and as a bonus it works with JXL and much more, prolly needs some PHP plumbing too.

docker ain't some magic bullet for all, I don't trust it in general, some code goop getting pulled from random places. It shares the same kernel, uses root by default and needs actually babysitting in security terms if you really want to get it running safe(er), and at the end if really differs from running bare metal? Not sure. It is more easy for a newbie to setup and forget and use it only on your LAN, sure, but better? I would not be so hasty claiming it in this age of AI.

[Redsandro]

@ildyria thank you! I'm happily uploading Jpeg-XL now after installing imagemagick from deb-multimedia.

@FerrumMaster I'm happy JXL is finally becoming early mainstream! So much better. Same for docker though. It is actually an industry standard because it solves a lot of problems. We are super lucky these volunteers share with us their projects. One additional benefit of docker is that serves as documentation, a support manual.

In the past volunteers stopped working on projects because users like us became increasingly demanding in support questions. A user would say: It doesn't work. A volunteer would say: Well it works for me, because they didn't volunteer as a developer to provide support.

Now there is Docker and we don't have to use it. I consider it documentation: It is proof that it works on a clean environment, and it documents exactly how to get it to work in that environment.

For example, I run Debian 13 Trixie. I see in the Dockerfile that Lychee's docker image uses Debian 12 Bookworm and installs php8.4-imagick from deb.sury.org. I don't know Sury.org so opinionated as I am, I used deb-multimedia for no other reason than that I know it. If it wouldn't work, I would have for sure tried Sury next.

[ildyria]

For example, I run Debian 13 Trixie. I see in the Dockerfile that Lychee's docker image uses Debian 12 Bookworm and installs php8.4-imagick from deb.sury.org. I don't know Sury.org so opinionated as I am, I used deb-multimedia for no other reason than that I know it. If it wouldn't work, I would have for sure tried Sury next.

The repo you are looking at is read-only. This has been merged to the current Lychee repository:

• https://github.com/LycheeOrg/Lychee/blob/master/Dockerfile
  This is the docker image which provides frankenphp webserver instead of nginx, which has interesting capabilities.
• https://github.com/LycheeOrg/Lychee/blob/master/Dockerfile-legacy
  This is the docker image that you would be using if you want to have a more old way setup.

Note that both of those images are based on Trixie. We do keep high quality standard here. ;)

docker ain't some magic bullet for all, I don't trust it in general, some code goop getting pulled from random places. It shares the same kernel, uses root by default and needs actually babysitting in security terms if you really want to get it running safe(er), and at the end if really differs from running bare metal? Not sure.

Sure, but why not go as far as reviewing all the lines of code of the kernel manually, and also of the compiler as per Reflection of Trusting Trust at that point. The point of Docker is to produce a reproducible set-up and shift the blame of the configuration on us LycheeOrg if it does not work (unless extremely weird behavior as on unraid). As said by Resandro, it also gives you a global view on how to set-up your environment. As a maintainer, debugging and figuring out why things don't work when access rights are involved, paths etc on someone else server is just the worst. So yeah, the view of LycheeOrg is use our docker image (or the one from LSIO) and you will get good help. If you don't then our support will be significantly more limited.

PS: @Redsandro deb.sury.org is the most widely used way to install php on debian/ubuntu. :)

• https://www.reddit.com/r/PHP/comments/1xby04t/sponsor_ond%C5%99ej_sur%C3%BD/
• https://www.reddit.com/r/PHP/comments/1xbwyd3/hats_off_to_ond%C5%99ej_sur%C3%BD/