Removes capture coordinates, device model, software name, comments and dates in the headers. The video stream itself is copied byte for byte — no re-encoding, so quality and picture size stay exactly as they were.
Your files never leave your device. Everything runs inside your browser: no file is uploaded to a server.
Drop clips hereor click to choose
MP4 · MOV · M4V
Metadata in MP4 and MOV sits in service boxes next to the video stream. Those boxes go, the stream stays untouched.
| What | Where it lives | Why it matters |
|---|---|---|
| Capture coordinates | ©xyz in udta, key com.apple.quicktime.location.ISO6709 | The filming spot, accurate to a building |
| Device model | ©mod, com.apple.quicktime.model | Links your clips to each other |
| Manufacturer | ©mak, com.apple.quicktime.make | Apple, Samsung, GoPro and the rest |
| Software | ©too, ©swr | What recorded and what edited the clip |
| Comments and title | ©cmt, ©nam, ©des | Sometimes carry platform identifiers |
| Capture dates | mvhd, tkhd, mdhd headers | They survive tag cleaning and are easy to forget |
| XMP and C2PA | uuid boxes | Editing layer and provenance manifest |
An MP4 stores absolute offsets of the video chunks: a table says “the data for this frame starts at byte N”. Cutting a metadata block out physically would shift everything after it and the player would read garbage. So the decision depends on the layout: when the service block sits after the video data it is cut out and the file shrinks; when it sits before the data it is turned into an empty free box with its contents zeroed, and the size is preserved. Either way no metadata is left in the file.
No. There is no re-encoding at all: the compressed video stream is copied byte for byte and only the container's service wrapping changes. Resolution, bitrate, audio and duration stay exactly the same. Easy to check — open the original and the result side by side.
Yes, and it is not alone. iPhone puts the filming spot into the com.apple.quicktime.location.ISO6709 key inside the meta box, while cameras and Android devices more often use the ©xyz atom in udta. It looks like +55.755800+037.617300+120.000/ — latitude, longitude and altitude. Proyavka parses both variants and shows the coordinates before removing them.
Platforms append their own identifiers to the service block: TikTok, for example, writes a string like vid:v10044g50000… along with an aigc_info marker telling whether the video was generated by a neural network. All of that sits in the same udta and goes with everything else.