Clean a video without re-encoding it
AI video tools and editors write provenance straight into the container. We neutralise those boxes in place and leave the streams untouched, so the clip you upload is the clip you rendered - to the byte.
Nothing is uploaded
Every byte is parsed in this tab. There is no server to send a file to, so there is nothing to trust us with.
Lossless by construction
JPEG, PNG, WebP and MP4 are rewritten at the container level. The image and video data is copied byte for byte.
You see what was found
Every file is inspected before and after, and each finding is named with its size. No silent operations.
No account, no limit
Fifty files at a time, any size your browser can hold, free. No sign-up wall in front of the tool.
Padding, not deletion
This is the part every other browser tool gets wrong, and getting it wrong corrupts video that people may not have a backup of.
The offset problem
Each track carries a table of absolute file offsets pointing into the media. Cut a 40 KB XMP box out from in front of that media and every offset in the table is now wrong by 40 KB.
What that looks like
The file still opens. It plays garbage, or silence, or nothing at all - and it does so only on some files, which is worse than failing outright.
The fix
Rewrite each metadata box as a free box of the same size and zero its payload. The spec defines free as skippable padding, so nothing moves and nothing can break.
Video questions
Does cleaning re-encode my video?
No. The video and audio streams are never touched. Only the metadata boxes are modified, so the output is bit-identical to your render where it matters.
Why is the output exactly the same size as the input?
Because the metadata is overwritten in place rather than cut out. An MP4 addresses its own media with absolute byte offsets, so removing bytes ahead of the media would shift every offset and break playback. We replace each metadata box with a standard padding box of identical size: the bytes are zeroed, the offsets never move, and every player skips padding.
Which boxes are neutralised?
Top-level uuid boxes carrying XMP or C2PA manifests, the top-level meta box, and moov/udta, moov/meta and moov/uuid. Everything else - ftyp, mdat, mvhd, every trak - is left exactly as it was.
How large a file can I clean?
As large as your browser can hold in memory. There is no server limit because there is no server; the practical ceiling is your device, and a few gigabytes is realistic on a desktop.
Does it work on WebM or MKV?
Not yet. Those use the Matroska container rather than the ISO base media format, which needs a different parser. MP4, MOV and M4V cover the exports from every major editor and AI video tool.
One cleaned file works everywhere
Meta, TikTok, Pinterest and LinkedIn read the same class of markers. Each guide covers what that specific platform does with them.
Check a file before you post it
The inspector is read-only and takes a second. If it comes back clear and a label still appears, the cause is not in the metadata -- and you will know that instead of guessing.