How to Open AHK File: Run, Edit and Check AutoHotkey Scripts

What is an AHK file?

An AHK file is a plain-text script written for AutoHotkey, a free, open-source automation program for Microsoft Windows. The script tells AutoHotkey what to do: remap keys, type a phrase when you enter an abbreviation, click buttons, move windows or launch programs. The file itself is ordinary text you can read in Notepad; nothing happens until AutoHotkey runs it. That's why there are two ways to open AHK files: run them with AutoHotkey, or open them as text to read or edit.

AutoHotkey was first released in November 2003 by Chris Mallett and is licensed under the GPLv2. Two incompatible generations of the language exist. AutoHotkey v2 (v2.0 released December 20, 2022) has been the official primary version since January 22, 2023. AutoHotkey v1.1 is now legacy: its final update was published in March 2024. Many scripts you find in old forum posts and tutorials are still v1, which is why "this script requires AutoHotkey v1/v2" messages are so common.

A typical script is just a few lines. This one makes Ctrl+J show a message and expands "btw" as you type:

#Requires AutoHotkey v2.0
^j::MsgBox "Hello!"        ; Ctrl+J shows a message box
::btw::by the way           ; typing btw + space types "by the way"

How to open an AHK file (quick answer)

Short answer: to open AHK files, run them with AutoHotkey on Windows, or open them as text to read and edit them. Do this:

1. Read it first. Drop the file into the viewer above or right-click it > Open with > Notepad. Check what the hotkeys do and whether anything is flagged.
2. Install AutoHotkey. Download the v2 installer from autohotkey.com (the official site) and click Install. Choose Current user if you aren't an administrator.
3. Double-click the .ahk file. A green H icon appears in the notification area (bottom right): the script is running. If it was written for v1, the launcher offers to download v1 for you.
4. Use, edit or exit it. Press its hotkeys. Right-click the tray icon to Edit Script, Reload Script or Exit.

How to run an AHK script on Windows 11 and 10

To run an AHK script you need AutoHotkey installed; Windows has no built-in support for the format, so on a new PC you can't open AHK files as programs until you add it. Install AutoHotkey v2, the current version, even if your script is old: its launcher can fetch v1 automatically when a script needs it.

1. Go to autohotkey.com and click Download. Take the current v2 installer (named like AutoHotkey_2.0_setup.exe). Avoid download sites and look-alike repositories: the official sources are autohotkey.com and the AutoHotkey project's own GitHub page.
2. Run the installer and click Install. Without administrator rights, select Current user; it installs to %LocalAppData%\Programs\AutoHotkey instead of Program Files.
3. When installation finishes, the Dash opens. It's AutoHotkey's control panel (later reachable from the AutoHotkey entry in the Start menu) with New script, Compile, Help files, Window Spy, and the launcher and editor settings.
4. Double-click your .ahk file. The script starts and its green H tray icon appears. Many scripts don't open a window at all; they just wait for their hotkeys.
5. To stop it, right-click the tray icon and choose Exit. You may need to click the ^ arrow on the taskbar to see hidden icons.

Running v1 and v2 scripts on the same PC. You don't need two separate installs. AutoHotkey v2's launcher lets multiple versions share the .ahk extension; the official guide says installing v1 and v2 into different folders "is not necessary and is currently not supported". The launcher reads the script's #Requires line, or guesses from the syntax, and starts the matching interpreter. If it can't decide, it shows a menu so you can choose.

AutoHotkey v1 vs v2: which version does your script need?

Check the first lines: #Requires AutoHotkey v2.0 means v2, and #Requires AutoHotkey v1.1 means v1. If there's no such line, the syntax gives it away. v2 removed the old "command" syntax, so v1 scripts don't run on v2 without changes, and v2 scripts don't run on v1.

These are the same kinds of clues AutoHotkey's own launcher looks at: commas after command names, legacy = assignments, #NoEnv/#If versus #HotIf, single quotes and fat arrows. Hotkeys (^j::) and simple hotstrings (::btw::) look the same in both versions, so checking the version first saves trouble when you open AHK files found online. The checker shows exactly which lines point to which version.

