No filming:An AI avatar or clone yourself

    Publishing and performance

    Scheduler strip meaning

    Also called C2PA strip, Manifest strip on upload, Cross-post provenance loss.

    Scheduler strip is C2PA dying on a cross-post or API upload: the signed manifest is bound to one file's bytes, and the re-encode is a new file.

    Content credentials hash the exact bytes of a copy. Validation is a match or a miss. A social ingest, a scheduler that transcodes to a delivery codec, an API that accepts the file and writes a new MP4 — each of those produces different bytes. The manifest does not degrade. It is gone. That is the mechanism working, not a bug in Buffer, Later, or a platform's Graph API. Provenance as a category still exists; the signed record of this copy does not travel.

    Syndication is the honest distribution job: a new file per surface, adapted for ratio, caption burn-in, and chrome. Scheduler strip is what happens when that job is implemented as 'upload the same MP4 everywhere' or 'hand the bytes to an API and trust the metadata.' Invisible watermarks are the class of mark built to survive that pipeline. A visible corner logo is not. A description-field disclosure is not. Burn the line a viewer is owed into the picture if the file will be re-wrapped.

    Keep the generator's export as the archival copy whose hash still matches. Treat the scheduled social file as a descendant with no manifest left to check. Auto-labels that read C2PA on ingest will not see a record that the scheduler already invalidated.

    In practice

    • Archive the original export. The scheduled or API copy is a different file.
    • Burn a viewer-facing disclosure into the frame if the clip will be cross-posted. Do not leave it in a manifest the ingest will drop.
    • Do not read a missing C2PA tick after a scheduled upload as proof the generator never signed.

    The mistake to avoid

    Trusting a scheduler's 'preserve metadata' toggle with C2PA. A re-encode changes the bytes the manifest is bound to, whatever the checkbox said.

    Go deeper

    Why C2PA manifests die on upload

    A C2PA manifest is a hash over exact bytes, so re-encodes and screenshots kill it by design. How to find the hop in your pipeline where provenance is lost.

    Related terms

    The all-in-one AI studio for creators. 60+ models for video, image, voice, music and lipsync, in your browser or on your phone.

    Free on the web and on iPhone, one account.

    All terms →