C2PA 2.3 live video support: does it reach AI clips made on Sume?
C2PA 2.3 adds live video and streaming support. Sume's video jobs return finished MP4 files, so the live feature changes little for generated clips.
C2PA announced Content Credentials 2.3 on 23 February 2026, and its release post says the standard now supports "broadcast and streaming content" (C2PA, read 2026-10-02). Sume's video endpoints produce finished, job-backed files rather than live streams, so for a clip made on Sume the live-video feature changes little today.
What the 2.3 post lists
The post groups the release into a few headline changes. Live video is the one that sounds biggest, but the others may matter more for file-based workflows.
| Change | What the post says |
|---|---|
| Live video | Supports broadcast and streaming content |
| File formats | Manifests newly available for plain text, OGG Vorbis audio, large AVI video and EXIF Original Preservation Images |
| Editing detail | More specific details about changes such as resizing, markup or redactions |
| Cloud | Credentials can point to trusted information stored in the cloud |
| Security | Updated validation and tampering detection |
Why live video is a side issue for generated clips
Sume's video docs describe generation as a job: you submit a request, poll or receive a webhook, and fetch a result file. That is a recorded-media workflow. A signed live stream is a different system with continuous signing at capture or broadcast time, and nothing in Sume's docs describes one.
What does apply is the editing-history work: Sume's trim and Timeline render re-encode into a new MP4, and 2.3 gives credentials a way to describe changes like resizing. Whether any given tool writes that record is something to test on the delivered file.
What to do now
- Treat a generated clip as recorded media and check the delivered file with a Content Credentials verifier before promising credentials to a client.
- Do not call a Sume export "signed" unless you have seen a valid manifest on that file.
- If you re-stream a finished clip on a live platform, ask that platform what it does with credentials; the 2.3 live feature is about the broadcast chain, not your file.
- Keep your own record: job id, artifact URL and edit steps.
Honest limit
Sume's docs do not say that its video output carries a C2PA record. This page explains a standard release and does not claim that Sume implements it.
Sources
Related posts
More in Use cases
- C2PA 2.3 file types: OGG, AVI and text, and the files Sume returns
C2PA 2.3 newly names text, OGG Vorbis, large AVI and EXIF originals. Sume returns MP4, WAV and MP3, so check your format before promising credentials.
- California AB 2713: no deleting AI watermarks, and Sume re-encodes
California's 30 September 2026 release lists AB 2713 as barring deletion of digital watermarks. What Sume's re-encoding trim does and does not say about marks.
- California SB 1111 digital replicas: avatar and face-swap checklist
California's governor signed SB 1111 on digital replicas on 30 September 2026. A checklist for avatar and face-swap work, and what Sume's docs cover.
- Character turnaround sheet by API: front, profile, back views
Make a turnaround sheet by API: render the front view, then send it as a reference for profile and back. Google's 360-view method, and the Sume request.
Written by Sume