May 27, 2026

How to remove metadata from MP4, Reels, and TikToks in your browser

Short answer: Video files (MP4, MOV, WebM) carry their metadata in container atoms separate from the audio and video streams. A browser-based remux (using ffmpeg.wasm) can drop every metadata atom in one pass without re-encoding a single frame. Same quality, same audio sync, no AI tags, no GPS, no watermark metadata. AI Info Remover does this in your browser — files never leave your device.

What’s actually inside an MP4

A modern MP4 is a tree of “boxes” (also called atoms). The pixels and audio samples live in mdat. Everything else — including all the metadata a platform might read — lives in surrounding atoms:

moov / udta — user data: camera model, encoder, sometimes GPS in a ©xyz atom for files straight off a phone.
moov / meta — structured metadata: iTunes-style tags, copyright, creator.
uuid boxes — where C2PA content credentials live in Reels, AI-generated videos, and anything edited in Adobe’s suite. This is what triggers Meta’s “Made with AI” label on Instagram reposts.
XMP packets — Adobe edit history (which clips were trimmed, which filters applied, sometimes the original filename).
Chapter metadata — in vlogs and longer-form content.
Track-level metadata in moov / trak / mdia / hdlr — encoder brand, language, handler name (often leaks the recording app).

You can see all of this with mediainfo or exiftool on any random reel you’ve downloaded. It’s a lot.

Why re-encoding is the wrong tool

The instinct from the image world is: re-encode the file, the metadata disappears. For video, that’s catastrophic. Re-encoding a typical reel means decoding every frame, redrawing, re-encoding with H.264 or AV1, and re-muxing audio. That takes minutes per video, burns CPU and battery, and degrades quality every pass.

The right tool for metadata stripping is remuxing — rewriting the container while keeping the audio and video streams bit-for-bit identical. ffmpeg calls it “copy mode.” The one-liner is:

ffmpeg -i reel.mp4 -c copy -map_metadata -1 -map_chapters -1 reel_clean.mp4

-c copy says “don’t re-encode, just copy streams.” -map_metadata -1 says “don’t carry any metadata over to the output.” -map_chapters -1 strips chapters too. The result is a new MP4 with the same pixels, same audio, same encoding — just no metadata atoms. Takes seconds.

Doing it in the browser, with no server

You don’t need to install ffmpeg. The full ffmpeg runtime has been compiled to WebAssembly — ffmpeg.wasm — and runs entirely in your browser tab. AI Info Remover loads a small (32 MB, one-time) engine from this same domain (not a CDN) on the first video drop, then runs that same -c copy -map_metadata -1 command against the file in your browser’s memory.

The privacy claim isn’t marketing. Open dev tools, switch to the Network tab, drop a reel into the cleaner. You’ll see the engine download (the first time), and then zero network requests when the file is actually processed. Disconnect from the internet after the page loads and the cleaner still works.

Step-by-step

Open aiinforemover.com on any modern browser. Works on desktop and phone.
Drop your MP4, MOV, or WebM into the dropzone.
First time only: the video engine downloads (a one-time ~30 MB, cached in your browser after).
The cleaner remuxes the file in seconds. You see a progress bar.
Click Download. The output has every metadata atom stripped.
Verify with exiftool reel_clean.mp4 — output should show only container basics (codec, duration, dimensions). No GPS, no udta, no uuid C2PA, no edit history.

What it removes vs. what it doesn’t

Removed: C2PA “Made with AI” manifest, GPS coordinates, device model, encoder identifier, edit history, chapters, all custom user atoms, platform watermarks living in udta/meta.

Preserved: Every pixel, every audio sample, audio/video sync, framerate, duration, codec.

Not removed (be honest):

Pixel-level watermarks like Google’s SynthID-for-video, or TikTok’s baked-in branding pixels. Remuxing copies pixels unchanged, so anything in the pixels survives. You’d need full re-encoding to weaken these — and even that doesn’t guarantee removal.
Visible watermarks. The TikTok logo in the corner stays exactly where it is.
Perceptual content hashing. Instagram and TikTok also fingerprint videos by content; remuxing changes the file hash but not the perceptual hash. Same caveat applies as it does with images.

When to use this

Reposting a reel you legitimately want to share without leaking the original creator’s C2PA credentials or your own location.
Sharing AI-generated video where the C2PA tag would trigger a “Made with AI” label on Meta platforms.
Cleaning phone-recorded video before backing it up to cloud or sharing in a group chat — strips GPS and device info.
Removing edit history that Adobe or other editors might have written into XMP packets.