4 ms·
Unfortunately, targeting same SSIM makes this test basically bullshit. It would be far better to make images that are the same size, and then we can use both ou
by bscphil 6y ago
Unfortunately, targeting same SSIM makes this test basically bullshit. It would be far better to make images that are the same size, and then we can use both our eyes and various objective metrics to compare the images.
The reason for this is basically that most codecs do not target SSIM internally. They're using their own algorithms to determine how to allocate bits, so two images with the same SSIM may look better or worse depending on what codec is used. Many modern codecs (e.g. from x264 onwards) deliberately take approaches that lower the score of the result on objective metrics but usually look better to the human eye.
This exact issue was originally highlighted on the x264dev blog: "How to cheat on video encoder comparisons" #3: "Making invalid comparisons using objective metrics". [1]
If you really want to compare image codecs, I'd look at one of the many comparisons from this family on Github. [2]
In my judgment WebP is clearly better than Mozjpeg for most images.
[1] https://web.archive.org/web/20141103202912/https://x264dev.multimedia.cx/archives/472 https://web.archive.org/web/20141103202912/https://x264dev.m...
[2] https://wyohknott.github.io/image-formats-comparison/#abandonned-factory&webp=s&jpg=s https://wyohknott.github.io/image-formats-comparison/#abando...
- viluon 6y agoThis should be higher up. siipo.la's benchmark is anecdotal evidence, the image formats comparison shows crisper edges and smoother gradients for WebP even at large filesizes. For small files, mozjpeg can't compare.
- krick 6y agoThis. JPEG has way too many artefacts on naturally smooth areas (like sky) to be ever considered a pinnacle of lossy image compression. WebP or not, but some adaptive technique must be the future, if there is any space for lossy compression in the future at all.