Pixels vs File Headers: The Two Distinct Layers
Every digital visual file consists of two completely separate zones:
- The Payload (Pixels): The raster grid of RGB values representing the visual picture. This is where visible watermarks, logos, and timestamps reside.
- The Header (Metadata): Standardized text containers at the beginning or end of the file. This is where C2PA cryptographic manifests, EXIF camera tags, IPTC photo attributes, and software signatures are stored.
When you use a generic photo editor or clone stamp to paint over a logo, your editor modifies the pixel values in the payload. It does not inspect, parse, or purge the C2PA JUMBF containers stored in the file headers.
Why Social Algorithms Still Detect Your File
When you upload an image to LinkedIn, Meta platforms, or TikTok, their automated ingestion pipeline does not perform computer vision on the corner pixels. Instead, the server inspects the file header in milliseconds:
- It looks for the JPEG APP11 marker (`0xFF 0xEB`) or PNG `caBX` chunk indicating a signed C2PA manifest.
- It scans for the IPTC tag `digitalSourceType: trainedAlgorithmicMedia`.
- It checks for software claims from OpenAI, Google, Midjourney, or Adobe Firefly.
Because the file headers still contain these signed assertions, the platform automatically attaches a "Content Credentials" or "AI Info" badge even if the visual logo was completely painted over.
How to Perform a Complete Two-Stage Sanitization
To prepare an asset for clean publishing:
- Clear the Visible Mark: Use our Gemini Watermark Remover to mathematically reverse the corner sparkle without introducing blur.
- Scrub Container Metadata: Open the Social AI Label Checker or Metadata Viewer to strip the C2PA manifests and IPTC markers losslessly.
This ensures that both the visual picture and the digital headers are completely clean before publication.