What Is C2PA? History, How It Works and Its Limits

Every day, billions of digital assets are created, shared, and used to make decisions with real-world consequences: purchasing property based on photographs, publishing investigative reports based on video evidence, settling insurance claims documented with images. The fundamental question remains constant: is this content authentic? Does it faithfully represent what it claims to represent?

To address this question, the Coalition for Content Provenance and Authenticity (C2PA) was established in 2021 as an open technical standard designed to track digital provenance from creation to distribution. The C2PA specification has since become the global reference for content authenticity, promoted by the Adobe-led Content Authenticity Initiative, which reported more than 6,000 members in January 2026. But the critical question persists: is this provenance metadata standard alone sufficient to guarantee that a piece of content is authentic?

The answer, supported by technical evidence and independent research, is no. C2PA is a necessary but structurally insufficient tool when used in isolation. The standard certifies the history of content, not its truth. To bridge this gap, C2PA must be combined with a forensic acquisition methodology that certifies content at the source: precisely the approach adopted by TrueScreen, the Data Authenticity Platform that combines C2PA content credentials with certified forensic acquisition.

What is C2PA?

C2PA (Coalition for Content Provenance and Authenticity) is an open technical standard that enables embedding verifiable provenance metadata into digital content such as images, videos, audio, and documents. Founded in February 2021 by Adobe, Arm, BBC, Intel, Microsoft and Truepic, C2PA addresses the growing challenge of media manipulation by creating a tamper-evident chain of custody from content creation through distribution. The standard uses X.509 digital certificates and cryptographic hashing to sign provenance manifests that record who created content, what tools were used, and what edits were made. Members and supporters include Google, Meta, OpenAI, Sony, Nikon and Leica, while the Content Authenticity Initiative that promotes the standard reported more than 6,000 members in January 2026. Unlike deepfake detection tools that analyze content after the fact, C2PA operates at the point of creation, establishing digital provenance before content enters circulation. Content Credentials can be read with viewers such as Verify from the Content Authenticity Initiative or TrueScreen's C2PA viewer, which is free and works in the browser without uploading the file.

Who created C2PA, and when?

The story of C2PA begins in 2019, when Adobe launched the Content Authenticity Initiative (CAI), a consortium focused on building an attribution system for digital content. The insight behind CAI was that fighting disinformation could not rely solely on detecting fake content (a reactive approach destined to chase increasingly sophisticated forgery techniques), but had to start from certifying the origin of authentic content.

In parallel, Microsoft and BBC developed Project Origin, a research project aimed at combating media disinformation through provenance traceability. Project Origin focused specifically on the news sector, with the goal of creating a system enabling audiences to verify that an article, video, or image genuinely came from the outlet publishing it and had not been altered during distribution.

Which version of the C2PA specification is current?

In February 2021, these two initiatives converged in the founding of the Coalition for Content Provenance and Authenticity. The founding members, announced on 22 February 2021, were Adobe, Arm, BBC, Intel, Microsoft and Truepic, spanning creative software, chip design, broadcasting, semiconductors, cloud platforms and image authentication (C2PA founding press release). The decision to involve actors across the entire value chain, from hardware to software to media, reflected the understanding that a digital provenance system works only if the entire chain supports it.

The first official specification was released in January 2022. The specification has been revised several times since. The current version, 2.4, was published in April 2026 and adds, among other changes, an AI disclosure assertion, a receipt recording that a manifest has been stored in a manifest repository, and support for embedding manifests in HTML and structured text (Specification 2.4, section 5.3.1).

The decision to merge forces stemmed from the recognition that two parallel initiatives with overlapping objectives would fragment the ecosystem rather than strengthen it. A single open standard, governed by a multi-stakeholder consortium, had a greater chance of achieving the critical mass necessary to function in a global digital ecosystem.

How does a C2PA manifest record a file's history?

The core mechanism of the C2PA protocol is the manifest: a structured block of metadata embedded directly within the digital file. The manifest contains these categories of information:

• Assertions: declarations about the content's provenance, including the creation tool, declared author, and actions performed on the file (cropping, resizing, filter application, AI generation).
• Cryptographic signature: a digital signature based on X.509 certificates that binds the assertions to a verifiable identity and makes the manifest tamper-evident.
• Content binding (hash): a digital fingerprint of the file that inseparably links the manifest to the specific content, preventing the same manifest from being applied to a different file.

When content is modified by a C2PA-compatible tool, a new manifest is added without deleting previous ones, creating a digital chain of custody that documents the file's entire history. This additive model is a deliberate architectural choice: preserving previous manifests enables reconstruction of the complete transformation timeline, from the moment of original capture to the latest modification.

An important aspect to understand is that the C2PA manifest does not modify the visible content of the file. A JPEG image with a C2PA manifest appears identical to one without: provenance metadata is incorporated in a data structure separate from the visual content. This means non-C2PA-compatible tools can continue to read and display the file normally, even though they will not be able to interpret the provenance metadata.

Who uses C2PA today?

C2PA adoption has expanded from a small group of founders to a broad ecosystem: the Content Authenticity Initiative, the Adobe-led community that promotes the standard, reported more than 6,000 members in January 2026 (CAI, The State of Content Authenticity in 2026). However, the level of implementation varies significantly between those who have integrated C2PA into their products operationally and those who have simply joined the coalition as supporters.

How far have the founders implemented C2PA?

Among the founders, Adobe has the most advanced implementation. Starting with Photoshop and Lightroom, Adobe has integrated automatic content credentials writing across all major Creative Cloud products, including Firefly, its AI image generator. Every piece of content created or modified with Adobe tools can include a C2PA manifest documenting the entire editing chain.

Microsoft has integrated C2PA support in Bing and Microsoft Designer, automatically labeling AI-generated content with content credentials. Intel contributes on the hardware front, working on chip-level implementations that can ensure cryptographic signing directly in silicon. The BBC has conducted experiments in news gathering, testing the provenance workflow from field capture to publication.

Which cameras and generative models write C2PA?

The expansion of the C2PA ecosystem in 2025-2026 has seen the entry of key players across strategic sectors:

The turning point: phones that sign at capture and the generative AI labs

Google's Pixel 10 marked the turning point, bringing signing at capture from the professional niche to the mass market: Google says the Pixel 10 is the first lineup with Content Credentials built in across every photo taken with its native camera. Earlier in 2025, Samsung described the Galaxy S25 as the first smartphone lineup to support Content Credentials, but only on images edited with its Galaxy AI tools. Sony's PXW-Z300 extends this logic to professional video, a sector where verifiable provenance is particularly critical for broadcast journalism and documentary production.

On the generative AI front, the participation of OpenAI, Google DeepMind, and Meta is significant because it addresses the side of the equation that generated the urgency for the C2PA specification in the first place: the ability to generate synthetic content indistinguishable from authentic media. These players commit to labeling their outputs with content credentials that explicitly declare the AI-generated nature of the content, providing a provenance trail that, at least in theory, accompanies the content from generation to distribution.

What is the difference between C2PA and Content Credentials?

The term content credentials refers to the user-facing implementation of the C2PA standard. While C2PA defines the technical specification (manifest structure, cryptographic algorithms, metadata format), content credentials are what the end user sees: an icon, badge, or information panel showing content provenance.

The website contentcredentials.org, operated by Adobe's CAI, offers a public verifier where anyone can upload a file to examine its content credentials. This tool displays the manifest chain, associated signatures, and declared actions, making the content's history transparent.

However, as we will explore in the limitations section, the mere presence of content credentials does not guarantee that content is truthful: it only guarantees that the declared history is intact and signed by an identifiable entity. The distinction between "verifiable history" and "truthful content" is the critical node that determines the boundaries of what C2PA can and cannot do.

How does C2PA work technically?

Understanding the technical mechanisms of C2PA is essential for evaluating both its value and its limitations. The standard operates on interconnected levels: manifest structure, cryptographic system, and verification process.

What does a C2PA manifest contain?

A C2PA manifest is a structured data object in CBOR (Concise Binary Object Representation) format, embedded directly within the digital file according to container format specifications (JUMBF for JPEG, dedicated boxes for PNG, MP4, and other supported formats).

The manifest structure includes:

• Claim: the core of the manifest, which declares a set of assertions about the content and binds them through a cryptographic signature.
• Assertions: specific declarations. The most common include c2pa.actions.v2 (actions performed on content), c2pa.hash.data (binary content hash) and metadata assertions such as c2pa.metadata, which carry selected EXIF, IPTC or XMP fields. The schema.org CreativeWork assertion that earlier versions used for author information is deprecated in version 2.4 (Specification 2.4, Appendix C).
• Ingredient list: references to source content manifests, enabling provenance tracing even when multiple files are combined.
• Signature: the cryptographic signature authenticating the entire claim.

The specification supports both embedded manifests (incorporated within the file) and cloud-based manifests (stored on external servers and referenced via URL), to handle formats that do not support internal metadata or scenarios where the file must remain unaltered.

Cryptographic signatures and X.509 certificates

Every C2PA manifest is digitally signed using the X.509 standard, the same certificate system used for HTTPS and for qualified digital signatures under the eIDAS regulation. The signature identifies the signer named in the certificate and guarantees manifest integrity (any post-signing modification invalidates verification).

The C2PA signing system relies on a hierarchical chain of trust: a certificate authority (CA) issues certificates to signers, and the verifier checks that the certificate is valid and issued by a recognized CA. However, as highlighted by Hacker Factor's analysis in December 2023, before the official C2PA Trust List existed, the C2PA specification also permits self-signed certificates or certificates issued by CAs not included in official trust lists, creating a gray area where "anyone can sign anything" without the system preventing it.

This flexibility is intentional: it enables adoption even by small players and independent developers. But it introduces a fundamental risk: a manifest signed with an untrusted certificate has the same technical appearance as one signed by a verified organization, unless the verifier explicitly checks the trust list.

How is a C2PA manifest verified?

Verification of C2PA content works as follows:

1. Manifest extraction: the verifier reads C2PA metadata from the file.
2. Signature validation: verification that the cryptographic signature is valid and the certificate belongs to a recognized CA.
3. Integrity check: the content hash is recalculated and compared against the one declared in the manifest. If they don't match, content has been altered after signing.
4. Chain analysis: ingredient manifests are examined to reconstruct the file's complete history.

The public verifier at contentcredentials.org runs these checks and presents results in a readable format. Professional tools, such as those integrated into the TrueScreen platform, add a layer of forensic analysis that goes beyond technical validation of the manifest. The free C2PA viewer on truescreen.io runs the extraction, signature and integrity checks in the browser, with nothing uploaded; it reports who signed the manifest but does not look the signer up in a trust list.

How does C2PA differ from EXIF metadata?

Traditional EXIF metadata records basic capture parameters such as camera model, aperture, and GPS coordinates, but it offers no cryptographic protection. EXIF data can be edited or stripped by any image editor without detection, making it unreliable for provenance verification. C2PA addresses this gap by wrapping provenance data in a cryptographically signed manifest that uses SHA-256 hashes and X.509 digital certificates. While EXIF records "what settings were used," C2PA records "who created this file, with what tool, and what edits were made" in a tamper-evident format. However, C2PA does not replace EXIF: the two standards are complementary, with C2PA manifests often incorporating EXIF data as assertions within the manifest structure. The key distinction is verifiability: altering any byte of a C2PA-signed file invalidates its cryptographic hash, while EXIF modifications leave no trace.

What are the limitations of C2PA?

The limitations of C2PA are described in the coalition's own documents: the Explainer, the technical specification, currently at version 2.4 (April 2026), and the Security Considerations threat model. Each point below links to the section that states it.

• It does not say whether content is true. Content Credentials "do not provide value judgments about whether a given set of provenance data is 'true'", only whether it is well-formed, free from tampering, valid and trusted (C2PA Explainer 2.4, section 2; Specification 2.4, section 1.2).
• Adoption is opt-in. The standard is designed for "global, opt-in" adoption, so most files carry no credentials at all, and whether a tool records the use of AI depends on that tool (Explainer, section 2; Security Considerations, section 4.3.4.5).
• Credentials can be stripped. The threat model states that an attacker can download a file, remove its manifest and repost it, after which a viewer may show no provenance at all (Security Considerations, section 4.3.1.1). Soft bindings, a fingerprint or an invisible watermark, can match the file to a stored copy of the manifest (Specification, section 9.3), but they bring their own collision risks (section 4.3.2.6).
• A valid signature can cover false data. If a claim generator is compromised, "the resulting manifests would pass validation checks but would contain incorrect or misleading provenance information" (section 4.3.2.13). The hardware example is data injected between a camera lens and its processor to make the camera sign fake images (section 4.2.2.1).
• Trust depends on who received a signing key. "The C2PA does not currently specify requirements regarding issuance of claim signing keys" (section 4.3.2.4). Each validator decides trust through the trust lists it maintains (Specification, section 14.4), and trust in what a credential says rests on the relationship between its creator and its consumer, which the C2PA does not define (Explainer, section 7.5.1).
• Validators can disagree or be out of date. A validator working from an outdated trust list may display manifests signed with revoked credentials as valid (section 4.3.2.10). Independent testing published in April 2026 found the same image labelled valid by one tool and invalid by another (Golaszewski et al., arXiv 2604.24890).
• Signatures can expose the creator. A rarely used signing certificate can identify a person or a device (section 4.3.5.1). Pseudonymous identities, optional identity assertions and redaction reduce the risk where implementations offer them (section 2.6).

A C2PA manifest records what a file declares about its history; it does not show how the content was acquired. Content certified by TrueScreen, the Data Authenticity Platform, carries a C2PA manifest that any compatible viewer can read, but the certification rests on a forensic acquisition made at the source and recorded in the certification package itself, so it remains verifiable when a platform strips the file's metadata. The free C2PA viewer on truescreen.io shows what a manifest declares and who signed it, and runs entirely in the browser without uploading the file.

Why do platforms strip Content Credentials?

The most immediate and widespread limitation of C2PA is metadata loss during distribution. When an image with content credentials is shared on a platform that reprocesses files (compression, resizing, format conversion), C2PA metadata is typically stripped away. For a step-by-step demonstration of what removal actually deletes, and what stays in the file, see the guide on how to remove C2PA Content Credentials from an image, a video or a PDF.

The RAND Corporation, in an analysis published in June 2025 titled "Overpromising on Digital Provenance and Security", highlights that "the success of C2PA depends on end-to-end compliance by all elements of the ecosystem, but in an open ecosystem this is unrealistic." A simple screenshot eliminates any trace of provenance. An upload to a social media platform that recompresses images produces the same result. Format conversion using non-compatible tools erases the manifest entirely.

This creates an operational paradox: content that most needs verifiable provenance (content shared virally on social media) is precisely the content most likely to lose its C2PA metadata during distribution.

Do the proposed solutions prevent metadata loss?

Proposed solutions, such as cloud-based manifests or complementary imperceptible watermarking, mitigate the problem but do not solve it. Cloud manifests require the server to be reachable and the file reference to survive reprocessing. Imperceptible watermarking has its own limitations in terms of robustness and information capacity.

This is why TrueScreen, the Data Authenticity Platform, does not rely on the embedded manifest alone: each certification is backed by a forensic acquisition record kept inside the certification package itself, which remains verifiable independently, even if a platform strips the file's original metadata.

The scale of the problem becomes evident when analyzing the typical flow of viral content: an image with content credentials is published on a website, shared on Twitter (which recompresses the image stripping metadata), screenshotted by a user, shared on WhatsApp (further recompression), and finally republished on a blog. At each step, the probability of C2PA metadata survival decreases dramatically. By the end of the chain, the content reaching the widest audience is almost certainly devoid of any provenance trace. When the content is still online, the practical fallback is to move the proof up a level and certify the web page that publishes it, sealing what was visible, at which address and on which date.

Do Durable Content Credentials stop metadata stripping?

To counter metadata stripping, the C2PA ecosystem is moving toward Durable Content Credentials. Instead of relying only on metadata embedded in the file (hard binding), durable credentials add a soft binding: an invisible watermark and a perceptual fingerprint of the content. Watermarking systems such as Google SynthID embed a signal that can survive common transformations such as re-encoding, resizing, and screenshots, letting a verifier recover the provenance manifest even after the original metadata is gone.

This mitigates stripping but does not eliminate it. Watermarks can be degraded by heavy editing, cropping, or adversarial removal, and fingerprint matching depends on the content staying in a reachable database. More importantly, durable credentials still document an asset edit history, not how the content was captured: a forged document photographed with a compliant camera receives perfectly valid credentials. This is why a record of the capture itself, made at the source, remains necessary alongside C2PA.

Does a valid C2PA manifest prove the image is true?

This is the most important conceptual limitation of C2PA, and the least understood. The standard certifies that content was created by a specific tool, signed by a specific entity, and underwent specific modifications. It does not certify that the content faithfully represents reality.

A concrete example: a photograph taken with a C2PA-compatible device will have a perfectly valid manifest declaring "captured with camera X at time Y in location Z." But C2PA does not verify that the photographed subject is what the author claims it to be. A staged photo, a forged document photographed with a certified device, a reconstructed scene: all produce technically impeccable C2PA manifests.

This limitation is particularly relevant in legal disputes and insurance verification. An adjuster who documents non-existent damage with a C2PA-compatible camera produces digital evidence with perfectly valid manifests. An individual who photographs a forged document with a phone that signs at capture, such as a Pixel 10, generates a file with technically impeccable content credentials. In both cases, C2PA faithfully certifies the file's history, but that history says nothing about the truthfulness of the photographed subject.

As the RAND Corporation emphasizes, "C2PA signing tools do not verify that metadata is accurate." The manifest attests that tool X declared certain information, not that the information is true. This distinction is critical in high-stakes contexts such as legal proceedings, investigative journalism, or insurance assessment, where the truth of content matters more than its technical history.

Can C2PA expose the identity of the creator?

An often-overlooked aspect of C2PA concerns its privacy implications. Content credentials, by design, embed information about the creator's identity: name, organization, digital certificate, and potentially precise geolocation data and timestamps.

An investigation by Fortune published in September 2025 revealed that "Big Tech sees C2PA as a way to combat deepfakes, but the standard puts user privacy on the line." The concrete risk is doxing: the non-consensual exposure of a content creator's identity through provenance metadata. For journalists operating in authoritarian contexts, whistleblowers, activists, and domestic violence survivors, the automatic association between content and identity can have severe consequences.

The World Privacy Forum published a comprehensive technical analysis in 2025 on privacy, identity, and trust in C2PA, highlighting the structural tension between provenance transparency and identity protection. Proposed solutions, such as pseudonymous certificates, exist in the specification but are rarely implemented in practice.

Can C2PA be circumvented?

The most alarming limitation of C2PA concerns the possibility of creating forged content with technically valid manifests. These are not theoretical vulnerabilities: they have been publicly demonstrated.

According to Hacker Factor's December 2023 analysis, a Content Authenticity Initiative webinar in November 2023 showed that authenticated forgeries can be created in minutes using standard tools. The fundamental problem, at the time, was that C2PA imposed no constraints on who could sign what: anyone could obtain a certificate and sign any content with any set of metadata. Since 2025 the C2PA Trust List decides which signers validators show as trusted, but signing itself is still open to anyone. The worst-case scenario described by Hacker Factor is particularly troubling: forged content with a valid C2PA manifest is presented as evidence in court. The defendant cannot prove the content is fake because the C2PA system shows "no evidence of tampering."

The clearest real-world case came from a camera maker. Nikon added C2PA signing to the Z6III with a firmware update in August 2025 (Nikon). In September 2025 Nikon temporarily suspended the service (Nikon notice). According to PetaPixel and Digital Camera World, users had shown that the camera could produce a validly signed image containing content it had not captured, and Nikon revoked the C2PA certificates it had issued for the Z6III.

Another documented case involves LinkedIn, which implemented content credentials support but with problematic results: date display bugs for C2PA certificates and failure to show the Content Credentials logo despite valid C2PA metadata being present in the file. These episodes demonstrate that even implementation by major platforms presents significant issues.

Why is the problem structural?

The core of the problem is structural: C2PA operates as a history notarization system, not as a truth verification system. A notary certifies that a document was signed by a person, not that the document's content is true. Similarly, C2PA certifies that a manifest was created by an identifiable entity, not that the assertions in the manifest correspond to reality.

Bad actors can also undermine trust in the system indirectly: obviously real and authentic content can have invalid or entirely absent C2PA metadata simply because it left the compatible ecosystem during processing. If users and platforms begin treating the absence of C2PA as a signal of suspicion, a system emerges where perfectly legitimate content is penalized, while forged content with valid manifests is erroneously considered trustworthy.

Who can sign content that validators show as trusted?