Common AHK errors and how to fix them

Most errors you see when you open an AHK file come from a version mismatch: a v1 script meeting v2, or the reverse. Here are the messages you're most likely to see and what each one means.

"It looks like the script you are trying to run requires AutoHotkey v1, which is not installed."

The v2 launcher decided the script is v1 code. Click Yes to "download and install AutoHotkey v1", which keeps your v2 install working next to it. If you'd rather stay on v2 only, the script has to be converted to v2 syntax. The same message appears with "v2" if an older setup meets a v2 script.

"#Requires AutoHotkey v2.0 … This line does not contain a recognized action."

An old AutoHotkey v1 that doesn't understand the #Requires directive is trying to run a v2 script. Install AutoHotkey v2 from autohotkey.com; its launcher then routes each script to the right version.

Error dialog pointing at a line like MsgBox, Hello or x = 5

That's v1 syntax running under v2. Add #Requires AutoHotkey v1.1 as the first line so the launcher uses v1, or rewrite the line in v2 style (MsgBox "Hello", x := 5). The reverse also happens: MsgBox("Hello") isn't valid v1.

Accented characters or emoji come out garbled

v2 reads script files as UTF-8 by default, while v1 doesn't. Save the file as UTF-8 with BOM (in Notepad: File > Save as > Encoding) so both versions read the special characters correctly.

Hotkeys don't work in some windows

Windows stops a normal script from sending keys to programs that run as administrator. If you use an administrator account, start the script with Run with UI access from its right-click menu: it can then work with admin windows without itself running as admin. Running the whole script as administrator also works, but only do that for scripts you trust.

Nothing seems to happen when you double-click

Most scripts run silently in the background. Look for the green H icon in the notification area, then try the script's hotkeys; the viewer's Hotkeys tab lists them all.

How to edit an AHK file

Any plain-text editor can open AHK files for editing. The quickest way is right-click > Edit script, which opens the file in the editor set for AutoHotkey (Notepad unless you change it in the Dash under Editor settings). After saving, right-click the script's tray icon and choose Reload Script so your changes take effect.

Don't edit with Word or WordPad: they can save formatting or change quote characters, which breaks the script. If you just need a safe copy to send or archive, the viewer's Download as .txt button saves the script with a .txt extension so nobody can run it by double-clicking.

How to read hotkeys and hotstrings in an AHK script

Hotkeys are the lines with :: after a key, and each symbol before the key is a modifier. ^!j:: means Ctrl+Alt+J. Hotstrings start with a colon: ::btw::by the way replaces "btw" with "by the way" as you type.

Hotstring options sit between the first two colons: :*: fires without an ending key, :?: fires inside words, :C: is case-sensitive, :X: runs code instead of typing text, :R:/:T: send raw text, :B0: keeps the abbreviation, and :O: omits the ending character. The viewer decodes all of these for you.

How to run an AHK script when Windows starts

Put a shortcut to the script in your Startup folder. That way you don't have to open AHK files by hand after every restart. This is the method AutoHotkey's FAQ recommends:

1. Find the .ahk file in File Explorer, select it and press Ctrl+C.
2. Press Win+R, type shell:startup and press Enter.
3. Right-click inside the folder that opens and choose Paste shortcut.

The script now starts each time you sign in. To stop that, delete the shortcut from the same folder; the original script stays where it was. Using a shortcut rather than moving the file keeps edits in one place.

How to convert an AHK file to EXE (Ahk2Exe)

AutoHotkey's compiler, Ahk2Exe, turns a script into a standalone .exe that runs on PCs without AutoHotkey installed, so the people you share it with never need to open AHK files at all. The .exe contains the AutoHotkey interpreter, your script, any files it includes and any files added with FileInstall.

1. Open the Dash (Start menu > AutoHotkey) and choose Compile. Ahk2Exe is a separate automatic download, so the first time the Dash offers to install it.
2. Pick your .ahk file as the source, choose where to save the .exe (and, if you like, a custom icon), then start the conversion. The .exe appears in the folder you chose.
3. Afterwards you can also right-click any .ahk file > Compile script, or use the Convert .ahk to .exe shortcut in the Start menu.

