Plugin Doesnt Store Color Profile
-
Before leaving a review, id like you to reply for a solution.
I installed the plugin and uploaded some images to a local test. All worked fine, the images were converted to webP.
However the images loose their color profile, and as im looking to use this for a photography site, this simply isn’t usable as color accuracy is vital.
I then downloaded the webp plugin for PS https://github.com/webmproject/WebPShop/releases to run some tests.
Taking the same original jpeg image, saved as 12 quality (best) that i ran though your plugin, i then saved it as 80% quality (same as your recommended setting in your plugin), both with “Keep Color Profile” on and off:
– Original Jpeg: 704KB
– Your Plugin conversion: 86.7KB
– PS WebP at 80% with Color Profile OFF: 79.8KB
– PS WebP at 80% with Color Profile ON: 80.4KBAs you can see the PS versions, both with and without color, are smaller than yours, but im not to phased about that, as my main point here is that even with the Color Profile on, the PS version is able to match the size of both the OFF and your plugin, so there is no negligible hit in file size.
in other words, why no add it as an option in your plugin and there is no downside and increases color accuracy of images?
Then just for fun, I see you also support AVIF in your pro version, so also downloaded to PS plugin for that https://github.com/0xC0000054/avif-format/releases
– PS AVIF at 80% with Color Profile ON: 81.7KB
The compression quality was better (sharper) than WebP, while keeping the same file size, so it is definitely a better algorithm. But again, I assume that you too don’t support color profile in you plugin, so again this makes it useless for anyone who cares about color accuracy in their websites images.
Conclusion
Are you able to add Color profiles to both compression formats?
Id really like to use your plugin, as it more automated and thus convenient than individually saving webp or AFVI files through PS, but without a color profile, it simply isnt usable.
Thanks
-
But the ICC is stored in the meta data of every image, so therefore WordPress can read it, just like Photoshop can.
Your plugin strips the meta data the exact same way as the two PS plugins do (unless you tell it not to when saving).
Therefore your plugin should be able to also save the ICC as well.
https://drive.google.com/drive/folders/1ejBycTkXQQ-7GoB3kGT-q-NxEeg7kuPr?usp=sharing
OK so I also found a error with the plugin and the “Keep images metadata stored in EXIF or XMP formats (unavailable for GD conversion method)” setting
Check these two images https://drive.google.com/drive/folders/1Nj-xDQY4Cq8H9NbUx9lGUbatD4v2ACoF?usp=sharing :
– The “From Photoshop saved with ALL METADATA.jpg” show the webP file saved from PS with all three META data options (EXIF XMP & ICC) turned on> As you can see, Bridge is able to see all the metadata, the same as the original Jpg, meaning that it properly preserved the meta data within the webp image, as it also grew to 105KB from 87KB.
– The “From PLugin saved with ALL METADATA.jpg” is the image that your plugin generated with the “Keep images metadata stored in EXIF or XMP formats (unavailable for GD conversion method)” setting turned ON. As you can see in Bridge, all the metadata was stripped regardless, meaning this setting isn’t working as intended. It also remains at the same file size which is impossible if the meta data is included.
This could also be the reason that the ICC is being stripped out as well even when this setting is turned on.
- The topic ‘Plugin Doesnt Store Color Profile’ is closed to new replies.
