• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

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

Community Beginner ,
Oct 28, 2024 Oct 28, 2024

Copy link to clipboard

Copied

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.

TOPICS
macOS , Windows

Views

1.5K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

LEGEND , Oct 28, 2024 Oct 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. (Actuall

...

Votes

Translate

Translate

correct answers 1 Pinned Reply

Adobe Employee , Oct 29, 2024 Oct 29, 2024

As-designed

In case of already signed JPEGs, metadata and develop settings are written to sidecar XMPS so as not to invalidate the CAI signature.

 

Votes

Translate

Translate
Contributor ,
Jan 16, 2025 Jan 16, 2025

Copy link to clipboard

Copied

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:

 

johnrellis_0-1737062963231.pngexpand image

 

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

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 16, 2025 Jan 16, 2025

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 16, 2025 Jan 16, 2025

Copy link to clipboard

Copied

LATEST

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

 

The Photoshop beta content credentials is only implemented for JPEG and PNG currently. I assume it will be extended to other file formats eventually.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Jan 16, 2025 Jan 16, 2025

Copy link to clipboard

Copied

 


johnrellis  schrieb:

"I believe that enabling content credentials causes Lightroom to write metadata to XMP files on export, even for images that normally would not have an XMP file."

 

Adobe verified this:

https://community.adobe.com/t5/lightroom-classic-discussions/p-content-credentials-signed-images-wil...


 

i did not enable that feature. nor have my files content credentials embedded.

 

it does not happen on export it happens when i press CTRL+S or change metadata (keywords) in lightroom.

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Jan 06, 2025 Jan 06, 2025

Copy link to clipboard

Copied

Yes, all I created all the jpegs in Photoshop, some possibly with content credentials enabled, but the .XMP files were not created when I exported the jpegs, nor were they created when exporting from LRC (I imported in LRC only), but only today when I added them to the LRC catalog. And there seems to be no rhyme or reason to them, as some images have XMP files some don’t.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 06, 2025 Jan 06, 2025

Copy link to clipboard

Copied

Upload a sample JPEG that didn't get a .xmp sidecar and a sample JPEG that did get a sidecar, along with its sidecar, to Wetransfer, Google Drive, Dropbox, or similar and post the sharing link here. That will be the most efficient way of determining what's going on.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Jan 07, 2025 Jan 07, 2025

Copy link to clipboard

Copied

OK, I put copies of the three files here – and renamed them so they make sense as to which is which.

 

I have Photoshop Content Credentials set as follow, which I enabled before I created these images:

Content Credentials.pngexpand image

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 07, 2025 Jan 07, 2025

Copy link to clipboard

Copied

Looking at the history recorded in the XMP metadata of both files, the last recorded action on ripps_with_sidecar.jpg was saving metadata (e.g. from Metadata > Save Metadata To file or the catalog setting Automatically Write Changes Into XMP), but there was no such action recorded for ripps_without_sidecar.jpg.

 

This comports what was discussed in this thread and confirmed by Adobe employee Rikk Flohr:

https://community.adobe.com/t5/lightroom-classic-discussions/p-content-credentials-signed-images-wil...

 

When LR saves metadata to a non-raw that already contains content credentials, it saves the metadata in a .xmp file rather than back into the file. It does this to avoid invalidating the digital signatures in the existing credentials.  

 

So the metadata had been saved for ripps_with_sidecar.jpg, and thus it got a sidecar. The metadata wasn't saved for ripps_without_sidecar.jpg, so it didn't get a sidecar.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Jan 07, 2025 Jan 07, 2025

Copy link to clipboard

Copied

Okay, trying to wrap my head around what you’re saying here, maybe I’m not fully grasping everything but…

 

When you say, the last recorded action was listed as …Metadata > Save Metadata To file or the catalog setting Automatically Write Changes Into XMP” is that the only that was metadata written into the file (not including normal EXIF, etc)? Or are there other entries?

 

I’m guessing that action was from when I added keywords to the base image when it was in Lightroom, and it automatically saved that metadata, but since I used the same base image to create all of the final images that I then saved from Photoshop as JPEGs, I’m not sure why some would have that metadata that would cause Lightroom to not write other metadata into the file, thereby creating an XMP file, and some would not.

 

And I am not sure why Lightroom is attempting to save metadata to the jpegs when I added them, since all I did was add the jpegs to my catalog, but not add any metadata, apply presets, etc. after adding them, or save them.

 

Just a little background on my workflow– I use Lightroom Classic to download the original raw files and import them into LRC’s catalog, applying develop settings, and basic metadata, which is saved in each corresponding XMP file. I then manually save the raw files, rate them and possibly delete some at that point, again, saving the files. I then go to Adobe Camera Raw to make any adjustments to the files, then go back to LRC to renumber the files, and save all the changes back into the XMP files. I then open a couple of the raw files, make a layered file within Photoshop, and then flatten and save them as JPEGs. At some point I take a bunch of those JPEGs and import them into LRC, but do not add any develop settings or metadata at that point. It was when I was doing that, that I noticed that some had created XMP files and some had not.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 07, 2025 Jan 07, 2025

Copy link to clipboard

Copied

Below are the histories extracted from ripps_with_sidecar.xmp and ripps_without_sidecar.jpg (edited slightly for readability). Note that these are different from the History steps in the Develop panel -- they record the basic operations of creating and updating the photo file.

 

As you can see, the last step for ripss_with_sidecar.xmp is "changed: /metadata".  As far as I know, the only two operators in LR that would cause that is Save Metadata To File and Automatically Write Changes To XMP.  Do you have the latter enabled?

 

-----------------------------------------------------------------------------------------------------------

ripps_with_sidecar.xmp:

 

action: saved
instanceID: xmp.iid:3ab4ea3b-27be-4efe-8536-72c3d7a43c8d
when: 2024-10-29T16:58:40-04:00
softwareAgent: Adobe Photoshop Lightroom Classic 14.0 (Macintosh)
changed: /metadata
----------
action: saved
instanceID: xmp.iid:b1ded996-065e-4afd-9d5c-18d245043c5c
when: 2024-11-07T08:33:32-05:00
softwareAgent: Adobe Photoshop Lightroom Classic 14.0 (Macintosh)
changed: /metadata
----------
action: derived
parameters: converted from image/x-nikon-nef to image/tiff
----------
action: saved
instanceID: xmp.iid:51cc4ff5-8d46-4875-8c73-e440a8c404b3
when: 2024-12-21T17:22:47-05:00
softwareAgent: Adobe Photoshop Camera Raw 17.1 (Macintosh)
changed: /
----------
action: saved
instanceID: xmp.iid:287d2ef7-9995-44e9-b775-6c3ba04e4cac
when: 2024-12-22T19:55:47-05:00
softwareAgent: Adobe Photoshop 26.2 (Macintosh)
changed: /
----------
action: converted
parameters: from image/tiff to application/vnd.adobe.photoshop
----------
action: derived
parameters: converted from image/tiff to application/vnd.adobe.photoshop
----------
action: saved
instanceID: xmp.iid:91549e67-08df-4d94-83e4-357fbdff0328
when: 2024-12-22T19:55:47-05:00
softwareAgent: Adobe Photoshop 26.2 (Macintosh)
changed: /
----------
action: saved
instanceID: xmp.iid:402e0cbc-9136-4ad5-bac5-d0022cf750e2
when: 2024-12-22T19:56:35-05:00
softwareAgent: Adobe Photoshop 26.2 (Macintosh)
changed: /
----------
action: converted
parameters: from application/vnd.adobe.photoshop to image/jpeg
----------
action: derived
parameters: converted from application/vnd.adobe.photoshop to image/jpeg
----------
action: saved
instanceID: xmp.iid:5a9a4319-f942-49d2-928d-c1be9f3434a1
when: 2024-12-22T19:56:35-05:00
softwareAgent: Adobe Photoshop 26.2 (Macintosh)
changed: /
----------
action: saved
instanceID: xmp.iid:91becedb-11e5-4306-be73-1f9f21640e45
when: 2025-01-06T15:46:21-05:00
softwareAgent: Adobe Photoshop Lightroom Classic 14.1.1 (Macintosh)
changed: /metadata

 

-----------------------------------------------------------------------------------------------------------

ripps_without_sidecar.jpg:

 

----------
action: saved
instanceID: xmp.iid:3ab4ea3b-27be-4efe-8536-72c3d7a43c8d
when: 2024-10-29T16:58:40-04:00
softwareAgent: Adobe Photoshop Lightroom Classic 14.0 (Macintosh)
changed: /metadata
----------
action: saved
instanceID: xmp.iid:b1ded996-065e-4afd-9d5c-18d245043c5c
when: 2024-11-07T08:33:32-05:00
softwareAgent: Adobe Photoshop Lightroom Classic 14.0 (Macintosh)
changed: /metadata
----------
action: derived
parameters: converted from image/x-nikon-nef to image/tiff
----------
action: saved
instanceID: xmp.iid:51cc4ff5-8d46-4875-8c73-e440a8c404b3
when: 2024-12-21T17:22:47-05:00
softwareAgent: Adobe Photoshop Camera Raw 17.1 (Macintosh)
changed: /
----------
action: saved
instanceID: xmp.iid:e9655d08-1964-4298-904e-73fff9888a12
when: 2024-12-22T19:51:15-05:00
softwareAgent: Adobe Photoshop 26.2 (Macintosh)
changed: /
----------
action: converted
parameters: from image/tiff to image/jpeg
----------
action: derived
parameters: converted from image/tiff to image/jpeg
----------
action: saved
instanceID: xmp.iid:d5dafeda-67e3-4264-ae9f-a0d7357e77f2
when: 2024-12-22T19:51:15-05:00
softwareAgent: Adobe Photoshop 26.2 (Macintosh)
changed: /

 

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Jan 08, 2025 Jan 08, 2025

Copy link to clipboard

Copied

Yes, I have LR set to “Save Metadata To File and Automatically Write Changes To XMP.” So if make any changes in LR, it writes them to the files.

 

I see that the one with the XMP sidecar has that last saving step from LRC in 2025, which the other does not. But not sure why the files are different, as they were treated the same in LRC. The only thing I did in Lightroom, other than adding them, was to Edit Capture Time to Change to file creation date for each image, which I did to all 26 images. Of those 26 jpegs, other ones created from different images do not seem to have created XMP files when I added them, yet as far as I know, they were treated the exact same way in Photoshop, and in Lightroom when the raw files were imported.

 

So, going back to your earlier explanation, that one jpeg had metadata saved to it from Photoshop, and one didn’t, I am also not sure why they would differ, as I used the same images in each jpeg, and created a series of derivative images one after another, but of the 10 I created in that series, only 7 had metadata saved into the files, and 3 did not.

 

As an experiment, I created another variation, using the two original raw files, saving them as a JPEG, and adding them into Lightroom, where when I changed the Capture Time to File Creation Date, Lightroom saved the change to the JPEG, creating an XMP file. So again, I’m not sure why, some images have some sort of metadata written into the JPEGs and some don’t. I then discarded the XMP file, went back to Lightroom and manually saved the JPEG – I’ve made no subsequent changes to it, so Lighroom shouldn’t saved anything, as there’s nothing new to save, yet Lightroom did create a new XMP file next to JPEG. When I clicked on the JPEG in Lightroom, and manually saved it again, it updated the save time in the XMP file, but again, nothing is changing in the JPEG, so not sure what actually is being saved to that XMP file

 

I will try again, using some different images, and see if the resulting jpegs, when added to Lightroom, also generate XMP files. I guess if I can’t figure it out, I can always just delete the extraneous XMP files, but just can’t seem to understand why they’re being created in the first place. Thanks.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Jan 08, 2025 Jan 08, 2025

Copy link to clipboard

Copied

I opened 2 new raw files, combined them and exported as a jpeg from Photoshop. I did another variation, and exported it as well. Then I did a third variation, but turned on contact credentials in the palate, and exported the image as a JPEG as well. In the export location, for the last file only, I suddenly have a c2paws sidecar file! Never saw one of those before.

 

And then dropped all three of the JPEGs into Lightroom, updated the File Creation Date, but Lightroom did not create an XMP file for any of them. Later, I manually “saved” all 3, but none of them created an XMP file.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 09, 2025 Jan 09, 2025

Copy link to clipboard

Copied

"just can’t seem to understand why they’re being created in the first place."

 

As Adobe employee Rikk Flohr tersely confirmed, they're being created because when you ask LR to save metadata to a JPEG containing content credentials, Adobe's intent is that the metadata will be written to a .xmp sidecar rather than to the JPEG. (That avoids invalidating the content credential's digital signature, which signs the exact contents of the JPEG.)

 

When I do the following steps in LR 14.1.1 with my test catalog, I reliably see the .xmp sidecars appear. If you do these precise steps, do you see the sidecars appear reliably?

 

1. Uncheck the option Catalog Settings > Metadata > Automatically Write Changes Into XMP.

 

2. From LR, Export a raw to JPEG, with Content Credentials options Attach To Files, Producer (me), and Edits And Activity.

 

3. Import the JPEG back into LR.

 

4. Do Metadata > Edit Capture Time to change the capture date of the JPEG.  Observe that the metadata status indicator in the upper-right of the thumbnail changes to the down arrow, Metadata File Needs To Be Updated.

 

5. Do Metadata > Save Metadata To File. Observe in Finder / File Explorer that the .xmp sidecar appears.

 

"Later, I manually “saved” all 3, but none of them created an XMP file."

 

If you don't see the .xmp sidecars appear following the precise recipe above, that indicates there's a bug or we're missing some important variable.

 

If you do see the .xmp sidecars appear with the recipe, than that suggests there's something about the more complicated workflow you're using with Photoshop, either a bug or a variable we're missing.

 

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Jan 09, 2025 Jan 09, 2025

Copy link to clipboard

Copied

Followed your directions- after step 2, exporting from Photoshop created a matching .c2paws file. After step 5, manually saving the imported jpeg, no XMP file was created.

 

Also tried in Photoshop settings, changing “Enable for saved documents with Content Credentials” to “Enable for new and saved documents with Content Credentials”, then followed other steps, but after saving Lightroom also does not create an XMP file.


Lastly, tried changing Photoshop settings, from “Publish to Content Credentials cloud” to “Attached to file (JPG and PNG)”, still no XMP file.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 09, 2025 Jan 09, 2025

Copy link to clipboard

Copied

I omitted an important detail from step 2 -- export the JPEG from a raw in LR, not using Photoshop. Please try that.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Jan 09, 2025 Jan 09, 2025

Copy link to clipboard

Copied

Sorry, I misread that part- I can try it, but that is not a normal part of my workflow, nor is it something that I did that created those XMP files…

 

Okay, used Lightroom to save a raw file as a jpeg, readded jpgs back to Lightroom, changed date, saved, and it did create an XMP file.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 09, 2025 Jan 09, 2025

Copy link to clipboard

Copied

"that is not a normal part of my workflow"

 

Understood -- it's just a diagnostic to narrow down the issue.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 09, 2025 Jan 09, 2025

Copy link to clipboard

Copied

When I repeat the recipe above but with this step 2, I observe the .xmp sidecar but no .c2paws sidecar:

 

2a. From LR, select a raw and do Photo > Edit In > Edit In Adobe Photoshop 2025. 

 

2b. In Photoshop, do Windows > Content Credentials > Enable Content Credentials, selecting Producer and Edits And Activity.

 

2c. In Photoshop, do File > Export > Export As, selecting JPG and Content Credentials > Attach To File.

 

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Jan 09, 2025 Jan 09, 2025

Copy link to clipboard

Copied

As do I if I follow version 2.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 09, 2025 Jan 09, 2025

Copy link to clipboard

Copied

That you are getting .c2paws sidecars from Photoshop may be an important clue as to why you don't always get .xmp sidecars for JPEGs with content credentials.  

 

Those .c2paws sidecars are not documented in the Adobe reference documentation:

https://www.google.com/search?q=c2paws+site%3Ahelpx.adobe.com&rlz=1C5CHFA_enUS1064US1064&oq=c2paws+s...

 

There are several threads in the Photoshop forum about these sidecars mysteriously appearing, and in this one, after consulting the engineering team, Adobe employee CJButler has no idea why they appear.  The last post about them appearing is from 12/15/24.

 

It may be that your PS is confused and is sometimes creating the content credentials in a way that LR doesn't understand, possibly due to a bug in PS invoking some legacy code by accident.  Try these steps to stop .c2paws sidecars from appearing:

 

1. In PS, do Help > System Info. If you're not on version 26.2.0, do Help > Updates to get the latest version.

 

2. Restart PS.

 

3. Try these simple steps that worked for one user.

 

4. Try resetting PS preferences, making a backup copy to restore from if resetting doesn't help.

 

 

 

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Jan 09, 2025 Jan 09, 2025

Copy link to clipboard

Copied

I could not get this link to work. I tried searching on the Adobe help site, but it did not come up with anything. The c2paws files were not really the issue, but… I never saw a c2paws until yesterday, although now strangely every time I export an image that has Content Credentials enabled as a JPEG I’m getting them, even though I did not before yesterday, and I had updated to the current version of Photoshop back on 12/20/24.

 

Yes, I am on version 26.2.0 for macOS.

 

As per the suggested fix, I quit & relaunched Photoshop, reopened a PSD file, set History & Content Credentials to none, saved the file as a jpeg, but it still is creating that c2paws file. I then opened the fly out palette, and I see this file does have CC enabled even though the Photoshop preferences have CC turned off. I disabled CC for this PSD file, saved it as a jpeg again, and it did not create the c2paws file.

 

I then turned back on the PS settings for both, but left it off for that file, saved as a jpeg, but it still gave me the c2paws file, so that first fix did not work for me.

 

I am also unclear about the difference between tuning on CC in Photoshop settings vs enabling for a specific image- I would think even if turned on globally, if I have it disabled for a specific image it would not save the CC to the file- or try to.

 

I quit Photoshop, moved the preferences folder and re-launched Photoshop. I opened a new file and saved it as a JPEG which did not create the c2paws file. I’ve then turned on the CC in the Photoshop settings again, saving it as a JPEG and again it did not create the c2paws file. Finally, I enable CC for that image and save it again as a JPEG but this time it did save a c2paws file.

 

I again tried the suggestion of turning off CC in Photoshop settings and opening the image and saved it as a JPEG, which did not create the c2paws file. Then I enabled both in the Photoshop settings, saved the file again, but it still is not creating the c2paws file.

 

I then quite Photoshop & restored my old preferences.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 09, 2025 Jan 09, 2025

Copy link to clipboard

Copied

Not sure what's going on with your browser and that first link in my post, which works in Chrome:

https://www.google.com/search?q=c2paws+site%3Ahelpx.adobe.com&rlz=1C5CHFA_enUS1064US1064&oq=c2paws+s...

 

It's a Google search query:

 

c2paws site:helpx.adobe.com

 

that shows "c2paws" isn't mentioned anywhere in Adobe's help.

 

 

 

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Jan 09, 2025 Jan 09, 2025

Copy link to clipboard

Copied

"Your search - c2paws site:helpx.adobe.com - did not match any documents."

Screenshot 2025-01-09 at 8.34.58 PM.pngexpand image

 

Same for Chrome and Firefox...

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 09, 2025 Jan 09, 2025

Copy link to clipboard

Copied

""Your search - c2paws site:helpx.adobe.com - did not match any documents."

 

Right. That's Google saying that no web pages at helpx.adobe.com contain the term "c2paws". Whereas a similar search for "xmp site:helpx.adobe.com" yeilds an estimated 14,300 pages.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 09, 2025 Jan 09, 2025

Copy link to clipboard

Copied

This very much smells  like an issue with your Photoshop. It should not be generating .c2paws sidecars, but it is, as it has for a small number of users reporting in the Photoshop forum.  This suggests that it may sometimes be generating content credentials incorrectly that's not compatible with LR.

 

You could try posting a bug report in the Photoshop forum, but that hasn't help the other users posting about it.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines