What This Scanner Can Verify
- Whether a supported JPG or PNG contains an embedded C2PA package
- Whether that embedded package is absent from the cleaned copy
- Whether the encoded image payload, orientation, and color data stayed intact where supported
Content Credentials can carry verifiable provenance and editing history. Check what is embedded before deciding whether a separate publishing copy should remove it.
Quick Answer
Removing a supported embedded C2PA credential also removes that provenance package from the cleaned copy. The original file is never overwritten, and removing one embedded copy does not erase credentials that may be stored elsewhere.
Drop, paste, or choose image files
JPG & PNG · WebP inspection only · Up to 25 MB each · No image upload
iPhone photo in HEIC? Save or export it as JPG first.
No file handy?
Reviewed September 3, 2026 Platform claims: C2PA and Adobe documentation File behavior: local format tests Storage and platform behavior may change
C2PA is used to record provenance and editing history. Finding an embedded credential does not by itself establish that the whole image was AI-generated. The contents and their validation need to be interpreted separately.
An AI tag remover may remove a supported embedded credential from a new file copy, but that does not prove the picture was never edited or erase credentials held elsewhere.
Ask what the next copy is for. If a client, archive, or publication needs verifiable provenance, keep the original credential-bearing file. If you need a separate publishing copy without a supported embedded credential, create that copy and keep both files clearly named.
Adobe documents both file-attached and cloud-published Content Credentials. Removing an embedded package from one file cannot remove a credential stored in Adobe's cloud or another external location.
01
Scan the intended source file and confirm whether an embedded credential exists.
02
Decide whether provenance or attribution must remain available for this use case.
03
Download only a clean copy that passed verification.
04
Archive the original separately so the provenance record is not lost.
Official documentation supports the platform and file-format claims below. Community posts show reported questions, not proof of platform behavior.
Official source
Defines the manifest, provenance, validation, and storage model used by C2PA Content Credentials.
Official source
Documents current JPG and PNG export choices for attached, cloud-published, or omitted Content Credentials.
You lose the embedded provenance package and the editing history that can travel with that file copy.
Check supported file signals before posting a lightly edited real photo.
Guide →Inspect Photoshop exports for embedded credentials and AI-related metadata.
Guide →Review file-level signals before you publish a cleaned local copy to Facebook.
Guide →Understand which file signals, disclosures, and platform systems may contribute.
Guide →