Automatically serve webp images with imageProcessor
Hi all.
I found this good article on how to automatically serve webp images with imageprocessor https://kieron.codes/blog/using-webp-images-in-umbraco/ but half of my images is now triple size and half is about half size of the original.
"The WebP compression algorithm was created, according to Google, as an alternative for both PNG and JPEG files. While generally the resulting WebP image is, on average, 26% smaller than the original PNG and 25-34% smaller than the original JPEG, sometimes the resulting image can be bigger. Much bigger. We encountered cases when the WebP version of a PNG was double or three times the size of the original file size.
There is nothing to worry about: it is just a limitation of the WebP algorithm sometimes, especially when the original file is already optimized. Google explains it on this section of the previous page: Can a WebP image grow larger than its source image?"
Now does anyone have some experience or best practice with this, they would like to share?
I was thinking if there was a way of telling when to use webp and when not to use it automatically..
Automatically serve webp images with imageProcessor
Hi all.
I found this good article on how to automatically serve webp images with imageprocessor https://kieron.codes/blog/using-webp-images-in-umbraco/ but half of my images is now triple size and half is about half size of the original.
I then found an article on https://help.shortpixel.com/article/102-why-the-resulting-webp-images-are-bigger-than-the-original-png-files
"The WebP compression algorithm was created, according to Google, as an alternative for both PNG and JPEG files. While generally the resulting WebP image is, on average, 26% smaller than the original PNG and 25-34% smaller than the original JPEG, sometimes the resulting image can be bigger. Much bigger. We encountered cases when the WebP version of a PNG was double or three times the size of the original file size.
There is nothing to worry about: it is just a limitation of the WebP algorithm sometimes, especially when the original file is already optimized. Google explains it on this section of the previous page: Can a WebP image grow larger than its source image?"
Now does anyone have some experience or best practice with this, they would like to share?
I was thinking if there was a way of telling when to use webp and when not to use it automatically..
is working on a reply...