Trend report · r_artificial · 2026-06-06
AI Detection Text Scanners Do Not Work. None of Them
A thread on r/artificial hit trending last week with a blunt thesis: AI detection text scanners don't work. The author had spent 10 hours testing every major scanner, getting wildly inconsistent results even on content they knew was human-written. The thread exploded—hundreds of comments, most agreeing, many sharing their own horror stories. But here's what the discussion missed: text scanners are the easy problem. The hard problem is platform-level image and video detection—and in 2026, it's getting much, much harder to beat.
What Platforms Actually Scan For in 2026
Forget text. Major platforms have moved to visual content detection, and they use a layered approach that text-based tools can't touch. Here's what's actually in the scanning pipeline:
C2PA (Content Provenance and Authenticity) is now the gold standard. The C2PA 2.1 specification defines a cryptographically-signed manifest embedded directly in image and video files. This manifest contains fields like c2pa.claim_generator (identifying the software), c2pa.actions (listing edits made), and dc:creator (identifying the human or organization). When you export from Adobe Firefly, run a Sora generation, or use Midjourney, these tools write C2PA manifests. Instagram and TikTok now read them and apply "AI-generated" labels when detected.
AI metadata goes beyond C2PA. Tools like Stable Diffusion, DALL-E 3, and Sora inject proprietary markers into EXIF headers and XMP packets. Common fields include Software, Make, Model (sometimes set to values like "NVIDIA AI"), and custom MakerNote tags. Even if C2PA is stripped, these markers can survive—though the Sora watermark removal guides on Calabi show exactly which fields to target.
Missing GPS and metadata completeness is a simple but effective heuristic. Real smartphone photos carry GPS coordinates, device make/model, lens info, and timestamps. AI-generated images often have sparse or inconsistent metadata—present in some fields, absent in others. Instagram's classifier flags content where EXIF shows a camera but no GPS on a photo that "should" have location data.
What Actually Gets Flagged on Instagram and TikTok
Based on community reports and platform disclosures, here's what users are seeing:
On Instagram, posts with detectable C2PA manifests get auto-labeled "AI-generated" regardless of visual quality. Some users report reach suppression—posts labeled AI get 30-50% less reach than comparable human content. Reels showing AI-generated video with visible artifacts get harder treatment: reduced distribution and no recommendation eligibility.
On TikTok, the "AI-generated content" label is applied when metadata or detection models flag synthetic origin. Videos from certain AI tools (especially those with known encoder signatures) get labeled immediately on upload. Some creators report their accounts getting flagged after consistent posting of detectable AI content, leading to broader throttling.
Facebook/Meta applies similar rules through its AI Content Labels system. The key pattern: detection is probabilistic and metadata-based, so the fix needs to address both layers.
The Durable Fix: Strip and Inject
Stripping metadata alone doesn't work. You need a two-part process:
Step 1: Deep Strip
- Remove C2PA manifests entirely (look for
c2paUUID-based chunks in PNG,c2paatoms in MP4, or JUMBF boxes in JPEG) - Clear all EXIF fields:
GPSLatitude,GPSLongitude,Make,Model,Software,DateTimeOriginal,ExifImageWidth,ExifImageHeight - Strip XMP packets, IPTC headers, and ICC color profiles that might carry AI markers
- Re-encode the image (PNG → JPEG → PNG) to disrupt encoder signatures—not a full solution, but it noise-floods simple frequency analyzers
Step 2: Clean Injection
- Generate realistic phone identity metadata that matches the device model you're impersonating (e.g., "Apple", "iPhone 15 Pro", "2026:01:15 14:32:01")
- Add GPS coordinates that make geographic sense for the claimed device (phone photos cluster in real places)
- Inject consistent EXIF across the full metadata structure—real camera photos have coherent, complete metadata
- Add plausible lens info, exposure settings, and flash status that match the claimed device
The goal isn't to fool every detector—it's to make your content look unremarkable. Detectors flag outliers. Clean metadata makes an AI image look like thousands of others uploaded daily.
Why This Has to Be Done Right
Manual stripping and injection fails because it's incomplete. Miss the C2PA manifest and Instagram catches it. Leave inconsistent timestamps and TikTok flags it. Get the GPS wrong (coordinates in the ocean for a phone photo) and the classifier notices.
The only durable fix is systematic: strip everything, verify nothing remains, then inject a complete, internally consistent phone identity. That's what Calabi does in one pass—it's why "strip + inject clean phone identity" keeps working while metadata editing fails.
The Reddit thread was right about text scanners. But for creators working with AI images and video, the battle moved to the platform level, and the rules changed. In 2026, you don't beat the classifier by being clever. You beat it by being invisible.
→ Try Calabi free at calabilabs.com — 10 cleans, no card.