Signing is open to anyone with a key, but a validator shows a manifest as trusted only when the signing certificate chains to a trust anchor on the lists it maintains (Specification 2.4, section 14.3; section 14.4). Since mid-2025 those certificates come through the C2PA Conformance Program, and they are issued for conforming products (Generator Products), not for individuals (C2PA FAQ).

In practice, an independent photographer or a small newsroom gets credentials that validators show as trusted by using a conforming camera, phone or app, such as a Pixel 10, rather than by buying a personal signing certificate. Anyone can still sign with a self-signed or unlisted certificate, but validators will not show the result as trusted.

What is the C2PA Trust List, and who controls it?

The C2PA Trust List is the C2PA-managed list of certificate authorities that issue signing certificates to hardware and software signers (Specification 2.4, section 2.3.15). The coalition launched it together with its Conformance Program in mid-2025 and froze the earlier Interim Trust List on 1 January 2026, with no new entries or updates after that date (C2PA, Conformance). To receive a certificate from a listed authority, a generator product, such as a camera app or an editing tool, must pass a conformance and security evaluation and be accepted into the program; fees are set by each certification authority (C2PA FAQ).

Arguably, the open question is governance: the list is run under the coalition's Conformance Program, so the coalition decides which products and certification authorities qualify. For a standard that aims at universal adoption, trust ends up resting on the same industry that builds the conforming products, and content signed outside those products appears as untrusted however genuine it is.

Is C2PA enough for the EU AI Act?

The European and international regulatory landscape is converging toward mandatory transparency for content generated or modified by artificial intelligence. Signed provenance metadata of the kind C2PA provides is one of the techniques the Code of Practice expects, and the Code pairs it with a watermark rather than relying on it alone.

The EU AI Act, in Article 50, establishes transparency obligations for AI-generated content that apply from August 2, 2026. Providers of AI systems that generate synthetic content (images, audio, video, text) must ensure that outputs are marked in a machine-detectable manner as artificially generated. Under the Digital Omnibus on AI (Regulation (EU) 2026/1744, in force since 27 July 2026), systems already on the market before that date have until December 2, 2026 to meet the machine-readable marking requirement of Article 50(2); the other Article 50 obligations have no grace period.

Article 50 obligations fall on providers and deployers of AI systems. For organizations that need the opposite proof, that a photo, a video or a document was captured and not generated, TrueScreen, the Data Authenticity Platform, certifies the acquisition at the source, and the certified file also carries a C2PA manifest that any compatible viewer can read.

On the practical side, the guide on how to certify a photo covers the acquisition steps, and the use case on certified journalism and digital evidence shows how newsrooms apply the same method to visual material.

The European Commission published the final Code of Practice on transparency of AI-generated content on 10 June 2026. The Code is voluntary. For machine-readable marking, signatories commit to digitally signed, time-stamped metadata and to an imperceptible watermark meant to complement it; fingerprinting or logging is an optional further layer and is not considered sufficient on its own (Code of Practice, Measure 1.1). The Code does not name C2PA, but it notes that, among marking techniques, only digitally signed metadata already has established interoperability standards (Measure 3.4). Signatories also commit, to the extent technically feasible and with limited exceptions, to keep existing metadata markings and to forbid deployers and other third parties from removing them (Measure 1.2).

The Code's pairing of metadata with a watermark is consistent with the C2PA's own threat model, which states that a screenshot, a social media upload or a format conversion can remove the manifest (Security Considerations, section 4.3.1.1).

What do eIDAS and the US Federal Rules of Evidence require?

Under the eIDAS regulation, which establishes the framework for electronic identification and trust services across the European Union, digital signatures and qualified electronic seals have established legal recognition. C2PA uses X.509 certificates, the same format used by eIDAS qualified certificates, but a C2PA signature alone is not a qualified electronic signature or seal under eIDAS: nothing in C2PA requires the signer's identity to be verified the way eIDAS requires for qualified certificates.

In the United States, the Federal Rules of Evidence (particularly Rules 901 and 902) govern the authentication of digital evidence. While C2PA metadata may serve as supporting evidence, courts may require additional authentication. The mere presence of a C2PA manifest does not, on its own, establish that the content is what it claims to be (Rule 901).

Regulated sectors and eIDAS 2.0

