Calabi Labs · Guide · 2026-06-14
```html
You can't erase a visible logo or text overlay pixel-by-pixel with Calabi — that's a photo editing task, not what this tool does. But if you're uploading AI-generated images to Instagram, TikTok, Reddit, or YouTube and getting flagged or suppressed, the problem isn't the visible watermark you can see — it's the invisible detection layer baked into your file that platforms scan for automatically. Calabi strips those invisible signals and replaces them with authentic phone-capture identity so your file looks like a normal photo, not an AI export. Here's exactly what that means and how it works.
When a platform审核你的上传,它不是在目视检查每个像素。It runs automated forensic scans that look for specific invisible signals embedded in your file — and an AI export carries several distinct layers of them.
The first and most significant is C2PA / Content Credentials, stored as JUMBF (JPEG Universal Metadata Box Format) metadata. This is a cryptographic manifest that says, cryptographically, "this image was generated by AI." Major platforms including Adobe, Microsoft, Google, and OpenAI have adopted C2PA as part of the Content Authenticity Initiative. If your Sora export, Midjourney save, or Leonardo AI download carries a C2PA atom, an automated scan can detect it in seconds — often before a human ever sees your post.
The second layer is XMP metadata flags. Specifically, fields like DigitalSourceType: trainedAlgorithmicMedia — a precise XMP tag that explicitly declares the image came from a model trained on scraped data. The moment that tag is present, a platform's detection pipeline has a clear signal to act on.
Third are encoder fingerprints embedded in the video bitstream or image codec metadata. AI video exports from tools like Runway or Sora carry identifiable encoder signatures — Lavc (FFmpeg's libavcodec), x264 SEI (Supplemental Enhancement Information) messages, and similar codec-level markers that don't appear in a real phone recording. These fingerprints survive re-encoding because they're not in the visual content — they're in the technical wrapper around it.
Finally, platforms look for absence signals: a file missing GPS coordinates, capture timestamp, and device identity looks different from a genuine phone photo. Real camera captures carry a consistent set of EXIF fields. An AI export either lacks them or carries a different, recognizable pattern.
If you've tried cropping, screenshotting, or re-saving through a basic metadata stripper, you already know: platforms still flag your file. Here's why each common approach falls short.
Cropping removes the visible mark, not the invisible signal. A visible watermark — Sora's sparkle, a platform's corner logo, a "Generated by AI" text overlay — lives in the pixel content. Crop it out and the pixels are gone, sure. But the C2PA manifest, XMP flags, and encoder fingerprints are stored in the file's metadata structure, not in any visible region of the image. Cropping doesn't touch that layer. Platforms can read metadata without ever looking at the image content.
Screenshotting disrupts some metadata but leaves a fingerprint trail. Taking a screenshot of an AI image and re-uploading strips some metadata — but re-screenshotted images carry their own detection signals: compression artifacts, resolution anomalies, and missing EXIF data that still look different from a genuine photo capture. Plus, you've now lost resolution and introduced visual noise.
Basic metadata strippers remove some fields but miss the C2PA layer entirely. Most free EXIF strippers remove a few EXIF tags, but they don't know how to parse or remove JUMBF/C2PA atoms. The cryptographic manifest survives. Platforms specifically check for C2PA — not just general EXIF — so a partial strip is functionally useless for avoiding a flag.
Calabi runs a three-stage pipeline in a single pass: strip the detection signals, inject authentic phone-capture identity, and verify the result before you download.
DigitalSourceType: trainedAlgorithmicMedia XMP flag, strips encoder fingerprints like Lavc and x264 SEI, and reduces your file's 144+ metadata tags down to roughly 94 neutral structural tags. This isn't editing pixels — it's removing the invisible evidence trail.The result isn't a pixel-edited image — it's a file that passes the automated forensic scan as a normal phone capture, because at the metadata level, that's exactly what it looks like.
Does Calabi erase visible logos or text watermarks from my image?
No. That's a pixel-level editing task — think inpainting, content-aware fill, or clone-stamp, which Calabi does not do. Calabi works on the invisible metadata and encoder signals that platforms scan for automatically. If your image has a visible logo, cropping removes it; Calabi handles the metadata layer that cropping doesn't reach.
Will this guarantee my post won't get flagged?
No tool can guarantee that. Platform detection systems vary, update, and layer multiple signals. Calabi removes the metadata and encoder signals it can fully strip — and those are specifically what automated scans look for before a human ever sees your post. Results depend on the platform, the source model, and how the file is processed after cleaning.
Try Calabi free at calabilabs.com — 10 cleans, no card.