Video Sanitizer
Strip metadata from MP4, MOV, MKV and WebM videos without re-encoding them. The picture and sound are copied byte for byte into a fresh container, and a before-and-after list shows exactly which tags were removed.
How to Use
- Drop a video (MP4, MOV, MKV, WebM, AVI, M4V or 3GP). The first time, the page loads a video engine of about 32 MB.
- Read the list of metadata found in the file: dates, location, device, title, chapters and any data tracks.
- Click Sanitize. The streams are copied into a new container that carries none of those tags.
- Check the before-and-after table, then download the clean copy.
Worked Example
A 30-second phone clip. A 1080p clip recorded at 24 Mbit/s weighs 24 × 30 ÷ 8 = 90 MB. Stream copy writes the same compressed packets into a new container, so the clean copy is only a few kilobytes smaller: the tags, not the picture, were what was removed. While it runs, the original and the copy are both held in memory, roughly 2 × 90 = 180 MB.
What the dates mean. MP4 and MOV store a creation time as the number of seconds since 1 January 1904 (UTC). A clip filmed at 14:30:00 UTC on 15 June 2024 is stored as 1,718,461,800 + 2,082,844,800 = 3,801,306,600. The sanitizer leaves no such field behind.
The common mistake: assuming a re-encode is needed. Tags live in the container, not in the picture, so no re-encode is required to remove them. Re-encoding only becomes necessary for what is inside the pictures themselves, such as a burnt-in date or a voice.
Show Work
Formulas
Where Video Metadata Hides
MP4 and MOV files are built from nested boxes (QuickTime called them atoms): a media-data box holds the compressed pictures and sound, and a movie box describes them. Titles, creation dates, device names and locations sit in the movie box and in optional metadata boxes, which is why they can be dropped without touching a single frame. Matroska (MKV) and WebM keep the same sort of information in tags, chapters and attachments.
Action cameras go further and write whole extra tracks of GPS and motion samples next to the picture. These are real streams in the file, so they have to be left out of the copy rather than just blanked, and that is why the tool maps only the video, audio and subtitle streams.
About the Video Sanitizer
Phones and cameras write more than pictures into a video file. An MP4 from a phone usually records when it was filmed, where (as coordinates), and the device model; action cameras add whole tracks of GPS and motion data; editing software adds its own name, titles and chapter markers. This tool removes all of that while leaving the video itself untouched.
A WebAssembly build of ffmpeg first reads the file and lists every tag it finds. Sanitizing then runs the equivalent of ffmpeg -i input -map 0:v? -map 0:a? -map 0:s? -map_metadata -1 -map_chapters -1 -c copy -fflags +bitexact output: the video, audio and subtitle streams are copied packet for packet into a new container, while metadata, chapters, data tracks and attachments are left behind. The clean copy is then read again, so the before-and-after table shows what is really in the output.
Everything runs on your device; the video is not uploaded. Related tools: Video Inspector, Video Converter, and Metadata Scrubber.
Frequently Asked Questions
Does this lower the video quality?
No. The video and audio are stream-copied, not re-encoded, so every compressed frame and audio packet in the clean copy is identical to the original. Only the container around them is rebuilt.
What exactly gets removed?
Every container and per-stream tag ffmpeg can read (creation time, location or GPS coordinates, camera make and model, title, comment, encoder and handler names), chapter markers, data tracks such as GoPro GPS and gyro telemetry, and attachments. Boxes that ffmpeg does not understand, such as XMP packets and maker notes, are not written into the new container at all.
What is kept, and which format is the clean copy?
The video, audio and subtitle streams, and by default each stream's language label (eng, fra and so on) so players still pick the right track. Untick the option to drop those too. The container also needs a few structural fields (brand, generic handler names), which are listed as kept. The clean copy uses the same container as the original where possible (MP4 stays MP4, MOV stays MOV, MKV stays MKV, WebM stays WebM); if a file cannot be rewritten in its own container, the tool saves an MKV instead and says so.
Is anything left that could identify me?
Possibly, if it is part of the picture or sound itself: a timestamp burnt into the image, a voice, or a short encoder note stored inside the H.264 stream by the camera. Removing those needs a re-encode, which the Video Converter can do.
How large a file can it handle, and is it uploaded?
The engine holds the original and the clean copy in browser memory at the same time, so the practical limit is about 1.5 GB, less on a phone. Copying is fast because nothing is re-encoded. Nothing is uploaded: reading and rewriting happen on your device in a WebAssembly build of ffmpeg.
How do I use the Video Sanitizer?
Simply type your numbers and read the result, which refreshes the instant you change something. There is nothing to submit and nothing to wait for.
Does it cost anything or need an account?
No. The tool is completely free, there is no account to create, and it keeps working offline after the page first loads.
Is anything I type uploaded?
No. The tool works entirely on your device, so the values you enter never leave your browser.
Common Use Cases
Before posting
Remove the location and recording date a phone stores in every clip.
Action-camera footage
Drop the GPS and gyro telemetry track a GoPro writes alongside the video.
Sharing drafts
Clear titles, comments and editing-software tags before sending a file to someone else.
Check what a clip reveals
Read the before list for a 90 MB phone video to see its creation time, device and location before you decide to share it.
Last updated: