Does Sora (video; discontinued) add Content Credentials?

If you publish Sora (video; discontinued) output in the EU

Marking outputs in a machine-readable way is the duty of the tool’s provider under Article 50(2) of the AI Act. If you use the output for work and it is a deepfake, the visible disclosure is yours (Article 50(4)), whatever OpenAI adds to the file. What that means for your content: AI video.

Scope and limits

• The launch post is historical: it describes Sora at launch, not a current service.
• The launch post documents a visible watermark at launch and C2PA metadata. It does not name a separate invisible pixel watermark for video.
• The launch post and the discontinuation article were read directly on OpenAI’s pages on 3 November 2026.

If the credentials are removed

C2PA data travels inside the file, so a re-encode, screenshot or upload that does not carry it across leaves an image with no credentials. A watermark or fingerprint can help find a record again, if one was stored (see the C2PA specification’s soft bindings). Proofcan is independent of OpenAI: for images you mark with Proofcan it writes a C2PA manifest, an invisible watermark and a registry record. It does not change or vouch for how OpenAI marks its own outputs.

Check a file yourself

The Content Credentials checker reads the C2PA data in an image in your browser and shows who signed it, the generating tool and whether the signature still matches. It reads what a file declares; it does not detect AI from pixels, and a file with no credentials proves nothing either way. See why metadata gets stripped.