What to Record When Checking a Potentially Synthetic Video

A questionable video can move faster than the information needed to assess it. A clip may arrive without its original post, with a new caption, or after repeated compression and reposting. If you only save a detection result, the next reviewer may not know what they are actually looking at.

A video check can provide signals worth investigating. It cannot prove who created the video, where it first appeared, why it was made, or whether the claim shown in it is true. A useful review record keeps those separate.

ZeroTrue supports detection for text, images, audio, video, and code. For a video review, use any result as one part of your notes, alongside the source and the surrounding circumstances.

Start with the version in front of you

Record the exact version you reviewed. If there is an original link, save it. If someone sent the clip directly, note who sent it and when you received it. Do not assume that a file with the same scenes is the same version: a repost may have a different soundtrack, a shortened ending, added subtitles, or a new caption.

Write down:

• the original source or link, if available
• the date and place where you encountered the video
• the caption, claim, or message attached to it
• the account, channel, or person who shared it
• relevant surrounding context, such as an earlier post or a reply that changes the meaning
• known reposting, trimming, subtitling, or editing history

This is not busywork. It lets another person trace what was available at the time of the decision, rather than trying to reconstruct it from memory.

Note conditions that can change what you see

A detection result applies to the submitted material, not to every possible version of the scene. Record conditions that may affect both the clip and its review: screenshots, transcoding, compression, noise, editing, and social-media reposting. Also note whether you reviewed a full video, a short excerpt, a screen recording, or a clip downloaded from another platform.

These details matter because sample quality, compression, editing, language, generator shifts, screenshots, transcoding, noise, and social-media compression can affect output. They are reasons to be careful with interpretation, not reasons to discard the review altogether.

Before submitting sensitive video content, review the current privacy and security terms. That is especially important when a clip includes private conversations, personal information, or material connected to a regulated workflow.

Keep four kinds of notes separate

Mixing facts, assumptions, and detector output is how a cautious check becomes an overconfident conclusion. Use four labels in your record.

Observations are things you can directly see or hear. For example: “The speaker’s mouth is partly obscured for most of the clip” or “The audio cuts at 00:12.”

Source claims are what the caption, sender, or uploader says. For example: “The repost says this was recorded today in a particular location.” Attribute the statement instead of treating it as established fact.

Detection signals are what the result indicates. Supporting evidence may include timestamps, annotations, or signal context depending on the content type and result. Record the relevant moment and what the result points you toward reviewing, without translating it into an authorship claim.

Open questions are what remains unresolved: Is there an earlier upload? Does the claimed location match other available context? Can the sender confirm the message through a channel you already trust?

A worked record example

Imagine that you receive a 20-second video in a group chat. Its caption says that it shows a public official making an announcement that could affect your community.

Your review record could say:

• Version reviewed: a 20-second file received in the group chat on the date you encountered it.
• Source: no original post supplied; the sender says it came from a social-media account.
• Claim attached: the caption attributes the statement to the official and says it was recorded that day.
• Context: the clip begins mid-sentence and ends before any location or event is visible.
• Known conditions: the file was forwarded in chat and may have been compressed; no earlier version has been located.
• Detection notes: record any relevant timestamps or annotations from the result, along with the fact that they are signals for review.
• Open questions: can an official channel, a trusted news source, or the alleged speaker confirm the statement? Is there a longer version with verifiable context?

The next decision is proportionate to what is at stake. For a casual post, you may simply avoid sharing it as fact. For a consequential claim, pause and seek confirmation from a source that can verify the event or speaker. Do not treat either a convincing-looking clip or a single detection result as the final answer.

Video review checklist

Before you share, report, or act on a questionable video, make sure your record includes:

• The version reviewed and where it came from
• The date you encountered it
• The caption or claim attached to it
• Relevant surrounding posts, messages, or context
• Known edits, reposts, screenshots, compression, or transcoding
• Clear separation between observations, source claims, detection signals, and open questions
• Any timestamps, annotations, or signal context worth another look
• A next step that matches the importance of the claim

A complete record does not turn uncertainty into proof. It makes uncertainty visible, so the next reviewer can check the right thing instead of inheriting an unsupported conclusion.