AutoHotkey

ApplicationAutoHotkey Foundation

Dem still dey call am ahk, autohotkey v2, autohotkey v1

AutoHotkey FoundationSystem

Hotkey and automation scripts for Windows. v1 versus v2 syntax dey different. Di process na AutoHotkey.exe. No be Power Automate.

Wetin you need know

AutoHotkey na local scripts. v1 versus v2 dey different. No be Power Automate.

AutoHotkey.exe dey run .ahk files. v2 syntax no be v1. Power Automate na Microsoft product.

Wetin e be?: Scripting and hotkeys
Still current?: Yes, see Current status
Official download?: Use di vendor link inside dis article

Feex tok say

If .ahk file throw v2 syntax error, I dey check whether na v1. I no dey open Power Automate for dat script.

Wetin be AutoHotkey?

AutoHotkey dey run .ahk scripts. v1 and v2 na different languages. Power Automate flows no go open here.

If you never use am before

If you want keyboard shortcut wey dey type text or remap keys, AutoHotkey na script file plus interpreter. Install am from autohotkey.com. v2 na di current one and v1 scripts dey often break. Power Automate na Microsoft cloud/desktop flow product, no be dis exe.

Wetin dem dey use am for?

Hotkeys and remaps

.ahk files. Power Automate desktop flows na different editor.

Window automation

Send, click, and window titles. Dis one still remain AHK, no be cloud flow.

v1 versus v2

Current docs na v2. v1 script need v1 or porting. Dat na di normal break.

Na who e dey for?

People wey dey remap keys
Anybody wey receive .ahk file
Users wey dem tell make dem "just use Power Automate" for local hotkey

Current status

AutoHotkey (2004) na current scripting and hotkeys from AutoHotkey Foundation. Di vendor still dey point Windows users to https://www.autohotkey.com/.

How old e be?

AutoHotkey fork from AutoIt ideas for 2004. v2 change syntax. 2012 v1 script fit need rewrite. Power Automate land much later as different Microsoft product.

Versions

Major channels first. Exact build numbers no dey all verified here.

AutoHotkey v2

AutoHotkey v1 (legacy scripts)

System requirements

Values dey follow wetin di publisher release publicly. Workload still dey change di real need.

Minimum

Minimum system requirements
Operating system	Current supported Windows 10 or Windows 11 release, according to di vendor
RAM	E reach for Windows plus dis app. Heavy projects go want more.

Resource profile

CPU demand: Dey follow wetin you open inside di app
RAM demand: Dey follow documents, tabs, or libraries

Installed processes

Dese executables belong to dis product when e dey installed.

Installed processes
AutoHotkey.exe	Main Windows executable
AutoHotkey64.exe	64-bit v2 interpreter on top current installs

Startup components

.ahk inside Startup folder dey common. Dat na di script, no be Windows service.

File locations

Common AutoHotkey locations
Typical install	C:\Program Files\AutoHotkey\

File formats

AHK

Common wahala dem

v1 script on top v2-only install

Install v1 or port di script. Power Automate no go parse .ahk.

Antivirus flag compiled .exe

Compiled AHK na common false-positive class. Better make you use di .ahk plus official interpreter.

How to get unstuck

Install from autohotkey.com and read di v2 docs

Di docs site get versions. 2014 forum snippet na often v1.

Right-click di script and compile only if you trust am

Di interpreter plus .ahk dey easier to check pass random Autohotkey.exe inside Downloads.

No replace local hotkey with Power Automate unless you want dat kind stack

Different product, different cloud sign-in.

Alternatives

PowerToys Keyboard Manager dey remap keys without scripts. Power Automate na Microsoft flows. AutoIt na cousin language.

Official help and downloads

Start with di vendor. Random exe sites no be support channel.

Official contacts
Download	www.autohotkey.com/ Official installer or vendor page
Help	www.autohotkey.com/docs/ Vendor support
Official site	www.autohotkey.com/ Start here, no be random exe host

Related hardware

AHK light well-well. Di actions wey you dey automate (games, heavy apps) na dem dey set di load.

Technical details

Vendor version numbers dey change. Dis article no pin down any build.

Sources and verification

Recorded source label: August 2026. Dis label no establish independent verification. How we dey do research.

AutoHotkey official site · Vendor product page
AutoHotkey help · Vendor support
Foxhole process map · First-party samples on top Windows PCs. No be lab benchmark.

Dis article make sense to you?

Yes or no dey enough. Choose reason if you want, or add short note.