Runs entirely in your browser

Remove AI metadata before you post

Instagram, TikTok, Pinterest and LinkedIn read the bytes you upload, not the picture. Strip the C2PA credentials, XMP and EXIF that trigger an AI label - without re-encoding, without uploading, without an account.

JPG, PNG, WebP, AVIF, HEICMP4 and MOVBatch of 50Free

Nothing is uploaded

Every byte is parsed in this tab. There is no server to send a file to, so there is nothing to trust us with.

Lossless by construction

JPEG, PNG, WebP and MP4 are rewritten at the container level. The image and video data is copied byte for byte.

You see what was found

Every file is inspected before and after, and each finding is named with its size. No silent operations.

No account, no limit

Fifty files at a time, any size your browser can hold, free. No sign-up wall in front of the tool.

What is actually in the file

Four layers sit between your picture and the label

A tool that treats all of them as metadata is selling false confidence. Here is exactly which two we address, and which two nobody can address from a browser.

01Out of scope

Visible pixels

What a person sees. Crops, filters, burned-in logos and subtitles. Changing them proves nothing about the hidden layers.

02Out of scope

Pixel watermarks

SynthID and similar systems embed a signal into the image data itself, designed to survive editing. No browser tool removes these, including this one.

03We remove this

C2PA content credentials

A cryptographically signed record of origin and edit history. This is the strongest single trigger for an automatic label.

04We remove this

EXIF, XMP, IPTC and text

Ordinary file metadata: camera fields, GPS, editor names, prompts, seeds, workflow dumps and the IPTC field that marks an image as algorithmic.

Removed

Every marker a platform reads at upload

Each of these is detected, named and reported with its size before it is taken out -- and each can be switched off if you want to keep it.

C2PA content credentials

Signed provenance describing the tool, the account and the edit history. The single strongest label trigger.

XMP packet

Adobe's metadata format. Carries generator names, model versions, prompts and edit descriptions.

EXIF metadata

Camera and software fields. Also where AI editors leave their signature, alongside your GPS coordinates.

IPTC attribution

Includes digitalSourceType, the field that says an image came from a trained algorithm.

Text chunks

PNG tEXt/iTXt and JPEG comments. Where Stable Diffusion and ComfyUI store prompts, seeds and whole workflows.

Container metadata

MP4 udta and meta boxes: editor tags, device info, project traces.

How it works

Inspect, clean, verify, publish

Under a minute per file, and the order matters -- work from the asset the platform will actually receive.

01

Drop the final export

The exact file you are about to publish -- not a screenshot, not a copy that came back through a messaging app. Those are different files with different metadata.

02

See what is inside it

Every file is parsed on drop. Findings appear as chips naming the signal, its size and, where the payload says so, which tool wrote it.

03

Clean without re-encoding

The container is rewritten and the image or video data is copied untouched. Colour profiles stay, pixels stay, metadata goes.

04

Download and publish

The cleaned copy is a new file; your original is never modified. Post that copy, and keep the original for your own records.

Platforms

One cleaned file works everywhere

Meta, TikTok, Pinterest and LinkedIn read the same class of markers. Each guide covers what that specific platform does with them.

AI exports

What each generator leaves in your file

Different tools write different things. Knowing which one produced the export tells you what to look for.

FAQ

Frequently asked questions

What does this tool actually remove?

C2PA content credentials, XMP packets, EXIF blocks, IPTC attribution fields, PNG text chunks and JPEG comments, plus the metadata boxes inside MP4 and MOV containers. Each finding is named with its size before it is removed.

Are my files uploaded anywhere?

No. Every parser runs in your browser and there is no upload endpoint in this application. You can disconnect from the network and the tool still works, which is the simplest way to verify the claim.

Does cleaning reduce image or video quality?

For JPEG, PNG, WebP and MP4, no. Those are rewritten at the container level and the compressed data is copied byte for byte, so the result is bit-identical after decoding. HEIC and AVIF are the exception: their metadata cannot be separated from the image structure, so they are decoded and re-encoded, and the tool tells you when that happens.

Why is my cleaned video the same size as the original?

Because video is padded rather than trimmed. MP4 files address their own media by absolute byte offset, so deleting bytes ahead of the media would break playback. We overwrite each metadata box with a standard padding box of the same size: the bytes are zeroed, the offsets never move, and every player ignores padding.

Can it remove SynthID or invisible watermarks?

No. SynthID and similar systems are embedded in the pixels and are designed to survive editing. This tool only touches file metadata. Any tool claiming otherwise from a browser is overstating what it does.

Can I remove a label from something I already posted?

No. The platform stores its own copy of your upload and no local tool can reach it. Clean the original export and publish again if it matters.

Why does a real photo get an AI label?

Because credentials record that an AI tool touched the file, not how much of the image it changed. One generative fill, one AI denoise or one AI upscale is enough to attach provenance describing that edit.

What is the camera EXIF option for?

After cleaning, a JPEG has no camera block at all, which is itself unusual. The option writes a plausible one back. It is cosmetic - it changes metadata, never pixels, and it is off by default.

Should I always remove content credentials?

Not necessarily. Editorial, compliance and client workflows often need provenance kept, and disclosure can be the right call. The point of this tool is that you decide deliberately instead of discovering what was in the file after the post is live.

Check a file before you post it

The inspector is read-only and takes a second. If it comes back clear and a label still appears, the cause is not in the metadata -- and you will know that instead of guessing.