Back to the episode map

Evergreen

Why Media Provenance Beats Guessing What Is Fake

Media provenance preserves evidence of origin and change. Visual tells and AI detectors estimate patterns. Learn why verification needs both context and records.

Aug 4, 20266 min readBy Dalton Anderson

Why Provenance Beats Guessing Whether Media Is Fake

Media provenance is more useful than guessing because it can preserve evidence about origin and change. A visual impression or detector score usually estimates whether a file resembles known synthetic patterns. That estimate may help, but it does not provide a chain of custody.

Provenance is not perfect and does not prove truth. It still improves the question. Instead of asking whether an image feels real, a reader can ask who created the available record, what the record says, whether it remained intact, and what outside evidence supports the caption.

The real-or-fake question combines several problems

People often say "is this real?" when they mean one of at least five things.

They may want to know whether a camera or generator created the pixels. They may want to know whether an editor changed a particular feature. They may be asking whether the person, place, or event exists. They may question whether the caption identifies the correct time and location. They may simply want to know whether the publisher is trying to mislead them.

No single technical signal resolves all five.

QuestionStronger evidence
Where did this file come from?Original source, signed provenance, custody record
How was it transformed?Edit history, ingredients, version record, signed actions
Was it generated by a supported tool?Tool-specific watermark or generation assertion
Did the depicted event occur?Independent reporting, records, witnesses, other media
Is the communication misleading?Full context, claim, omissions, audience, and intent evidence

Visual inspection addresses none of these directly. It can expose a clue, but the clue must be connected to the question.

Appearance is becoming a poor custody record

Early synthetic images trained people to look for a narrow class of errors. A hand with six fingers was memorable. So were invented lettering, asymmetric jewelry, and waxy skin.

Those examples made image literacy feel like connoisseurship. A careful observer could supposedly recognize the machine. But the skill never came with a stable standard. Models changed, outputs varied, and ordinary cameras and editors produced their own defects.

The preserved E093 monologue captures this shift as a personal threshold. Dalton Anderson looked at recent Nano Banana Pro and Z-Image examples and believed casual inspection had lost much of its value. The episode called that threshold the synthetic Rubicon.

That is a dated observation, not a universal benchmark. Google now documents newer image models alongside Nano Banana Pro, and the Z-Image project continues to publish checkpoints and updates in its official repository. The durable point is not which model looked best in one screen share. It is that appearance provides no stable record of origin.

Detectors estimate patterns, not history

An automated detector can analyze features and return a score. That is useful when its evaluation conditions resemble the file being tested. It becomes weaker when the content comes from an unfamiliar generator, passes through compression, is resized, is cropped, or is deliberately modified.

The current NIST synthetic-content report recommends evaluations that reflect subject matter, cultural context, benign distortions, attacks, sample size, and generators not seen in training. NIST also emphasizes the cost of false positives, especially when a human creator could suffer reputational harm.

The GenImage benchmark paper published at ICCV 2025 focuses on the gap between idealized and real-world evaluation. Sharing operations and transformations matter because internet media rarely arrives as a pristine benchmark file.

A detector may support "this model assigned a high synthetic probability under these conditions." It should not be silently translated into "the publisher lied."

Provenance creates a different kind of evidence

The C2PA specification provides a way to bind a signed provenance record to an asset. Participating systems can record creation, editing, ingredients, and other assertions. A validator can inspect the signature and determine whether the available record remains internally consistent.

That is evidence of a recorded process. It has a named signer and a structure that can be checked. A detector's estimate is different. It analyzes the current file without reconstructing a signed history.

flowchart TD
    A["Media claim"] --> B["Appearance"]
    A --> C["Detector"]
    A --> D["Provenance"]
    A --> E["Corroboration"]
    B --> F["Visual hypothesis"]
    C --> G["Pattern-based estimate"]
    D --> H["Recorded origin and transformations"]
    E --> I["Evidence about the depicted event"]
    F --> J["Qualified assessment"]
    G --> J
    H --> J
    I --> J

The provenance branch is usually stronger for questions about origin and editing. The corroboration branch is stronger for questions about events and captions. Neither should absorb the other.

A valid record can accompany a false story

Suppose a credential-enabled camera records an actor performing a staged rescue. The file can have valid capture provenance. A dishonest account can still post it as footage of an actual emergency.

The credential has not failed. It accurately records a capture path. The caption is the problem.

Now reverse the case. A witness uses an old phone to record a genuine event. A messaging application strips metadata, and the only available copy has no credentials. The absence of provenance weakens what a distant reader can verify. It does not turn the event into fiction.

These paired cases are why authenticity and truth need separate treatment. [[Authenticity Is Not the Same as Truth]] states that rule in its shortest form.

Provenance has real failure modes

Provenance can be absent because adoption is incomplete. It can be stripped by an incompatible distribution path. A signer can record a limited or misleading assertion. A capture device can faithfully sign a staged scene. A compromised system can create bad records before later validation. A reader can ignore warnings or misunderstand the display.

The C2PA system addresses some implementation risk through signatures, trust lists, and a conformance program. It cannot remove the need to decide whether a signer is relevant and whether the real-world claim is supported.

This is still better than aesthetic confidence because the weakness is inspectable. A missing chain can be named. An unknown signer can be identified. A broken validation can be reported. A claim can be compared with independent evidence.

The better verification norm is layered

A strong assessment begins with the original publisher and the exact claim. It uses signed provenance when available, tool-specific watermarks when relevant, metadata as contextual evidence, detector output as a qualified estimate, and independent corroboration for the depicted event.

That process will not always produce a binary answer. It will produce conclusions that match the evidence: source supported, caption contradicted, generation signal detected, provenance incomplete, or origin unknown.

The purpose of verification is not to sound certain. It is to make the smallest defensible claim and preserve the path another person can review.

[[What Are Content Credentials]] explains the signed record in plain language. [[Can You Tell If an Image Is AI Generated]] turns the layered model into a practical investigation.

This essay was developed from the preserved E093 transcript, current C2PA and NIST materials, official model records, and primary detection research. AI assistance was used for research organization, drafting, and validation. Publication remains unauthorized.

Sources

Follow the evidence.

  1. support.google.com: 14328491support.google.com
  2. iptc.org: iptc standardiptc.org
  3. c2pa.org: faqsc2pa.org
  4. FTC Disclosures 101ftc.gov
  5. eur-lex.europa.eu: ojeur-lex.europa.eu
  6. c2pa.org: conformancec2pa.org
  7. github.com: Z Imagegithub.com
  8. ftc.gov: consumer reviews testimonials rule questions answersftc.gov
  9. FTC: Endorsements, Influencers, and Reviewsftc.gov
  10. deepmind.google: synthiddeepmind.google
  11. iptc.org: IPTC PhotoMetadata 2025.1iptc.org
  12. nist.gov: reducing risks posed synthetic content overview technical approaches digital contentnist.gov
  13. openaccess.thecvf.com: Li Bridging the Gap Between Ideal and Real world Evaluation Benchmarking AI Generated ICCV 2025 paperopenaccess.thecvf.com
  14. asa.org.uk: testimonials and endorsementsasa.org.uk
  15. deepmind.google: prodeepmind.google
  16. arxiv.org: 2507arxiv.org
  17. spec.c2pa.org: C2PA Specificationspec.c2pa.org
  18. ndsa.org: levels of digital preservationndsa.org
  19. deepmind.google: identifying ai generated images with synthiddeepmind.google
Why Media Provenance Beats Guessing What Is Fake