A downloaded video does not establish who created it, when or where it was recorded, or whether its caption is accurate. First preserve the post’s visible context, then keep a permitted local copy, examine several keyframes, trace earlier appearances, and corroborate claims with independent evidence.

Treat these as separate questions: Is the footage genuine? Is its context accurate? Has its soundtrack changed? Real footage can support a false claim when someone adds a misleading caption or replaces the audio.

Record the post’s context first

Before collecting material, check applicable rights, privacy requirements, and your organization’s evidence-handling rules. Public visibility does not automatically authorize copying or redistribution.

Record the details below while the post remains accessible. Preserve what the page actually shows, not what you assume it means.

Field What to record
Post URL Complete individual-post address
Account handle Exact username
Display name Name shown during capture
Caption Full text, including attribution
Visible posting detail Exact date or relative timestamp
Claimed location Caption claim and location tag
Claim being checked Specific, answerable assertion
Capture time Date, time, and time zone
On-screen text Overlays, subtitles, signs
Audio Speech, music, notable sounds
Tagged accounts Handles and stated relationships
Relevant comments Attribution, corrections, firsthand claims
Capture responsibility Researcher or organization
Rights and handling Permission, restrictions, sensitive details

For example, write capture time as 2026-06-14T15:42:00+01:00, rather than “this afternoon.” If the post displays “3 days ago,” record that exact wording alongside the capture time. Do not silently convert it into a precise posting date.

  1. Capture the surrounding context. Take screenshots showing the account, caption, visible timestamp, and relevant attribution. Avoid collecting unrelated private information.
  2. Separate claims from observations. “Caption says downtown flooding today” is a claim; “water covers a road” is an observation.
  3. Distinguish uploader from creator. The account sharing the clip may be a repost account, witness, broadcaster, or unrelated commentator.
  4. Record relevant comments carefully. A comment identifying a location is a lead, not independent proof of that location.

Screenshots preserve visible context, but they do not establish that the caption or account’s claims are true.

Preserve a local copy and companion record

Viewing plays the content. Instagram’s in-app Save feature bookmarks it for later access. Neither should be confused with keeping a separate media file on your device.

Use this workflow for accessible content you are permitted to retain:

  1. Check access and permission. Confirm that the post still opens through your authorized access. If copying is not permitted, retain an allowed citation or seek guidance instead.

  2. Copy the individual post’s link. Open the specific post and look for Copy link in its sharing options. Placement varies by app version. Avoid profile, feed, search, and collection addresses.

  3. Choose the matching acquisition method. For a supported video post, Grabfy offers an Instagram Video Downloader. Paste the post link and follow the current instructions for supported content. The service is a third-party tool, not an official Instagram or Meta product.

    If the footage is a Reel: do not assume that a regular-post method supports it. Ask the creator for an authorized file, or use Instagram’s own download option if it is available for that Reel and your intended use is permitted. Record which route supplied the copy.

  4. Find and open the completed file. Check the browser’s download list and configured download folder. On phones, a browser download may be in a file-management app rather than the photo library; the location depends on browser and device settings.

  5. Compare it with the source. Check the opening, ending, visible scene sequence, duration, and any available audio. Note missing sections or differences rather than assuming the copy is complete.

  6. Connect the file to its evidence record. Assign a stable evidence ID and a descriptive filename. Preserve the received extension; renaming it does not convert the file.

  7. Keep an untouched acquired copy. Put extracted frames, crops, transcripts, and other working files in a separate folder.

A simple folder structure might be:

case-014/
  acquired/
    case-014_clip-01.mp4
  context/
    source-record.txt
    post-context.png
    rights-notes.txt
  working/
    frames/
    frame-log.csv
  findings/
    findings.txt
    hashes.txt

The .mp4 filename is illustrative, not a promised output format.

Keep captions, usernames, comments, URLs, capture times, screenshots, and rights notes in the companion record. Do not assume the media file contains them. Never enter Instagram credentials into an untrusted service or attempt to bypass private, blocked, or restricted access.

Understand metadata limits

Metadata describes aspects of a file, but not every field describes the original recording. Separate three information layers:

Layer Examples Main limitation
Embedded media fields Duration, dimensions, codecs, encoded timestamps May be absent or rewritten
Local filesystem properties Filename, size, path, local times Usually describe this copy
Instagram page context Caption, username, comments, post URL Preserve separately

