Releases: mozilla/mozjpeg
mozjpeg v2.1
- The ‘-baseline’ option for cjpeg has been re-defined to produce baseline mode JPEGs. This makes it possible to produce baseline JPEGs with cjpeg while also using trellis quantization and other improvements. Previously the ‘-baseline’ flag simply specified that baseline quantization tables be used, and the only way to produce a baseline mode JPEG was to use the ‘-revert’ option.
- Fix for using trellis quantization in non-progressive mode
- Build fixes for various platforms
- More helpful error messages from cjpeg
- Various other minor fixes
mozjpeg v2.0.1
Forgot to bump the version number, doing so correctly is the only change in v2.0.1.
mozjpeg v2.0
- We’ve implemented trellis quantization to reduce file sizes for both baseline and progressive images.
- The cjpeg utility now supports JPEG input in order to simplify re-compression workflows.
- We’ve added options to specifically tune for PSNR, PSNR-HVS-M, SSIM, and MS-SSIM metrics.
- We now generate a single DC scan by default in order to be compatible with decoders that can’t handle arbitrary DC scans.
mozjpeg v1.0.1
mozjpeg v1.0
mozjpeg v1.0 is a fork of libjpeg-turbo with 'jpgcrush' functionality built in.
The 'jpgcrush' feature finds the progressive coding configuration which uses the fewest bits. This most frequently reduces file size by 2-10%, but those are not hard limits. Significantly greater reductions have been observed.
Library configuration defaults are the same as for libjpeg-turbo, in order to make transitions as painless as possible. There are new configuration options for new features, but they are not enabled by default.
The 'cjpeg' program defaults are not the same as for the equivalent program in libjpeg-turbo. The 'cjpeg' defaults for mozjpeg are set to aggressively optimize for smaller file sizes.