find-the-original-image
Reverse image search across Yandex, Google Lens, Bing Visual Search, TinEye and Baidu to find where a picture came from and who published it first. Use when reverse image searching, identifying a photo, face, logo, product, uniform or building, tracing a profile picture or avatar, finding the oldest copy of an image, checking whether a photo is stock or a repost, or reverse-searching a video by keyframes. Applies to romance and investment scam investigation, fake-profile and synthetic-identity detection, disinformation and media verification, counterfeit and brand-infringement work, and insurance claim review. Reference at useosint.com/skills/find-the-original-image.
UseOSINT · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add UseOSINT/Skills --skill find-the-original-imageAbout this skill
name: find-the-original-image description: >- Reverse image search across Yandex, Google Lens, Bing Visual Search, TinEye and Baidu to find where a picture came from and who published it first. Use when reverse image searching, identifying a photo, face, logo, product, uniform or building, tracing a profile picture or avatar, finding the oldest copy of an image, checking whether a photo is stock or a repost, or reverse-searching a video by keyframes. Applies to romance and investment scam investigation, fake-profile and synthetic-identity detection, disinformation and media verification, counterfeit and brand-infringement work, and insurance claim review. Reference at useosint.com/skills/find-the-original-image.
Find the original image
The goal is almost never "find a match". It is find the earliest publication and read its page. A match tells you the image exists elsewhere; the earliest page tells you the photographer, the date, the caption, and the names — which is what you actually pivot on.
The beginner mistake: uploading the full frame to one engine, getting nothing, and concluding the image is unindexed. Cropping to one distinctive object and re-searching finds things full-frame search cannot.
Pick your engine by what you are holding
| You have | Start with | Why |
|---|---|---|
| A face | Yandex | Its index is built around facial similarity, so it returns different people who look alike and the same person in other photographs. No other general engine does this. |
| A face, and Yandex fails | A dedicated face engine (see below) | Only after you have cleared the legal and consent questions. |
| A street scene outside North America / Western Europe | Yandex | Deeply indexed Russian, Central Asian, Eastern European, Turkish and Chinese web content that Google under-crawls. |
| A product, book cover, artwork, plant, animal | Google Lens | Object and entity recognition, tied to Shopping and Knowledge Graph. |
| Text inside the image | Google Lens | It OCRs the frame and lets you search the extracted string. Often the text is the answer and the image search is irrelevant. |
| A landmark or a well-known building | Google Lens | Landmark classification is its strongest single feature. |
| A specific region of a cluttered photo | Bing Visual Search | Draw a box on the uploaded image and it re-searches only that region — the fastest crop-and-retry loop of any engine. |
| A press photo, meme, or anything you suspect is old | TinEye | The only major engine that sorts by oldest and that reliably surfaces modified copies. |
| Chinese-language or China-hosted content | Baidu image search | Coverage the others simply do not have. |
Run at least three. They disagree constantly, and that disagreement is information: TinEye finding an exact copy from years back while Lens finds only recent reposts is the signature of recycled media.
What each engine is actually doing
Yandex matches on visual similarity with a strong face component. Its results page groups "sites containing this image" separately from "similar images" — only the first group is evidence. It tolerates crops, rotation and heavy recompression better than the others.
Google Lens has moved away from whole-image duplicate matching toward "what is this, and what can I sell you". For provenance work use the option that lists pages containing the image rather than the visual-match carousel, and expect it to return visually similar but unrelated photos as if they were matches.
Bing Visual Search sits between the two. Its region-select tool is the reason to use it: no download, crop, re-upload cycle.
TinEye is crawl-based and comparatively small — plenty of images return zero results, and absence from TinEye proves nothing. What it does that nothing else does: exact and near-duplicate matching with the ability to sort by oldest, and detection of copies that have been cropped, colour-shifted or watermarked, which it will show you side by side against your input.
Method
- Fix the input. Get the highest-resolution copy you can — the file itself,
not a screenshot of it. Screenshots add a resize and a recompression that cost
you matches. Strip nothing yet; run
secrets-in-file-metadataon the original before you start editing copies. - Full frame, all engines. Cheap, sometimes instant.
- Crop and re-search. This is the highest-yield step in the whole skill. A full frame's fingerprint is dominated by the background; crop tightly to the face, the sign, the logo, the vehicle, the tattoo, the building corner, and search each crop separately. Reposts get cropped and re-framed, so the crop often matches when the frame does not.
- Flip horizontally. Mirroring is a routine way to dodge automated matching and a routine artifact of screen-recording and video reposting. Flip and re-run the same engines.
- Preprocess and retry on low-quality inputs — upscale, denoise, correct levels. See reference/preprocessing.md.
- For video, extract keyframes and search them as stills. Search a frame from the start, the middle and the end, plus any frame containing a sign or a face. A keyframe hit is usually what breaks a video case.
- Sort for oldest. On TinEye, sort by oldest. Then treat that date as a ceiling, not an answer, and go to step 8.
- Read the match pages. Open them. Harvest: photographer credit, agency,
caption, named people, on-page date, filename in the image URL (often
2019-04-city-event-03.jpg), and any surrounding article text. This is where the selectors are.
Establishing first publication, not just a match
An earliest-known-copy date is a claim about your search coverage, not about the world. To harden it:
- Check the match page's own date against
read-deleted-pages— the archive's first capture of the URL bounds when the page really existed, and the pag