You took the photograph. You corrected the color, exported it, and posted it on LinkedIn. Then a small Content Credentials icon appeared with Adobe's name inside. Why does your work seem to be credited to your software?
“Issued by Adobe” identifies the credential's issuer, not the photographer or copyright owner. The distinction matters before you change export settings or remove anything.
Why a normal photograph can show a credentials icon
A photographer raised exactly this concern on Reddit: ordinary color correction and framing, no remembered generative edits, but a panel saying “Issued by Adobe” and “Issued to Adobe.” They also questioned a date that did not match when they took the photo.
Their original file was not available for inspection. What we can establish is that Content Credentials are not reserved for AI-generated pictures. LinkedIn's documentation includes camera photographs and describes an icon that opens available provenance information. The icon is a prompt to read that information, not a verdict that someone else created your image.
Separate the signer, the creator, and the date
Read the panel as several different fields, not one combined photo credit:
- Issued by: LinkedIn defines this as the entity that created and signed the credential. A software company can appear here without being the photographer.
- Created by: a separate creator field, when available. An issuer's name does not fill in missing creator attribution.
- App or device: information about the tool or capture device, not ownership.
- Issued on: LinkedIn describes this as when the credential was created and signed, not necessarily when the shutter fired.
For a view that also says “Issued to,” inspect the certificate details rather than treating its holder as the author. The C2PA explainer distinguishes the certificate holder signing a claim from optional information identifying people involved in the work. An unexplained date needs the same care: first establish which record it describes.
The signature concerns provenance and integrity. It is not, by itself, a transfer of rights. If you need to authenticate the signer, follow our Content Credentials verification guide. Detecting metadata and validating its signature are separate tasks.
Prepare a deliberate sharing copy with FreeAIWiper
Use FreeAIWiper to inspect the actual export and remove supported portable metadata when you want a sharing copy without those records. It keeps inspection and cleanup together, locally in your browser.
- Keep your archive. Preserve the camera original, editable project, and credential-bearing export separately.
- Select the finished export. Open FreeAIWiper and choose your JPEG, PNG, or another supported image format. Review the detected provenance before cleaning.
- Choose the cleanup. Remove the supported AI/provenance records you do not want in this copy. Review optional private-metadata removal separately, especially if you want to retain useful attribution.
- Download the checked output. FreeAIWiper reinspects the rebuilt file before download, without pixel recompression. Open the result and give it a distinct sharing filename.
This prepares a new local file; it does not edit an existing LinkedIn post. Keep your actual photo credit in the caption or agreed delivery notes. A software issuer's name and your authorship answer different questions.