For publishers verifying citizen-contributed media
Per-scene timeline and metadata-integrity checks on the file before it lands in the article.
Citizen photos, field audio, and short video arrive faster than they can be vetted. Detecto checks the file itself, a per-scene timeline, synthesis indicators, and metadata integrity, and returns an AI-likelihood before the media lands in the article.
Built for the people who review other people’s content
- Editors at independent magazines
- University writing centers
- Newsroom verification desks
- PR review teams
- Content QA leads at agencies
What publishers typically scan with Detecto.
- Citizen-submitted photos and short videos
- Audio interviews submitted from the field
- Press-release supplied imagery
- Stock-like media used in editorial composites
The failure modes Detecto is built to surface.
- A synthetic image or clip is submitted as on-the-ground footage
- A real photo is altered or re-encoded to hide manipulation
- Press-supplied imagery is partly AI-composited
- A deepfaked voice passes as a recorded interview
The workflow, end to end.
Five steps. None of them is automated.
- 01
Upload the file, image, audio, or video.
- 02
Read the overall likelihood and confidence band.
- 03
For video, scan the per-scene timeline to see where signals spike.
- 04
Check metadata integrity for signs of re-encoding or stripping.
- 05
Keep the report on file as the basis for running or holding the media.
Evidence that goes in the file.
A 0–100 AI-likelihood with a High / Medium / Low confidence band, per modality.
A per-scene timeline for video, plus surface-artifact and metadata checks for images.
A private, timestamped record tied to the exact file you reviewed.
What not to do with AI detection
The same posture every Detecto reviewer reads. The score is evidence, not a verdict.
- Don’t publish or spike a file on the score alone, corroborate the source.
- Don’t read “Likely human” as “verified authentic”; it means no strong AI signal, not provenance.
- Don’t treat metadata as conclusive, it can be stripped or forged.
- Don’t drop the desk’s normal verification because a number looks clean.
Whatever shape the submission arrives in.
Questions publishers ask.
If this fits, these probably do too.
Score, signals, and a notes pane you can attach to a decision.
Read the workflowFor pr teamsThe score lands before the client sees the deliverable.
Read the workflowFor content agencysBrand-voice drift and outsource-pipeline integrity, in one report.
Read the workflowBuilt around how publishers actually review.
Sign up free. Private by default. Vendor names never reach the browser.