C2PA 2.3 editing history: what trim and filter return in Sume

C2PA's Content Credentials 2.3 lets users see more specific details about changes to a file, such as resizing, markup or redactions. In Sume, trim and filter each return a new MP4 and leave the source untouched, while inspect only reads. Sume's docs do not say a C2PA record is carried onto the new file, so check the output yourself.

C2PA facts are from its 2.3 announcement, read 2026-10-01. Sume facts are from the trim, filter and inspect docs.

What is new in Content Credentials 2.3?

The announcement lists live video, manifests for plain text, OGG Vorbis audio, large AVI files and EXIF Original Preservation Images, clearer editing history, cloud links to trusted information, and updated validation to detect tampering. It describes manifests as showing a file's history.

Which Sume routes write a new file?

Each route's docs state what it returns, which decides where an edit history would have to live.

Does a resize after trim show up in the history?

Sume's docs do not describe provenance records for these outputs, so it cannot be answered from them. What the docs do fix is the shape: each edit makes a new artifact, so any history you need to keep is a property of the file you receive. Run a C2PA-capable reader on that final file rather than the source. On the filter route, ops[] offers dim and crop, and scale is on the filtergraph allowlist, so a resize is possible there; the docs say nothing about whether it is recorded as history. See what survives on Sume.

What should I do in a pipeline?

Keep the source, treat each trim or filter output as a separate asset, and record your own edit log (source id, route, parameters) beside it. Inspect before and after if you need to compare duration or codecs. Do not rely on 2.3 features being present on outputs unless you have verified them on a real file.