P: (Early Access) Content Authenticity Initiative (CAI) for (CR & LrClassic)

[Rikk Flohr: Photography]

This thread is for Camera Raw & Lightroom Classic feedback on the (Early Access) Content Authenticity Initiative (CAI)
For the Lightroom Ecosystem feedback, click here. 

The Lightroom team is dedicated to building capabilities that foster trust and transparency in the age of AI. Our latest release, as part of the Content Authenticity Initiative (https://contentauthenticity.org/), allows you to add content credentials to your work when exporting in Lightroom to ensure provenance and preserve authenticity.

New content credential capabilities are available across the Lightroom ecosystem (Lightroom, Lightroom Classic, Lightroom for mobile (iOS & Android), Lightroom for web), and Adobe Camera Raw in Early Access. When exporting a JPEG from Lightroom, you can attach your name, social media handle, and a list of edits via a digital signature.

You can find the option to apply Content Credentials while exporting a JPEG in the export panel. It is, by default, turned OFF. You can choose to enable this option at the time of each export or enable it in App preferences for every export. Learn more.

If you choose to attach credentials, the information you submit will be tied to your image and can be verified by uploading the photo to contentcredentials.org/verify. Try out the early access version of Content Credentials and share your feedback with us.

Please include the following details in your post:

• App version/platform
• System details
• Example image(s) if you wish to share

Thanks!

Komal Desai: Product Manager - Lightroom Ecosystem

Posted by:

[nycDeke]

The CAI feature seems to be more applicable to teamwork and sharing than to solo photographers and their aesthetic needs.

[Dash28309532spck]

I'm unable to export JPGs with Content Credentials from Camera Raw and I'm not sure why. I'm also not able to do it through Bridge's export dialog - the dropdown option doesn't even appear there.

I'm on Windows 11 23H2 and the latest versions of Bridge and CR. In Bridge, the option to enable viewing Content Credentials in the preferences is enabled. The file I'm trying to export is a single CR2 I took a few weeks ago with a Canon 77D.

Any help would be much appreciated!

[robf1x]

The first thing I have noticed is "Producer" has my actual name, not my business name. Would it be possible to maybe link this field to the Lightroom name-plate as opposed to the Abobe account name? (I registered before starting the business :)). Thanks, Rob.

[johnah_6970]

Png

[S01AC]

This is a little nit and not a functional matter but there is a misspelled word in the Lightroom Classic descripiton for Content Credentials within the Export dialogue box. You use the word "seperate" in the description but the correct spelling is "separate".

[ashleys18899981]

lol - was just about to post this 🙂

[peter_4508]

This is definitely more than a nit. If the Adobe UI folk can't spell, how do we know their developers can code? It's the little things that are most telling.

[nycDeke]

Yes. There is “a rat” in “separate.” Most literate people know that.

[Rikk Flohr: Photography]

Should be correct in the 14.1.1 version released a moment ago. 

[reisememo]

Great initiative, thanks!

I would like to also have the option to add my blog URL besides the social networks. 

[ossac68678682]

How can I use different "Producer" Name depending on each of my brand name... ? Thank you !

[leonardhughet1972]

The new generative remove feature is nearly perfect, and such a welcomed update! However, adding credentials other than the METADATA that's already include in each file we export feels like giving permission to ADOBE to use our images (in any future capacity), under the guise of sharing our social media profiles. That is simply not enough to agree to these terms. I personally don't need ADOBE to help me promote my photography business. I'm also confident that I don't need ADOBE to promote my social media presence. While I continue to use ADOBE products to edit my photos, I too am starting to feel the overreach with each new feature necessitating a sign off.

[SpikeShotThis]

I've been trying to link with my Instagram account but consistently get "400 Session Invalid" error. I'm on Mac and here is the System info 

Lightroom Classic version: 14.0.1 [ 202410161356-30922cfc ]
License: Creative Cloud
Language setting: en-US
Operating system: Mac OS 15
Version: 15.0.1 [24A348]
Application architecture: arm64
Logical processor count: 8
Processor speed: NA
SqLite Version: 3.36.0
Power Source: Plugged In, 100%
Built-in memory: 16,384.0 MB
Dedicated GPU memory used by Lightroom: 185.1MB / 10,922.6MB (1%)
Real memory available to Lightroom: 16,384.0 MB
Real memory used by Lightroom: 553.1 MB (3.3%)
Virtual memory used by Lightroom: 405,701.9 MB
Memory cache size: 540.2MB
Internal Camera Raw version: 17.0 [ 2043 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2
Camera Raw virtual memory: 43MB / 8191MB (0%)
Camera Raw real memory: 45MB / 16384MB (0%)

Cache1:
NT- RAM:0.0MB, VRAM:0.0MB, Combined:0.0MB

Cache2:
m:540.2MB, n:0.0MB

U-main: 111.0MB

Standard Preview Size: 2940 pixels
Displays: 1) 2940x1912

Graphics Processor Info:
Metal: Apple M2
Init State: GPU for Export supported by default
User Preference: Auto
Enable HDR in Library: OFF

Application folder: /Applications/Adobe Lightroom Classic
Library Path: /Volumes/T7 Shield/Photography/Catalogs/SpikeShotThis/SpikeShotThis.lrcat
Settings Folder: /Users/<USERNAME>/Library/Application Support/Adobe/Lightroom

