Newsroom verification workspace

Build an auditable image verification report.

Upload a news image. Img ID separates visible observations, provenance, OCR, source-search leads, and open questions. Complete the human sourcing checklist and export a Markdown report without turning a detector score into proof.

Dark UI mockup of a journalism image verification dashboard showing a news photograph of a city street being analyzed with overlaid markers for geolocation clues, visible signage OCR extraction in cyan boxes, shadow direction analysis lines, and metadata timestamp display, with verification checklist showing Source Confirmed green badge, EXIF Camera Canon EOS R5, GPS Coordinates on mini-map, AI Detection Low Confidence green, and OCR Extracted Text list

Newsroom workspace

Upload an image. Separate known, inferred, and unverified.

Review provenance, OCR, visual context, safe search leads, sourcing actions, and report export while the image remains visible.

Distinct newsroom output

Evidence collection plus human-owned verification work.

Provenance checklistFile hash, C2PA state, EXIF context, source, uploader, rights, time, and location work.
Source leadsSafe search queries from visible signs, captions, landmarks, and objects. No model-generated URLs.
Known vs inferredVisible findings stay separate from source claims and unresolved questions.
Markdown reportExport hash, OCR, findings, uncertainty, source URL, and verification checklist.
Start newsroom report →

Where Img ID helps a verification desk

Img ID is not a replacement for sourcing. It is a first pass that can make follow-up faster. OCR can reveal signs, badges, license plates, watermarks, captions, and screenshots. Metadata can show camera or software clues. The AI verdict can flag visual patterns that deserve closer human review.

  • Use OCR output to search names, signs, locations, and visible claims.
  • Compare metadata with the alleged time, place, and publishing path.
  • Inspect evidence lists for anatomy, lighting, reflection, and object inconsistencies.
  • Preserve source URLs, timestamps, uploader claims, and original files separately.

Recommended verification chain

Start with the highest-resolution original. Run Img ID. Save the report URL for internal notes. Run reverse image search. Compare against trusted wire services, geolocation clues, weather, landmarks, and social account history. Contact the uploader or rights holder before publication.

Editorial caution

Avoid publishing a detector score as proof. Use language like "image-analysis tools flagged possible AI-generation artifacts" only when paired with visible evidence and source reporting. False positives can damage trust, especially with compressed or heavily edited real images.

How to document a triage result

Keep the original URL, uploader name, timestamp, downloaded file, Img ID share link, OCR output, metadata output, and notes on visible artifacts. If an image later changes or disappears, those notes preserve the review path without turning the detector score into the story.

A strong verification note should separate what is known, what is inferred, and what is still unverified. Img ID can help with the inference layer: visible text, camera clues, and AI-like artifacts. Sourcing, rights, location, and context still need human reporting.