Guide · creator playbook
How to post Sora videos on X (Twitter) without getting flagged
X reads embedded provenance metadata and flags AI media via Community Notes, throttling reach on posts it marks as synthetic. OpenAI Sora ships with exactly the signals X (Twitter) looks for. Strip every one and post clean.
Strip the Content Credentials (C2PA / JUMBF)
Cryptographically signed block that proves the file was AI-generated. Visible to anyone running a verification check. Calabi removes this automatically — no manual ExifTool work.
Strip the Visible animated sparkle watermark
OpenAI's branded sparkle in the corner of every Sora export. Calabi removes this automatically — no manual ExifTool work.
Strip the XMP DigitalSourceType=trainedAlgorithmicMedia
Hidden text field most metadata scanners look for first. Calabi removes this automatically — no manual ExifTool work.
Strip the OpenAI generator identifier in EXIF
Tool name stamped into the file's metadata stream. Calabi removes this automatically — no manual ExifTool work.
Inject authentic phone identity
Calabi writes a real Make / Model / Software / GPS / capture-timestamp so the file presents as a normal phone recording, not an AI export.
Verify, then post to X (Twitter)
Check the forensic proof card — it lists every signal stripped and injected — then upload to X (Twitter) clean.
Stop guessing. Calabi automates every step above — 10 free cleans, forensic proof on each.
Try free →
Why this matters now
AI detection on social platforms in 2026 is no longer a coin flip. Instagram, TikTok, YouTube, Twitter/X, and Reddit all run automated scanners on every upload before a human moderator sees it. The flag-rate on raw AI output is approaching 100% for the major generators (Sora, Veo, Kling, Midjourney). The only path forward is full sanitization — strip every signal, inject authentic phone identity, verify before posting.