Installed Plugins:
1) AdobeStock
2) Any Tag
3) Any Vision
4) Aperture/iPhoto Importer Plug-in
5) Flickr

Config.lua flags:

[João Rodrigo235811198p51]

Great little feature.
But the detail that shows up is "Content Creator - Adobe Photoshop Lightroom Classic (Macintosh), instead of my actual name. I've customized everithing, even linked insta and linked in and nothing shows up.

Again, great little feature that needs improvement.

[ryans97066424]

I'm working with another artists catalog, I manage several of them, and the only "Producer" option I am given is for me, I guess because I'm it's my licence I'm using. I would like to have the option to have this information match the metadata for the files not just the owner of the licence.

[Minaris]

Hello,
It's a great idea. But it is so long to export files.
Usually when I export 100photos 4K to jpg fullHD it just takes only a few seconds.
Now with content credential and only productor and account (not modifications) it takes maybe 10min. Crazy too long.
And it crashes usually on some files. I think it's because of undersized servers. Maybe.
So sadly I stopped using this option.

Lrc 14.0.1

Windows11pro, I7 14700k, 64goddr5, rtx4070tisuper

[tomfoto]

I'm just looking into this and I have questions:

1) If I attach to cloud and then post my jpg to a social media site, how does an individual looking at that check the image to see if it is really mine or what edits I made. I have had people challenge me that my image was AI and I can't see any simple way to verify that to them. Seems this would help if the user could check/verify.

2) If I decide I don't want to use this feature any longer, is there a way I can remove the information that I have already allowed up to the cloud?

3) Is there any sort of "certificate" that I can generate from this to give to individuals who purchase a print from me? I like to leave them with something that they can use to verify that it is indeed my image, or at least I registered it somewhere and didn't just steal it and resell it.

4)  I would like to be able to attach more than just X, Instagram, LinkedIn to photos.

5) I don't see any option in LrC to prevent AI scraping or the "I own this . . . " checkbox.

6) Will this evolve into a subscription or pay app? Meaning will it be free forever to upload as many content credetials as I want?

7) A possible problem in the chain of editing is that I often use 3rd party apps to Denoise. These generate a tiff image that when exported with credentials doesn't really tell anybody very much except my person contact information and linked media sites. Not sure much can be done about that, but it also means that almost any AI image can be exported as a tiff and then have credentials uploaded and there does not seem to be any way that can be detected or tracked.

8) If I change location/address/email/phone, is there any way to update that on previous image data uploaded.

9) Is there a way to log into my account and see what I have there and modify/edit it?

Hope thats not too much to ask at once, but thats my immediate feedback.

Thanks,

~ tommy

[SStrackside]

This "Content Credentials" was a waste of development time & skill.... It would have been a better use of developpers time to team up & improve functionality of other "upgrades".

[Enthusiastic_Wave]

I would like to see an option during export that only states whether AI has been used or not, instead of showing "edits" along that info. If building trust around AI usage is the goal, then I believe showing "edits" other than AI usage is not necessary, unless I would choose so.

[martinnohr]

In the dialog description it says "seperate". "separate" would be more accurate.

[Abby2565837539aq]

There seems to be some sort of glitch where the content credentials are not always able to be added. It will work sometimes and then others it will say content credentials failed and then it wont save the file at all until I click the credentials tab off.

[paul3.14159]

What's the difference between this and simply adding metadata to my exports? 

[Seth25814003ur58]

I am unable to share too many details for business infosec reasons. I'm currently using Adobe Bridge 14.1.3 on Mac OS, and I'm using this version specifically in order to avoid the forced use of "CAI." I work in image production in the entertainment industry, and there is great and growing concern that this unwanted Adobe-proprietary format is being forced on us - and that is indicated by the Creative Cloud descriptions and various submenus of the newest versions of Adobe Bridge, Lightroom, Photoshop, and Camera RAW.

This "Content Credential" product is NOT a well-accepted nor industry-adopted standard or system for data management, nor is its use recognized as a best practice by any major corporate businesses in the photography industry, especially not in the realm of entertainment photography where I've worked for 20 years.

Disallowing the ability to erase faulty, mis-entered, or even personally-identifying editing and file metadata, even when it is "junk data" or traces left by users/vendors who aren't image owners, is a complete failure point conceptually for infosec as well as for the whole idea of using Adobe's "Content Credentials" for data management. The uploading of privately-owned and proprietary images to Adobe's "Cloud" service alongside these "Content Credentials" is another separate and unique security violation. These are just a couple of many systemic failure points of this format that make it especially unsuitable for the professional image production environment. Businesses that work in imagery have a direct, easily understood business need to erase and/or change metadata. That's been true of every single photo business and photographer I've worked for and worked with.

If Adobe takes further steps to force the adoption of this protocol that breaks actual established industry best practices for data management (the ability to erase personal private identifying information, and the ability to erase and wipe old/incorrect metadata) it will drive Adobe business customers to seek other options, and to forego further Adobe upgrades and product purchases. Simply put, these Adobe "credentials" must be kept entirely optional and they must remain dormant unless affirmatively requested. And Adobe needs to be much, much clearer that that is going to remain the case.

[Kristenpasta]

Unabke to export photos from Camera Raw with content credentials... Consequently cannot export with Copyright