-
-
Notifications
You must be signed in to change notification settings - Fork 468
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 file size changed after saving #870
Comments
IG is set to save the image as 100% quality by setting "quality" in Magick.NET library. In other apps (MS Paint,...) it's about 75-80% |
The image in question is a PNG image. Image quality "normally" doesn't apply to PNG. When IG saves at 100% quality, the image size usually increases. The OP's image size has decreased. We'd need to have a copy of an image which shows the problem. Did IG strip Exif or other Metadata? Change the bits-per-pixel? |
Before I forget (again!) - the image you show is very nice! Would you share the source? Thanks! |
I tried different formats and different sizes of pictures, some became bigger and some became smaller. Now I provide these files, you can try。 |
Thanks for the samples! What IG needs to do is save the image using the same configuration the image was loaded with. As Phap points out, in the case of JPEG, IG is potentially using a different quality setting. But there is more to it:
|
Add option to change image quality in Settings > Edit tab in IG Moon: https://imageglass.org/moon |
I cannot find that option in 8.0.12.8. |
@mirh |
|
I just rotated a JPEG 90° right once. The file was originally 12.2 MB, and after saving it became 18.7 MB. If I rotate it using the Windows Photos app the file size doesn't change. I wonder if this could be optimized. |
System information:
When I use the function: save image as, the saved image size has been changed. I don’t know if the others have changed.
I want the saved image to retain the same attributes as the original image, just like copying.
On the left is saved, and the right is the original
@d2phap
The text was updated successfully, but these errors were encountered: