What do you risk by waiting?
Waiting means building an archive of assets that can't prove their own history. A signature applied by a camera at the moment of capture can't be recreated later. So, unless one takes advantage of digital watermarking technologies, every file that loses its record stays unverifiable for good.
Long term, this means more internal uncertainties about stored files and fewer abilities to prove their authenticity.
What should leaders require from their systems today?
The first step is to create a plan for how to include C2PA across the technical ecosystem. Once the plan is in place, the next step is to start treating content provenance as a policy, making sure it's prioritized across the entire workflow.
These six steps give both news and communication leaders a practical starting point:
-
Set a provenance policy. Decide which content must carry Content Credentials, for how long, and what should happen if they arrive without this.
-
Map every transfer. List each system a file passes through between initial capture and publication, including editing tools, the DAM, cloud storage tools, CMS, syndication and social channels. Each hop is a place where the record can be dropped.
-
Make the DAM the anchor. Require C2PA support on ingest, on edit, on round trips to third-party tools and on export, with an untouched original kept as a reference. Ask vendors to show a signed crop and a signed export in a live demo.
-
Put provenance in front of the people who publish. Editors and communication staff need to see credential status where they search and select assets, and should be able to filter out files with invalid credentials or AI involvement before publication.
-
Name an owner. Provenance crosses the picture desk, communications, legal and IT. Give one role responsibility for the policy and its exceptions.
How does Fotoware support digital provenance tracking in DAM?
Fotoware supports Content Credentials end to end, following the open C2PA standard, and has been a member of the Content Authenticity Initiative since 2023. The Content Authenticity capability preserves provenance data on ingestion and keeps it intact throughout the asset's lifecycle.
Read more: Fotoware launches Content Authenticity: complete C2PA support in the DAM
Every edit, crop and metadata adjustment made in the DAM is recorded in the file's traceable history, and edits made in third-party systems are signed and traced in the same way. Users can inspect credentials in detail without leaving the system, and use search filters to exclude files with invalid credentials, AI manipulation, or no camera origin.
At Visa pour l'Image 2026, Fotoware and Canon demonstrated how this works across a real photo workflow, from capture to consumption.
Every organization that publishes images will be asked to show where they came from. The ones able to answer will be those that decided early which systems may touch the file, and required each of them to keep a verifiable record.
.jpg){kind=tracking}
