mozjpeg VS guetzli

[2] https://github.com/mozilla/mozjpeg

It would be nice if the author would add mozjpeg[1] to the comparison. At certain sizes, it can produce smaller sizes than WebP, and because it is still a jpeg, it has a much better compatibility story, which the author alluded to.

[1]https://github.com/mozilla/mozjpeg

image-shrinker is a simple, easy to use open source tool for shrinking images. Under the hood it uses pngquant, mozjpg, SVGO, and gifsicle. You can also install these tools individually if you need to compress some images. I often use pngquantafter exporting PNGs for web projects from Figma or similar tools. I literally run it like this:

> MozJPEG is a patch for libjpeg-turbo. Please send pull requests to libjpeg-turbo if the changes aren't specific to newly-added MozJPEG-only compression code.

https://github.com/mozilla/mozjpeg#mozilla-jpeg-encoder-proj...

FWIW, Mozilla has been maintaining their own fork for quite a while now[1]

AFAIK most Linux Distros have been using libjpeg-turbo as a drop-in replacement for libjpeg, after some drama in ~2010 where libjpeg came under new management, decided to break ABI/API several times over and add incompatible, non-standard format extensions[2].

[1] https://github.com/mozilla/mozjpeg

[2] https://en.wikipedia.org/wiki/Libjpeg#History

No.

See https://github.com/mozilla/mozjpeg

Also, there is a fairly big problem with JPG that the ‘quality’ setting is not calibrated. That is you might look at one image and think it looks fine (which is subjective, depends on what you want to use the image for…) with a quality of 60%, but then you compress a million images at that rate, delete the originals, then you find that many of them look really awful. Not only that but there are images you could have compressed more and still been happy with the output.

If you are publishing images for the web consider using WebP which is consistently better, well supported now, and has a calibrated quality knob.

https://github.com/mozilla/mozjpeg's cjpeg tool is the command line version of the mozjpeg library, itself a fork of libjpeg-turbo. Mozjpeg performs lossless JPEG optimization. There are plenty of others out there.

Use the Mozilla JPEG Encoder, which implements several tricks for smaller file size / better visual quality. The result is still JPEG standard compatible that other software can decode.

Guetzli was already mentioned and roughly does what you are talking about.

MozJPEG [1] includes several quantization tables that are optimized for different contexts (see the quant-table flag and source code for specific tables[2]), and the default quantization table has been optimized to outperform the recommended quantization tables in the original JPEG spec (Annex K).

It's also worth noting that MozJPEG uses Trellis quantization [3] to help improve quality without a per-image brute force quantization table search. Basically rather than determining an optimal quantization table for the image, it minimizes rate distortion on a per-block level by tuning the quantized coefficients.

[1] https://github.com/mozilla/mozjpeg

[2] https://github.com/mozilla/mozjpeg/blob/5c6a0f0971edf1ed3cf3...

[3] https://en.wikipedia.org/wiki/Trellis_quantization

They're still being used. A newer, optimized JPEG encoder, mozJPEG[0], seems to use progressive encoding by default. I suspect with faster internet speeds, most images download and decode so fast that the cool 'enhance' animation doesn't happen anymore.

[0] https://github.com/mozilla/mozjpeg

JPEGLI = A small JPEG

The suffix -li is used in Swiss German dialects. It forms a diminutive of the root word, by adding -li to the end of the root word to convey the smallness of the object and to convey a sense of intimacy or endearment.

This obviously comes out of Google Zürich.

Other notable Google projects using Swiss German:

https://github.com/google/gipfeli high-speed compression

Gipfeli = Croissant

https://github.com/google/guetzli perceptual JPEG encoder

Guetzli = Cookie

https://github.com/weggli-rs/weggli semantic search tool

Weggli = Bread roll

https://github.com/google/brotli lossless compression

Brötli = Small bread

A JPEG encoder developed by Jyrki Alakujala, Robert Obryk, and Zoltán Szabadka, and released by Google in 2017. Guetzli specializes in high-end image quality where it is claimed to produce significantly smaller files than prior encoders at equivalent quality, albeit at very low speed. It is named after the Swiss German expression for biscuits, in line with the names of other compression technology from Google. github.com/google/guetzli

I'm a huge fan of AV1 for video, but for images JPEG-XL is simply the better codec than AVIF. If you've not actually looked closely at a comparison and are just on the side of AVIF in this debate because it's based on AV1 (and maybe you hate HEVC / HEIC), I'd urge you to look closer. Jpeg XL is pretty unrelated to Jpeg, Jpeg 2000 and Jpeg XR and instead a successor of Google Guetzli, FLIF and newer research.

I've never had much luck using jpegoptim. In most cases it's only removing the metadata, which isn't much on high-res files.

Guetzli is nice, if you don't have too many images to recompress (quite slow): https://github.com/google/guetzli

If you're going for full re-encoding, it might help to decode the current JPEG with https://github.com/google/knusperli ... but if you re-JPEG that you might have second-order artifacts. Give it a try. Then compress with https://github.com/google/guetzli

You know. I was actually quite annoyed ( to say the least ) with the post. For one the post is lacking a date, and you have to search yourself it was published in April 2017. And without a date the article is completely lacking context because Guetzli [1] hasn't been worked on for 5 years. And as [2] mentioned its work and derivative was ultimately merged into JPEG XL, which is a very decent image format. ( People should definitely check out JPEG XL if it is not on your radar yet )

But then I notice it was Dan luu who submitted it, which likely means there must be something much deeper than is what is shown on the surface. So what is the context here ?

[1] https://github.com/google/guetzli

[2] https://news.ycombinator.com/item?id=30622303