Skip to main content

How to Detect AI Images: 9 Practical Checks

Learn how to detect AI images by checking sources, reverse search, C2PA, and SynthID without trusting a single detector or visual clue.

FHFinn Hillebrandt
AI Technology
How to Detect AI Images: 9 Practical Checks
Links marked with * are affiliate links. If a purchase is made through such links, we receive a commission.

Have you ever scrolled through social media and wondered whether an image was photographed or generated with AI?

Here is the answer.

You cannot decide that from one finger, a filename, or a detector score. Current AI image generators can create convincing images. Real photographs can also look strange after compression, retouching, or difficult shooting conditions.

You need a verification chain rather than one supposed giveaway. I show you nine checks, each answering a different question.

TL;DRKey Takeaways
  • Start with the source and context. An image without traceable provenance deserves closer review.
  • Check official provenance signals such as OpenAI SynthID, Google SynthID, and C2PA Content Credentials.
  • Visual artifacts and general detectors are clues, not proof.
Image verification
How much weight to give each image signal
1
Strong provenance and context
Check first
Original source
Reverse search
Provider signal
Valid C2PA data
2
Supporting technical signals
Interpret together
EXIF data
File history
Watermark
Editing traces
3
Weak signals on their own
Never decide from these alone
Hands and text
Light and shadows
General AI detector
Source: own review method
gradually.ai

1. Check the source and context

Look for the original post first. Is there a named photographer, agency, venue, or another independent image of the same event? Do the date, weather, clothing, and surroundings match the claim?

A screenshot without a link, a newly created account, or a sensational caption does not prove AI use. Each is a reason to investigate further.

2. Run a reverse image search

Use Google Images to look for similar files, older publications, and possible originals. If necessary, crop a distinctive part of the image and search again. That often works better than uploading a screenshot full of text and interface elements.

Using Google Images for a reverse image search

Reverse search will not find every original. It is particularly useful when someone attaches a new story to an old photograph or manipulates a genuine image.

3. Verify OpenAI provenance signals

OpenAI says images from ChatGPT, Codex, and its image API contain both C2PA Content Credentials and SynthID. The free verifier for OpenAI-generated images accepts images as PNG, JPG, WebP, or GIF files and now audio files too. It looks for OpenAI's SynthID signal and OpenAI C2PA data. Developers can run the same check through the OpenAI API.

Official OpenAI verifier for checking OpenAI-generated images

A match indicates generation with OpenAI tools, and OpenAI says false positives are rare. No match does not exclude OpenAI or another generator, for example when the image comes from an older model. Editing, compression, or screenshots can impair the signals. The verifier also says nothing about truth, copyright, ownership, or context.

4. Check Google SynthID

Google adds SynthID to media generated with Gemini and other supported Google AI tools. According to the official instructions, you sign in to Gemini, upload a single file, and ask something like "Is this AI-generated?" For screenshots, Google recommends cropping closely to the image itself and avoiding collages.

Gemini also checks C2PA Content Credentials. Besides images, you can check videos under 90 seconds and audio files under one hour, each up to 100 MB.

A detected SynthID signal connects the content to a supported Google AI system. If Gemini finds no signal, the image may come from another system or may have been altered enough to affect detection.

5. Inspect Content Credentials

C2PA Content Credentials are cryptographically signed provenance records. The Content Credentials verifier shows whether it found a validly bound manifest, who signed it, and which edits were recorded.

Missing credentials are not evidence of deception. Not every camera or AI tool supports C2PA, and platforms or export tools can remove metadata. My technical guide to C2PA explains those limits in detail.

6. Put metadata and filenames in context

An original camera file may include EXIF details about the camera, lens, exposure, and focal length. A genuine photo downloaded from social media often no longer has them. EXIF fields can also be copied or changed.

Example of camera and exposure metadata in an image file

Filenames are only a historical clue. Older Midjourney or DALL·E files sometimes include a tool name, prompt, or job ID. Renaming or downloading the file again destroys that clue.

7. Inspect anatomy, text, and geometry

Trace fingers, glasses, jewelry, railings, windows, and repeated patterns across the image. Look for substituted characters in text and stairs or edges that end without a logical connection.

Older AI-generated image with anatomically inconsistent fingers

These artifacts are common in older or weaker models. Current models such as GPT Image 2.5 and the latest Midjourney versions avoid many of them. Correct hands and readable text therefore do not prove that an image is a photograph.

AI-generated image with anatomically plausible hands

8. Compare light, shadows, and reflections

Find the strongest light source and compare the direction and hardness of every shadow. Check mirrors, windows, water, and glossy surfaces. A person may cast a shadow to the left while a nearby object produces an implausible angle.

AI-generated image with inconsistent shadows

Multiple light sources, flash, HDR, and editing can also make genuine photographs look unusual. Treat lighting errors as a clue, not a verdict.

9. Use general detectors only as supporting evidence

A general AI detector estimates whether an image resembles patterns in its training data. New generators, compression, cropping, and post-processing can change the result. A percentage looks precise but is not meaningful without a suitable, independent test dataset.

For a serious case, I use this order:

  1. Preserve the original source and the claim being made.
  2. Check reverse search results and independent reporting.
  3. Test provider-specific provenance signals.
  4. Inspect C2PA, EXIF, and file history.
  5. Review visual details and, at most, add a general detector result.

If the conclusion affects a person, publication, or business decision, document each step. When the result remains uncertain, do not state that the image is AI-generated. Explain which signals you found and which questions remain open.

Frequently Asked Questions

Check the source first and run a reverse image search. Then look at provenance signals such as C2PA or SynthID and the available metadata. A detector only gives a probability, and no single hit or missing signal reliably proves whether an image is real or AI-generated.

Only to a limited degree. A general detector provides a probability, not proof. Results can change with the generator, edits, compression, and test dataset. Never use one as your only evidence. A valid provider-specific provenance signal is more informative when available.

No. A missing watermark does not prove that an image is authentic, and an odd-looking hand does not prove that AI was involved. A stronger review combines source checks, reverse search, provenance signals, metadata, and visual inspection.

No. Article 50 separates providers’ machine-readable marking duty under paragraph 2 from deployers’ deepfake disclosure duty under paragraph 4. For systems placed on the market before August 2, 2026, providers must take the necessary steps to comply with Article 50(2) by December 2, 2026.

Separately, deployers must clearly and distinguishably disclose qualifying deepfakes no later than a person’s first exposure; machine-readable provider marking alone does not meet that duty. Purely personal, non-professional use is excepted, and for evidently artistic or satirical works an appropriate notice is enough. See the guide to labeling AI-generated content for the detailed rules.

Google reverse image search can surface older copies or possible originals. OpenAI's verifier checks supported OpenAI provenance signals; signed-in Gemini checks for Google's SynthID and, on compatible files, Content Credentials. The Content Credentials verifier shows provenance information and recorded changes when credentials are present. These checks cover specific sources or credentials; a missing signal does not rule out AI use.

No, there is no complete technical safeguard. Robots rules and provider opt-outs are useful signals but cannot stop copies from other sources. Glaze aims to make style imitation harder; its developers say it does not reliably protect against image-to-image attacks. Nightshade alters images with the aim of disrupting training signals, but it is not a guarantee either. Contracts and licenses can document permissions and rights, but they cannot technically prevent copying. Keep original files and records.

FH

Finn Hillebrandt

AI Expert & Blogger

Finn Hillebrandt is the founder of Gradually AI, an SEO and AI expert. He helps online entrepreneurs simplify and automate their processes and marketing with AI. Finn shares his knowledge here on the blog in 50+ articles as well as through the AI Business Club.

Learn more about Finn and the team, follow Finn on LinkedIn, join his Facebook group for ChatGPT, OpenAI & AI Tools or do like 17,500+ others and subscribe to his AI Newsletter with tips, news and offers about AI tools and online business. Also visit his other blog, Blogmojo, which is about WordPress, blogging and SEO.