mozjpeg VS Scour

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. - Source: Hacker News / 5 months ago

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:. - Source: dev.to / 8 months ago

> 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.... - Source: Hacker News / 10 months ago

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. - Source: Hacker News / 10 months ago

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... - Source: Hacker News / about 1 year ago

You could install the optimizer Inkscape uses internally and process your files with a super simple shell script. When reading the inkscape command line help, it does not seem to offer any option to export optimized SVGs from there. Source: 11 months ago

Inkscape uses Scour under the hood for optimized SVG export. Source: about 1 year ago

First make sure all your icons are saved as 'Optimized SVG' to remove Inkscape specific data and unnecessary id-attributes. Inkscape uses 'Scour' for this under the hood, so you can just use that directly to convert your files from the command line. I recommend the options --strip-xml-prolog --remove-metadata --enable-id-stripping --renderer-workaround. Now you only need to replace the outermost ... With ... For... Source: almost 2 years ago

The script optimised the SVG using Scour. This removes some metadata and also shortens IDs as well as strip out comments. For the PNG files we used OptiPNG on the maximum optimisation setting. This can be slow on larger files, but for favicons should not take long. Here’s the before and after comparison of files sizes for a particular favicon, using the script:. - Source: dev.to / almost 2 years ago

I also recommend Inkscape, it also has scour built-in to it. When saving a SVG select the option "optimized SVG" which will give you options to pass to scour to lower the amount of markup there is. You can then do some hand editing after this to further remove any markup you don't want. Source: over 2 years ago