Platform · pre-upload
Remove the AI Info label from Instagram photos
Almost every AI Info label on Instagram comes from C2PA or XMP inside the file. It does not judge pixel by pixel whether you drew it with AI — which is exactly why real photographs get flagged too.
On-device/No upload/Quality unchanged/No sign-up
Drop images here, or click to choose
JPG, PNG, WebP, AVIF, HEIC · 15 MB each · up to 30 per batch
You can also paste a screenshot with ⌘V / Ctrl+V
Cleaning options
Want to look first? Themetadata inspectorlists every field in the file, so you can see exactly what is there before deciding what to strip.
C2PA is read first, XMP second; feed, story and Reels cover are three separate files
The same image in different slots — feed, story, cover — may be three separate files, and each one has to be handled.
What the platform reads
| Entry point | Notes |
|---|---|
| Feed image | C2PA and XMP are read at upload; a hit attaches AI Info |
| Story | Uploaded separately from the feed; the same photo needs its own clean |
| Reels cover | The custom cover is a separate JPG and is often missed |
| Platform compression | Pixels are re-encoded, but metadata removal is not guaranteed |
Pre-upload checklist
- 11. Clean the images you are about to post, so you have a clean copy
- 22. Clean the story version separately — most people only do the feed
- 33. The Reels custom cover is a JPG; run it through the image cleaner, not just the video
- 44. Run the inspector over the exact file you are going to upload
- 55. Upload that copy, with no editor or forwarding in between
Common traps
- Opening the file in an in-app editor and saving writes the metadata back
- Editing in the gallery and re-exporting can bring the original EXIF along
- With several images in one post, each has to be cleaned — not just the first
If it is still flagged after cleaning
That means the trigger was never in the file metadata. It could be an invisible pixel-level watermark, the platform's own visual classifier, or history held on the platform side. None of those live in the metadata layer, and cleaning again will not change them.
The full boundaries are in thedisclaimer; if you just want to confirm the file really is clean, use thewatermark check.
Common questions
Will it still be flagged afterwards?
If the trigger was C2PA or XMP, normally not. If the platform uses a pixel watermark or a visual classifier, it still may — that is outside the metadata layer.
Do story and feed need two separate cleans?
If it is the same file, one is enough. But many people use a separate export for stories, and that one has to be handled on its own.
Why is the Reels cover always missed?
Because the cover is a separate JPG chosen at upload time; it is not the video file. A clean video does not mean a clean cover.
Does adding a filter in the app write metadata back?
Possibly. Any edit made inside the platform can trigger a re-encode and a write. Finish all editing before uploading.