How to Remove Metadata from Video Files
Use local FFmpeg processing to remux supported containers without global metadata, then check what technical stream data remains.
What “video metadata” actually includes
A video file is usually a container holding one or more encoded video, audio, subtitle, image, or data streams. The container can carry global tags such as title, author, comment, creation time, location, device, or software. Individual streams also have technical descriptors such as codec, resolution, frame rate, sample rate, language, duration, and bitrate.
The technical descriptors are normally required to play or identify the streams. Removing them all would not produce a useful file. The privacy review should focus on descriptive tags and identifiers rather than expecting the codec or resolution to disappear.
How to remove supported video container metadata
- Keep an original. Remuxing creates a different container file even when encoded media streams are copied unchanged.
- Select the video locally. Open the video tool and choose a common supported container such as MP4, MOV, MKV, WebM, AVI, WMV, or MPEG.
- Wait for the media engine. FFmpeg JavaScript and WebAssembly resources are downloaded when the audio/video path is first needed; the selected video itself is not sent to that resource host.
- Review detected tags. Look for creation time, location, make/model, software, title, author, comment, copyright, and other descriptive fields.
- Create the cleaned copy. metapeel invokes FFmpeg with stream mapping, disabled global metadata copying, and stream copy.
- Play and inspect the result. Verify both media compatibility and the tag fields that matter to you.
The exact FFmpeg cleaning boundary
The active command follows the same concepts documented in the FFmpeg command reference: map the input streams, disable automatic global metadata copying with -map_metadata -1, and copy encoded streams with -c copy.
What this cleaning path targets
- • Global container tags that the output muxer would otherwise copy, including common title, author, comment, date, location, and software fields when represented there.
- • A rewritten container produced locally in the browser without transcoding the mapped audio and video streams.
What still needs separate review
- • Codec, resolution, frame rate, duration, bitrate, channel layout, and other technical information required to describe the streams.
- • Every possible per-stream tag, attachment, subtitle, thumbnail, data stream, proprietary box, or device-specific payload.
- • People, voices, landmarks, screens, plates, documents, or location clues visible or audible in the media.
- • Filename, file-system timestamps, platform records, or metadata added later by the upload destination.
An output muxer may also write a neutral format or encoder tag. That is different from retaining the original author, device, GPS, or creation-time value, but it should still appear during verification.
Does remuxing change video quality?
With stream copy, FFmpeg copies the encoded packets rather than decoding and compressing the picture and sound again. That avoids transcoding loss. The container itself is rebuilt, so byte-for-byte file identity, signatures, chapter behavior, attachments, unusual stream layouts, and player compatibility are not guaranteed to remain unchanged.
Container support is also codec-dependent. A filename extension accepted by the picker does not guarantee that every unusual codec or malformed file can be remuxed back into that container. The FFmpeg formats documentation is the source of truth for demuxer and muxer behavior; the browser build can still impose memory and compatibility limits.
What stays local, and why large videos take longer
The file is written into the browser-hosted FFmpeg virtual file system and processed on the user's device. metapeel does not upload its contents for server-side conversion. FFmpeg code and its WebAssembly core are downloaded on demand, which is a resource request—not a file upload.
Browser processing needs memory for the input, virtual file, and output. Large or complex videos can exhaust memory on a phone or low-memory computer. Close unnecessary tabs, keep the original file, and test with a short non-sensitive sample if you are unsure whether a container/codec combination will work.
How to verify the cleaned video
- Play the entire cleaned copy, checking video, audio, subtitles, orientation, chapters, and seek behavior that matter to you.
- Load the output into metapeel again and compare the descriptive fields with the original.
- For an independent inspection, run
ffprobe -show_format -show_streams cleaned.mp4. The ffprobe documentation explains how format and stream information is reported. - Expect codec and other technical stream descriptors to remain. Investigate original GPS, make/model, author, comment, creation-time, or software values if they still appear.
Audio uses the same local remuxing engine but different tagging conventions. See the audio metadata guide, or return to the cross-format metadata map for the wider picture.
Sources and primary references
These links point to format specifications, official documentation, or the implementation library used by metapeel.
- ffmpeg Documentation
FFmpeg Project
Primary documentation for stream mapping, the -map_metadata option, and stream copy used by metapeel.
- FFmpeg Formats Documentation
FFmpeg Project
Documents the demuxers, muxers, and format-level behavior that determine whether a particular container can be read and rewritten.
- ffprobe Documentation
FFmpeg Project
Official reference for independently examining format, stream, and tag information in a cleaned media file.
- QuickTime File Format Specification
Apple Developer Documentation Archive
Background on the atom-based container model behind MOV and closely related MP4 metadata structures.
Written and maintained by
metapeel Editorial TeamWe review every capability statement against the current code path, distinguish metadata cleaning from hidden-content sanitization, and link the primary references used.
Read our editorial methodPrivate by design
Inspect the file before you share it
File contents stay on your device. metapeel shows the fields it can detect and creates a cleaned copy using the supported path for that format.
Open the video metadata remover