I've looked into using
cwebp and no matter what quality settings I used (-q, -psnr, -size) the encoder is overly aggressive. Even with -q 100 the quality loss is very visible.
Maybe it's the scanline pattern in this image, but here is an example of an image that turns into a mess when using:
cwebp -m 6 -q 100 -mt -noalpha -progress %1 -o "%~n1.webp"
The forum does not support webp. So to demonstrate the quality this was converted back to a png. Check the attached zip-file to compare with the source.
Especially the 'IDEAS ARE BULLET-PROOF!' text in the background washed out compared to the source png or jpg. Feel free to prove me wrong and give me your encoder settings. I've not tested with transparency yet since the quality is already a 'no go' for me.
cwebp also fails to remove an unnecessary alpha channel if the image is 100% opaque.
The JPG looks much better for a few KBs more. An attempt to manually allow more space for
cwebp with
-size 200000 results in a file still under
100 KB.
- 578.212 bytes PNG source unoptimized with alpha channel
- 138.025 bytes JPG exported with GIMP quality 94%, Adv. Options [x] Progressive, Subsampling 4:4:4
- 94.142 bytes WEBP -m 6 -q 100 -mt -noalpha -progress
Look's like WEBP and I won't become friends due to the quality:
You must be registered to see the links
For the future I hope that the (not yet stable) AV1 Image File Format (AVIF) will receive better support than WEBP or
You must be registered to see the links
.
WEBP was only pushed by Google and FLIF got ignored by everyone even though it did beat all other formats in compression.