Extract text and inspect suspicious screenshots.

Why screenshot OCR matters

A screenshot claim often depends on text: chat messages, receipts, timestamps, usernames, prices, warnings, emails, or app notifications. OCR makes that text searchable and easier to compare. Img ID also identifies UI components so you can spot strange buttons, mismatched fonts, broken icons, and interface pieces that do not belong together.

• Extract chat text, usernames, prices, dates, warnings, and payment details.
• Spot UI elements that are misaligned, copied, or inconsistent with the app design.
• Review generated-screen artifacts such as fake icons, broken status bars, and odd labels.
• Compare OCR output against the visible screenshot before trusting the claim.

What Img ID cannot prove

A screenshot scan cannot confirm whether a message was sent, a payment happened, or an account exists. It can only inspect the pixels. Use it to decide whether a screenshot needs source verification: original export, message link, transaction ID, app record, or direct confirmation.

Best workflow

Upload the uncompressed screenshot when possible. Read the OCR text, inspect annotated UI components, then check the AI detection explanation. If the screenshot is cropped, ask for the surrounding context before making a decision.

Common screenshot red flags

Watch for inconsistent status bars, impossible notification times, copied message bubbles, broken app icons, blurry text pasted into sharp UI, and dates that do not match the surrounding conversation. Generated screenshots often get the broad layout right but miss small interface rules.

For disputes, ask for an export, screen recording, original message link, or system record. Img ID is useful because OCR makes the screenshot easier to audit, but it cannot confirm that the underlying event happened.