Organizations in regulated sectors often need evidence of how content was captured, which C2PA alone does not provide.

The eIDAS 2.0 regulation, in force since 2024, introduces the European Digital Identity Wallet and new categories of trust services. C2PA signing alone is not a qualified signature or seal under eIDAS.

Why is C2PA alone not enough as evidence?

C2PA records the history a file declares; a forensic acquisition documents how the content was captured. They answer different questions, and they intervene at different points: C2PA can sign at capture on supporting devices or later in editing tools, whereas forensic acquisition controls the capture process itself. TrueScreen, the Data Authenticity Platform, certifies content at the source with a forensic methodology: the acquisition runs in a controlled environment, the device and the captured data are checked before sealing, and the result is sealed with an official digital seal and a qualified timestamp, both recognized internationally. The certified file also carries a C2PA manifest that any compatible viewer can read. Certification documents how the content was acquired, not what stood in front of the lens: a staged scene remains an authentic recording of a staged scene. C2PA metadata can be stripped during distribution, while the certification package is self-contained and stays verifiable by a third party without relying on TrueScreen. How much weight that evidence carries is always for the court to decide.

C2PA certifies history, forensic methodology certifies how content is acquired

The fundamental difference between the C2PA protocol and a forensic acquisition system is the point of intervention in the value chain.

How forensic acquisition works instead

Forensic methodology operates on a different principle: it does not merely sign existing content, but controls the acquisition process itself. TrueScreen certifies authenticity at the source: the platform acquires content directly from the source (device camera, web page, chat, document) in a controlled environment, where alteration is prevented during acquisition and detectable afterwards. The certified file combines technical provenance (C2PA) with a forensic record of how the content was captured.

The difference is analogous to that between a surveillance camera and an expert who supervises the recording. C2PA is the surveillance camera: it records what passes in front of the lens and signs the file. Forensic methodology is the expert who checks the equipment and the capture conditions, keeps the recording out of reach of manipulation while it is made, and documents every step. Neither can tell whether the scene itself was staged: what the combination adds is a verifiable account of how, when and where the content was captured, on top of the history the file declares.

The combined approach: Content Credentials + forensic acquisition

TrueScreen exemplifies the combined approach through its C2PA integration. The platform operates on both fronts:

• Reading and validation: TrueScreen reads and validates C2PA manifests already present in incoming files, extracting and displaying the full chain of provenance claims (creator identity, tool used, subsequent modifications) to help users assess content trustworthiness before certification.
• Writing: TrueScreen writes a C2PA manifest into certified content, which any compatible viewer, platform or verification tool can read and validate independently.
• Forensic acquisition: in parallel, TrueScreen acquires the content in a controlled environment, with a chain of custody that begins at the source rather than at the first editing tool.

This approach resolves the main limitations of C2PA in isolation:

• Metadata stripping becomes less critical because forensic certification exists independently of the manifest embedded in the file.
• The trust problem is mitigated because forensic methodology certifies authenticity at the source, not just the declared history.
• The forgery risk is reduced because content cannot be altered while it is acquired, and any later change is detectable through the seal and hash.

Use cases: journalism, insurance, legal proceedings

The combined C2PA + forensic acquisition approach finds concrete application in domains where content authenticity has direct consequences:

Journalism: a photojournalist in the field uses a C2PA-enabled device to capture images. The manifest certifies the image was taken with that camera, at that time, in that location. But the manifest can be stripped as soon as the image is shared, and it says nothing about how the capture was made. Forensic acquisition adds a record of how and when the material was captured, which stays verifiable after a platform strips the manifest.

Insurance: a claims adjuster documents damage with photos and video. C2PA content credentials attest that images are original and unretouched. But the insurance company also needs to know where and when the photos were taken. Certified acquisition with TrueScreen records the place and time reported by the device sensors, on a device checked before sealing, and shows that the content has not changed since; whether the damage itself was staged remains part of the adjuster's assessment.

Legal proceedings: in court, the mere presence of a C2PA manifest is not sufficient to confer evidentiary value on digital content. A certified acquisition gives the court a documented method and a self-contained package it can examine, which can help support authentication under Rule 901 of the Federal Rules of Evidence and equivalent rules elsewhere, depending on jurisdiction and case context. The decision always stays with the court.