Private digital intelligence bureau Lawful OSINT · Cyber monitoring · Due diligence
Media analyst comparing video frames, audio continuity and source provenance in a London laboratory

Synthetic media guide · 12 min

Verify synthetic or manipulated media without relying on one spectacular clue.

A visual artefact, an unusual voice or an automated detector is not a verdict. Strong verification begins with provenance, context and independent confirmation.

Published Updated Publisher and method: IIS

At a glance

Four rules for a useful review.

  • Find the origin before hunting for defects.
  • Preserve the file and discovery context.
  • Combine independent lines of evidence.
  • Use confidence levels, not intuition.

Step-by-step method

A reproducible path from question to conclusion.

  1. 1

    Preserve what you received

    Keep the original file, message, address, time, apparent sender and discovery channel. Messaging recompression may remove useful information.

  2. 2

    Find the earliest publication

    Trace reposts, search for earlier versions and identify the first known account or site. An older copy may reveal different framing or caption.

  3. A chart being explained with its context document — AI-generated photograph
    3

    Check the context

    Verify location, weather, chronology, people, objects and visible events using independent dated sources.

  4. 4

    Examine continuity

    For video and audio, inspect transitions, motion, shadows, reflections, synchronisation and cuts. For images, compare edges, perspective, repetition and compression zones.

  5. Review of a digital-wallet authorization with a security key.
    5

    Use metadata carefully

    Metadata can guide the review but may be absent, changed or stripped. Consistency supports a case; absence does not prove fabrication.

  6. 6

    State a graded conclusion

    Distinguish consistent with available evidence, probably manipulated, probably synthetic or undetermined. State limits and the next check that could change the assessment.

Provenance outweighs a single artefact

Generation and editing tools change quickly. Checklists of supposed defects become outdated and can falsely discredit authentic media.

A coherent chain of provenance, independent contemporary publications and verifiable scene details usually matter more than an opaque detector score.

Use tools as instruments, not judges

Reverse-image search, frame review, spectrograms and metadata analysis each answer a limited question. Record the result, date, tool version and tested hypothesis.

An automated score is useful only when its scope, error rate and media type are understood. Do not publish a percentage without explanation.

Avoid amplifying a false item

Do not repost the complete item merely to ask whether it is fake. Describe the concern, share the minimum necessary and keep a separate working copy.

When a person is targeted, consider harassment, defamation, fraud and privacy risk before sharing.

Separate file, transformation and scene

A platform may recompress media, remove metadata or create thumbnails. Different bytes do not prove scene manipulation. An internal timestamp may concern the file rather than the event: preserve its value and context before interpreting it.

Assess provenance declarations

Record tool, signer and declared operations where provenance exists. Separate technical validation from trust in declarations. Independently check caption, location and date. Documented provenance may accompany a misleading caption; absence may result from copying.

Reading technical evidence

A hash compares files; it does not authenticate their story

SHA-256 produces a 256-bit digest, represented here by 64 hexadecimal characters. It is calculated from the file’s bytes.

Field or situation and its interpretation
Observed itemWhat it means
Renamed copyThe name is not part of the calculation; the content can retain its hash.
Recompressed image or resaved documentBytes may change even when the document looks identical.
Hash calculated todayIt proves neither creation date, authorship nor authenticity of the scene.

Record algorithm, digest, file and collection context. Compare against a reference retained separately.

  1. Retained file
  2. SHA-256 digest
  3. Compare with the reference

Calculate and compare a file hash locally →

NIST — FIPS 180-4

Apply the method

Separate media provenance from the truth of its caption

Seek the earliest known publication, original context and independent views. A genuine image can carry a false caption. Examine the visual content, claimed location and claimed date separately: disproving one does not establish the others.

Retain the original link or file, circulating caption, searches and earlier versions. State when only a cropped copy is available. Detection scores and visual clues are not conclusive. Provenance or marking may document file history without proving the depicted event; their absence does not prove synthesis. Report an appropriately bounded conclusion rather than an unsupported accusation.

Origin
Seek the creator, date and earliest known publication.
Context
Compare location and event with independent evidence.
Conclusion
Distinguish unverified from demonstrated false.

Fictional example: viral video. A supposedly recent protest clip has a longer version published years earlier. The reviewer corrects the date before assessing possible visual manipulation.

Can an AI-detector score settle the question?

No. Examine provenance, context and the tool’s limitations; the score alone is an indication.

Try the reasoning

A detector labels an image synthetic with no other evidence. Can you publish an accusation?

Reasoning: No. State uncertainty and seek provenance, context and earlier versions.

NIST — Reducing Risks Posed by Synthetic Content

Read the original record

Read Content Credentials without treating them as a verdict

