Your editor signed the file
Upscalers, background tools, and generative fill write Content Credentials on export. The picture looks the same as before. The record inside it does not.
Instagram can show AI Info when an upload carries SynthID, C2PA, or AI metadata. Drop your image or video below, clean the hidden signals, then post a file that looks like yours.
Drop an image to inspect its Content Credentials locally.
The label describes the file, not your intent. Meta says AI info can show up when its systems detect industry-standard indicators, or when a creator discloses AI-generated content. A photo you shot yourself can still carry those indicators after one export.
Upscalers, background tools, and generative fill write Content Credentials on export. The picture looks the same as before. The record inside it does not.
Anything made with Gemini, Veo, Imagen, or a comparable model leaves a SynthID watermark in the pixels plus a provenance block in the metadata.
Instagram checks the file the moment you publish, before a single follower sees it. That timing is why the tag turns up straight away instead of hours later.
signal groups checked
typical pass on a still
files sent to a server
file ready for reposting
Machine-readable, every one of them. None change how the image looks, which is why an ordinary photo can still trip the AI tag.
Google weaves an invisible watermark through the image data and across every video frame. Cropping or re-saving will not wash it out, and a detector still reads it.
A signed provenance record, plus the XMP block that carries it. Editing and AI tools write both on export, and the XMP fields often outlive a re-save that clears everything else.
Model names, prompt notes, and software fields sit in the EXIF header. Small, easy to miss, and enough on their own to earn a post an AI info tag.
Stable Diffusion and ComfyUI write the whole workflow into a PNG's text chunks: prompt, model, sampler, seed. It is plain text sitting inside the file, and a scanner reads it without effort.
Meta describes its labelling approach in the AI image labelling announcement and the later AI info update. C2PA documents provenance metadata in the Content Credentials specification.
The same file signals feed Pinterest's GenAI labels, TikTok's AI-generated media disclosure, and Threads, so a file you clean once travels cleanly everywhere you post it.
Ordinary edits cause most of it, not generated art. These are the ones we see behind a mislabelled post:
Generative Fill in Photoshop. One fill on one corner signs the whole export.
AI sky replacement on product shots. Common in ecommerce batches, and it marks every file in the run.
Lightroom AI Denoise. A raw workflow staple. It writes an AI edit marker into the output.
CapCut exports used as Reel covers. The cover frame carries its own metadata, separate from the video.
Background removers and upscalers. Both are AI now, and both sign on the way out.
Gemini, Imagen, and Veo edits. These add a SynthID watermark on top of the provenance record.
Instagram has no setting that switches the AI info label off while the file still carries the markers. The label is produced from file contents at upload time, so there is nothing in the app to flip. That is the whole answer, and it is the part most guides get wrong.
If you've read that you can tap the three dots, choose Edit, and turn an AI label off, that screen doesn't exist. Some of those posts were wrong when they were published. The rest describe an interface that changed. As of 2026, none of them work.
What you can do inside the app is report a label you believe is wrong on some posts. That is a review request, not a switch. Everything else happens in the file before you upload it.
Read the file first. The checker above lists what is actually present, so you learn whether the tag came from a watermark, a credential, an XMP field, or your own disclosure. Sometimes the answer is that nothing needs removing, and that is a useful answer too.
Inspect, decide, then clean. In that order.
Start from the file you will actually publish, not a screenshot or a compressed re-save. We scan it, take the supported signals off, and hand back the same resolution you gave us. Nothing leaves the browser.
SynthID watermark remover for Gemini-style AI stills and clips.
AI metadata remover for generator notes, model markers, and provenance fields.
C2PA remover for files that ship with Content Credentials.
| Signal | Before | After |
|---|---|---|
| SynthID | Detected | Clean |
| AI metadata | Present | Removed |
| AI info risk | High | Lower |
Order matters more than anything else here. Every re-export can write a fresh credential, so clean the file last.
Finish the crop, the colour, the text overlay. Then export once and treat that copy as the version you will upload.
Drop the export into the tool above. SynthID, Content Credentials, and supported AI metadata all go in one pass.
Upload what we give back, then archive the original. If you ever need the provenance record, it is still sitting in that file.
Photoshop and Lightroom both let you turn Content Credentials off in export settings, before the file is ever generated. In Photoshop it's the Content Credentials panel; in Lightroom it's a checkbox in the export dialog. Switch it off once and your exports stop carrying the record.
That's the cleanest route, because nothing has to be taken off afterwards. Our tool covers the other case: the file already exists, the credential is already inside it, and going back to re-export from the original isn't realistic.
Here's the part most pages skip. There's no way to relabel a post that's already up. Instagram doesn't reprocess published media, and no file tool can reach into a live post and rewrite what sits on Meta's servers. Anyone promising otherwise is guessing.
So if you want to remove AI info from an Instagram post after posting, the route is manual: delete the post, clean the source file, repost it. You'll lose the comments and the likes, which is a real cost, so weigh that against how much the tag bothers you. Meta also lets you flag a label you believe is wrong on some posts. Try that first.
One case where you shouldn't do any of this: if you generated the media, or altered it in a way Instagram's policy asks you to disclose, leave the label where it is.
We list what's actually in your file: watermark, credentials, metadata fields. No guessing about which one caused the tag.
The supported signals come off in a single pass, on stills and across every frame of a clip, at the resolution you brought.
We re-scan the output so you can see it came back clean, then you download it. Nothing was uploaded at any point.
People posting their own work, where a file-level flag would describe the picture wrongly.
Retouched a portrait, upscaled a frame, and now the carousel carries an AI tag it doesn't deserve.
Product shots that go through a mockup pipeline, where the export tool signs every file on the way out.
Real photographs with AI edit markers left behind by denoise or sky-replacement steps.
Client deliverables that need to look like the client's work, not like a tool chain's output.
Meta uses AI info language for signals that can come from creator disclosure or from industry provenance records attached to media. That is context about a file, not a verdict on a photograph.
We are built for accidental file-level noise on content you own. When a post is generated, or materially altered in a way Instagram asks viewers to understand, keep the disclosure. That is not a loophole we are interested in closing.
Because something in the file said so. Meta reads industry-standard indicators such as a SynthID watermark, C2PA Content Credentials, and generator metadata, and it also shows the label when a creator discloses AI-generated content. A photo you shot yourself can pick those indicators up from an editor's export.
It means Instagram found a signal saying AI was involved somewhere in the file's history, or you told it so yourself. It is context attached to the media, not a claim that every pixel was generated.
You can clean the file signals that trigger it before you upload. On a post that is already live, no. Instagram does not reprocess published media, so the only route left is delete, clean the source, repost.
Open this page in Safari on the phone, tap the upload area, and pick the photo or clip from your library. Everything runs on the device. Save the cleaned file back to Photos, then post that version.
A highlight reuses a story you already published, so the label travels with it. Clean the source file, post a fresh story, and add that one to the highlight.
Because the label describes the file, not the camera. An edit made after the shoot, a denoise pass, a sky swap, an upscale, can write a credential or an XMP field into the export. Instagram reads that marker and adds the tag. The photograph is yours; the marker came from the software.
No, and we will not pretend otherwise. We handle the file-level signals we support. Instagram can also label media from your own disclosure, from visual classifiers, or from signals we do not cover.
Yes. The same pass clears the SynthID watermark, the C2PA Content Credentials block, and the AI metadata fields we support, so the file goes out without the provenance record attached.
Open the remover page that matches the platform and format you plan to publish.
Clean the image or video first, then publish the copy that has nothing hidden inside it.
Clean an image now