Logo

Remove Metadata From Video

Phone footage carries the coordinates, the device name and the exact second you pressed record. Most cleaners strip that by re-encoding the whole clip, which costs you quality and half an hour. We rebuild the container and copy the streams across untouched.

Choose a video to clean

MP4, MOV, MKV and WebM up to 300 MB. We show you what it carries first, then you decide.

How to remove metadata from video in two steps

Open the clip, look at what it carries, then press the button. We show you the tags before we touch anything, because deciding blind is not really deciding.

Nothing is uploaded. The file is read and rebuilt inside this browser tab, which matters here more than almost anywhere — the clips people clean are usually the ones filmed at home.

The honest limit is memory. Rebuilding a container holds the input and output at once, so we cap this at 300 MB rather than let a long job die near the end on an ordinary laptop.

Why a video metadata cleaner should never re-encode

Most tools take the easy route. They decode every frame, recompress it and hand back a new file, which does remove the tags because the new file was written from scratch.

It also costs you two things. Quality, because a second lossy compression is permanent and visible on detailed footage. And time, because re-encoding ten minutes of 4K can take longer than the clip runs.

We rewrite only the container. The compressed video and audio are copied across as they are, so the picture in the clean file is bit-identical to the picture in yours. A 200 MB clip finishes in seconds rather than minutes.

Timing survives the trip as well. Footage shot at a shifting rate keeps that same shifting rate afterwards, which a re-encode would quietly flatten — run a variable frame rate test before and after if you want to see that for yourself.

There is a real trade in this approach and we would rather name it. A straight remux cannot reach data buried inside the encoded stream itself, and a small number of exotic containers refuse a clean copy. We read the finished file back and tell you what survived rather than declaring success.

How to strip GPS from an MP4 before it becomes an address

Coordinates are the field that actually causes harm. A phone writes them into a location atom accurate to a few metres, which is enough to put a clip of your living room on a map at a house number.

The leak is mundane. You film something to sell, upload it to a marketplace, and the coordinates travel with the file. Nobody decided to publish an address.

Rebuilding the container takes the location atom with it, along with the device make, model and every timestamp. Which phones write coordinates in the first place is covered in whether videos store GPS, and you can see exactly what a given clip holds with our video metadata viewer.

Clearing the creation date from a video, and when not to

Timestamps go too, and that deserves a caveat rather than a sales line.

A container usually carries several dates: when the muxer wrote the file, when the tags were last touched, and on Apple devices a separate creation date with a real timezone offset. All of them disappear in the rebuild.

Most of the time that is exactly what you want. Sometimes it is not. Insurance claims, rental condition footage, workplace incidents and anything that might be disputed all benefit from an untouched original — keep it and clean a copy instead. A file that has obviously been rewritten invites a question you did not need, which we go through in whether video metadata can be faked. The timestamp fields themselves are explained in working out when a video was recorded.

Which clips to clean before uploading anywhere

Not every video needs this, and treating it as universal is how the habit collapses.

Clean anything going to a marketplace listing, a rental advert, a public forum or a dating profile. Those are direct uploads seen by strangers, and several platforms store what you gave them without processing it. Email attachments too — mail clients pass a file through byte for byte.

You can usually skip it for the large social platforms, which re-encode on upload and drop most tags as a side effect. That is a side effect rather than a promise, and it happens after they have your original.

And check the picture itself, which is the half no tool addresses. A street sign, a house number through a window, a delivery label, a screen reflected in a monitor.

What stays behind after the tags are gone

Three things survive, on purpose or by nature.

  • The name of the remuxer. Matroska makes a writing-application element mandatory, so a valid MKV cannot come back with that field empty. The cleaned file names the tool that rebuilt it and nothing else — not you, not your device, not where you were. We flag it in the result rather than pretending the file is perfectly bare.
  • The encoded streams. That is the point — we do not touch them — but it means encoder quirks and noise patterns stay put. Those are a weak fingerprint, not a name, and no metadata tool removes them.
  • The picture and the sound. Faces, signs, voices, a doorbell in the background.
  • Everything outside the file. The account you upload from, the copy you already sent, the message it was attached to.

This is why we will not say a cleaned clip is anonymous. It is a file that no longer announces where it was filmed, which is worth doing and is not a disguise.

Clean the copy, then check it

The habit is small. Remove metadata from video that is heading somewhere public, keep your original untouched, and verify the result the first few times instead of trusting a success message.

We read the cleaned file back automatically and report what is left, and you can confirm it independently with the codec and bitrate checker, which will also show that the streams came through unchanged. If the file needs to be smaller for an upload limit, compress the video first and clean afterwards — compressors stamp their own name into whatever they produce. For photographs rather than clips, strip a photo instead does the same job on JPEG, PNG and WebP.

Frequently Asked Questions

Does stripping metadata reduce the quality of my video?

+
Not here, because we never decode the picture. The video and audio streams are copied across bit for bit and only the container around them is rewritten. Tools that re-encode do lose quality, and a clip run through one twice is visibly softer. That is the whole reason we took the slower route.

My clip still shows a location after cleaning. What happened?

+
A few containers store location in a place a straight remux carries over, and we tell you rather than assuming success. We read the cleaned file back and report what survived. If coordinates persist, converting to a different container first and then cleaning usually clears them.

Will I lose my subtitle or second audio track?

+
No. We pass every stream through explicitly rather than accepting ffmpeg's default of one stream per type, which silently drops extra audio languages and all your subtitles. Chapter markers are the deliberate exception, because chapter titles are metadata and often name people or places.

Does this remove the timestamp a court or insurer might want?

+
Yes, and that cuts both ways. If a clip may ever support a claim, keep the original untouched and clean a copy. A file that has clearly been rewritten invites a question you did not need. We say more about that in our piece on what video metadata proves.

Is the video anonymous once the metadata is gone?

+
No, and anyone promising that is overselling it. The picture still shows what it shows, and the encoded stream keeps its own fingerprint — encoder quirks, frame structure, noise patterns. Removing container tags closes one door, not the building.

Why is there a 300 MB limit when the viewer has none?

+
Reading only needs small chunks, while rebuilding holds the input and the output in browser memory at once. Past a few hundred megabytes a tab starts failing on ordinary laptops. We would rather state a ceiling than let you watch a long job crash near the end.

Should I compress before or after cleaning?

+
Compress first, then clean. Compression rewrites the container and encoders routinely stamp their own name, version and a fresh timestamp into the result. Cleaning last means those additions go too, and the strip costs no quality either way.

Does uploading to YouTube or Instagram do this for me?

+
They re-encode and drop most container metadata as a side effect, which is not the same as a promise. It also happens after they have received the original file. If the coordinates matter, remove them before the upload rather than relying on the upload to remove them.

The cleaned file still names a writing application. Why can you not remove that?

+
Because the format will not allow an empty one. Matroska makes muxing-application and writing-application mandatory elements, so a valid MKV always carries the name of whatever built it. What is left names our remuxer, not you — no device, no location, no timestamp. We flag it in the result instead of claiming a perfectly bare file.

Can the metadata be recovered from the cleaned file?

+
Not from that file. The tags are absent rather than hidden, so there is nothing to undo. Your original stays untouched on your disk, which is deliberate — we never modify the file you selected. Delete it yourself once you have checked the copy.

Related Tools You Might Like

Advertisement