For a SynthID check, start with Google's official SynthID Detector for supported images, video and audio. Review its current coverage for Google and participating partners. AIFakeScan's visual scan and a compatible watermark check inspect different evidence.
Official routes reviewed October 19, 2026. The worksheet below records file versions and results; it is not an accuracy benchmark.
Where can you check SynthID?
Google announced global English access to SynthID Detector on October 7, 2026. The public service checks supported image, video and audio files. Its availability does not establish public API access or enable Google verification inside AIFakeScan.
Open official SynthID Detector and review its current file requirements. Keep the original, upload the supported file, read the result and save its exact wording with your check date. See Google’s access announcement.
SynthID embeds an imperceptible watermark in generated media. Google describes it as designed to withstand some transformations, including cropping and lossy compression. That design goal does not establish a success rate for the particular file in your hands.
How to verify an image in Gemini
Follow Google's current Gemini verification instructions. Sign in with an eligible personal or Workspace account, open Gemini, use Add files, and upload one image. Ask whether Google AI created or edited it. Read the returned verification explanation and preserve the exact response alongside the file.
For Gemini, check the current help page for upload limits and account requirements before submitting a file. Gemini, SynthID Detector and AIFakeScan have separate limits.
If only a screenshot is available, Google advises a tight crop around one image rather than a collage. Keep the untouched screenshot as well, and record the crop. Request the original download when possible.
What does the result support?
Record detected, not detected and unclear outcomes separately, using the service’s exact wording. Check the current media and provider coverage of the verifier you used. A supported watermark finding does not verify a scene or caption.
Use this interpretation checklist; the labels below are review categories, not promised interface wording.
| What you receive | What to record | What to do next |
|---|---|---|
| A reported SynthID detection | Exact response, file, date, and any described scope | Distinguish generation from editing; verify the image's caption separately |
| No reported detection | The negative finding for this submitted file | Keep other generators and the image's source history in scope |
| An unclear determination | The explanation without converting it to a yes or no | Seek a better source file and retain the uncertainty |
| Upload failure or no completed check | Error or missing coverage | Mark it as not checked; do not record a negative result |
A detector response should not silently become a broader claim about a person, event, or publisher. For example, finding evidence of an AI edit does not identify every changed region or establish that an accompanying news claim is false.
SynthID, Content Credentials, and visual detection
These evidence channels can appear in the same review. Keep their outputs separate.
| Evidence channel | Question to ask | Limit to preserve |
|---|---|---|
| SynthID verification | Did a compatible provider check find its watermark? | A watermark check has defined provider coverage |
| C2PA Content Credentials | What provenance declarations were verified, and under which trust rules? | Signed history is not a guarantee of factual truth |
| Ordinary metadata | What camera, software, or export clues remain? | Editable fields are context, not independent proof |
| Visual model | What did this model report about these submitted pixels? | A classification does not reconstruct creation history |
Gemini can also inspect Content Credentials. Save those findings separately from its SynthID response. Our C2PA guide explains validation and trust states.
A worksheet for originals and shared copies
Keep one record per file. If you compare an original with a social download or screenshot, label the versions before uploading. Do not overwrite an original while trying to obtain a different detector answer.
| Field | Fill in during your review |
|---|---|
| Review question | The specific claim about generation, editing, or source |
| File identity | Filename, format, dimensions, and optionally a SHA-256 hash |
| Acquisition | Source URL or sender, download date, and whether it is an original or copy |
| Known changes | Crop, screenshot, resize, export, or platform route; unknown if unavailable |
| Official verification | Service, date, exact response, and whether the check completed |
| Other evidence | Credential details, publication history, creator explanation, and conflicting findings |
| Conclusion | What the evidence supports and what is still unknown |
This is an empty review template. It contains no measured watermark survival results. A comparison of two unknown files also cannot tell you which signal existed before either file reached you.
Where AIFakeScan fits
Use the AI image detector to inspect available file evidence and read the coverage notes. AIFakeScan does not run Google's proprietary SynthID verifier. Its beta visual signals remain Inconclusive on their own and do not provide a calibrated AI probability.
For a broader source review, follow How to Detect AI-Generated Images. If a detector flag conflicts with the source history, use the false-positive review guide.
Use the interactive SynthID verification route
The AIFakeScan SynthID checker lists provider-specific access and coverage. Use the official external Detector for supported media; Gemini remains an alternative image workflow. Check the provider status before submitting anything inside AIFakeScan.
Following an external route does not upload a file to AIFakeScan or import the result. Only a confirmed, enabled in-tool verifier can receive files here. Record the service used, exact response, file version and date.
This guide remains the detailed reference for coverage, file-version handling and result interpretation. The tool page is the operational entry point for `synthid checker` intent.
Frequently asked questions
Is a general AI image detector a SynthID checker?
No. A visual classifier and a compatible watermark verifier inspect different evidence. Look for an explicit description of the check that actually ran.
Does no SynthID detection prove an image is a real photograph?
No. The result does not rule out every other AI system or establish the truth of the depicted scene. Record the narrow finding and continue the source review.
Can AIFakeScan verify SynthID?
Google verification inside AIFakeScan remains subject to integration access. Use the official external SynthID Detector for its supported media, or Gemini for the documented image workflow. Other in-tool provider checks run only when their individual status confirms availability.
Can a screenshot be reviewed?
Yes, but preserve it as a separate file version and seek the original. Do not treat a result about the screenshot as a complete history of the unseen original.
Sources
- Google DeepMind: SynthID — Google DeepMind
- Verify AI-generated images, videos, and audio — Google
- C2PA and Content Credentials Explainer — C2PA
