Heavy retouching
Aggressive noise reduction, uniformed skin, upscaling: they erase the micro-texture that authenticity checks look for first. The photo is yours, but the file no longer reads as coming from a camera.
For Reddit, forums and photography communities
A real photo mistaken for AI: what to do
It happens more and more: you post a photograph you took, and in the comments someone swears it was generated by AI. The answer isn't an argument — it's the right evidence, and knowing how to read it.
This page is written for the discussions that start on Reddit and in photography communities: why the accusation happens, which evidence holds up in a debate, and how to present an analysis without turning it into an attack.
Why a real photo gets mistaken for one generated by AI
Computational photography
Phones stack and reprocess images on the fly: multi-exposure, synthesized texture, rebuilt skies. Nobody generated the photo, yet the process makes it unlike a straight camera file.
The file's journey
A screenshot passed through a chat app has already been recompressed several times: data lost, details destroyed. "Too clean to be true" is not evidence — it's an artefact of sharing.
Habitual suspicion
As generated images spread, every unusual photograph gets doubted first. The suspicion isn't an insult: it's a habit. The answer isn't an argument — it's evidence.
The evidence that holds up in a discussion
The original file, not the screenshot
The accuser looks at a screenshot; the photographer brings the original. Every hop — chat, social network, screen capture — strips the data needed to establish where the file came from.
EXIF and provenance credentials
Not a guarantee: they can be lost or removed. But when they are present they tell the file's story — camera, lens, date, editing software — and can be shown as part of the report.
A photographic reading, not a number
Where the light meets the shadows, whether reflections genuinely repeat the scene, how skin behaves against backlight. Observations you can discuss point by point, with or without the tool.
A report anyone can reopen
The PDF exported from the analysis carries a verification code: anyone in the thread can check its authenticity instead of having to take your word — or theirs.
If it's someone else's photo that looks suspicious
In a community, a wrongly aimed accusation destroys trust — which is why how you verify matters as much as the result. Four rules that keep the discussion civil:
- Ask for the original file before declaring a photo was generated: it changes everything.
- Examine the image, not the person: the report distinguishes a generated photograph from an authentic retouched one.
- A flagged area is a point to verify, not a conviction: every flag comes with its reason, for you to check.
- When the signals contradict each other, the report declares insufficient evidence: a valid answer, and often the right one.
If it's your own work being doubted
Don't defend yourself with opinions: bring the document. The report explicitly separates three cases — a generated photograph, an authentic retouched photograph, insufficient evidence — so pushing contrast or cleaning skin never gets treated as proof of generation. And answer with the original: a recompressed file can defend nobody.
If the photo is under review for professional reasons — a publication, a collaboration, a client asking for proof — the verification workflow for people who work with images shows you how to prepare your materials before the analysis.