-
Notifications
You must be signed in to change notification settings - Fork 25.8k
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
[Feature Request]: Disable PNGInfo #5806
Comments
Under the "Saving images/grids" section in settings there is a setting called "Do not add watermark to images". I think that does what you're asking here. |
@ClashSAN consider closing this since this feature is already there |
'Chunks' refer to additional data that is being saved with the file. The PNG file structure is made up of different chunks of data, and some of them are for image, others are for metadata like comments |
But in fact that terminology is not used for this. The method is called PNG
Tags, based on TIFF Tags. I dunno where chunks is coming in. It's just
header tags.
…On Sat, Dec 17, 2022, 12:43 AM Billy Cao ***@***.***> wrote:
'Chunks' refer to additional data that is being saved with the file. The
PNG file structure is made up of different chunks of data, and some of them
are for image, others are for metadata like comments
—
Reply to this email directly, view it on GitHub
<#5806 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIZEZKBGORUH4BFAVE2BNTWNV4MBANCNFSM6AAAAAATBWOQDA>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***
com>
|
Is there an existing issue for this?
What would your feature do ?
I personally find the PNGInfo a gimmick, and abusing PNG Tags concept, which is for ownership information and camera information for post processing.
Is this able to be disabled? I shouldn't have to sanitize my creations before I share them, and I myself have warned a few people that they were selling assets with full reproducibility and ability to easily derive from, no payment necessary, cause their preview images load fine into webui. Pretty sure a lot of modern image editors respect PNG Info and roll it over to new saves, too even if you edit it (like post processing).
Proposed workflow
Additional information
I don't feel this is safe default behavior for a end-point usage utility. That's like if TIFF had save layers by default, or meta data stating every filter/operation used in a DCC.
The text was updated successfully, but these errors were encountered: