Guide · TagWipe

Removing Instagram's "Made with AI" Label: What Reddit Recommends, Fact-Checked

Didactic Initiatives · Updated August 4, 2026 · 8 min read

Search this problem and you'll land in a Reddit thread — r/photography, r/Instagram, r/photoshop or r/AdobeLightroom, where the same argument replays every few weeks. A photographer posts a shot they took themselves, Instagram brands it AI, and forty replies offer forty theories.

Some of that advice is exactly right. The single most upvoted reply pattern is flatly wrong, and following it wastes your time. Here's the mechanism, then a fact-check of what Reddit tells you to do.

What Instagram is actually reading

The crucial thing the good Reddit answers get right: Instagram is not looking at your picture. It's reading a text field inside your file. When you upload, Meta inspects the embedded metadata for provenance tags — machine-readable notes that editing software leaves behind describing how the image was made. Three formats matter:

• C2PA / Content Credentials — a cryptographically signed manifest listing the tools and edits applied. Full explainer here.
• IPTC DigitalSourceType — one field naming the image's source. Two values trigger labels: trainedAlgorithmicMedia (fully AI-generated) and compositeWithTrainedAlgorithmicMedia (real photo, AI-assisted edit).
• XMP generator tags — vendor-specific fields naming the software, and on some PNGs the entire generation prompt.

If any are present, the label is applied automatically. There's no "but it's mostly real" threshold — a composite tag is a composite tag. That's why the r/photography complaint is legitimate rather than paranoid: a one-second AI denoise pass and a fully synthetic render produce the same outcome.

The edits that quietly add the tag

The r/iphone version of this story is the most common of all: you removed one stray tourist from a beach photo with Clean Up. That's it. The file now carries an AI provenance credit for the rest of its life — through iMessage, through AirDrop, and into your upload.

Fact-checking the Reddit answers

❌ "Instagram strips EXIF anyway, so it doesn't matter"

The most confidently upvoted wrong answer in every one of these threads. Instagram does strip most metadata from the copy served to other users — which is why people believe this — but it reads your file on ingest first, and that read is what applies the label. The strip happens after the decision. Verifiable in one test: upload a Firefly export, watch it get labeled, then download it back and find the metadata gone.

❌ "Just crop it or re-save it in Photos"

Apple's editing pipeline preserves file metadata by design, and Adobe's re-attaches credentials on export. Neither is a cleaning step.

❌ "Convert it to PNG" (or to another format)

Format conversion carries metadata across more often than not — and PNG has its own text chunks that happily hold provenance data. Sometimes it works, which is exactly what makes it dangerous advice: it fails silently.

⚠️ "Screenshot it"

This genuinely works. A screenshot is a brand-new file with none of the original's metadata. The cost is real: your screen's resolution rather than the photo's, the display colour profile instead of the embedded one, and letterboxing if the aspect ratios don't match. Fine for a Story; not fine for a portfolio piece — which is precisely the objection the r/photography replies raise.

✅ "Turn off Content Credentials in Adobe's preferences"

The best preventive advice on Reddit, and correct. Adobe apps expose a Content Credentials setting you can disable so new exports don't get a manifest attached. Two limits: it does nothing for files you already exported, and it doesn't stop the IPTC DigitalSourceType field that generative features write.

✅ "Use exiftool"

exiftool -all= photo.jpg is the reference answer and it's correct. It's also a command line on a computer, which is why the thread usually stalls there for anyone shooting and posting from a phone. Worth knowing it doesn't specifically target Apple's Clean Up credit field, so verify rather than assume.

✅ "Strip the metadata, keep the pixels"

The right instinct, and the one that needs an on-device tool to be practical. TagWipe does this on iPhone:

1. Open TagWipe and select the photo — or the whole batch you're about to post.
2. Read the scan. It itemises what it found: C2PA manifests, DigitalSourceType, generator tags, the Clean Up credit, plus GPS and device EXIF.
3. Clean, choosing save a copy or replace the original.
4. Upload the cleaned file as normal.

Choose "save a copy" the first time. Replacing the original is irreversible — the metadata is gone and the untouched file is deleted. A copy costs you one duplicate in your camera roll.

You can't remove the label after posting

Reddit gets to the right answer here eventually, usually after several people have hunted through the post menu. The label is decided at ingest. Editing the caption, the alt text, or anything in the post's menu does not re-run the check. The sequence is delete, clean, re-upload — so do the cleaning first if you'd rather not spend the engagement twice.

The honest limits

Cleaning metadata removes the automatic, metadata-driven label. It does not do two other things, and the more careful Reddit commenters are right to keep pointing this out:

• Invisible pixel watermarks stay. Google's SynthID and similar schemes encode a signal into the image data itself. It isn't metadata, so no metadata tool can remove it — TagWipe included.
• Platform-side classifiers still run. A platform can guess from the image alone. Removing tags removes the certainty, not the possibility.

For a real photo you edited lightly, that's the whole problem solved: the label came from a tag, and the tag is gone. For a fully synthetic image, treat metadata cleaning as file hygiene rather than a disguise, and disclose AI use where it matters.