Why you ought to post the imagesearch code you have tried

why-post-imagesearch-code-tried-Infographic-topYou may already know how Autohotkeys Imagesearch works or you may still be learning. Whether your new or not, sometimes you still need to ask questions. One of the best places to do that is the Autohotkey forums.

Most of the time I’d say just ask, but when asking about complex commands like Imagesearch the possible things that can go wrong are so many that without seeing the tried code, it is often very hard to be of any help.


Why ImageSearch you say?

Having helped a lot of people with anything from simple macro’s or autofire scripts using ImageSearch, up to full browser or office automation programs where ImageSearch was a small part.

I find that most of the time I need to ask the poster of the question for any code that they have tried, so i started thinking about if others needed to ask the same thing.


Researching Autohotkeys Imagesearch

So I looked in to some older ImageSearch topics and ended up using some of my free time doing a lot of research on forum posts about Autohotkeys Imagesearch and to share some of the insight with you, I have made an infographic of Why you ought to post the ImageSearch code you have tried.




Use This Graphic for FREE on Your Site!

You may use the infographic above on your website, however, the license I grant to you requires that you properly and correctly attribute the work to me with a link back to my website by using the embed code below.





…and an Embed Code:


  1. AutoHotkey ImageSearch returns “not found” when Windows changes only few pixels in an image. ImageSearch would be a lot more useful if it was possible to do a partial match, e.g. 95%, 99%.

    1. Yeah Autohotkeys ImageSearch does not support a true partial match, but most of the time you can get close to the same thing by using the shades of variation option and/or the transparency option, as this will let you match most images even if a few pixels are off.

Leave a Reply