Slow down. Trace it. Check it.

You do not need to decide whether media “looks real.” When a post, clip, call, or message matters, pause and build a source trail before you react or share.

Aerial photograph of the Six Flags Over Georgia roller coaster surrounded by floodwater
Shared online in 2024“Six Flags after Hurricane Helene”
The same Six Flags flood photograph shown with its original September 2009 context
Original source recordAtlanta flooding, September 22, 2009
Photographs from the post showing a weather-related closure sign and the roller coaster on dry ground

Why the claim felt believable: the post also showed a real-looking weather closure. A true detail can make an unrelated old photograph feel current.

Same photograph, different story. Reuters found that the flood image dates to 2009 and rated the Hurricane Helene claim miscaptioned. Read the fact check.

Source and context come before technical tools.

01

Pause before reacting or sharing

Urgency, fear, outrage, and pressure make quick action feel necessary. That is exactly when to stop. Do not forward, pay, reply, or accuse anyone while the claim is still unverified.

The goal is not to trust your eyes.
The goal is to give yourself time to verify.

02

Find the original source

Open the full post and check who uploaded it first. A large account repeating a clip is still a reposter, not the source.

  • Who first posted or recorded it?
  • Is there a full-length or higher-quality version?
  • Does a primary source or established outlet publish the same claim?
Viral repostCredited accountOriginal upload
03

Check the media in context

Search the claim, not only the file. Combine the person’s name, location, event, and date. Search a distinctive spoken sentence in quotation marks.

person + place + eventexact spoken phraseclaim + fact check

A real image does not prove its caption. Compare dates, landmarks, weather, uniforms, and the complete surrounding post as context, not as a magic authenticity test.

Content Credentials Verify showing a landscape issued by OpenAI, identified as AI-generated, with creation and format-conversion actions recorded
A real verified record. The file is issued by OpenAI, identified as AI-generated, and shows the actions recorded in its process.

05 · Content Credentials / C2PA

Inspect any signed history that travels with the file.

Content Credentials are tamper-evident records that can describe who or what signed a file, how it was made, and which edits were declared. They provide provenance; they are not a universal AI detector.

  1. Save the media or copy its public URL.
  2. Open Content Credentials Verify and upload the file or paste the URL.
  3. Read the signer, creation method, edits, and validation status, then compare them with the claim.

“No credentials found” proves nothing by itself. Metadata may be absent, stripped by a platform, or never added. It does not establish whether the media is authentic.

Open Content Credentials Verify

06 · Provider watermark checks

Use the checker made for the provider.

OpenAI Verify looks for supported OpenAI provenance signals. Gemini can check for SynthID signals associated with Google AI. These tools identify supported origin signals; they do not decide whether the surrounding claim is true.

OpenAI Verify upload screen for an image or audio file
OpenAI Verify

Upload the original file

Open the verifier and upload one image or audio file. The original download preserves more useful signals than a screenshot or converted copy.

OpenAI Verify reporting that a landscape was generated with OpenAI tools
OpenAI result

Read which signal was detected

This example reports that the file was generated with OpenAI tools. A positive result supports origin, but it does not establish the truth of a caption or claim.

Gemini reporting that a landscape contains signals indicating it was generated or edited with Google AI
Gemini and SynthID

Ask whether Google AI signals are present

Upload the file to Gemini and ask whether it was created or altered with Google AI. This example reports that Google AI signals were found.

07 · Detector evidence

Compare models in DeepFake-O-Meter.

DeepFake-O-Meter is a University at Buffalo research platform that can run image, video, or audio through several published detection models. Use it only on media you are permitted to share.

  1. Open DeepFake-O-Meter and sign in to a free account.
  2. Upload a file or provide a public YouTube URL, then select several applicable detectors.
  3. Wait for each model and compare the outputs with your source, context, and provenance checks.

A detector score is evidence, not proof. Results can change with the model tested, compression, cropping, editing, video quality, or unfamiliar generation methods. A low signal does not clear a video; a high signal should be confirmed elsewhere.

Open DeepFake-O-Meter
DeepFake-O-Meter processing an uploaded landscape with four selected detection models
This real interface shows four selected models still processing. Wait for every selected model before comparing their results.

08 · Calls, voices, and urgent requests

Verify the person on a separate channel.

If a call, voice message, video call, or urgent request claims to come from someone you know, stop the interaction. Contact that person using a phone number or account you already trust, not contact details provided in the suspicious message.

For high-risk situations, agree on a private family verification phrase. Do not rely on a familiar voice, face, caller ID, or speaking style alone.

What should I do right now?

If it matters, do this before you act.

  1. Stop the action.Do not share, send money, reply, or accuse.
  2. Save the claim.Note the link, account, names, place, event, and time.
  3. Trace and compare.Find the original; search the context and a few keyframes.
  4. Add technical evidence.Check credentials or a suitable detector when useful.
  5. Confirm independently.Use an established source or a trusted channel for identity before acting.

Still unsure? Label it unverified and do not pass it on as fact.