Images from DALL·E, Adobe Firefly, and increasingly other AI generators ship with embedded content credentials — C2PA manifests and XMP tags that record the image was AI-generated, by which model, when, and sometimes under which account. Most people have no idea it's there.
What AI generators embed
- C2PA manifest — a cryptographically signed provenance record (the standard behind “Content Credentials”), stored in the file. OpenAI adds these to DALL·E images; Adobe Firefly and some camera vendors do too.
- XMP tags — fields like
digitalsourcetype=trainedAlgorithmicMediaor a generator name in the Software/Creator Tool field. - IPTC fields — some pipelines write “AI generated” into description or credit fields.
Separately, some services also add invisible pixel watermarks (like Google's SynthID). That's a different mechanism — it lives in the pixels, not the metadata, and no metadata tool touches it.
How to check what an AI image carries
Drop the image into the image metadata viewer. Look for XMP blocks, a Software/Creator field naming a generator, or JUMBF/C2PA segments. The parsing is local — the image never leaves your browser.
How to remove AI metadata
The metadata remover strips the metadata segments where C2PA manifests and XMP tags live (APP1/APP11 in JPEG, iTXt/eXIf chunks in PNG), losslessly. Drop the file, click remove, download the clean copy, and verify by re-checking it in the viewer.
Should you remove it?
Be deliberate. Legitimate reasons to strip metadata: removing account identifiers before publishing, cleaning files for clients who require metadata-free assets, or reducing file size. But content credentials also serve a real purpose — provenance and transparency in an era of synthetic media — and some platforms are beginning to require AI disclosure regardless of what the file says. Removing the metadata does not change your disclosure obligations, and pixel watermarks like SynthID survive metadata removal anyway. Know your platform's rules and label AI content where it's required.
The bigger picture
Metadata cuts both ways: it can protect provenance and it can leak identity. Whether you're checking what a generator wrote into your renders or what your phone wrote into your photos, the habit is the same — view first, strip deliberately.