Why a real photo gets an AI tag
Platforms read provenance data that editors attach to the file. Why real photos get an “AI info” label covers the details; the usual triggers are:
- A C2PA manifest recording a generative step such as Generative Fill, AI erase or AI expand.
- An IPTC or XMP DigitalSourceType value saying the image was composited with AI.
- Content Credentials that an editing app adds by default on export.
How to post with no AI tag
It takes under a minute and nothing leaves your device:
- Drop the edited photo into the box at the top of this page.
- Read the verdict and the fields behind it — the report names the exact C2PA action or IPTC value.
- Press “Wash all images” and save the clean copy.
- Upload the clean copy, not the original export.
Stop the tag at the source
If you edit often, turn off Content Credentials in Photoshop and Lightroom so they are not written in the first place. Which platforms label AI images lists what Meta, TikTok, YouTube and others read.
What “no AI tag” can and cannot promise
Removing the metadata removes the file-based reason for the tag, which is the cause on most edited photos. It cannot remove pixel watermarks such as SynthID, and a platform may still label a post from its own detection or ask you to self-disclose. This page is meant for genuine photos with minor edits: if an image is AI-generated and could mislead people, disclose it.
What is removed and what stays
JPEG / JPGMarker segments
Washed out
- APP1 (EXIF
- XMP)
- APP11 (C2PA/JUMBF)
- APP13 (IPTC)
- COM
- MPF
- JFIF/JFXX thumbnail
Left in place
- SOF
- DQT/DHT
- SOS → EOI
- APP0
- APP2 ICC
- APP14
- Orientation
PNGChunks
Washed out
- tEXt
- zTXt
- iTXt (prompt
- workflow
- XMP)
- eXIf
- caBX (C2PA)
- tIME
- dSIG
Left in place
- IHDR
- PLTE
- IDAT
- tRNS
- gAMA
- cHRM
- sRGB
- iCCP
- acTL/fcTL/fdAT
- Orientation
HEIC / HEIFISOBMFF boxes
Washed out
- uuid (C2PA
- XMP)
- Exif / XMP items
- moov udta + timestamps
Left in place
- ftyp
- mdat (HEVC)
- ispe
- irot/imir
- colr