C2PA Remover
Strip Content Credentials from your own photos and videos. The manifest is cut out of the container — the picture and the audio are never re-encoded, so quality is untouched.
What this removes: the embedded C2PA manifest — the signed record of which tool made the file and what was done to it — plus any XMP pointer to a copy of that manifest hosted online.
What it does not remove: invisible watermarks encoded into the pixels or audio themselves — Google SynthID, Adobe TrustMark, Meta Content Seal and similar. Those live in the media data rather than the header, so no metadata tool can touch them. Note that C2PA explicitly supports these as “soft bindings”: a watermark can carry an ID that lets a verifier fetch the original credentials from the cloud even after the embedded manifest is gone.
EXIF, GPS and other XMP fields are also left alone — this tool touches Content Credentials and nothing else. Stripping metadata does not make a file undetectable as AI-generated, and platforms such as YouTube and TikTok increasingly label content using their own classifiers regardless of what the file contains.
How it works
Surgery on the container, not a re-export.
Locate the manifest
We find exactly where the credentials live — an APP11 segment in a JPEG, a caBX chunk in a PNG, a top-level UUID box in an MP4.
Cut it out cleanly
Those bytes are dropped and the container is repaired — RIFF sizes corrected, and for video every chunk offset in the sample table rewritten so playback still works.
Verify and download
We re-read the file we just produced to confirm nothing remains, then hand it to you. The encoded media is byte-for-byte what it always was.
Why use this remover
Most guides tell you to re-export the file. That quietly costs you quality.
Zero quality loss
Screenshotting or re-saving through an editor recompresses everything. We only delete header bytes, so the decoded result is provably identical.
Video without ffmpeg
MP4 and MOV are handled in the browser by rewriting the sample tables. No upload, no server round trip, no waiting for a transcode.
Genuinely private
Files you want stripped are exactly the files you should not upload to a stranger's server. Nothing here leaves your machine.
Checks its own work
Every output is re-scanned before you download it, so you get a straight answer about whether the credentials are really gone.
Common use cases
Why people strip credentials from their own work.
Removing personal details
A manifest can name the account, the device and the software that produced a file. Before posting publicly, plenty of people would rather not publish their workflow along with the picture.
Used by photographers, freelancers, and privacy-minded posters.
White-label delivery
Agencies hand finished assets to clients under the client's name. Shipping files that still advertise the studio's internal tooling is rarely what was agreed.
Used by agencies, studios, and contract designers.
Cutting file size
Manifests carry embedded thumbnails and certificate chains, and can run to hundreds of kilobytes. On a large batch of images that adds up quickly.
Used by web developers, e-commerce teams, and CDN operators.
Perfect for
Who benefits from lossless credential removal.
Deliver a clean master without pushing it back through an editor and losing a generation of quality.
Wedding, product, and editorial shooters.
Strip a manifest from an MP4 in a second instead of waiting on a full remux.
Editors, motion designers, social producers.
Hand off assets that carry no trace of internal tooling or staff accounts.
Creative directors, producers, account managers.
Normalise media in a pipeline and see exactly which bytes were responsible.
Platform engineers, CMS maintainers.
Frequently asked questions
Does removing credentials reduce image or video quality?
No. We delete the metadata block and leave the encoded media untouched, so the file decodes to exactly the same pixels and frames. This is the main reason not to use the common advice of re-saving through an editor, which recompresses and does lose quality.
How is video handled without ffmpeg?
In an MP4 the credentials sit in a top-level UUID box, usually near the start. Deleting it shifts everything after it, which would break playback because the sample tables store absolute file offsets. We rewrite those offsets so the file stays valid — the same job a remux does, but only on the few kilobytes that matter.
Does this remove SynthID or other invisible watermarks?
No, and nothing that edits metadata can. SynthID and similar watermarks are encoded into the pixels or audio samples themselves and survive metadata removal entirely. This tool is explicit about that rather than implying a clean file is untraceable.
Will my EXIF and GPS data be removed too?
No. We only remove the C2PA manifest and any XMP pointer to a remote copy of it. Camera settings, timestamps and location tags are left exactly as they were. If you want those gone as well, use a dedicated EXIF stripper afterwards.
Is it legal to remove Content Credentials?
For your own files, in most places yes — it is your metadata. But stripping provenance to pass AI-generated media off as authentic can breach platform rules, advertising standards and, increasingly, disclosure law. Use it on your own work and disclose AI content where it is required.