A C2PA manifest is a signed record stored inside the file: who signed it, which tool or model produced it, what edits it declares, and a hash of the asset at signing time. This tool reads that record first, then removes it, so you can see exactly what you are deleting. It does not touch the image or video data, and it will not claim that removing a signature removes an invisible watermark — it does not.
Engine
File API
Runs in
Web Worker
Needs account
No
C2PA is stored in a container box rather than in EXIF, which is why some tools strip EXIF and leave the signature behind — and why removing it is a container edit, not a re-encode.
Once a file is signed, the manifest travels with it: into a client review folder, a marketplace upload, a forum attachment. Some platforms read it and display a “made with AI” badge, some ignore it, and some strip it silently. Removing it means you decide what travels, not the platform.
For generated images the manifest frequently names the service and the model, and lists the actions taken — created, converted, watermarked. For photos it names the camera app or the editor and the organisation that signed. Either way it is a description of your workflow that you may not want to publish.
The manifest sits in its own container box. Removing it leaves the compressed image or video data byte for byte identical, so there is no generation loss and no change in file duration, colour or quality.
The report lists what the manifest actually said before it is removed: signer, generator, actions and source type. That matters if you are removing it for a legitimate reason — a client file name, an internal tool chain — and it is the part a “just strip everything” tool throws away.
Drop a photo or video into the panel. The manifest is read on your device, not uploaded.
Read the report: signer, generator, declared actions and source type, with the metadata around them.
Download the cleaned file. The manifest is gone; the image and video streams are untouched.
Before you rely on it
Removing a manifest to protect privacy — a client name, a device identity, an internal tool chain — is ordinary metadata hygiene. Removing it so that AI-generated media can be passed off as a photograph is deception, and no tool should help you claim the opposite. This page shows you the signer and the declared source type before removing them, precisely so the decision stays visible.
No. It removes one signed claim from this copy. Invisible watermarks, perceptual hashes, platform-side records and the original upload may all still identify it. Treat this as metadata hygiene, not anonymity.
Yes. The manifest is a metadata block; removing it does not touch the image or video samples. Test the cleaned copy before deleting the original, as with any file editor.
The AI remover covers all five AI-adjacent carriers — manifests, IPTC labels, generator tags, PNG prompts and comments. This page is the focused one: it explains the manifest itself and what removing it does to the provenance story.
Yes, that is the report above the download button. To verify the signature rather than just read it — chain, trust list and asset hash — use the C2PA viewer at /verify first.
Yes. In MP4 and MOV the manifest lives in a uuid box, which is emptied in place and retyped as free space, so the offsets in the container stay valid and the video plays exactly as before.