Drop a file here
or · removal supports JPEG, PNG, WebP, GIF, WAV and MP3 for now (beta)
Questions and answers
How do I remove Content Credentials from a photo?
Drop the file above. If it carries C2PA Content Credentials and is a JPEG, PNG, WebP, GIF, WAV or MP3, one click removes the embedded manifest from the file's container and gives you a cleaned copy to download. The result is re-checked by the official C2PA validator library running locally in your browser (nothing is sent anywhere) before the download appears.
Is the removal lossless?
Yes. C2PA data lives in a well-defined slot in each format (an APP11 segment in JPEG, a caBX chunk in PNG, a RIFF chunk in WebP and WAV, an application extension in GIF, an ID3 frame in MP3). Only that slot is removed - the pixels or audio are byte-for-byte untouched, nothing is re-encoded, and other metadata such as EXIF is kept. Your original file is never modified; the download is a new copy.
Is it OK to remove C2PA metadata?
From your own files, removing provenance metadata is a normal privacy choice - Content Credentials can embed a name, an account or a device, and the C2PA standard itself anticipates removal (it calls it redaction). C2PA is not copy protection. The trade-off is real though: a stripped file loses its proof of authenticity, and you cannot re-attach the original signature later.
Which formats can be cleaned, and why not MP4 or PDF?
The beta handles JPEG, PNG, WebP, GIF, WAV and MP3 - formats where removal is a clean container edit. MP4/MOV store sample offsets that shift when bytes are removed, and PDF and TIFF weave the manifest into their object structure, so those need heavier surgery and are not supported yet.
Is my file uploaded anywhere?
No. The removal and the before/after validation all run in your browser - this site has no backend, no accounts, no analytics and no cookies. Load the page, go offline, and it still works.
Does this strip EXIF and other metadata too?
No - it removes only the C2PA credential block. EXIF, XMP and other metadata are left exactly as they were. If the file's XMP contains a pointer to the removed manifest it is left in place; it carries no signature and no provenance data by itself.