Possible embedded fields also include frame rate, audio and video stream counts, encoder information, and rotation data. Local properties include download and modification times. Page context additionally includes display names, engagement details, visible posting information, and a clip’s position within a carousel.

A recent file creation date does not establish a recent recording date. It may simply reflect when the local copy was created.

Inspect available fields

If you have ffprobe installed from a trusted source, inspect the file locally:

ffprobe -v error -show_format -show_streams -of json "case-014_clip-01.mp4"

Look for:

  • Duration and dimensions: useful for comparing copies.
  • Video and audio streams: whether each is present.
  • Codecs and frame rate: clues about playback compatibility and encoding.
  • Timestamp tags: leads requiring corroboration, not recording-date proof.

Three terms matter:

  • Extension: the filename suffix, such as .mp4.
  • Container: the structure holding streams and metadata.
  • Codec: the method used to encode an individual stream.

An MP4 container can hold different codecs, so its extension alone does not guarantee compatibility. Missing or inconsistent metadata can result from ordinary platform processing, export, or re-encoding; it does not by itself prove deception.

Extract and search several keyframes

A thumbnail can hide the most useful evidence. Search several visually distinct frames, especially those containing signs, road layouts, landmarks, vehicles, or recognizable terrain.

  1. Review the full clip. Note scene changes and useful playback timestamps.
  2. Extract frames at scene changes. If that is impractical, sample every 2–5 seconds.
  3. Choose distinct frames. Start with three to five useful views where available, rather than near-identical images.
  4. Record every selected frame’s source playback timestamp. Do this for each searched still, including full frames and detail crops.
  5. Search each image separately. Use a reverse-image service such as Google Lens.
  6. Preserve the results. Record the search date, matching URLs, claimed dates, and why each match matters.

With FFmpeg, this command samples one image every three seconds:

ffmpeg -i "case-014_clip-01.mp4" -vf fps=1/3 "frame-%04d.jpg"

frame-%04d.jpg contains sequence numbers, not source timestamps. A filename such as frame-0005.jpg does not, by itself, establish the exact playback position. Sampling and timestamp handling can affect the relationship.

Use the samples to find useful scenes, then locate the selected image in the source playback and record its timestamp. For a specifically chosen position, extract a still like this:

ffmpeg -i "case-014_clip-01.mp4" -ss 00:00:12.400 -frames:v 1 "clip-01_at-00-00-12-400.jpg"

This selects a frame at the requested playback position, subject to the source’s frame timing. If you require frame-level precision, retain the actual decoded frame timestamp as well.

Keep a frame-search log

An illustrative entry:

Acquired filename: case-014_clip-01.mp4
Source playback timestamp: 00:00:12.400
Extracted image: clip-01_at-00-00-12-400.jpg
Search date: 2026-06-14
Search service: Google Lens
Result: No relevant match returned
Interpretation: Earlier circulation remains unresolved
Next check: Search the station sign as text

When a full-frame search returns irrelevant results, crop around a distinctive sign or building. Keep the uncropped frame, identify the crop’s parent image, and retain the same source timestamp.

Search coverage is incomplete. A match may reveal an earlier indexed copy; no match proves neither originality nor recency.

Trace the uploader and earlier copies

Create a source-tracing worksheet with separate fields for these five roles. They may point to different people or pages:

  • Instagram uploader: the account sharing the post under examination.
  • Alleged creator: whoever is credited with recording the footage.
  • Earliest located appearance: the oldest candidate copy you have found.
  • Earliest verified appearance: the oldest appearance whose date and relationship to the footage you have substantiated.
  • Corroborating source: independent material supporting a specific claim.

For each located copy, record its URL, account identity, displayed date, date basis, caption claims, visible edits, and confidence notes.

  1. Follow attribution backward. Look for credits, watermarks, tagged accounts, licensing references, and links.
  2. Search distinctive wording. Caption phrases, spoken phrases, and visible signs can reveal copies missed by image search.
  3. Compare versions. Look for longer footage, different crops, missing introductions, altered overlays, and changed soundtracks.
  4. Compare claims across captions. Track changes in alleged location, date, participants, or event.
  5. Seek the creator’s documented relationship to the recording. An original file, contemporaneous account, or recording-location explanation can help.
  6. Find independent corroboration. Use credible reporting, eyewitness material, event records, or other separately sourced evidence.

