Ps 2024 Export PNG Now Retains Resolution Metadata But JPEG Doesn't

[Stephen_A_Marsh]

Previously Export As and Quick Export would strip resolution metadata.

Now in version 25.4.0 it retains resolution metadata for PNG, but not for JPEG.

This is also the same in the new 25.5.1 update.

So, is this a bug that resolution metadata is now included in PNG exports?

If this isn't a bug, then why is JPEG resolution metadata stripped?

Users need consistency.

I understand the Adobe vision or philosophy of Export vs. Save As... But despite this, end-users have been asking for the option to include or exclude resolution metadata in PNG and JPEG for a long time.

https://community.adobe.com/t5/photoshop-ecosystem-discussions/how-can-i-quick-export-as-a-png-witho...

[Stephen_A_Marsh]

Can somebody from Adobe please comment?

[Stephen_A_Marsh]

EDIT: It looks like a moderator removed the troll's posts...

[Stephen_A_Marsh]

The bug is still present in the new 25.6.0 (Intel Mac).

Resolution metadata is present in the Export As PNG (unlike previous versions, i.e. prior to 25.4.0).

Resolution metadata is stripped from the Export As JPG (as per previous versions).

What's going on Adobe? Either strip it out for both formats as you have always done, or as many users have requested – retain it for both formats via a GUI user option. A mismatch in results isn't helpful when both formats fully support the retention of this metadata. Either remove it or allow it to be kept for both.

[Stephen_A_Marsh]

The bug is still present in the new 25.7.0 (Intel Mac).

[Lumigraphics]

This is one reason I still use Save for Web. I can include it in an action and it allows reasonably (but not perfect) grandular choice of metadata. I would love to see more configuration options, as it is I have to use custom scripting in both Photoshop and Bridge to retain some metadata fields which I rely on.

It would also be really nice if Adobe supplied a suite of scripts to extend these apps, that users could modify. Instead of making us do all the work. My boss wonders why I have to be a programmer instead of a photographer.

[Stephen_A_Marsh]

This bug is still present in the new 25.9.1 release (Intel Mac)!

[Stephen_A_Marsh]

Bump...

[Stephen_A_Marsh]

A new release, 25.11.0 – same problem.

PNG includes resolution info when it shouldn't (based on legacy behaviour which sets expectations).

JPEG excludes resolution info, just like it always has.

[Sam Gannaway - Ps]

I don't have the context of why it was excluded originally.  Looking at it now, I would add it for jpg.  

[Stephen_A_Marsh]

@Sam Gannaway - Ps 

Thank you for the reply.

Export As has always removed unnecessary metadata to reduce file size for web/device viewing. That's the context that I have understood from Adobe's perspective. That Export As only has limited metadata functionality compared to Save for Web (Legacy) is another discussion.

Despite Adobe's vision of what Export As is designed for and the features that it offers or doesn't offer, end users don't always understand the nuances of regular save as vs. web optimisation and complain that their exports don't contain resolution metadata.

We all know that you can't make everyone happy, so if you now change things so that both JPG and PNG retain resolution metadata then some will not like the change to historical behaviour.

Export as ideally would offer a checkbox to include or exclude resolution metadata alongside the existing radio button option for metadata inclusion (or perhaps use a another radion button option or a dropdown menu).

[Lumigraphics]

Export should be BETTER than Save for Web. All of the granularity should be included, and additional functionality (how about full scripting, even if its only via UXP.)

I'm a product photographer and use SfW in production because Save As and Export lack the features I need.

[Sam Gannaway - Ps]

Yes, I agree that Export As should have more controls available.  In the mean time, we need to decide how to proceed here. 

Through this investigation, I learned that Ps will assume 72ppi if no metadata (XMP or file-specific) exists.  That assumption causes some confusion especially with placed images (smart objects).  Knowing that we have those kinds of bug reports, I'm inclined toward adding the resolution metadata for JPG by default to match the current state for PNG.

[Stephen_A_Marsh]

Hi Sam, I follow your reasoning, however, including resolution metadata for either PNG or JPEG breaks the many years of behaviour from when Export As was first implemented. This would need to be documented.

Additionally, would Quick Export behave any differently, i.e. as it does with ICC profiles?

[Lumigraphics]

Security

Stability

Benefit to the user

easy of use

consistency

ease of maintenance/extension

IMHO, allowing more control over metadata is a winner all around.