DropMetadata

Video

Remove metadata from MP4 and MOV video.

Video files carry the same location and device data as photos, tucked into the container around the frames. Removing it does not require re-encoding a single frame — and re-encoding is what most advice gets wrong.

Strip metadata from a video

Drop a photo or video

or browse your files

.JPG · .PNG · .MP4 · .MOV · any size

Video metadata lives in the container, not the frames

An MP4 or MOV file is a tree of boxes (also called atoms). The compressed video and audio sit in one box; everything describing the recording sits in others. That separation is what makes lossless cleaning possible.

The boxes that carry identifying information are:

The QuickTime location tag
An ISO 6709 coordinate string. This is what an iPhone writes when you record with location services enabled.
The 3GPP loci box
Used by Android devices and by ffmpeg. It holds coordinates plus an optional place name.
ilst and keys
Apple’s metadata pair, carrying device model, software version, comments and custom tags.
uuid boxes
Containers for XMP editing history and C2PA content credentials, which record the editing chain and AI-generation provenance.
mvhd, tkhd and mdhd headers
Header boxes holding creation and modification timestamps for the movie and each individual track.

Why re-encoding is the wrong tool

The usual advice is to run the file through a converter, which does remove metadata — as a side effect of decoding every frame and compressing it again.

That costs you real quality. Every re-encode of lossy video discards detail permanently, and the generational loss compounds if the file is ever processed again. It is also slow, turning an instant operation into minutes of CPU work, and it changes the file size, the bitrate and often the audio.

None of that is necessary. The frames were never the problem.

How lossless container editing works

There is a complication: an MP4 file contains a sample table with absolute byte offsets pointing at every frame. Delete a box from the middle of the file and every one of those offsets shifts, and the file no longer plays.

The fix is not to delete. A metadata box is relabelled as “free” — the standard padding type that players skip — and its contents are overwritten with zeroes. The box still occupies exactly the same number of bytes, so every offset in the sample table remains correct, and the data is genuinely gone rather than merely unreferenced.

The result is a file whose frames are bit-identical to the original, whose size is unchanged, and which plays in exactly the same players. Cleaning completes in the time it takes to read the file.

What stays, and what that means

Everything needed for playback is preserved: codec configuration, resolution, frame rate, duration, the audio track and the sample tables themselves. A cleaned video is indistinguishable from the original to a player.

What is removed is the layer describing the recording rather than the recording itself — where it was shot, on what, with which software, and when.

Common questions

Does this re-encode or compress the video?

No. Frames are copied byte for byte and never decoded. Only the metadata boxes in the container are rewritten, so quality is mathematically identical to the original.

Will the file size change?

No. Metadata boxes are zeroed and relabelled as padding rather than removed, which keeps the sample table offsets valid. The output is the same size as the input.

Do videos really contain GPS coordinates?

Yes. Phones write the recording location into the container the same way they write it into photos. iPhones use a QuickTime location tag; Android devices generally use a 3GPP loci box. Both are handled.

Which video formats are supported?

MP4 and MOV, which share the same ISO base media container. MKV, AVI and WebM use different container formats and are not supported yet.

Is a large video uploaded somewhere to be processed?

No, and that matters more for video than for photos — a large file would otherwise mean a long upload. Processing happens in your browser, so a multi-gigabyte file never crosses the network.

What are C2PA content credentials?

A signed manifest recording how a file was created and edited, including whether AI tools were involved. It is stored in a uuid box and is removed when you select the AI provenance category.

Related