Content Credentials (C2PA) on export

Every master Horoptic renders gets a C2PA provenance manifest recorded alongside it by default — a machine-readable record of how the file was assembled.

This page describes what that manifest contains today, and is deliberately specific about what is not there yet. Provenance claims are only worth anything if they are exact.

What’s in the manifest

Whether an AI model in Horoptic made or changed any clip in the export, declared for the file as a whole. A master with a generated clip, or a clip an AI tool changed (an upscale, slow motion, noise or voice cleanup, a restyle, an object removal, a background removal), is marked edited using generative AI. A master cut only from your own clips is marked a composite — a mix of elements that makes no claim either way, because Horoptic cannot know how a file you imported was made.
Every source clip that went into the master, each recorded with a SHA-256 hash, plus a hash of the delivered file itself.
The tool that assembled the master.

What isn’t in it yet

The individual generation models are not named. The manifest currently records the rendering tool that assembled the master, not which model produced each generated clip. Threading the per-clip model and provider through to the manifest is planned; until it lands, don’t read the manifest as a model-by-model account.
It does not distinguish AI-generated from AI-edited. A master with AI in it is marked with a single composite declaration covering the file as a whole, rather than separating the two cases.
Disclosure is whole-file. Region-level assertions — marking which parts of a frame are AI — are a real feature we may add later, not something we claim today.

Getting the manifest

In the desktop app, when an export finishes, the list of your files includes Content Credentials — the manifest as its own file, saved beside your master as <your file>.c2pa.json — and downloading everything at once takes it along. It is a separate file: it is not embedded inside the media file yet. The phone app does not offer it yet.

That also means the official Content Credentials verification tools cannot read it yet — those read a credential embedded and signed inside the file, which is the step below. We would rather say that plainly than let you assume a public verifier will show something it won’t.

Cryptographic signing

C2PA also supports a cryptographic signature that lets a viewer confirm a manifest hasn’t been altered, and allows the credential to travel inside the file. Signing requires a trusted signing certificate; we’ll enable it once the signing certificate lands. The code path is built and switches on the moment a certificate is in place — until then, exports carry the provenance record without a trusted signature, and we won’t describe them as “signed.”

Why it’s there

Disclosure is built into the export, not bolted on. It’s how Horoptic meets emerging AI-transparency rules (such as the EU AI Act’s Article 50 disclosure duty and California SB 942) — and it gives you, the creator, an honest, portable record of how your frames were made. Horoptic also doesn’t train on your media: we keep a provenance record of what was made — not a dataset of your footage.