Remove Metadata From a Screen Recording — Device and OS Tags in the Capture

A screen recording is not a camera clip. It often lacks GPS and still carries software, OS, and creation-time atoms from Xbox Game Bar, QuickTime, ReplayKit, or an Android recorder. MetadataWipe does not parse MP4. Clean stills and posters here; strip the movie in a local editor.

Ready to clean a photo? MetadataWipe processes JPEG and PNG files locally — no account, and the file stays on this device.

Open MetadataWipe tool

This site already has generic video metadata pages. Those mix camera-shot clips (drones, phones, GPS tracks) with ‘video’ as a word. A screen recording is a different capture: the framebuffer, not a lens. iOS ReplayKit, macOS Screenshot toolbar / QuickTime, Windows Xbox Game Bar and Snipping Tool video, Android screen recorders, and OBS all write containers (usually MP4 or MOV) with software and timing metadata. They rarely write a latitude for ‘where the laptop sat’ the way Camera does for a backyard vlog — unless a tool explicitly geostamps. The leak is often the encoder string, the OS build, the capture clock, and everything visible in the pixels: Slack names, a password manager, a URL bar.

Generic movie-file help is remove metadata from video. Another video-strip walkthrough is strip metadata from video online. This page is screen-capture-specific: what tags to expect, what stays in the picture, and which files this JPEG/PNG tool can actually open.

What screen-recording metadata tends to be

Software and encoder: the atom that says which app captured the session. That can fingerprint a corporate image (‘Game Bar on a work Windows build’) or a macOS version. Creation time: when you hit record, which can contradict a caption that said ‘old footage.’ Duration and resolution are not secrets; they are still identifying in a set of clips from the same machine.

Usually not: Camera GPS, lens model, f-stop. If you also recorded webcam picture-in-picture, that overlay may be pixels from a camera that had its own tags on a separate file. The muxed MP4’s header is still a screen-capture story plus whatever the muxer copied. Inspect the file you will send; do not assume ‘screen record means no location’ if you imported a geotagged webcam MOV into the same timeline.

Pixels vs tags: a notification with a two-factor code is in the picture. No EXIF strip removes it. Pause, cover stills in an image editor or HideShot, or crop the timeline. MetadataWipe will not black-box a video frame inside an MP4.

What this tool opens

JPEG and PNG. That means: custom thumbnails, end cards, a PNG you exported from the timeline, a screenshot of the player. It does not mean the .mp4. Dragging the movie here will fail. That is the same split as the generic video pages, restated because screen-record searchers expect a ‘clean my Game Bar file’ button.

How to handle a screen recording honestly

  1. In the editor or OS: export the MP4 with metadata minimized if the software offers it. QuickTime, Premiere, and many ‘share’ dialogs have a location or properties checkbox — use it. This page cannot rewrite the movie.
  2. Cover secrets in the picture (names, tokens, URLs) in the editor before export, or export a still, cover the still, and do not ship the unmarked movie.
  3. Wipe stills in the MetadataWipe panel: poster frames, YouTube thumbnails, Discord preview PNGs.
  4. Do not send the project plus the wiped PNG if the project still has the unmarked capture.

For container-level video discussion see remove metadata from video and strip metadata from video online. Use those when the file is camera video. Use this page when the source was the screen.

Scenarios

A bug-report Game Bar clip that includes Outlook in the taskbar. The pixels are the leak. The header may still name Game Bar and a capture time. Cover or crop the taskbar in an editor; wipe a PNG thumbnail if you attach one; do not expect this tab to ingest the MP4.

An iPad ReplayKit session of a lecture with a student named in a banner. Banner is pixels. ReplayKit tags are software/time. Wipe stills here; strip or re-export the movie locally.

A QuickTime screen record of a map. The map locates you in the picture. GPS in the header is less likely than with iPhone Camera video — still inspect. Wipe the thumbnail JPEG you will post.

OBS to YouTube, plus a camera photo as the custom thumbnail. The thumbnail is a camera JPEG with GPS. That is the file this tool is for. The screen-record MP4 is the editor’s job.

Mistakes

Dropping the MP4 here and assuming a silent wipe. Unsupported.

Assuming screen record = no metadata of any kind. Encoder and time are still there. Inspect with a desktop tool if the movie must travel.

Wiping a thumbnail and shipping the unmarked MOV to the client ‘for quality.’ The MOV is the product.

Confusing this with camera-video GPS pages. Different capture. Same JPEG/PNG tool for stills.

Related guides

See also:

Frequently asked questions

Can I drop an MP4 screen recording onto MetadataWipe?

No. The homepage tool accepts JPEG and PNG. A screen recording is a video container. Export a frame or thumbnail as JPEG/PNG to wipe stills here. Strip container tags in the editor or OS tool you already use for the movie file.

Is screen-recording metadata the same as phone-camera video?

Usually not. Camera video often has GPS and camera Make/Model. Screen capture more often has encoder names, OS version, capture software (‘QuickTime Player’, ‘Xbox Game Bar’, ReplayKit), and timestamps. Window titles and notifications are often in the pixels, not the header — cover those in an editor or on stills.

Does a YouTube re-encode wipe my Game Bar tags?

Platforms re-encode and may drop some tags. Do not rely on that for the master you keep or send to an editor. Strip at export. Wipe custom thumbnails as JPEGs — they are separate files.

Does MetadataWipe send the screen recording to a server?

It never receives the MP4. JPEG/PNG you open stay on this device.

Remove EXIF data, GPS location, and common photo metadata in your browser.

Try MetadataWipe free