When Instagram, Facebook, or Threads attaches an AI Info label to a photo, it is rarely because a computer vision model analyzed your image pixels. In almost every case, Meta's upload system simply detected a signed provenance manifest embedded in the file's container metadata. Meta checks for Coalition for Content Provenance and Authenticity (C2PA) Content Credentials, along with related IPTC and XMP metadata fields, and automatically surfaces that data as a label on the post.

This guide explains where these metadata tags are stored, why taking a screenshot causes more problems than it solves, how C2PA differs from standard EXIF data and invisible watermarks like SynthID, and how to safely strip container metadata in your browser without quality loss or cloud uploads.

Use these techniques on files you own or are authorized to publish. Stripping metadata is a privacy and packaging choice; it should not be used to violate client contracts or regulatory disclosure requirements.

1. Why Meta flags your photos as “AI Info”

C2PA is an open technical standard designed to attach a cryptographic manifest to digital media. Unlike a simple caption or EXIF tag that you can edit in photo management software, a C2PA manifest is a signed data structure (typically CBOR formatted inside a JUMBF container) containing:

  • The software or generator used (e.g., Adobe Photoshop, Firefly, Midjourney)
  • The digital source type (e.g., algorithmic or generative media)
  • An action log recording edits (e.g., generative fill or touch-ups)
  • A cryptographic hash of the image data at the moment of signing

When you upload a file, Meta's servers inspect the file header. If the signature is valid, Instagram treats the file as containing generative content and displays the "AI Info" badge.

In image and video containers, these manifests are located outside the actual image raster:

  • JPEG: Stored inside an APP11 marker segment wrapping a JUMBF (JPEG Universal Metadata Box Format) superbox. Standard tools that only inspect EXIF APP1 markers will miss it, but Meta's backend parses APP11.
  • PNG: Stored in custom chunks such as caBX containing the Content Credentials graph.
  • MP4 / MOV: Stored as a uuid box (or dedicated c2pa / meta / udta atoms) within the ISO-BMFF box structure, located alongside movie metadata (moov) rather than inside media samples (mdat).

Most creators encounter this unexpectedly when using mainstream editing tools:

  • Photoshop Generative Fill and Adobe Firefly attach Content Credentials by default during export.
  • DALL·E / ChatGPT and various Midjourney download tools embed C2PA manifests or XMP source tags.
  • Even minor retouching—like removing a power line, fixing a small background defect, or extending a canvas border—adds an action entry to the C2PA manifest that triggers Instagram's label.

Meta also checks standard non-cryptographic tags. Fields like IPTC Digital Source Type (trainedAlgorithmicMedia) and XMP DigitalSourceType attributes are evaluated during upload. If you remove GPS data but leave the C2PA or IPTC tags intact, Instagram will still show the label.

Crucially, the label is triggered by file container metadata, not an artistic assessment of your work. Once the signed container is replaced or stripped, the cryptographic claim no longer exists.

2. Why taking a screenshot is the wrong fix

A common workaround recommended on social media is displaying the photo full-screen and taking a screenshot. While this removes the original C2PA header, it introduces serious drawbacks:

You lose resolution and color fidelity. A 24 MP or 48 MP photograph is immediately downsampled to your phone or monitor display resolution. The operating system re-encodes the screenshot using high-compression JPEG or standard sRGB PNG, discarding wide color gamuts (Display P3) and fine detail in textures and highlights.

Screenshots create a new device fingerprint. Operating systems automatically attach their own metadata to screenshots: iOS and Android record device model, OS build, screenshot capture timestamp, and display dimensions. Anyone inspecting the downloaded file can easily see it was a screen capture rather than an original export.

Pixel-level watermarks remain untouched. Invisible watermarks such as Google's SynthID are embedded directly into the pixel frequency domain rather than file headers. Because a screenshot captures the exact pixels displayed on screen, it carries any pixel-level watermarks right along with it.

If your goal is clean media without signed claims, you need a native-dimension Canvas redraw or box pruning—not a screen capture.

3. Comparing C2PA, EXIF, and Pixel Watermarks