C2PA information concerns provenance and declared operations. Technical validation alone does not establish that a depicted scene is true.

Fields to retain and interpretation limits
ItemRecord to retainLimit
Examined fileExact file version and tool used.Cropping or a platform copy can lose information.
ProvenanceSigner, declared actions and the exact validation result. Record the tool name and version.Log an absent credential, an untrusted signer or a failed integrity check as distinct observations.
ContextLocation, time and caption corroborated separately.Missing credentials do not prove AI generation.

C2PA — Content Credentials, version 2.5

Worked example

Two detectors disagree about the same video

Fictional teaching case, not a client investigation.

Does the content document the claimed event independently of detector verdicts?

Observation, interpretation and limit
ObservationWhat it establishesWhat remains unproven
Two tools classify the same compressed file differently.Tool outputs conflict for this version.Neither fabrication nor authenticity is established by consensus here.
A longer version shows a caption absent from the short extract.The initial framing omitted context.The new caption remains a claim requiring verification.
A visible landmark does not match the place named in the examined post.An observed marker contradicts the proposed geographic attribution.That finding alone does not determine how the video was produced.

Conclusion to record

Event attribution is unresolved. Keep the versions and contradictory landmark; do not treat an AI verdict as evidence that an event occurred.

What would change the conclusion?

Seek original publication, full sequences and independent place and date markers.

Check your reasoning

Can real footage with a false caption and synthetic footage cause similar harm? Are the checks required identical?

· Open the verification log

Your working sheet

Turn the method into a documented review.

For each point, record what the material actually supports. “Supported” applies to the specific observation, not to the entire case. A contradiction needs explanation; missing material remains an open question.

  1. Define the question
  2. Record the source
  3. Test the observation
  4. State the limits

Entries stay in this page until you leave or reload it. Nothing is saved or submitted by this tool. Use neutral references instead of personal data or credentials.

1. Origin

Received file, earliest located publisher and reposting chain.

Limit: The earliest found occurrence may not be the original.

2. Context

Claimed place and date, plus independently corroborated visible details.

Limit: Real media can be used in a false context.

3. Automated detection

Tool, version, analysed format and stated limitations.

Limit: A detector score cannot establish fabrication on its own.

How to write a useful conclusion
Editorial examples, not findings about your case
MaterialUseful wordingNext check
One dated sourceThe consulted source stated X on the recorded date.Check its origin and whether it still applies.
Multiple copies of one claimSeveral pages repeat X; independent corroboration is missing.Find the original and a source with independent evidence.
Conflicting sourcesA states X while B states Y; the difference is unresolved.Compare dates, scope, identifiers and definitions.
No matching resultNo result was found in the recorded scope.Describe queries, coverage and access limitations.

What to check and what to record

Use this grid to turn the method into a reviewable case file. A missing item remains an open question. The interpretation limit prevents a finding from becoming an unsupported conclusion.

Topic-specific checks
CheckUseful recordInterpretation limit
OriginReceived file, earliest located publisher and reposting chain.The earliest found occurrence may not be the original.
ContextClaimed place and date, plus independently corroborated visible details.Real media can be used in a false context.
Automated detectionTool, version, analysed format and stated limitations.A detector score cannot establish fabrication on its own.

Common pitfalls

Four shortcuts that weaken the result.

Hunting for one defect

Odd details may result from compression, motion, lighting or ordinary editing.

A model and sketches documenting a project's stages — AI-generated photograph

Trusting one detector

Performance varies by model, format and transformation.

Losing the original

A screenshot often removes the file, audio and metadata needed for review.

Confusing false context with false media

Authentic media can be paired with a false date, place or caption.

Practical questions

Frequently asked questions.

Does metadata prove authenticity?

No. It may support a timeline or reveal processing, but it can be removed or changed.

Can deepfakes be spotted by eye?

Some inconsistencies may be visible, but no visible artefact proves nothing. Provenance and corroboration remain essential.

Should a detector score be published?

Only with its context, limitations and other evidence. An isolated percentage can mislead.

Public references

These primary references support the checks described here. The sequence and working sheet are an IIS editorial method; a cited organisation does not endorse this guide. Read each reference within its stated date, jurisdiction and scope.

NIST AI 100-4 — Synthetic content (2024). Technical overview of provenance, watermarking and detection approaches. These are different signals with different limits; a detector output must be interpreted within its tested conditions, rather than as a universal authenticity verdict.

Editorial scope

Published by Internet Intelligence Service on 15 September 2026. Last content update: 15 November 2026. This educational guide describes a lawful, defensive method. It is not legal advice, an emergency service or authority instruction.

Find primary portals and their limitations

Editorial responsibility, examples and corrections