Batch saving (only) PNGs no longer embed color profiles

[BTA-1138]

This issue appears for the first time in version 24.2. So, 24.1.1 is the last version that works like it should. All newer versions, including the Beta, are breaking my Actions and Scripts that batch save PNGs (using "Save as" or "Save as a copy") so that the color profiles no longer remain embedded. This does NOT happen when using the Export function, but I need PNGs which are not for Web and force a 72ppi or an 8bpc encoding. I need to be able to Batch save PNGs in either 150 or 300ppi, and/or with a 16bpc encode.

If I manually save out one PNG and check the "Embed color profile" option, it's fine. But each time I run an action or script using Batch, the first PNG (usually) keeps the color profile embedded, but all subsequent PNGs save out "untagged". Apparently, using Batch Save As breaks the condition that is supposed to keep the "Embed color profile" selection checked after each save.

This issue has severely hampered our workflow at my company. No Script or Action that we write can overcome this inherent problem in the latest Photoshop builds. So, we cannot take advantage of any new updates past version 24.1.1. PLEASE HELP!

Here is an example of an Action that is broken: 

[Stephen Marsh]

@BTA-1138 – EDIT: Tested and confirmed in 24.7.0 on Intel Mac even when the action has a correct available save path available:

EDIT: Export >  Save for Web (Legacy) retains the profile and can be recorded in actions and scripts, but resolution info will be lost.

Software such a ExifTool could be used to either embed the ICC profile or resolution metadata in a batch operation as a work-around.

[BTA-1138]

Thanks for the information on Image Processor Pro. The built-in "Image Processor" won't do PNGs. I tried "Image Processor Pro" and it also seems to not be able to get around the inherent bug, even when I make sure it needs to include the source file's color profile and channel bit depth. I couldn't find a script named "Picture Processor".  I have tried this on both an Intel and a M1 Mac.

And yes, the broken save path in the action is not a problem. The action was created on a different machine and so any user who installs the Action set will no longer have the folder path the original user created.  But it makes no difference as long as you check the box for "Override Action 'Save As' Commands" in the Batch menu.  At least, it makes no difference in all of the versions we've used up until 24.2. But I don't think that is the issue. There is something inherent to the code in the new versions which "unsticks" the Embed color profile option after the first file is saved out in the batch.

I just made a new action, just like the one you show in your latest edit to your post, which now includes a legit file path, and it still does not work. You tried the batch on several PSDs at once, correct?  The first saved out PNG from the first PSD does correctly embed the color profile, but each subsequent PNG from each subsequent PSD in the batch is missing a profile when opened. And you do have your preferences set to give you a warning on missing profiles when opening files to check, correct? 

 

[Stephen Marsh]

I just tested the old Picture Processor script from Paul Riggott and it preserves the ICC profile - but resolution metadata is lost.

[Stephen Marsh]

Yes, I have tried many different scripts that use Save As and they are all stripping the ICC profile. For some strange reason, Save As to PNG had problems for many years with ICC, when Save for Web didn't. This was finally fixed, but appears to be broken again. Also confirming results with ExifTool and Photoshop for both ICC and resolution metadata.

[BTA-1138]

Okay, we actually have a workaround action for the resolution, but if you have a solution for embedding the color profile AND the 16bpc data into each batched PNG files, that would suffice. Does Picture Processor do that?

[BTA-1138]

Okay, thanks. Glad you were able to confirm it. Hope you guys can get it fixed again! Please keep us posted!

[BTA-1138]

ExifTool won't really work for us. Needs to be somewhat user friendly and just work inside Photoshop as that is what our users are equipped to handle.

[Stephen Marsh]

I understand, using a CLI, ExifTool isn't for everybody... But it is possible to set it up so that it can be more user-friendly, using drag-n-drop or right click etc. The following is for the Mac, but Windows has native options too.

https://prepression.blogspot.com/2016/12/automator-diy-exiftool-gui-services.html

[BTA-1138]

I just tested the latest updates for 2023 (v24.7.1) and 2024 (v25.0), and this issue still persists in both.

[Dan33993885qlce]

Would love to know what your workaround action is. The only solution I have is to run a separate action on the PNG's afterward convert to my chosen profile.