“Earliest found” does not necessarily mean “original.” Older copies may be deleted, private, unindexed, or hosted elsewhere. Likewise, multiple reposts repeating one caption are not multiple independent sources.

Check the claimed place and time

Location analysis asks whether the scene matches a place. Time analysis asks whether it matches a date or period. Neither should rest on one suggestive clue.

Compare location signals

  1. List visible features without interpreting them. Record road geometry, building shapes, signs, terrain, transit markings, and language.
  2. Find candidate locations. Compare those features with reliable maps, street imagery, municipal references, or independently dated photographs.
  3. Match spatial relationships. A distinctive building beside a curved road and bridge is stronger than a generic storefront alone.
  4. Look for contradictions. Check intersection layout, landmark orientation, and terrain.
  5. Account for changes. Businesses, signs, construction, and transit routes can change over time.

Language and license-plate patterns may narrow a region but rarely establish an exact location alone.

Compare time signals

  1. Start with documented appearances. A substantiated older copy can contradict a claim that footage was first recorded today.
  2. Compare weather and event records. Check conditions, event schedules, and contemporaneous reporting.
  3. Inspect changing features. Construction stages, vegetation, signage, and business openings can help bound a date.
  4. Treat shadows and clothing cautiously. Shadow analysis needs location and orientation; clothing may suggest a season but cannot establish a precise date.
  5. State the narrowest supported range. “Recorded before this documented appearance” may be defensible when an exact date is not.

Classify each claim consistently

Outcome Meaning Evidence threshold
Confirmed Claim supported within stated scope Independent evidence; major conflicts resolved
Contradicted Reliable evidence conflicts with claim Clear incompatibility
Unresolved Evidence remains incomplete or conflicting More investigation needed
Unsupported No adequate support currently identified Assertion lacks a sufficient basis

For this workflow, require at least two independent corroborating signals before presenting a time or location inference as confirmed. Two clues copied from one repost are not independent, and two weak clues do not automatically become strong evidence.

For example, a distinctive intersection matched to municipal mapping and a separately sourced eyewitness recording may jointly support location. Two accounts quoting the same caption do not.

Check edits, audio, and captions

Review the entire clip more than once: first with sound, then muted, and again around any suspicious transitions.

  1. Mark discontinuities. Note abrupt cuts, repeated frames, inconsistent object positions, overlays, or lighting changes.
  2. Compare sound with visible events. Check lip movement, impact sounds, crowd reactions, and changes in background noise.
  3. Search for longer or earlier versions. Missing context may explain an apparent anomaly.
  4. Inspect streams where useful. Stream information or a waveform can help locate transitions, but cannot establish whether audio is truthful.
  5. Consider ordinary technical explanations. Compression, re-encoding, interpolation, or interrupted online playback can produce misleading artifacts.

Do not treat a single visual defect as proof of AI generation or deliberate manipulation.

Genuine old footage, false current-event caption

Suppose a post describes flooding as “today,” but reverse searches locate the same sequence in an older report.

Compare recognizable frames, landmarks, and scene order. Then examine the earlier report’s date, historical weather, event records, and the current caption’s claim.

The supported finding may be:

The footage appeared before the event named in the current caption. The caption’s claim of a new recording is contradicted.

That does not make the underlying footage fabricated. It identifies a contextual mismatch.

Genuine footage, replaced or misleading audio

Suppose a street scene carries dramatic shouting, while an earlier copy has different ambient sound.

Compare both versions at matching visual moments. Check audio transitions, lip synchronization, and whether sounds correspond to visible actions. Muted playback helps isolate what the images actually show.

The supported finding may be:

The examined version has a different soundtrack from the earlier located copy. The images alone do not establish the shouted claims.

Do not automatically call the earlier soundtrack original. Establish its source relationship and retain that uncertainty if necessary.

Calculate and recheck a SHA-256 hash

A SHA-256 hash is a fingerprint of a file’s bytes. Calculate it soon after acquisition, before making working copies or edits.

On systems with sha256sum:

sha256sum "case-014_clip-01.mp4"

In Windows PowerShell:

Get-FileHash "case-014_clip-01.mp4" -Algorithm SHA256

On macOS, a common option is:

