Standard EXIF (Exchangeable Image File Format) data is a still-image metadata standard embedded primarily in JPEG files, with related chunks in PNG and container metadata in WebP, while video files such as MP4, MOV, and MKV store their descriptive information inside container-specific structures like ISOBMFF boxes, QuickTime atoms, or Matroska tags rather than EXIF segments. The browser-based EXIF Remover rebuilds a JPEG, PNG, or WebP from its decoded pixels entirely in your browser, discarding the source file's EXIF, GPS, lens, capture-time, and ancillary metadata in the process, and accepts compressed images up to 20 MB and decoded images up to 40 megapixels. Because video containers store metadata in a fundamentally different place than JPEG files, the EXIF Remover cannot open MP4, MOV, or MKV at all; those formats need a container-aware tool like FFmpeg, ExifTool, or your operating system's built-in properties panel. Treat the EXIF Remover as the cleanup step for any still image frames, thumbnails, or cover art you pulled from a video, and use a separate, video-aware workflow for the .mp4, .mov, or .mkv file itself.
Why Video Files Don't Use Standard EXIF the Same Way Images Do
EXIF is one specific metadata specification, defined by JEITA and the original camera-industry bodies, that was designed to attach camera, lens, capture-time, and GPS fields to a single still-image file. JPEG is the format where EXIF lives most visibly: the file begins with a JPEG marker that names an APP1 segment, and inside that segment is a small TIFF header followed by a tree of IFD entries, which is where you find Make, Model, DateTimeOriginal, LensModel, and GPSLatitude. PNG files do not use EXIF directly; instead they use named ancillary chunks such as tEXt, iTXt, and zTXt, plus optional embedded EXIF chunks when authored that way. WebP files use RIFF container metadata in their EXIF and XMP chunks.
MP4, MOV, and MKV files take a different approach. An MP4 file is structured as a series of ISOBMFF boxes (also called atoms), and the descriptive fields sit in a moov box, often inside a udta sub-box or a metadata handler mdat. A MOV file uses QuickTime atoms. An MKV file uses Matroska tags. None of these is EXIF in the strict sense, even though casual writers often call any video metadata "EXIF," which is why the phrase "remove EXIF data from video" appears so often in privacy guides. In practice, you are usually trying to remove a mix of QuickTime metadata, MPEG-4 user data, XMP packets, and sometimes a literal EXIF stream embedded inside the video track itself.
What the EXIF Remover Tool Actually Strips
The EXIF Remover is built for the still-image side of that problem. When you hand it a JPEG, PNG, or WebP file, the browser validates the MIME type, the compressed size (capped at 20 MB), and the decoded pixel count (capped at 40 megapixels to avoid running the tab out of memory). It then decodes the image, applying the source's display orientation tag so the pixels are rotated to look correct, draws those pixels onto a fresh canvas, and re-encodes the canvas in the same general format. Because the output is a new file rather than a copy of the original segments, none of the source's EXIF fields (Make, Model, DateTimeOriginal, LensModel, GPSLatitude, GPSLongitude, Software, Artist, comments, embedded thumbnails) make it into the result.
The same is true for the non-EXIF metadata that can ride along in still images. PNG tEXt, iTXt, and zTXt chunks from the source are not copied, and the WebP EXIF and XMP container chunks are not copied either. What is preserved is whatever shows up in the decoded pixels, which is the visual content of the image. The browser does not upload, store, or transmit the file at any point; decoding, drawing, and re-encoding all happen in the browser tab, and the resulting Blob is offered to you through a short-lived Object URL that is revoked when the job ends.
| Format handed to EXIF Remover | Source metadata the rebuild discards | What survives in the output |
|---|---|---|
| JPEG | EXIF, XMP, IPTC, ICC profile, comments, embedded thumbnail | Visible pixels re-encoded by the browser (lossy) |
| PNG | tEXt, iTXt, zTXt ancillary chunks, embedded EXIF | Visible pixels re-encoded losslessly by the browser |
| WebP | RIFF EXIF chunk, RIFF XMP chunk, ICC profile | Visible pixels re-encoded by the browser (lossy) |
Notice what is not in the "survives" column: there is no color profile and no provenance trail. The tool is designed for everyday privacy cleanup, not for archival masters, legal evidence, color-managed production assets, or authenticity records. Keep the original file separately if any of those properties matter to you.
Strip Metadata From the Video Container Itself
For the .mp4, .mov, or .mkv file itself, you need a tool that understands the container's metadata locations. The EXIF Remover does not open these formats; treating it as a video cleaner will leave you stuck on the file picker. Three reliable options cover most cases without sending the video to a remote service.
- Pick the tool that matches your comfort level: FFmpeg (command-line, container-aware, runs locally), ExifTool (command-line, broad format support), or your operating system's built-in properties panel (graphical, shallow coverage of visible tags).
- Run the cleanup. With FFmpeg: ffmpeg -i input.mp4 -map_metadata -1 -c copy output.mp4 drops global metadata, and adding -map_metadata:s:v -1 -map_metadata:s:a -1 also drops per-stream tags. With ExifTool: exiftool -all= -overwrite_original input.mp4; for Matroska files larger than the 2 GB default safety buffer, run exiftool -api LargeFileSupport=1 -all= input.mkv. On Windows: right-click the file, choose Properties, open the Details tab, and click Remove Properties and Personal Information. On macOS: open the file in QuickTime and edit visible tags via File > Show Movie Inspector, or use Finder's Get Info panel for the same subset.
- Verify the result with a video metadata inspector. ffprobe -show_format -show_streams output.mp4 is the standard way to confirm that tags, location atoms, and embedded EXIF streams are gone; running exiftool output.mp4 a second time is the equivalent check for ExifTool users, and re-opening the file's Properties or Get Info panel is the equivalent check on a desktop OS.
- Save a known-clean copy and re-verify before sharing. Editing the cleaned file in another application, exporting it through a chat app, or re-saving it from a preview window can attach fresh metadata on top, so the file is clean only at the moment of verification.
These four steps run end to end on your own machine. None of the tools named above sends the video to a remote server, so the privacy property that the EXIF Remover provides for images carries over to the video side through this workflow.
Clean Image Frames With EXIF Remover
Even when your real problem is a video file, there are usually still images in the mix: poster frames, cover art, embedded thumbnails, and the stills you extracted for social posts. That is where the EXIF Remover fits cleanly. To clean an image the tool can accept, choose a JPEG, PNG, or WebP file that is no larger than 20 MB on disk and decodes to no more than 40 megapixels. Wait while the browser decodes the pixels and draws them onto a fresh canvas; for a typical phone photo this takes only a moment, but large scans and high-resolution WebP files can take longer because the browser is rebuilding the file locally. Preview the result, then download the new file. The downloaded copy is the clean one; the original you selected from disk was never uploaded or sent anywhere.
If you want to read more about why a browser-based, no-upload workflow is the standard for everyday EXIF cleanup, see the guide to removing EXIF data from photos without uploading files.
Three caveats apply to every frame you clean this way. JPEG and WebP outputs are re-encoded by the browser and can show small visual differences or a different file size compared with the source; PNG outputs are encoded losslessly from the canvas pixels, so the pixels themselves match exactly. Color-profile information is not preserved, so do not use the cleaned copy as a color-managed deliverable. And stripping metadata does not anonymize what is visible: faces, signs, reflections, documents, and location clues can still identify a person or place even with a perfectly clean EXIF block.
What Survives Metadata Removal (and Why It Matters)
Removing EXIF and similar metadata segments is a privacy step, not an anonymity step. Once the metadata is gone, anything visible in the pixels remains visible: faces, license plates, street signs, business names, screen reflections, paper documents in the background, tattoos, and recognizable landmarks. Audio tracks in a video can carry their own identifying information, including voice, room reverberation, and background speech, that metadata removal does nothing to suppress.
There are also metadata fields the EXIF Remover and video strippers cannot recover because the originals were already lossy on capture. Color profiles are stripped from JPEG and WebP outputs during the rebuild, so a color-managed production pipeline will lose its profile chain. Original file timestamps at the filesystem level are not part of EXIF and survive independently of any metadata tool. If authenticity, chain of custody, or color accuracy matters, do not run your master file through a metadata-removal tool; work from a copy and keep the original separately.
Finally, remember that "clean now" is a snapshot, not a guarantee. Editing the cleaned file in another application, exporting it through a chat app, uploading it to a social platform, or re-saving it from a preview window can attach fresh metadata on top. For sharing workflows where you specifically want a known-clean state, the safest habit is to verify the file at the moment you hand it to someone else, then hand them the freshly verified copy rather than a copy that may have been touched by another tool in between.
Related reading: How to View EXIF Data on iPhone Without an App.