You see a photo inside a post, a group chat, or a story. You can't download the original file — all you have is a screenshot. So you drop it into Google, and it returns a wall of unrelated pictures. That failure isn't your search skills; it's the screenshot itself. Capturing the screen throws away the original filename, the embedded metadata, and often a chunk of resolution, then wraps whatever's left in interface clutter.
The good news is that a screenshot is still perfectly searchable once you handle it correctly. The whole trick is preparing the image before you search and using more than one engine after. Six steps, most of them a few seconds each.
The workflow
Crop away everything that isn't the picture
This is the step most people skip, and it's why their search comes back empty. A screenshot carries the phone's status bar, the app's buttons, a caption, sometimes a watermark — and a matching engine treats all of that as part of the image. Open the screenshot in your Photos or Gallery editor and crop tight around the actual photo, so the frame contains the picture and nothing else. Bellingcat's investigation toolkit treats tight cropping as a baseline step, not an optional one.
Search the full cropped image in Google Lens
Lens has the widest index and is the right first pass. On desktop, go to images.google.com, click the camera icon, and drag the cropped file in. On a phone, open the screenshot and use Share → Search with Google Lens (Android) or save it and open it in the Google app (iPhone). Read what comes back as 'visually similar', not 'identical' — Lens is generous, so scan for pages that clearly use the same photo, not just the same subject.
Run the same crop through TinEye
TinEye indexes different pages than Google and is better at finding exact and modified copies. Upload the crop at tineye.com, then change the sort from 'Best match' to 'Oldest'. The oldest result is usually the closest thing you'll get to an original source — a 2026 'breaking' image that TinEye first indexed in 2019 is recycled, full stop. This one setting does more verification work than any other click on this page.
If nothing matches, crop a distinctive detail
A busy composite frame — a person standing in a crowd, a photo of a photo — often matches nothing as a whole. Crop again, this time down to one clean element: a single face, a shop sign, a jersey number, a building, a logo in the corner. Search that fragment on its own. Detectives call this 'searching the tell', and it routinely surfaces sources that the full image never did.
Add a second and third engine for coverage
No single engine sees the whole web. Yandex is unusually strong on faces and on Eastern-European sites; Bing Visual Search is good for products and objects. Running the same crop across Lens, TinEye, and Yandex takes under a minute and is the difference between 'not found' and a confident answer. Agreement across two independent engines is a much stronger signal than any single result.
Read the dates before you trust the match
Finding where an image appears isn't the finish line — finding when is. Compare the article date, the page's archived versions, and the upload timestamp on the earliest copy. A real photo pulled from an old event and captioned as today's news isn't fabricated, but it's still misleading, and this is the single most common way honest-looking images deceive people.
Which engine, and when
Each of these indexes a different slice of the web, so "not found" on one means very little on its own. Start at the top and work down until two of them agree.
| Engine | Best for | Where |
|---|---|---|
| Google Lens | Broadest index; best general first pass | images.google.com / Google app |
| TinEye | Exact & modified copies; sort by oldest | tineye.com |
| Yandex | Faces and Eastern-European sources | yandex.com/images |
| Bing Visual Search | Products, objects, logos | bing.com/visualsearch |
iPhone vs. Android, quickly
On Android, open the screenshot, tap Share, and pick Search with Google Lens — you can even pinch to crop inside Lens before it searches. On iPhone there's no direct Lens share, so save the screenshot, open the Google app, tap the Lens camera icon in the search bar, and load the image from your camera roll. Either way, do the tight crop first; cropping inside Lens works, but a clean file gives you cleaner matches.
When a screenshot simply won't resolve
Some screenshots are too small or too compressed to match anything — engines struggle badly once the image drops below roughly 200 pixels on its long edge. If you can, go back to the source and grab the actual image file instead of a capture: long-press to save, or open the post in a browser and pull the full-resolution file. A downloaded image keeps the detail (and sometimes the metadata) that a screenshot flattens away.
And if the picture looks a little too perfect — flawless skin, warped hands, text in the background that spells nothing — reverse search may find no source because there isn't one. That's the moment to switch from "where did this come from" to "was this generated", which our AI-image detection guide walks through. For photos that are real but possibly altered, the edited-photo guide covers the next checks.
Check a claim, not just an image
Traced the photo but still unsure about the story around it? FAXTR searches 100+ fact-checking organizations in one query — free, no login.