Skip to main content
Participant
November 25, 2025

Can't locate specific image — originally found in stock.adobe search

  • November 25, 2025
  • 5 replies
  • 237 views

I saw this image come up in a search and used it in a design comp — now the client wants this image, but I'm unable to now locate it for high resolution download. The image ID is also not availalble. Yes, I did a reverse image lookup and it yields only similar images, not this one. Shouldn't it locate this exact image? What gives? Same goes for reverse lookup on google: the only thing that comes up is on an asian version of freepik.com.

5 replies

Participant
December 10, 2025

Bugs are frustrating, and that's what I'd call this — a bug. I always try to capture an asset ID if I think an image might get used, but every now and then it gets missed...and you run into this. Sometimes Adobe fixes bugs, sometimes you live with them a long time before they get enough notice for something to happen, and sometimes they persist forever.

Participant
December 10, 2025

That's probably true, if you have the asset ID. As explained in the original post, I do not.

Participating Frequently
December 10, 2025

This is a constant frustration of mine. Adobe Stock does not seem to have a reverse image search; it only yields similar images. And somehow, it does not find the exact image even though it is technically the most similar.

Abambo
Community Expert
Community Expert
November 27, 2025

The asset ID should give you the path to the image.

ABAMBO | Hard- and Software Engineer | Photographer
Participant
November 25, 2025

Update: I went to freepik.com (english language version) and performed a reverse lookup there — success, found the image immediately. Fortunately this same client has a freepik account so I downloaded the image there. Maybe you're thinking I got confused and originally found the image on freepik and went back to stock.adobe thinking it was there — but no, this image came up in my stock.adobe search yesterday, there's no doubt about it. So I'll call this a search bug and move on now.