About Us
C2PA Studio is an independent, browser-based workspace for understanding the evidence attached to digital media. It is designed for creators and editors who want a more precise handoff: an explanation of what a file declares, which checks ran and which questions remain open.
Why this project exists
Media provenance is easy to overstate. A badge can sound like a judgment about truth, while a missing record can be mistaken for evidence of AI generation. This project uses plain status labels, visible limitations and inspectable JSON to help people ask better questions. It is a workflow tool, rather than a general-purpose AI detector.
The first release focuses on local file inspection, preserving evidence across exports and careful reporting. The field notes explain practical checks for editors, developers and publishers. They are written for separate production questions, rather than generated by swapping model names into a shared landing-page template.
How the local privacy design works
The page receives the File objects you choose. An official Content Authenticity Initiative SDK reads their bytes in a browser worker using WASM. The application sends no media upload request. The SDK settings disable remote manifest retrieval and online revocation requests. Report generation and supported certificate signing happen locally too.
This tradeoff is visible: identity trust and current revocation are not established here. The application’s static files still come from its host, and choosing an external link opens an independent service. “Local processing” describes the media pipeline, not a claim that your browser never makes a network request.
Framework and open-source foundations
The frontend is derived from River418/app-starter, using React, TypeScript, Vite and React Router with reusable client UI primitives. The source baseline is recorded in the project’s provenance notes. This release removes the starter’s customer account and media-storage requirements. A narrow Hono/Worker/D1 licensing service now follows the starter’s backend structure for one-browser activation; media inspection and signing remain local.
Credential parsing uses the official c2pa-js project. The project also depends on open-source UI, CBOR and PDF libraries, with notices included in the delivery. This tool is independent of C2PA, Adobe, Google, TikTok and YouTube; their names describe standards, dependencies or referenced policies.
People and editorial policy
C2PA Studio editorial maintains these guides for creators, editors and developers investigating media provenance. River418 is the public project maintainer. Writing and development use AI assistance; an editorial byline does not imply an independent expert review or a professional credential.
Our method separates documented standards and platform policies from our workflow recommendations. Each guide links to primary sources, states what a file check cannot establish, and preserves a publication and update date. Dates change when the content is substantively revised; rebuilding the site does not create a new review date.
The developer’s public reference is the River418 GitHub profile. This release makes no claim about professional credentials, institutional affiliation or work history that has not been supplied. The operator must add its real contact details before public commercial launch.
Each article has a review date and primary-source links. Corrections should identify the page, the disputed statement and a supporting source, without attaching private client media. Visit Contact Us for the current support status.