Calabi Labs · Guide · 2026-06-14
Now I have the context needed. Let me write the full page.
```html
When you use a free YouTube downloader — whether it's yt-dlp, a browser-based converter, or a mobile app — you get the video file on your device. That's it. What a downloader cannot do is strip the invisible detection signals embedded in that file. If you're downloading AI-generated videos (Sora exports, Runway clips, Pika generations) and re-uploading them to YouTube, the platform has a separate system that scans for exactly those signals. A downloader has no effect on that layer.
Here's what's actually happening under the hood, and what actually works if you need to re-upload without the AI flag.
YouTube doesn't rely on visual inspection. It runs automated scans against the file's metadata and embedded signaling infrastructure. The three layers that matter are:
DigitalSourceType: trainedAlgorithmicMedia gets written into the XMP metadata block by AI export pipelines. There are also Generator, Software, and CreatorTool tags that identify the AI source. These are separate from the C2PA layer and survive most re-encodes.Lavc (FFmpeg's encoder) and x264 SEI messages are embedded in the video stream itself. A phone records don't have Lavc fingerprints — they have hardware encoder signatures from Apple VideoToolbox or Qualcomm's hardware encoder.YouTube's May 2026 rollout added additional internal signals that cross-reference these metadata blocks against known AI generation patterns. The "AI-generated" label isn't just about disclosure — it's about detection. If the metadata says one thing and the file's technical fingerprints say another, that's its own signal.
Most creators try one of these approaches before looking for a real solution:
None of these approaches address the core problem: the file carries cryptographic and metadata evidence of its AI origin, and YouTube's systems are specifically designed to read that evidence.
Calabi runs a one-pass pipeline that strips the detection layer and injects authentic phone-capture identity. Here's what happens in that single pass:
DigitalSourceType: trainedAlgorithmicMedia XMP flags, all Generator and Software AI tool tags, and the Lavc / x264 SEI encoder fingerprints from the video bitstream.The result is a file that reads, at the metadata level, as a normal phone recording. The C2PA manifest is gone. The AI XMP flags are gone. The software encoder fingerprint is replaced with a hardware encoder signature. The forensic proof card confirms it.
No tool can guarantee a platform won't take action — YouTube's detection systems evolve and have some internal signals Calabi doesn't have access to. What Calabi fully removes is the C2PA manifest, all XMP AI flags, and the software encoder fingerprints that automated scanners specifically look for. These are the signals that trigger the "AI-generated" label automatically.
Yes — as long as the export contains C2PA manifests and XMP metadata flags (which all major AI video tools now write by default), Calabi strips them. The encoder fingerprint strip works for any software-encoded export, regardless of which tool produced it.
No. Calabi works on the invisible metadata and signaling layer — it does not remove visible watermarks, logos, or on-screen branding. If you're downloading someone else's content, copyright and visible watermarks are separate issues that a metadata tool cannot address.
Try Calabi free at calabilabs.com — 10 cleans, no card.
```