FotoKilof VS Efficient-Compression-Tool

Oh and I just discovered FotoKilof which is in fact a GUI frontend to imagemagick; though I don't actually have any experience using it.

FotoKilof might be interesting for you. While the initial setup is command-line (python), afterwars when running it, it will open a GUI.

check the issues on github. there was someone with the same problem: https://github.com/TeaM-TL/FotoKilof/issues/116

https://handbrake.fr/ you can use as alternative for ffmpeg and https://github.com/TeaM-TL/FotoKilof for images that is a GUI for imagemagick

mmm maybe some sort of image magick based software? https://github.com/TeaM-TL/FotoKilof

ImageMagick powerful CLI image editor, accepts an absurd amount of operations and formats as input and output, is very well documented, basically there is nothing like it when it comes to the amount of options to convert, resize and lossy compression images (and many other options). You can also try FotoKilof which is a GUI fork of ImageMagick if CLI is not your thing.

This one looks good, and has the capability to crop via mouse. now batch scaling is not a feature in said frontend, you'll have to write a shell script for that or use the tool you posted.

Would be interesting to see how all those jpegs fared if run though ECT (https://github.com/fhanau/Efficient-Compression-Tool). I’ve found it can save a surprising amount of space sometimes.

Ah, I misunderstood you there, yes you can build it from source but there are also Windows binaries available on https://github.com/fhanau/Efficient-Compression-Tool/releases/

Did you think about adding support for newer image formats? Video shouldn't be a problem because you already support .mkv and AV1 works within it. How would implementation work? Does ES-DE use libraries from the OS and makes this support easier for that? My biggest gripe are those big .png files. I optimized them with ect but it won't be as good as newer formats can be.

If png size is a concert of yours: Efficient Compression Tool

There are a myriad of PNG (and in general DEFLATE) optimizers and pingo hosts its own benchmark [1]. I believe ECT [2] is the only tool comparable to pingo in terms of compression ratio and speed. But pingo still lacks a license statement and it's even unclear whether you can use this for any purpose at all, probably because it is still "experimental", so if you don't like that you can try ECT instead.

> One thing I didn't check is that you might pay that in decoding time, I've never seen anybody talking about that though.

PNG and in general DEFLATE-based formats are mostly free from this concern because they are comparably simple. The maximum "overhead" you can intentionally trigger is a very large LZ77 window and a very deep Huffman tree; the former is however capped to 32 KB in DEFLATE, and the latter will mostly result in an inferior compression (a long prefix code means a larger file).

[1] https://css-ig.net/benchmark/png-lossless

[2] https://github.com/fhanau/Efficient-Compression-Tool

I personally prefer ECT, since that gave me the best results when I tested it several years ago.

ECT is the new stuff that is much faster and more efficient than zofpli

Efficient Compression Tool Basically the best FOSS for lossless compression for .png and .jpeg, although not the quickest.

I get the same issue. However, it seems that using ECT on the images fixes the issue: https://github.com/fhanau/Efficient-Compression-Tool