Skip to main content
lukasb79690852
Participating Frequently
October 28, 2024
解決済み

P: Content Credentials-signed images will create an XMP file for JPEG images

  • October 28, 2024
  • 返信数 3.
  • 9381 ビュー

I recently come across the following Issue:

 

I have a bunch of jpg files I have post-processed in Photoshop that I want to add geo locations to using the Lightroom Classic map module. After adding the locations I mark all images and do right click - metadata - save metadata to file. For some jpg files the data is written into the jpg file (desired behavior and how I know it from LR Classic for the past 6 years), while for others LR creates a seperate xml file (same location same name as the jpg) containing all metadata including the location.

 

Since this is a recent thing for me I suspected LR 14 to be the issue so I downgraded back to 13 but the issue persists.

I already cleared out my complete LR catalog and only importet a hand full of jpg files to test but the issues persists.

The issue can be reproduced, it is always the same jpgs causing the issue.

When I open one of the not functioning jpg files in Photoshop and save it again in a new location the issue persists. When I open it, create a new document of the same dimensions, mark all in the original, copy across to the new document and then save the new document as jpg I can then add gps locations to the new jpg in LR as expected.

I can also copy the gps data from a working jpg to one of the ones LR refuses to add gps data to using exiftools so the jpg file does not seem to be inherently broken in some way.

There is no different between the jpg files LR can write to and the ones where it insists on writing a xml file. They were taken using the same camera and have gone through the same workflow.

 

Any help would be appreciated since as of right now I am resorting to using a dummy image I assign the desired location to in LR and then use command line + exiftools to copy the gps tag across to the non functioning jpg which is extremely cumbersome.

解決に役立った回答 johnrellis

It appears this behavior is caused by the addition of Content Credentials to the JPEG, which are added to the JUMBF metadata section.

 

In the past, when LR didn't know how to update an industry-standard file format, LR would write a .xmp sidecar instead. For example, when LR first added support for HEIC, it wrote .xmp sidecars; a later version of LR wrote directly into the HEIC file. Similarly, LR still creates .xmp sidecars for AVIFs, even though that format supports updatable metadata. (Actually, when LR first added support for AVIF, it would corrupt the files if you did Save Metadata To File, so instead of fixing the bug Adobe changed LR to write .xmp sidecars instead.)

 

So perhaps LR doesn't yet understand how to update files containing JUMBF sections, and the developers decided to expediently create .xmp sidecars instead?

 

To reproduce this behavior in LR 14.0.1 / Mac OS 14.6.1

 

1. Import the attached file working.jpg.

 

2. Observe that Metadata > Save Metadata To File writes to the file directly.

 

3. Export working.jpg back into the catalog with these Export options:

 

4. Select the exported/imported working-2.jpg and do Metadata > Save Metadata To File. Observe that a .xmp sidecar has been created for it.

 

返信数 3

Inspiring
September 3, 2025

 

 I am unable to save tags to photos I have taken on my new Pixel 10 pro. I download the photos onto my Pc, but when trying to save tags using Lightroom Classic, the tags are not saved. I had no problems with photos from a Pixel 9 pro.

 

However, looking at the "Properties" tab on Windows, for each photo, the tags are being saved for the DNG file, but not for the corresponding JPEG file?

 

Does anyone know why and what I have to do to get over this problem? Is it a Lightroom issue or a Google issue?
johnrellis
Legend
September 3, 2025

Attach one of the problem JPEGs here and we can see in detail what might be going wrong.

Inspiring
September 4, 2025

I cannot save tags to this JPG

 

johnrellis
johnrellis解決!
Legend
October 28, 2024

It appears this behavior is caused by the addition of Content Credentials to the JPEG, which are added to the JUMBF metadata section.

 

In the past, when LR didn't know how to update an industry-standard file format, LR would write a .xmp sidecar instead. For example, when LR first added support for HEIC, it wrote .xmp sidecars; a later version of LR wrote directly into the HEIC file. Similarly, LR still creates .xmp sidecars for AVIFs, even though that format supports updatable metadata. (Actually, when LR first added support for AVIF, it would corrupt the files if you did Save Metadata To File, so instead of fixing the bug Adobe changed LR to write .xmp sidecars instead.)

 

So perhaps LR doesn't yet understand how to update files containing JUMBF sections, and the developers decided to expediently create .xmp sidecars instead?

 

To reproduce this behavior in LR 14.0.1 / Mac OS 14.6.1

 

1. Import the attached file working.jpg.

 

2. Observe that Metadata > Save Metadata To File writes to the file directly.

 

3. Export working.jpg back into the catalog with these Export options:

 

4. Select the exported/imported working-2.jpg and do Metadata > Save Metadata To File. Observe that a .xmp sidecar has been created for it.

 

lukasb79690852
Participating Frequently
October 28, 2024

Thanks, that's it! As to why it only happens to some photos and not to others, it seems like using generative fill for the object remove tool in Photoshop will create the JUMBF section.

lukasb79690852
Participating Frequently
October 29, 2024

@lukasb79690852: "As to why it only happens to some photos and not to others, it seems like using generative fill for the object remove tool in Photoshop will create the JUMBF section."

 

Looking at the metadata of not-working.jpg, it looks like you've enabled content credentials in Photoshop, which is why there is a JUMBF section in that file.  If you disable content credentials in Photoshop, will using generative fill on the file still cause your LR to write .xmp sidecars?


This is from an Adobe website: Adobe automatically applies Content Credentials to assets generated with Adobe Firefly features, such as Generative Fill in Photoshop. To learn more, check out Content Credentials for assets generated with Adobe Firefly.

 

To me this reads like I cannot disable content credentials when I used Generative Fill. I have definitely never actively enabled content credentials or selected anything to that effect when saving my images as jpg.

lukasb79690852
Participating Frequently
October 28, 2024

After posting I have tested this on a completely different Laptop and again the issue persistes for the same jpg files.

I have attached two sample files:.

working.jpg - LR Classic writes the metadata into the file as expected

not_working.job - LR Classic creates a seperate not_working.xml and writes the metadata into that

JohanElzenga
Community Expert
Community Expert
October 28, 2024

Most likely the image is locked, so Lightroom can't write to it.

 

-- Johan W. Elzenga
lukasb79690852
Participating Frequently
October 28, 2024

Thanks for your reply, could you elaborate on how to unlock a file? I checked and I found no way to lock or unluck a file anywhere. Under file properties in Windows the files are not marked as read-only.