Frame.io shows Content Credentials, it does not create them

The shot

Frame.io, the cloud review platform Adobe owns, describes Camera to Cloud as a workflow that moves camera-original footage, proxies, audio and metadata from set to editors as it is captured. At Adobe MAX, on 28 October 2025, Frame.io's own product blog announced a companion feature layered on top of that pipeline: a built-in Content Credentials display that shows whether an uploaded file carries C2PA-standard provenance data.

What the documents show

The Camera to Cloud page states the workflow “works with the widest range of cameras and production devices of any platform” and can “automatically upload audio files, metadata, CDLs, and more” alongside picture — a vendor claim about breadth, not a camera-by-camera audit. The Adobe MAX post is specific about the new feature: “Upload assets from any source—including Camera to Cloud, desktop, or mobile—and Frame.io automatically reads and preserves their credentials,” surfaced through a CR icon opening Adobe's Content Authenticity Inspect tool for edit history, listed AI tools and creation date. That describes Frame.io reading and carrying forward credentials that already exist in a file; it does not state that every connected camera embeds those credentials at capture, and no such claim appears in either document. C2PA's own site uses the identical ‘Content Credentials’ term, tying this feature to the C2PA specification rather than a Frame.io-only label.

The workflow

For a production already on Camera to Cloud, the documented change sits at review, not capture: metadata and proxies already flow to Frame.io automatically, and any Content Credentials already attached to a shot now survive the upload and a later export or integration, per the MAX post's “stays intact” line. A supervisor gets a visible marker rather than a separate tool to check provenance, with a click-through to Adobe's inspector for detail. Whether a camera or app writes Content Credentials at all remains a decision made upstream of Frame.io — a production still has to choose provenance-capable gear for credentials to exist before they reach the platform.

What the tool does not change

Frame.io's own pages describe a passthrough and display function, not a verification service that judges authenticity; a present CR icon shows that manifest data exists and can be inspected, not that Frame.io has confirmed the content is unaltered. Deciding what to disclose to a broadcaster or platform, and whether a shot's provenance record is complete, is left to the production and is not addressed in either document. This is an editorial caution, not one the documents state directly.

• Does the camera or app used on a shoot itself write Content Credentials, or does that depend on separate hardware or software the production must add?
• When a platform shows a provenance icon, does its documentation say the platform verifies the content, or only that it displays data supplied by an earlier step?
• Do downloads and third-party integrations preserve that data as claimed, checked against a real exported file rather than the marketing copy?

A provenance icon on a cloud review platform is only as informative as what a production put into the file upstream; Frame.io's own documents describe carrying that data forward, not creating it.