-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
image-actions versus TinyPng #90
Comments
Thanks for the report @bazzadp, if you've got some file compression stats to share it may be helpful to figure out a target for us to reach. To answer your questions:
Nope. Though you can inspect the resulting files to explore their properties using the ImageMagick
Verbose command output
Maybe there's some clues there?
Internally image-actions uses
AFAIK, the differences you've observed are not metadata related. @bazzadp Once we've some details on the images themselves, we can start to explore the differences in output and take it from there. |
Thanks @benschwarz ! Please find attached all the details It looks to me like the histogram is about half the size - which is directly reflected in the file size. I dunno if they just have a much more aggressive compression level, or if they use any magic to figure out what they can get away with in terms of compression level? |
TinyPNG.com seems to produce much smaller images (40-60% smaller) with no noticeable loss in quality as far as my untrained eye can see. Any ideas how they do this? As I do really like this integration in GitHub Actions but at the moment I end up using this for the immediate effect and then going back and TinyPNG-ing the images later when I have time.
Any way to look at images and see what compression ratio they are using?
Or are they stripping meta-data that Calibre is not?
Or something else?
Would love it, it there was a simple config change to get same savings and save me this effort!
The text was updated successfully, but these errors were encountered: