A photo on Threads catches your eye. It might be a profile picture that looks too polished, a product shot in a post that seems stolen, or an image in a reply you want to trace back to its source. Your first instinct is to reverse image search it right there in the app. That is where the process stalls, because Threads does not give you a button for it.
Threads has no built-in reverse image search. Save the photo to your device first, then upload it to Google Lens or TinEye. On iPhone, take a screenshot of the photo and crop it tight; on desktop, right-click the image and choose Save Image As. Lens is best for visual matches and context, while TinEye is best for exact copies and the earliest use.
This guide walks through the whole two-step method. You will learn how to get a photo out of Threads on iPhone, Android and desktop, how to run it through Lens and TinEye, and how to read the results. Every step below was checked against live sources on 22 November 2026, and the worked example at the centre of this article uses a real photo searched live on both engines.
Does Threads Have Reverse Image Search?
No. Threads has no reverse image search button, no image upload box in its search, and no filter that shows image posts only. Its search finds text, accounts and hashtags, and the advanced search update from December 2024 added profile and date filters only. Nothing in the official search documentation describes searching with a photo.
That matters because it changes the shape of the task. You are not searching inside Threads. You are taking a photo out of Threads and searching it somewhere else. Once you accept that, the method is simple, and it works the same way whether the photo is a profile picture, a photo inside a post, or an image someone sent in a reply.
One warning before you start: the check tells you whether a photo is reused and where it has appeared before. It does not tell you who the person in the photo is, and it should never be used to try to identify a private individual. That line runs through this whole guide, and the section on reading results explains why it matters.
The Threads Save-Then-Search Checklist
Keep this table open while you work. It is the whole method in one place.
| Step | What to do | Where | What you end up with |
|---|---|---|---|
| 1. Save the photo | Screenshot on iPhone and Android, right-click and save on desktop | Threads app or threads.com | A copy of the photo on your device |
| 2. Crop it tight | Trim away menus, usernames and white space so only the photo remains | Your Photos app or any editor | A clean image the engines can match |
| 3. Search on Google Lens | Upload the file at lens.google.com or paste its image address | Desktop or mobile browser | Visual matches, context, and an Exact matches list |
| 4. Search on TinEye | Upload the file or paste its image address at tineye.com | Desktop or mobile browser | Exact copies, sorted by oldest first, with a first-indexed date |
| 5. Read the results | Compare the two engines, open the earliest source, and check the source page | Both result pages | A reuse trail you can trust, or an honest zero |
How to Save a Photo from Threads
This is the awkward part, and it is worth being honest about it. Threads has no download button for photos in posts, on iPhone or Android. There is also no official Meta help page that documents saving a photo from a post. Everything below comes from third-party guides and from how the app and the website actually behave, so treat the Android row as unconfirmed until you test it yourself.
On iPhone: screenshot it
Open the post and tap the photo to view it full screen, then take a screenshot and crop it tight so only the photo remains. Threads has no download button for photos on iPhone. Older guides describe a long-press route where you swipe up on the share sheet and tap Save Image, but that option is gone from the current app, so do not count on it. A screenshot is a lower-quality copy than a saved file, so crop carefully and keep the photo as large as you can.
On Android: screenshot it
There is no confirmed built-in save on Android. Older guides mention a Download option in the three-dot menu, but more recent guides say it is not there, so do not count on it. Take a screenshot with the power and volume-down buttons, then crop it tight so only the photo remains. A screenshot is a lower-quality copy than a saved file, and that can matter for matching, so crop carefully and keep the photo as large as you can.
On desktop: right-click and save
Open the post on threads.com, right-click the image and choose Save Image As. This is ordinary browser behaviour rather than a Threads feature, and it works on most posts. If the right-click menu does not offer the save option on a particular post, screenshot the image instead and crop it.
What the in-app Save button really does
Tapping the three-dot menu on a post and choosing Save keeps the post in your saved items inside Threads. It does not download the photo, and it does not give you a file you can upload to Lens or TinEye. Do not confuse it with saving the image.
Your own photos only: Download your information
If the photo is one you posted yourself, Meta offers an export route: Threads Settings, then Account, then Download your information, or the same export through the Instagram Accounts Center. Meta says preparing the export can take up to 30 days and the download link expires after a few days. This only returns your own media, never other people’s posts, so it is no help for checking someone else’s photo.
Worked Example: Tracing a Threads Profile Photo to Its Source
The method above is only useful if it works on a real photo, so here is a real test. The scenario is the one this guide is built for: a profile photo on Threads that looks like a stock portrait, saved the way a Threads user would save it, then run through both engines live.
The test photo is a close-up portrait of a smiling woman, published on Unsplash on 15 May 2017 by photographer Michael Dam, taken in Kolding, Denmark. It is a widely reused stock portrait, with 899,921,007 views and 2,769,604 downloads on its Unsplash page at the time of writing, and it is free under the Unsplash Licence. That makes it a good test: if the engines work, they should find the original, and they should also show the reuse trail.
Google Lens: the source is there, but not where you look first
Lens was searched by pasting the image address into lens.google.com/uploadbyurl. The default visual matches tab loaded 60 result tiles, and none of them was the exact portrait. They were thematically similar images: other smiling women, women in red tops, and dental and smile-makeover pages. Lens understood the subject, a smiling woman, but it did not identify this exact photo in the visual tab.
The Exact matches tab told a different story. Google gave no headline total there, so the loaded links were counted by hand: 397 result links in that page view. The top results identified the photo as a widely reused stock portrait, led by Dreamstime copies. The exact Unsplash source page was in the list, dated 14 May 2017 in the Lens listing. The lesson is plain: on Lens, always open the Exact matches tab. The visual tab answers “what does this look like”, while the Exact matches tab answers “where has this exact photo appeared”.
TinEye: exact copies, and a date for the first sighting
TinEye was searched by image address at tineye.com. It returned 3,439 results on the first load, and 3,440 on a second load, after searching 86.9 billion images. Its headline figure was “First indexed by TinEye on May 26, 2017”. The top results named the same widely reused stock portrait: a Shutterstock copy first, then a Dutch law firm page using the file, then a student news site.
The exact Unsplash source page did not appear in the unfiltered top results, but filtering by website gave 31 unsplash.com results, and the exact source page was on the second page of that filtered view. That is the TinEye habit to learn: when the top results are crowded with copies, filter by website to find the original.
What the test proves
Both engines found the original Unsplash page, but neither put it first. Lens needed the Exact matches tab, and TinEye needed the website filter. That is normal for a photo that has been copied thousands of times. It also shows what a reuse trail looks like when it works: a stock portrait leaves a long trail of copies, while a genuinely private photo, or a photo made by AI, may return few or no exact matches at all. A short result list is information, not a failed search.
Google Lens vs TinEye on a Threads Photo
Use both engines. They answer different questions, and the worked example above shows why one alone is not enough.
| Engine | Best for | What it showed in our test | Watch out for |
|---|---|---|---|
| Google Lens | Visual matches and context: what the photo shows, and pages that use it | 60 visual tiles of similar images; 397 exact-match links counted by hand; exact Unsplash source page present in Exact matches | The visual tab shows lookalikes, not copies. Always open Exact matches. |
| TinEye | Exact copies and the earliest use: where the photo first appeared online | 3,439 results; first indexed 26 May 2017; exact Unsplash source found through the website filter | The source can sit pages deep. Filter by website and sort by oldest first. |
Lens is free and needs no account. You can drag a saved file into the search box on desktop, paste an image address, or right-click any image in Chrome and choose Search with Google Lens. On Android, open the Google app or Chrome, tap the Lens icon in the search bar, and take or upload a photo. Google’s own help page lists all of these routes, and it notes that results can include similar images, websites carrying the image, and objects found in it.
TinEye is also free for web searches. You can enter an image address, upload a file, paste an image from the clipboard, or drag and drop onto the search page. Its index holds over 86.8 billion images, and it states that your search image is never saved or indexed. Its sorting is the feature that matters most here: sort by oldest first to find the earliest appearance, which is usually the closest thing to the original.
How to Read the Results
A long list of matches is not the answer. The answer is the earliest credible source, and finding it takes a few minutes of reading.
Start with the oldest match. On TinEye, sort by oldest first and open the earliest result that looks like a real source page, a stock library, a news site, or a photographer’s portfolio. Check the date on that page. A photo first indexed in 2017 cannot have been taken for a Threads account created in 2025.
Then separate copies from the original. Stock copies on Dreamstime or Shutterstock, and reused copies on blogs and business sites, are signs that the photo is a stock image. The original is usually the stock library page itself, or the photographer’s own site. In our test, the Unsplash page was the original, and the Dreamstime and Shutterstock listings were copies sold under other licences.
Crop before you search, not after. If the photo is small inside a screenshot, Lens and TinEye match the whole frame, menus and all, and the results get worse. Crop to the photo itself, and if the photo shows a person, crop to the person rather than the background. Google’s Lens help makes the same point: for a more specific result, select a smaller area.
Run the search twice if the first run looks thin. A screenshot copy can return fewer matches than a saved file, and a cropped copy can return different matches from a full one. If Lens gives you lookalikes and TinEye gives you copies, you have two halves of the same answer.
What a Match Can and Cannot Tell You
A match proves that a photo has appeared somewhere before. It does not prove who the person in the photo is. That distinction is the whole point of this guide, and it is worth stating plainly.
A photo can show that a Threads profile picture is a stock portrait, a stolen photo, or an image copied from another account. It cannot confirm that the person in the photo runs the account, and it cannot name a private individual. Face-recognition tools claim to do exactly that, and you should not use them. They are built to identify private people from photos, and a visual match from one is not proof of identity.
The same caution applies to a zero result. A photo that returns no matches may be private, recent, AI-generated, or simply not indexed. Google’s own AI Overview on this keyword ends with the same warning: AI-generated images or private photos may return few or no exact web matches. Treat a zero as “not found online”, never as “this photo does not exist” or “this person is real”.
Private accounts and restricted posts are not broadly indexed either. Neither Lens nor TinEye can easily search inside gated social media content, so a photo that only ever lived behind a private account will leave almost no trail. That is a limit of the method, not a sign that the photo is original.
When the Photo Looks Like a Scam
Most people who reverse search a Threads photo are doing a scam check, not a curiosity check. The profile picture looks too good, the account is new, and the posts push an investment, a giveaway, or a romance. The method in this guide answers the first question: is this photo reused?
If the search shows the photo is a stock portrait or a stolen image used on other accounts, treat the account with suspicion and stop engaging. If you want the full catfish check, our guide to spotting a catfish covers the wider pattern: the story, the contact details, and the pressure to move off the platform. This article owns the platform how-to, and that guide owns the catfish check, so this section stays short on purpose.
Report the account inside Threads if the photo is stolen or the account is impersonating someone. Do not message the account to ask for proof, and do not send money, crypto, or gift cards to anyone who asks you to verify an identity by paying. No genuine person needs a payment to prove who they are.
What Not to Do
Three tools and habits will waste your time or put you on the wrong side of the line.
First, do not use “who viewed my profile” tools. Threads shows no notification, view count, or list of recent visitors, for personal, creator, or business accounts, and Meta does not expose profile-view data through its API. Any third-party app or site claiming to show who viewed a Threads profile is not legitimate. Such claims are typically used to harvest login details, show fabricated data, or earn ad revenue. The same warning applies to Instagram and Facebook, which also show no profile visitors in their standard apps.
Second, do not use face-recognition search tools on a profile photo. The top competitor guide for this topic recommends exactly that: screenshot the Threads profile photo and run it through a paid face-recognition search. That is the opposite of this guide’s method. A face search tries to name the person, and a visual match from one is not proof of identity. Lens and TinEye match the image, not the face, and that is the right tool for this job.
Third, do not pay for a lookup to “verify” a Threads account. Paid people-search sites that promise to identify the person behind a photo or a username are selling a guess. The free method in this guide, save the photo, search it on two engines, read the earliest source, answers the question that actually matters: is this photo reused?
The Method in Short
Open the Threads post and save the photo: screenshot and crop on iPhone and Android, right-click and Save Image As on desktop. Upload the saved file to Google Lens and check the Exact matches tab, then upload it to TinEye and sort by oldest first. Open the earliest credible source and compare it with the Threads post. If the photo is a stock image or a copy used elsewhere, you have your answer. If nothing matches, say so honestly and do not force a conclusion the results do not support.
The same two-step method works for photos from other messaging and social apps, not just Threads. Our guides to reverse image search on WhatsApp, reverse image search on Signal and reverse image search on Telegram follow the same save-then-search pattern, with each app’s own save steps. For the full method in one place, start with our how to reverse image search guide.
Can you reverse image search directly on Threads?
No. Threads has no built-in reverse image search, no image upload box in its search, and no filter for image posts only. Its search finds text, accounts and hashtags. To check a photo, save it to your device first, then upload it to Google Lens or TinEye. That two-step method is the only way to run the check.
How do I save a photo from Threads on iPhone?
Open the post, tap the photo to view it full screen, then take a screenshot and crop it tight so only the photo remains. Threads has no download button for photos on iPhone. Older guides describe a long-press route with a Save Image option, but that option is gone from the current app.
How do I save a photo from Threads on Android?
There is no confirmed built-in save for photos on Android, so use a screenshot. Press power and volume-down together, then crop the screenshot so only the photo remains. The three-dot Save option in the app keeps the post in your saved items only. It does not download the photo file.
Which is better for a Threads photo, Google Lens or TinEye?
Use both, because they answer different questions. Lens is best for visual matches and context, showing similar images and pages that use the photo. TinEye is best for exact copies and the earliest use, with a first-indexed date and sorting by oldest first. Lens needed the Exact matches tab and TinEye needed the website filter to find the original.
Why does my Threads photo search return no matches?
A photo with no matches may be private, recent, AI-generated, or simply not indexed. Neither Lens nor TinEye can easily search inside gated social media content, and private accounts leave almost no trail. Try a saved file instead of a screenshot, crop the photo tight, and run both engines before concluding the photo is original.
Can a reverse image search identify the person in a Threads photo?
No. A reverse image search shows where a photo has appeared before, not who the person in it is. A match can prove a profile picture is a stock portrait or a stolen photo. It cannot name a private individual, and face-recognition tools should not be used for that. A visual match is never proof of identity.







