Calabi Labs · Guide · 2026-06-14
Batch background removers strip visual elements from hundreds of images at once — but they leave an invisible trail that gets your content flagged even after you've edited everything to look perfect. Calabi doesn't remove backgrounds or pixels; it cleans the metadata layer that platforms actually scan, so your batch-edited images pass as phone recordings at the file level.
When you run 50 product photos through a batch background remover, every file comes out carrying the fingerprints of its transformation. The software embeds tool-name tags, model identifiers, and processing timestamps directly into the file's metadata. Export from Midjourney, Runway, or any generative tool and you get something more damning: a DigitalSourceType: trainedAlgorithmicMedia XMP flag, C2PA / Content Credentials manifests (stored as JUMBF atoms), and encoder signatures like Lavc or x264 SEI headers in video files.
Platforms like Instagram, TikTok, YouTube, and Reddit run automated forensic scans on every upload. They're not looking at whether the background looks removed — they're scanning for the invisible proof that AI generated or processed the file. A C2PA manifest can persist through re-encoding. The trainedAlgorithmicMedia tag survives recompression. Even if you crop out a visible watermark, the metadata layer that survived the crop is what gets you flagged on re-upload.
The problem compounds with batch processing because you're propagating the same AI fingerprints across every single file. One flagged upload is a warning; fifty flagged uploads from the same session is a pattern that can trigger account-level action.
Cropping removes the visible logo or corner mark, but the C2PA manifest embedded in the file structure is independent of pixel bounds. Crop the image, the manifest is still there. Screenshotting re-renders the pixels but doesn't strip structured metadata — the XMP block and JUMBF atoms survive a screen capture intact. Re-exporting through Photoshop or another editor adds your software's metadata on top but doesn't remove the original AI-tool signatures; it just buries them one layer deeper.
None of these approaches address what platforms are actually scanning for in 2026: cryptographic Content Credentials, encoder fingerprints, missing GPS and capture timestamps, and perceptual hash databases that flag AI-processed imagery regardless of how it looks visually.
Calabi runs a one-pass pipeline on every file you upload. Here's what it does to each image in your batch:
DigitalSourceType: trainedAlgorithmicMedia XMP tag is deleted. Encoder fingerprints like Lavc and x264 SEI headers are stripped from video files.Upload your entire batch, let the automatic pipeline run, and download files that read as authentic phone recordings at the metadata level — not AI-processed exports.
Does Calabi remove backgrounds from images?
No. Calabi is not a background remover, inpainting tool, or pixel editor. It works on the invisible metadata and encoder-signal layer. If you need to remove backgrounds, use a dedicated batch background remover first — then run the cleaned files through Calabi to strip the AI detection metadata before posting.
Will Calabi remove a visible watermark or logo?
No — and no tool can reliably strip a visible logo through metadata cleaning. If there's a visible watermark, cropping it out removes it from the pixel layer. Calabi handles the invisible detection layer that survives cropping: the C2PA manifests, XMP AI flags, and encoder fingerprints that platforms scan automatically.
Can I process a large batch at once?
Yes. Upload multiple files and Calabi processes each one through the strip-and-inject pipeline automatically. Every file gets its own forensic proof card so you can verify the clean on each individual asset before downloading.
Try Calabi free at calabilabs.com — 10 cleans, no card.