Inspect and strip video metadata and GPS location
Lossless in-browser privacy sanitization. View camera make, model, creation dates, and GPS coordinates, and wipe identifying metadata without touching audio or video frames.
Select an MP4 or MOV video
Inspect hidden GPS coordinates, device identifiers, and creation timestamps. Strip them losslessly without re-encoding video frames.
Related Video Tools
About this video metadata scrubber
Select an MP4 or MOV video file to inspect hidden GPS coordinates, device hardware identifiers, software versions, and recording timestamps. Click Strip Metadata to rewrite the container without user data atoms, producing a clean video file with zero privacy leaks and zero quality loss.
Modern smartphones automatically embed precise GPS latitude, longitude, and altitude coordinates into video recordings, alongside camera serial numbers, device model names, and exact timestamps. Sharing a phone video of your home or family online exposes your private physical location. This tool inspects ISO Base Media metadata atoms (udta, meta, ©xyz) and strips them losslessly without re-encoding video frames.
Step by step
- 1Select video fileChoose an MP4 or MOV video file. The metadata inspector scans the container header for user data atoms and timestamps.
- 2Review privacy findingsInspect identified GPS location coordinates, device make and model strings, software version tags, and creation dates.
- 3Strip tracking metadataClick Strip Metadata. The container surgery engine rebuilds the MP4 container, omitting all identifying user data boxes.
- 4Download sanitized videoSave the cleaned video file. The video and audio tracks are preserved byte-for-byte with zero quality loss and no location traces.
The privacy danger of smartphone GPS video tags
When you record a video on an iPhone or Android phone, the operating system writes an ISO 6709 coordinate string into the user data atom (udta) under the ©xyz tag (for example, +37.7749-122.4194+015.000/). Anyone who downloads the raw video can extract your exact street address, apartment location, and elevation. Conventional advice suggests uploading the video to a web stripper — but uploading a private video to an unknown server defeats the entire purpose of privacy. Our tool runs 100% locally in your browser tab, ensuring your video never leaves your device.
What metadata gets inspected and removed
The scrubber removes five distinct categories of identifying data: (1) GPS location coordinates (udta/©xyz), (2) Hardware device manufacturer and model strings (©mak, ©mod), (3) Operating system and software version numbers (©swr), (4) Original creation and modification timestamps in the movie header (mvhd) and track header (tkhd), and (5) User annotations, titles, artists, and comments (©nam, ©art, ©cmt).
Lossless stripping without video re-compression
Standard video editing software strips metadata by re-encoding the entire video file, which takes minutes and degrades visual crispness. Our tool performs pure container surgery: it reads the compressed H.264/AAC sample packets and writes a fresh container structure containing only the necessary media streams and timing tables. The export finishes in milliseconds with zero loss in visual quality.
Zero upload security guarantee
Every response from this site is served with a Content Security Policy whose connect-src directive is set to none. That is not a promise in marketing copy; it is an instruction to your browser, and the browser is the one enforcing it. While this page is open it cannot open a connection to anywhere — not to this site, not to anyone else — so there is no path by which your document could be uploaded, not by a bug, not by a future change, not by a script that should not be here. e2e/egress-proof.spec.ts asserts the served header and then tries to send data out by every route a page has and requires each attempt to be refused, and it runs on every build.
The second half of the guarantee is that the code has nowhere to send anything from. lib/tools/local-source-policy.test.ts reads every source file under lib/tools, workers, components and app on every test run and fails the build if any of them contains fetch, XMLHttpRequest, WebSocket, EventSource, sendBeacon or a peer connection, or even a remote address written down in a comment. A tool here cannot acquire an upload by accident, because the file that would have to contain one cannot be committed.
Client-side processing limits
Computations run directly on your own device using WebAssembly, Web Workers, and modern browser APIs including Web Crypto and TextDecoder. There are no server queues, no background telemetry, and no temporary cloud files created. Large operations remain responsive by offloading heavy parsing and conversion tasks to dedicated worker threads, ensuring the browser UI never freezes during intensive document and data processing tasks.
Questions people ask
- Does stripping metadata affect video or audio quality?
- No. Only container header metadata and user data atoms are removed. The video and audio streams are copied byte-for-byte with zero compression or quality loss.
- What GPS format do smartphones use in videos?
- Smartphones record coordinates according to ISO 6709 standards in the udta/©xyz atom, including latitude, longitude, and elevation coordinates.
- Are creation and modification dates reset?
- Yes. Timestamps in the mvhd and tkhd atoms are normalized to zero to prevent temporal tracking and metadata forensics.
- What video file formats are supported?
- MP4 and MOV video containers are supported with instant zero-copy in-browser metadata stripping.
- Is my video uploaded to your servers to inspect metadata?
- Never. All metadata parsing and stripping executes entirely within your browser tab under connect-src none security policies.