Visual hotkeys, macros, and text expansion for Windows. Same power, no .ahk files.
On a Windows ARM device? Download the ARM64 build.
AHK is powerful. It's also a programming language. Trigr gives you the same automation, without the .ahk files.
| Feature | Trigr | AutoHotkey |
|---|---|---|
| Setup | Click & assign | Write scripts |
| Learning curve | None | Steep |
| Visual interface | ✓ | — |
| See all bindings at a glance | ✓ | — |
| Hotkeys | ✓ | ✓ |
| Macros | ✓ | ✓ |
| Text expansion | ✓ | ✓ |
| Clipboard manager | ✓ Built-in | Custom script |
| App-specific profiles | ✓ Built-in | Custom script |
| Runs .ahk scripts | ✓ v1 + v2 bundled | ✓ |
| Custom scripting power | Limited | Unlimited |
| Source code public | Yes | Open source |
| Price | Free (beta) | Free |
Comparison reflects AutoHotkey v2 as of June 2026.
#IfWinActive blocks to maintain.AutoHotkey is more flexible, and that's not spin. If you write custom logic, parse text, loop over windows, or drive COM objects, AHK is a full programming language and Trigr isn't trying to be one.
Most people using AHK aren't doing any of that. They copied a script years ago that opens apps, pastes signatures, and remaps a few keys. That's hotkeys, snippets, and macros: exactly what Trigr does without code.
And for the scripts that genuinely need to stay code, keep them. Trigr bundles both AHK runtimes (v1 and v2), so you can paste an existing script in, assign it to a key, and run it alongside your visual bindings. Migrate the easy 90% to the editor and keep the stubborn 10% as scripts.
Get the same automation power without writing a single line of code.