Two things to know. First, compiling is not protection: AutoHotkey's documentation notes that compression "does not prevent the source code from being extracted by tools dedicated to that purpose", so don't put passwords in a script. Second, compiled scripts trigger antivirus warnings more often than plain .ahk files, especially if they are compressed with a packer such as UPX or MPRESS (the default install doesn't include one). You can't convert an AHK file to a BAT, VBS or PowerShell file automatically; the languages are different and would need rewriting.

Is an AHK file safe to open?

Opening an AHK file as text is completely safe; running it is as risky as running any program. Viewing the file in Notepad or the checker on this page can't do anything. Once AutoHotkey runs it, though, the script has your user permissions: it can type and click for you, start programs, download files, delete data and change settings. Some malware has been written in AutoHotkey, so treat a script from an unknown source like an unknown .exe.

Before you open AHK files that came by email, chat or a forum, read them. Red flags to look for before you run a script (the checker highlights all of these):

• Download or UrlDownloadToFile followed by Run: downloads something and starts it.
• powershell, mshta, certutil or cmd /c inside a Run command, especially with -EncodedCommand.
• Long blocks of random-looking letters (Base64), or text built from dozens of Chr() calls: a common way to hide commands.
• RegWrite to a ...\CurrentVersion\Run key or copying itself to A_Startup: makes it start with Windows.
• InputHook or Input that collects your typing and then writes it to a file or sends it somewhere.
• ProcessClose or WinKill aimed at antivirus or security tools.

A script that only defines hotkeys, hotstrings and window shortcuts, with no downloads, registry writes or command interpreters, is the normal, harmless kind. Still, a static check like ours reads text patterns only; it can't see what a script builds at run time, so it doesn't replace common sense or a real antivirus.

Open AHK files on Mac, Linux, iPhone and Android

On any system other than Windows you can open AHK files to read them, but you can't run them: AutoHotkey is a Windows-only program, and there's no official version for macOS, Linux, iOS or Android.

• Mac: open the file in TextEdit (right-click > Open With > TextEdit) or use the viewer on this page in Safari or Chrome. For similar automation on macOS, Hammerspoon is a free tool scripted in Lua; the logic must be rewritten.
• Linux: any text editor opens it. AutoKey is a free, open-source Linux program for hotkeys and text expansion, scripted in Python; it cannot run AutoHotkey scripts.
• iPhone, iPad and Android: save the file to Files (iOS) or your Downloads folder (Android) and open it with a text-editor app, or use the viewer on this page in your mobile browser to open the AHK file and see the script and its hotkeys.

If you need the script itself on a Mac or Linux PC, the realistic option is a Windows installation (for example, a Windows virtual machine) with AutoHotkey installed.

Related file extensions

Sources and technical references

Facts on this page were checked against AutoHotkey's official documentation and project pages on October 4, 2026.

• AutoHotkey — official website — official downloads; free and open source.
• How to Install AutoHotkey (v2 docs) — installer, Current user option, Dash, v1/v2 launcher co-existence.
• Using the Program (v2 docs) — the launcher's version detection, the Dash, install folders, Run with UI access.
• #Requires directive (v2 docs) — syntax and the error older versions show.
• Changes from v1.1 to v2.0 — removed command syntax, legacy assignment, ComObject.
• Scripts & Ahk2Exe compiler (v2 docs) — what a compiled .exe contains, source extraction, UTF-8 default.
• AutoHotkey FAQ — run at startup (shell:startup), antivirus false positives.
• Hotkeys and Hotstrings (v2 docs) — modifier symbols and hotstring options.
• Edit (v2 docs) — default editor and Editor settings in the Dash.
• AutoHotkeyUX on GitHub — source of the launcher and its "requires AutoHotkey v1" prompt.
• AutoHotkey — Wikipedia — history, v2.0 release (December 20, 2022), v1.1 end of life, license.
• AutoHotkey v2 Language Support (thqby) and AHK++ — VS Code extensions.
• Hammerspoon and AutoKey — Wikipedia — automation alternatives for macOS and Linux.

Frequently asked questions