New Local video clean-up

AI Video Metadata Cleaner

Remove AI metadata labels, C2PA provenance, XMP, location, and supported hidden records from MP4 and MOV videos—without uploading or re-encoding them.

⌂ Stays on this device◇ No quality change↯ Up to 250 MB
Video wash booth
Ready
10 / 10 free uses today No server uploadSee plans →

An honest cleaner

Hidden records can leave. Visible content stays.

AI label scrubber

Removes recognized C2PA or JUMBF provenance, XMP, generator, prompt, model, location, editor, creator, and supported container metadata.

What it cannot promise

Visible “AI content” labels, watermarks baked into frames, invisible pixel or audio signals, and records already held by social platforms may remain.

What it preserves

The encoded video and audio streams are not recompressed. Resolution, frame rate, sound, and visible pixels remain exactly as stored in the source streams.

Before you publish

How video metadata cleaning actually works

Video files are containers. The picture and sound streams sit alongside structural information and optional records added by phones, cameras, editing applications, export tools, and provenance systems. Some records can identify the software used to produce a clip, the time it was created, its author, or a geographic location. This cleaner inspects the MP4 or QuickTime container locally and prepares a separate sharing copy in which supported optional metadata containers are neutralized.

No upload and no quality-changing export

The file is read inside your browser. It is not posted to an aimetadataremover.co processing endpoint. The cleaner preserves byte-for-byte encoded media payloads rather than decoding every frame and producing another generation. That makes compatible files much faster to process and avoids the quality loss normally associated with video transcoding. The cleaned file keeps its original extension and should be reviewed in a normal media player before the source is archived or deleted.

A social label is not always file metadata

A label such as “AI content” displayed beside a social post can come from several places. It might be visible text already burned into the frames, a declaration supplied during upload, provenance information embedded in the file, or a decision made by the platform using information in its own systems. This feature removes recognized AI labels only when they are embedded file metadata. Visible labels and watermarks remain, and cleaning cannot remove a platform-side record or guarantee that an automated classifier will treat the clip differently. The tool is for privacy-oriented file sanitation, not policy evasion.

Why the format list starts with MP4 and MOV

MP4, MOV, and M4V share the ISO base media container family, allowing optional boxes to be handled without rewriting the encoded picture and sound. WebM uses a different container structure and is not accepted in this first release. Rejecting an unsupported or damaged file is safer than producing a download that only appears clean. The tool also checks the file signature instead of trusting a renamed extension and limits files to 250 MB to reduce the risk of exhausting browser memory.

Use a careful sharing workflow

Keep the original in private storage, clean a duplicate, download the result, and play it from beginning to end. Confirm the soundtrack, duration, orientation, captions, and visual quality. Check the filename and the actual frames for names, faces, addresses, notifications, license plates, or other visible information. Metadata cleaning reduces hidden baggage, but it does not replace a visual and editorial privacy review. If authenticity records matter to your recipient, do not remove them; share the original provenance-bearing file instead.

Important: removing provenance data may make authenticity harder to verify. Only clean files you own or are authorized to prepare, and never represent a cleaned file as having credentials it no longer carries.