Original vs platform download: why identical-looking clips differ
Trace where credentials disappear without confusing a derivative with the original file.
The short answer
A platform download is a different delivery copy, even when it looks like the original. Re-encoding, resizing or metadata handling can change the available C2PA record. Inspect the source and downloaded copy separately and record the export path; do not infer AI generation from credentials missing in a derivative.
Source context: Official SDK: working with manifests. The workflow recommendations below are editorial analysis.
The downloaded copy is a new review object
A client says the video looks unchanged, but the downloaded version no longer shows the record you saw before upload. That is a workflow investigation, not a contradiction. Start by naming the two files separately. “The video” is too imprecise when a master, a preview and a platform rendition all circulate under the same project name.
Build a short custody timeline: exported master, transferred original, platform upload, platform download and any subsequent messaging copy. Keep the acquisition time and route for each file. You do not need to speculate about a platform’s internals to document what your own copies contain.
Find the first observed difference
Inspect the earliest available copy first, then move forward one step at a time. Save the results without overwriting the previous record. When the output changes, mark the transition, the exact formats and the available error text. Avoid saying “the platform removed C2PA” if you only have a forwarded copy several transformations later.
Distinguish no embedded manifest from a failure to validate one. If the reader finds declarations but reports a binding problem, that is different from a derivative containing none. Your next test should reproduce the specific transition on a small permitted asset. This makes it easier to ask a vendor for actionable support.
Design delivery for evidence retention
If provenance matters to the receiving team, deliver the original as an original rather than relying on a social preview. Tell recipients which file the report describes and how they should obtain it. Keep a human-readable handoff note alongside the machine-readable result. A report without the corresponding media identity is easy to misapply.
Do not promise that a visible watermark solves missing provenance. It may serve a separate communication purpose, but it does not reconstruct the lost signing history. Improve the export and transfer path, retain source assets and document the gap honestly. That is a sustainable workflow even when a publishing platform creates derivatives you cannot control.
A comparison for your review
| Review copy | Practical question | Record |
|---|---|---|
| Master | What did the editor produce? | Original inspection |
| Transferred file | Did delivery carry the same evidence? | Acquisition route |
| Platform rendition | What is in this derivative? | Separate result and date |
Put it into practice
- Assign distinct names to each copy.
- Inspect in acquisition order.
- Locate the first observed difference.
- Reproduce with a non-sensitive test asset.
- Deliver original evidence alongside previews.
Bring your own evidence.
Inspect a local file and see what it actually declares.