C2PA & JUMBF Content Credentials Inspector & Remover
C2PA Content Credentials are signed provenance manifests stored in JUMBF boxes. Inspect the issuing vendor and any AI assertions, then remove the manifest from your image.
Drop images here
JPEG, PNG or WebP · up to 25 MB each · add as many as you like
Binary telemetry
- [1/4] ReadFile → ArrayBuffer
- [2/4] ParseWalk container segments
- [3/4] StripDrop selected metadata
- [4/4] RebuiltEmit cleaned bytes
Cleaning profile
Only the categories you check below are stripped.
Write a fresh Make, Model and ISO block into every cleaned image.
No images queued
Add JPEG, PNG or WebP images above to build a batch. You can queue 30+ files and clean them all at once.
Single-image inspector
nothing selectedNo image loaded
Add an image above to inspect its metadata in detail.
Awaiting an image
Drop a JPEG, PNG or WebP above to read its metadata. Parsed fields appear here as a grouped evidence table.
0 B uploaded · 0 bytes sent
How It Works
- 1
Drop an image; the scanner walks the JUMBF box tree inside the C2PA manifest store.
- 2
The C2PA tab lists the issuing vendor, claim generator and every detected box.
- 3
C2PA and AI markers are pre-selected so the provenance manifest is removed.
- 4
Clean and download an image with no Content Credentials attached.
Binary Format Breakdown
| Segment | Carries | Action |
|---|---|---|
| JPEG APP11 (JUMBF) | C2PA manifest store split across sequenced segments | All manifest segments reassembled and removed |
| PNG caBX | The C2PA manifest store in a PNG chunk | Chunk dropped whole |
| JUMBF jumd / c2ma boxes | Box labels, claim and assertion payloads | Reported in the inspector, then removed with the manifest |
Frequently Asked Questions
What are C2PA Content Credentials?
They are a cryptographically signed record of an image's origin and edit history, stored in a JUMBF manifest. They are used to prove provenance and to flag AI-generated content.
Why would I remove Content Credentials?
They can reveal the software, account and editing steps behind an image. If you do not want that history attached when you share, remove the manifest.
Can the tool read a damaged manifest?
Yes. A malformed, truncated or encrypted manifest is reported as unreadable rather than crashing, and the rest of the batch keeps processing.