Hide recording context
Creation dates, phone models, and coordinates can reveal when, where, and how a clip was captured.
Video privacy without giant uploads
Inspect MP4, MOV, and WebM container metadata locally before you publish or send a clip.
Files never leave your device — processed 100% in your browser. Free, no sign-up.
They stay on this device. Nothing is uploaded.
To remove metadata from video means deleting descriptive fields stored in the media container rather than altering the picture or sound tracks. MP4 and MOV files are organized as boxes. Boxes such as moov and udta can contain creation times, device models, editing application names, copyright text, and location strings. WebM uses a different container but can also hold title, writing application, and date information.
This page first reads the container structure in your browser so the video itself is not sent anywhere. For compatible MP4 and MOV files, it can rebuild metadata-bearing boxes while copying media payload bytes. Large or unusual files are handled conservatively: if a safe local rewrite cannot be confirmed, the tool provides the detected fields and a clear explanation instead of offering a misleading download. This approach avoids ffmpeg.wasm and its heavy initial download.
Video support focuses on descriptive container boxes and never transcodes the audio or video streams.
Creation dates, phone models, and coordinates can reveal when, where, and how a clip was captured.
Encoder and application strings can disclose production tools or an internal workflow.
A cleaned container shares the clip without unnecessary author, title, or location tags.
Video files are large and sensitive; local inspection avoids transferring them to a third party.
Select a video up to 50 MB so the browser can inspect its container safely.
See creation times, location strings, device labels, and software fields that were found.
For supported MP4/MOV layouts, download a locally rebuilt container; otherwise follow the specific guidance shown.
Yes. Inspection and compatible container cleanup are free with no account. The 50 MB browser limit is intentional: it avoids memory crashes and does not turn the page into a server upload service for larger videos.
No. The browser reads container bytes locally, and the site has no upload API. This matters for video because clips often contain faces, voices, homes, or confidential work that should not be copied to an unknown server.
The inspector recognizes MP4 and MOV box structures and provides limited WebM identification. Safe stripping is offered only when the parser can rebuild supported metadata boxes without touching media tracks. Other formats receive an explicit unsupported message.
It can detect common QuickTime location strings and metadata boxes in MOV files. Removal depends on the exact container layout produced by the phone or editor. Always review the cleaned file and recheck it before publishing sensitive footage.
No transcoding is performed. When cleanup is available, compressed audio and video data are copied as existing bytes while descriptive boxes are removed. If the file would require transcoding or unsafe offset changes, the browser refuses to create a cleaned copy.
The interface accepts multiple files, but browser memory and the 50 MB per-file limit still apply. Each file is checked independently. Compatible results are bundled locally; unsupported containers remain listed with a specific reason.
Last updated: November 3, 2026