To remove an AI label from a photo in the sense most creators mean, you strip file-level provenance that Instagram, TikTok, Facebook, and similar apps read when you upload — mainly C2PA Content Credentials and XMP/IPTC fields that say the image was made or heavily edited with AI. That is not the same as removing EXIF or GPS alone, and it is not the same as removing pixel watermarks such as SynthID. This page is the workflow: inspect, clean, upload, and know the limits.
What “AI label” usually means
Platforms show wording like AI Info, Made with AI, or contains AI-generated media when their ingest pipeline finds machine-readable markers in the bytes you send. For Meta properties, public documentation points at C2PA and IPTC digital source type in XMP. TikTok and others follow similar patterns for still images and cover frames.
The label on the live post is a platform decision. It is not stored as a normal EXIF tag you can edit in Photos.app. If the trigger was metadata in your upload file, cleaning that file before upload is the reliable fix. If the trigger was a pixel watermark or a visual classifier, metadata tools will not help.
Step 1: Inspect the file (checker)
Upload the image to the free AI metadata checker or EXIF reader, or run ExifTool locally:
exiftool -G1 -a -C2PA:all -XMP:DigitalSourceType -XMP:CreatorTool -IPTC:DigitalSourceType photo.jpgLook for:
| Signal | Typical meaning |
|---|---|
| C2PA manifest / JUMBF (JPEG APP11) | Signed Content Credentials — common on DALL-E, Firefly, ChatGPT exports |
XMP-iptcExt:DigitalSourceType | IPTC vocabulary for algorithmic or composite media |
| XMP from generators | Midjourney parameters, workflow blocks in PNG text chunks |
Deeper background: what C2PA Content Credentials are and Digital Source Type.
Step 2: Strip C2PA, XMP, and related blocks
For a full wipe of provenance plus privacy fields (GPS, camera serial, timestamps), use the remove AI label tool or metadata remover. It runs ExifTool’s strip on JPEG, PNG, TIFF, and WebP server-side and returns a download. Processing does not recompress pixels the way browser canvas exporters do; see how to remove metadata from photos for orientation and ICC side effects after a full strip.
Command-line equivalent:
exiftool -all= -overwrite_original photo.jpgThat removes C2PA when ExifTool can clear those segments, along with EXIF, IPTC, and XMP. Keep a private master copy if you still need camera settings for your archive.
If you only need to drop AI markers but keep copyright and camera EXIF, selective editing is possible with ExifTool or the EXIF editor on JPEG/TIFF — but most upload-prep workflows use a full strip on a export copy.
Step 3: Upload the cleaned file
Post the downloaded file, not the original. Re-exporting from an app can re-embed C2PA (for example Lightroom or Photoshop with Content Credentials enabled).
Platform-specific detail:
- Instagram posts, Stories, Reels covers: Instagram AI generated label
- TikTok covers and carousel stills: TikTok AI generated label
Which AI tools leave metadata labels?
These tools often embed C2PA, XMP, or PNG workflow metadata (not an exhaustive list):
| Tool | What tends to remain in the file |
|---|---|
| DALL-E / ChatGPT images | C2PA manifest |
| Adobe Firefly / Photoshop Generative Fill | C2PA + IPTC attribution |
| Midjourney | XMP generation parameters |
| Stable Diffusion / ComfyUI | PNG text chunks, workflow JSON |
| Lightroom AI Denoise / Remove | C2PA partial-edit manifests on some exports |
Stripping metadata addresses file-level triggers. It does not change whether the image looks AI-generated to a human or to a separate ML model.
False positives on real photos
A wedding photo after Generative Fill, a product shot with an AI sky, or a Reel cover edited in CapCut can pick up C2PA from the editing app even when the scene is real. Platforms may still show AI Info because provenance says AI was involved, not because every pixel is synthetic. Removing C2PA and digital source type before upload is the same practical step as for wholly generated images — on files you own and where your jurisdiction and platform terms allow it.
What this does not remove
- SynthID and similar pixel watermarks — embedded in image data, not metadata blocks
- Visual classifiers that ignore file headers
- Legal disclosure obligations — EU AI Act and platform policies may require labeling regardless of metadata; this is file hygiene, not legal advice