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
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.

 

Robert Ripps
Inspiring
January 6, 2025

I have LRC set to create .XMP files when I import raw images, applying develop settings and metadata to them, and have those changes/additions automatically written into the XMP files, but now it seems that LRC has started creating XMP files for some of some JPG images I just added to the catalog. For 26 files I added, it created .XMP files for 7 of them, even though I did not do anything to the files in Lightroom other than Edit Capture Time to Change to file creation date for each image to all 26, which never caused Lightroom to create an .XMP file before.

 

Previously adding JPG images to LRC’s catalog did not create the .XMP files in the folder they reside in, only adding or applying changes to raw files.

 

So not sure if something has changed with how Lightroom Classic treats JPG files, or if I have accidentally changed some setting somewhere.

 

Thanks.

 

Lightroom Classic 14.1.1, macOS 14.7.2

johnrellis
Legend
January 16, 2025

sorry but that is unacceptable.

 

that means in every image where i use the generative AI to fix some stuff, like retouching removing an object that is just 120x120 pixel i can´t embed keywords in it?

 

that is ridiculous.

i mean if these credentials would be secure in the first place.. they are not.
but now they are annoying on top.

 

at least LR could warn the user that the metadata is not embedded into the file.

 

and why is that only affecting JPG (and PNG as i noticed right now)?

i don´t think i have ever noticed this behavior with my TIFF files.

 

quote

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]

 

Adobe's Inspect Tool shows that your sample image contains content credentials for content generated by Adobe Firefly via Photoshop:

 

 

According to this help page, "Adobe automatically applies Content Credentials to assets generated with Adobe Firefly features, such as Generative Fill in Photoshop", regardless of your Photoshop settings.

 

 

of course that would also explain why shutterstock rejected a landscape image where i removed a sign with a logo because of "generative Ai".

 

that makes these AI tools pretty much useless for me.

 

thank for finding this out. now i have to look how i work around it..... 😞

 

i am using exiftoolgui.
any idea where exactly i can find the content credential entry that i have to delete?

how is the tag called?

 

edit:

ok i found the category of metadata i need to remove with exiftool.

after i created a batch for exiftool and executed it lightroom is writing the metadata fine.

 

thanks for your help


See the second paragraph of this page for the Exiftool command-line arguments for removing C2PA (content credentials) metadata:

https://exiftool.org/TagNames/Jpeg2000.html

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.