Generator · pre-upload
Cleaning container metadata from Veo video
A video's provenance lives at the container layer: udta, meta and possibly a uuid. Removing them needs no re-encoding, but a pixel watermark stays exactly where it was.
On-device/No upload/Quality unchanged/No sign-up
Drop a file here, or click to choose
MP4 / MOV only · 25 MB per file · up to 5 per batch
You can also paste a screenshot with ⌘V / Ctrl+V
Cleaning options
Want to look first? Themetadata inspectorlists every field in the file, so you can see exactly what is there before deciding what to strip.
Generator strings at the container layer; a pixel watermark cannot be removed
Different export paths can write different things. The reliable approach is to inspect one sample before batch processing.
Where it writes
| Location | Notes |
|---|---|
| MP4 container | Generator and editor strings in udta / meta |
| uuid | Possible C2PA or vendor identifier |
| Pixels | SynthID-style watermark, not removable |
Pre-upload checklist
- 11. Clean the container metadata
- 22. Handle the cover JPG separately
- 33. Accept that a pixel watermark remains
Common traps
- Cleaning the video but not the cover
- Believing nothing AI-related is left in the file
If it is still flagged after cleaning
That means the trigger was never in the file metadata. It could be an invisible pixel-level watermark, the platform's own visual classifier, or history held on the platform side. None of those live in the metadata layer, and cleaning again will not change them.
The full boundaries are in thedisclaimer; if you just want to confirm the file really is clean, use thewatermark check.
Common questions
Will it re-encode?
No. Only the container boxes are rewritten.
Why is there still an AI trace?
A pixel-level watermark is not in the container layer; no container cleaning affects it.
What if the file is over 25 MB?
Rewrite the container with ffmpeg: ffmpeg -i in.mp4 -map_metadata -1 -c copy out.mp4