Active manifest
See whether the file includes a readable C2PA manifest and which manifest is marked as active.
C2PA CONTENT CREDENTIALS
Inspect Content Credentials inside a file and understand whether it includes signed provenance, AI source declarations, editing actions or validation warnings.
Upload a file to check C2PA data and see a clear mdremove report.
JPG, PNG, WEBP, SVG, HEIC, TIFF, AVIF, PDF, MP4, MOV, MP3, WAV, M4A · Max file size: 200 MB
Choose a file to inspect Content Credentials.
After uploading a file, mdremove shows whether Content Credentials were found and summarizes the manifest, validation status, source signals, actions and ingredients.
C2PA is not the same as ordinary EXIF metadata. It is provenance data designed to show who signed a file, what tool touched it, and whether signed information still validates.
See whether the file includes a readable C2PA manifest and which manifest is marked as active.
Review valid, warning, issue or unavailable states in plain language so the result is easier to understand.
Check whether the file declares an AI-related source type or generator inside Content Credentials.
Inspect recorded edits, exports and source materials when this information exists in the manifest.
Use the result as a provenance signal, not as a final truth test. A file can be authentic without C2PA, and a signed file still needs context.
| Status | Meaning inside mdremove |
|---|---|
| Verified credentials found | A manifest was found and no blocking validation issue was returned by the verifier. |
| Credentials with issues | The file contains C2PA data, but the report includes warnings, invalid data, missing trust details or other problems. |
| No Content Credentials | No readable C2PA manifest was found. This does not prove the file is fake. |
| Marker found | The file contains C2PA/JUMBF markers, but the manifest could not be fully verified in the current check. |
mdremove helps you quickly inspect provenance before publishing, archiving, approving or sharing a sensitive file.
Check whether a photo or document includes a provenance trail before it enters an editorial workflow.
Review creator, tool and edit signals before approving campaign assets or public media.
Inspect signed capture or export information when sharing original work with clients or platforms.
Look for AI-related source declarations when a file includes Content Credentials from supported tools.
You can try common file types that may carry Content Credentials. Support depends on whether the creator tool actually embedded a C2PA manifest.
JPG, JPEG, PNG, WEBP, GIF, TIFF, TIF, HEIC, HEIF, AVIF, SVG
PDF and other files may expose C2PA data when signed by compatible software.
MP4, MOV, M4V and WEBM can be tested for provenance metadata.
MP3, WAV and M4A can be checked when provenance data is present.
Answers written for mdremove users who want to understand Content Credentials without technical confusion.
It checks whether Content Credentials exist, then shows readable details such as manifest status, source declarations, signer/generator signals, actions, ingredients and a JSON report.
The file may have been created without C2PA data, exported by unsupported software, compressed by another app or shared through a platform that removed metadata.
Only when the file contains a relevant source declaration or generator information. If there is no manifest, C2PA alone cannot confirm whether an image was AI-generated.
Yes. EXIF usually stores camera and technical fields, while C2PA focuses on signed provenance. A file can have EXIF without C2PA, C2PA without useful EXIF, both, or neither.
No. C2PA is helpful evidence, but it should be combined with source checks, context, visual review and editorial judgment.
C2PA focuses on provenance. Use the main metadata viewer to inspect broader EXIF, document, image and technical metadata.