shasum -a 256 "case-014_clip-01.mp4"
  1. Record the result. Store the full hash, filename, algorithm, calculation time, and time zone in the companion record.
  2. Copy the file to its evidence folder or backup.
  3. Hash the copied file again.
  4. Compare the complete strings. They should match exactly.
  5. Investigate a mismatch. Check whether you selected the wrong file, edited it, or encountered a copy problem.

Matching hashes establish file consistency to practical cryptographic confidence. A mismatch means the bytes differ.

A hash does not identify the creator, validate a caption, establish recording time or place, or prove real-world authenticity. It helps show whether the acquired file has changed since its recorded state.

Write findings that reflect the evidence

Use a separate finding for each claim. A clip can have a confirmed location, an unresolved recording date, and a contradicted caption.

Keep these labelled fields for every finding:

  • Claim: the exact assertion under examination.
  • Evidence: observations, relevant frames, and supporting records.
  • Source: URLs, account identities, files, and playback timestamps.
  • Outcome: confirmed, contradicted, unresolved, or unsupported.
  • Confidence: high, moderate, or low, with a reason.
  • Limitations: missing evidence, dependence on another source, or conflicts.
  • Next check: a specific action that could resolve uncertainty.

An illustrative finding:

Claim: The clip was recorded during today's storm.
Evidence: Matching footage appears in an earlier dated report.
Source: Earlier-report record R-03; frames at 00:04 and 00:12.
Outcome: Contradicted.
Confidence: High for rejecting "recorded today."
Limitations: Original recording date remains unknown.
Next check: Contact the credited camera operator.

Separate observable facts from inferences. “Rain is visible” is an observation. “This was recorded on Tuesday because Tuesday was rainy” is an inference requiring additional evidence.

Record negative search results precisely: “No relevant matches returned for four frames on this date,” not “No earlier version exists.”

Finish the record with a compact lineage summary:

Uploader → alleged creator → earliest located appearance
→ earliest verified appearance → independent corroborating evidence

Attach a source ID or citation to each entry. Mark unknown relationships explicitly rather than filling gaps with assumptions.

Troubleshoot preservation problems

Identify the failed stage before repeating the same action.

Symptom Possible cause Next check
Post will not load Unavailable or restricted content Open complete URL through authorized access
Link is rejected Wrong type or incomplete address Check individual-post URL and content type
No file appears Transfer pending or different folder Inspect browser downloads and destination
File will not play Incomplete transfer or incompatible codec Check completion and media streams
Audio is absent Missing stream or source difference Compare source and stream listing
  1. Check the source first. If the complete link no longer opens through authorized access, record that fact. Do not assume a tool error.
  2. Identify the content type. A regular video post, Reel, carousel, and temporary Story may require different acquisition methods. For supported Stories you have permission to retain, Grabfy's Instagram Story Saver provides a dedicated saving workflow. Do not assume one route supports every format.
  3. Check transfer status. Look for a completed, interrupted, or pending transfer in the browser. Check the configured download location before starting another copy.
  4. Inspect the local file. Confirm that the transfer completed, then examine its container and streams. Renaming the extension cannot repair missing data.
  5. Consider temporary conditions. Connection problems or service issues are possibilities, not proof of a particular cause.

Do not attempt to recover deleted or expired material, or access private, blocked, or restricted content, by bypassing controls. Use evidence lawfully preserved while available, authorized creator-provided material, or independently accessible sources.

Handle sensitive evidence responsibly

Acquiring a file does not transfer ownership or automatically authorize redistribution, commercial use, or reproduction.

  • Check rights before reproducing footage. Confirm permission or an applicable legal exception. Attribution alone does not replace authorization.
  • Minimize personal information. Exercise particular care with minors, victims, medical events, and identifiable bystanders.
  • Restrict graphic material. Label it appropriately, limit access, and avoid unnecessary copies.
  • Keep handling notes beside the evidence. Retain permissions, consent records, source details, and any restrictions.
  • Separate originals from presentation copies. Apply necessary redactions to a working copy while protecting the retained source under your handling rules.
  • Show only what supports the finding. Avoid exposing people or sensitive details merely because they appear in the footage.

A strong fact-check connects every important conclusion to a traceable source, separates what the footage shows from what a caption claims, and leaves unresolved questions visible.