Test file
Adobe Firefly · JPEG
The signed claim identifies Adobe Firefly 4.0 and a text-to-image action.
- Version
- 4.0.0-release-firefly_v4-main_78135.80468
- SHA-256
bdc5c19d4211…
Adobe / C2PA manifest
Inspect Adobe credentials inside your export
Read the signed C2PA claim and ordinary Adobe metadata first. Then create a derivative copy without the embedded sections you select.
CONTEXT / EVIDENCE
Content Credentials are not ordinary EXIF
Adobe Content Credentials use C2PA, which binds a signed claim to one particular asset. Change the claim text and the signature no longer validates. ClearTags takes a simpler, honest route: it can remove supported embedded blocks from a new copy, but it never rewrites Adobe’s signed history.
Photoshop currently lets you export supported JPG and PNG files with credentials published to the Content Credentials cloud, attached to the file, or omitted. Cloud-backed credentials can be more durable than embedded metadata and may be recoverable after stripping.
To control a new Photoshop export, open Export As, enable Content Credentials, and choose whether to publish them to the cloud or attach them to the file as Adobe documents. If the export already exists, inspect that exact file here. ClearTags changes only the derivative you create; it does not change Photoshop preferences or an issuer’s cloud record.
TESTED FILES / ADOBE
What our Adobe fixtures actually proved
We ran the production cleaner against two licensed files from the Content Authenticity Initiative example corpus. These results apply to these exact exports and versions—not every Adobe file.
Test file
Adobe Photoshop · JPEG
The sample was opened, cropped and resized in Photoshop 26.11 before export.
- Version
- 26.11.0
- SHA-256
17c9e5b9f40e…
Verified result
Both JPEG files were cleaned by the production path, then checked again. Their encoded JPEG image payload hashes stayed the same.
ClearTags Lab documents each fixture's scope and publishes its complete hashes.
DIRECT ANSWERS / ADOBE
Adobe Content Credentials: short answers
- ACTION
How do I remove embedded Adobe Content Credentials from a JPG or PNG?
- Load the exported JPG or PNG into ClearTags above, inspect the active C2PA claim, and select C2PA for removal. ClearTags creates a new local copy without the supported embedded manifest while preserving the original file and encoded image data.
- STRUCTURE
Why does an ordinary EXIF cleaner not remove C2PA?
- EXIF and C2PA are different container sections. Adobe Content Credentials use a signed C2PA manifest, commonly stored in JPEG JUMBF data or a PNG caBX chunk, so deleting only EXIF leaves that provenance layer in place.
- LIMIT
Does stripping the embedded manifest delete Adobe cloud credentials?
- No. Removing the embedded copy does not delete a credential published to an issuer’s cloud or remove references stored in another asset. Reinspect the output and retain the original when provenance matters.
Three layers to check
C2PA · EXIF · XMP · CONTAINERSigned manifest
Claim generator, actions, ingredients and signature validation belong to one provenance layer.
Adobe edit metadata
Creator details, application names, document IDs and edit history may also appear as ordinary XMP.
Durable credentials
Deleting an embedded copy does not necessarily delete a matching credential stored by its issuer.
Create a clean publishing copy
WORKFLOW / LOCAL COPY- 01
Export from the working file
Keep the PSD and export a separate JPG or PNG for publishing.
- 02
Read the claim
Check whether the export has an active manifest, who signed it and which actions it declares.
- 03
Remove selected sections
Choose C2PA alone or combine it with XMP, EXIF, IPTC and comments.
- 04
Reinspect the result
Confirm what is absent in the derivative instead of assuming every credential was removed.