Creators often conflate different forms of image metadata. Here is how they differ mechanically:

Channel Where it lives What it proves Does Instagram use it for “AI Info”? Removed by Canvas / box prune?
C2PA Content Credentials JPEG APP11 / JUMBF; PNG caBX; MP4 uuid / c2pa Signed producer, tool, actions, hash at signing time Yes — primary cryptographic trigger Yes — new bytes, signature dies
EXIF / GPS / XMP JPEG APP1, TIFF IFDs, XMP packets, IPTC IIM Camera serial, GPS, lens, software, digital source type Indirectly (IPTC/XMP source type) Yes — not copied into Canvas pixels
Invisible pixel watermarks (SynthID-class) Frequency / learned perturbation in the raster Statistical generator signature Possible via separate vision classifiers No — watermark is part of pixel data

A client-side tool that redraws images onto a 2D Canvas will always drop C2PA, EXIF, and XMP because those header blocks are never copied into the pixel buffer. However, no metadata tool can remove pixel-level watermarks without altering the visual content itself.

4. Step-by-step: how to strip C2PA before publishing

Trying to edit raw binary headers with a hex editor can easily corrupt JPEG markers or break MP4 box lengths. A clean, browser-based workflow handles this safely:

Images: Canvas redraw at native dimensions

The browser decodes the still to an ImageBitmap, draws it onto a Canvas sized to the source width and height, then exports a new JPEG (high quality, typically ~0.95), PNG, or WEBP. Nothing from APP1, APP11, XMP, ICC-as-sidecar, or Photoshop IRB is copied unless you explicitly re-attach it. The pixels retain their exact native dimensions, while the container is brand new without signed manifests.

Video: ISO-BMFF box pruning, not a transcode

MP4 and MOV files are composed of structured data blocks called boxes (or atoms). Video and audio samples reside in the mdat box, while C2PA manifests and tracking metadata live in metadata boxes (uuid, udta, meta, c2pa).

A client-side parser scans the box tree and copies the video and audio streams while skipping metadata boxes. This process is instant, completely lossless, and does not require re-encoding video frames.

A practical publishing checklist

  1. Export your creative master as usual (PSD flattened, Firefly download, camera JPEG).
  2. Open creatorprivacykit.com in Chrome (or another Chromium browser) — batch up to 50 files, all local.
  3. Drop the files. Confirm the inspector shows C2PA / generator / IPTC source type before you sanitize.
  4. Sanitize selected. Download the new clean files (or the ZIP).
  5. Upload the sanitized export to Instagram.

5. Platform policies, reach, and FAQ

Meta has stated that "AI Info" tags are intended as transparency markers rather than penalties. However, creators frequently report two concerns: audience perception (a tag indicating AI on photography with minor retouching can undermine trust) and algorithmic categorization (content flagged as synthetic may be evaluated differently by distribution feeds).

Stripping C2PA metadata removes the explicit container flag. It ensures that minor edits do not trigger automated badges. It does not alter your posting history or platform account standing.

Best practices for creators and agencies:

  • Keep a clean raw archive of original masters in cold storage. Sanitize only the public-facing web exports.
  • Always strip GPS data from photos taken at private residences, studios, or client facilities.
  • Avoid cloud-based metadata removers for private or unreleased commercial campaigns; stick to local client-side processing.
  • Check your files if you run them through Adobe applications, which may re-attach Content Credentials on export.

FAQ

No. You remove the cryptographic Content Credential and related IPTC/XMP source-type fields that travel in the container. Meta can still label from on-platform AI tools, reports, or perceptual models. SynthID-class marks stay in the pixels.
It often drops APP11, then degrades resolution and writes a new OS fingerprint. It also copies any invisible watermark. Use a same-size Canvas export instead.
No. CreatorPrivacyKit is a static client-side app. Canvas and ArrayBuffer work happen in your tab. Closing the tab discards the blobs.
Process files you own or are licensed to modify. Follow client disclosure rules and local advertising law. Metadata removal is hygiene, not a right to fake authorship.