Remove AI metadata before uploading to YouTube
YouTube asks creators to declare altered or synthetic content and reads provenance from uploads. Cleaning handles the accidental case; the declaration is still yours to make.
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.
What YouTube reads in your file
These are container fields, not an analysis of the picture. Remove them and the metadata-driven check has nothing to find.
- C2PA credentials in uuid boxes
- XMP packets in uuid boxes
- moov/udta tags written by editors and cameras
- moov/meta handler metadata
Editors leave more behind in video than in stills
A rendered MP4 usually carries an editor signature, project traces and often an XMP packet describing the timeline. When any AI-assisted step is in that timeline — an upscale, a background removal, a generative fill on a frame — that description can end up as provenance attached to the whole export.
We neutralise those boxes without touching the video and audio streams, so nothing is re-encoded and quality is bit-identical.
Disclosure is a separate obligation
If your video is genuinely synthetic or materially altered, declare it in YouTube's own upload flow. This tool is for the file, not for the disclosure, and it does not pretend to substitute for it.
Cleaning a file for YouTube
Four steps, under a minute, on the exact asset you are about to publish.
- 1
Render your final MP4 or MOV.
- 2
Clean it with the video cleaner.
- 3
Upload the cleaned file and complete YouTube's disclosure questions honestly.
YouTube questions
Will cleaning a video reduce its quality?
No. We overwrite metadata boxes in place with padding boxes and never touch the media streams, so the video is bit-identical to your render.
Why is the cleaned file the same size?
Because we pad rather than delete. Video files address their own media by absolute byte offset, so removing bytes ahead of the media would break playback. Padding is offset-safe and the metadata bytes are genuinely zeroed.
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.