AutoHotkey vs. FlitKey (2026): Which One Actually Fits Your Workflow?

AutoHotkey vs. FlitKey at a glance

Both rows say "$0," so this isn't a pricing decision. It's a scope decision.

The core difference: automation versus expansion

AutoHotkey is a programming language. A hotstring like ::btw::by the way expands text, but the same engine can inspect the clipboard, detect the active application, move the mouse, wait for a window to appear, or call a Windows DLL directly. Text expansion is a side effect of what AutoHotkey is actually for.

FlitKey doesn't try to be that. It defines a trigger, maps it to an expansion (static text, a date, clipboard content, or a cursor placeholder), and stops there. No scripting layer. No window detection.

That's a real limitation, not a marketing simplification. Say your workflow needs to pull a ticket number out of a copied URL and type just that; FlitKey can't do it, because it only expands what you've already defined ahead of time.

What is AutoHotkey?

AutoHotkey has been the default answer to "how do I automate Windows" since 2003. It's free, open source under GPLv2, and currently sits at version 2.0.26 as of May 2026, with the older v1 branch retired in 2024. It runs entirely on Windows.

Where it's strong

• Real automation, not just typing: Hotkeys can read the clipboard, extract text with pattern matching, launch applications, and simulate keystrokes or mouse actions.
• Deep Windows integration: DllCall and COM support let scripts reach into other applications and the OS directly, territory no text expander touches.
• A large, mature community: Two decades of forum threads, shared scripts, and Stack Overflow answers mean most problems already have a documented answer.
• Custom hotkeys for anything: Ctrl+Alt+P can open a folder and Ctrl+Shift+T can open a portal; hotkeys aren't limited to inserting text.

Where it's limited

• Windows only: There's no official macOS or Linux build. Running it under Wine or CrossOver on Linux is possible but unofficial, and behavior depends on which Win32 APIs a given script calls.
• You have to learn a scripting language: Hotstrings are approachable, but anything beyond basic text swaps means learning AutoHotkey's own syntax.
• No built-in way to find what you've already written: There's no default search across your hotkeys and hotstrings; you either remember the trigger or open the script file and read it.
• Sharing means sharing script files: There's no packaged import/export format built for handing snippets to a Linux or macOS teammate, because AutoHotkey doesn't run there anyway.

What is FlitKey?

FlitKey is a free, MIT-licensed text expander for Windows 10/11 and Linux, currently at version 0.6.0. It runs locally with no account, no cloud sync, and no telemetry, a claim you can check yourself by watching its network traffic (there isn't any).

Where it's strong

• Cross-platform, without a scripting language: The same trigger-to-expansion model works on Windows and Linux (X11), set up through a GUI snippet manager instead of code.
• Migration path built in: It imports Espanso .yml files, AutoHotkey .ahk hotstrings, and CSV/TSV/JSON snippet lists, so switching doesn't mean rebuilding a library from scratch.
• Starts stocked: Six built-in packs (developer, AI prompts, support, sysadmin, design, and everyday productivity) cover 46 snippets you can load with one click instead of writing them yourself.
• A searchable picker: Alt+Space opens a snippet overlay on X11 and Windows, so you can find a snippet by browsing instead of recalling the exact trigger.
• Open source, no upsell: Every feature ships in the free build. There's no paid tier to compare it against.

Where it's limited, genuinely

• It's new: Version 0.6.0 doesn't carry AutoHotkey's twenty years of edge-case testing. There's no long community track record to point to yet.
• No macOS build: Same gap AutoHotkey has.
• Wayland is partial: Typed triggers and global hotkeys don't work on Wayland sessions. That's a Wayland platform restriction that also affects Espanso and AutoKey, not something specific to FlitKey, but it still means Wayland users get the picker-and-clipboard workflow instead of full expansion.
• The Windows installer isn't code-signed: SmartScreen will flag it as an unknown publisher on first run.
• It can't touch clipboard-parsing or window-control automation: If the shortcut needs logic, not just text, FlitKey is the wrong tool.

Feature-by-feature comparison

Setting one up: the actual difference in practice

AutoHotkey's signature hotstring, straight from its own documentation:

::btw::by the way

Type btw, and it expands to "by the way." For anything more complex, like typing a signature on a hotkey instead of a hotstring, you write a script:

^!s::  ; Ctrl+Alt+S
Send Sincerely,{Enter}John Smith
return

That's still simple. But the moment you want the script to check the active window or grab clipboard text, you're writing real code. And you're maintaining that code as your workflow changes.

FlitKey skips the code entirely. Open the snippet manager, type a trigger like ;addr, enter the expansion text (or a placeholder for today's date, clipboard content, or final cursor position), and save. There's no script file to keep in sync. There's also no branch point to add logic later, if your needs outgrow text substitution.

When AutoHotkey is the better fit

You're on Windows only, and you're staying there. If cross-platform isn't a factor, AutoHotkey's Windows-only design isn't a cost.

The shortcut needs to do something, not just say something. Parsing a clipboard URL down to a ticket ID, opening a specific folder, controlling another application's window: none of that is text expansion, and FlitKey doesn't attempt it.

You want two decades of prior art. Whatever automation problem you're solving, someone has likely posted a working AutoHotkey script for something close to it.

You're comfortable maintaining scripts. If code review, version control, and debugging a syntax error don't scare you off, AutoHotkey's ceiling is much higher than any text expander's.

AutoHotkey to FlitKey Importer Fidelity (v0.6.0)

FlitKey's built-in .ahk importer parses AutoHotkey v1 and v2 scripts to extract hotstrings into visual JSON snippets. Here is what translates directly and what is intentionally omitted:

When FlitKey is the better fit

You work across Windows and Linux. AutoHotkey doesn't have an official answer for that; FlitKey's core expansion model does, with the caveat that Wayland sessions use Quick Insert.

You want zero scripting. If the job is "insert this paragraph when I type this trigger," writing and maintaining a .ahk file is more tool than the task needs.

You're migrating away from AutoHotkey and don't want to start over. The built-in importer reads .ahk files directly into your visual snippet library.

Offline verification matters to you. No account, no telemetry, and a claim you can check yourself rather than take on faith.

Use both

These aren't mutually exclusive. A common split: FlitKey handles day-to-day text (replies, addresses, code comments, signatures) across whatever machine you're on, while AutoHotkey handles the Windows-specific automation that actually needs logic, things like clipboard parsing or multi-step scripts. Different job, different tool.

Cost: a wash, with a catch

Both are free. AutoHotkey is GPLv2; FlitKey is MIT. Neither has a paid tier to unlock, so the real cost isn't money. It's time.

AutoHotkey's cost is the learning curve: budget real hours to get comfortable with its scripting syntax if you're starting from zero, offset by a community large enough that most patterns are already documented. FlitKey's cost is narrower scope: setup takes minutes, but you hit a hard wall the moment you need logic instead of text.

FAQ

Can FlitKey replace AutoHotkey entirely?

No, and it isn't trying to. FlitKey handles text expansion; AutoHotkey handles general Windows automation, including tasks that have nothing to do with typing. If your workflow depends on clipboard parsing, window control, or scripted logic, AutoHotkey remains the tool for that job.

Can I import my existing AutoHotkey hotstrings into FlitKey?

FlitKey's importer reads .ahk files and pulls in supported hotstring entries. Complex scripts, functions, and conditional logic don't translate; only the trigger-to-text mappings do, and FlitKey recommends a manual review after import.

Does AutoHotkey run on Linux or macOS?

Not officially. There's no native build for either. Running the Windows version through a compatibility layer like Wine or CrossOver on Linux is possible but unsupported, and results vary by which Windows APIs a given script relies on.

Is FlitKey's "free" actually free, or is there a catch?

It's MIT-licensed with every feature included in the free build: no trial, no tier, no account requirement. The source is public on GitHub, so the claim is verifiable rather than a marketing line.

Which one is more mature?

AutoHotkey, by a wide margin. It dates to 2003 and has a large, tested user base. FlitKey is at version 0.6.0: usable today, but without the years of edge-case hardening AutoHotkey has behind it.

The honest verdict

AutoHotkey and FlitKey solve different problems that happen to overlap at "type a trigger, get text back." AutoHotkey is the more powerful and more mature tool, no contest; if your work involves real Windows automation, clipboard logic, or window control, there's no honest argument that FlitKey substitutes for it. What FlitKey offers instead is narrower and simpler: it runs on Linux as well as Windows, skips the scripting requirement, and imports your existing AutoHotkey or Espanso snippets so switching doesn't mean starting from zero.

Neither answer is universally correct. Pick based on what the shortcut actually needs to do, not on which tool has the longer feature list.

Sources

• AutoHotkey official site — product overview, feature claims, license status (verified August 2026)
• AutoHotkey v2 License documentation — GPLv2 licensing (verified August 2026)
• Chocolatey package listing — AutoHotkey 2.0.26 — current version number (verified August 2026)
• FlitKey official site — feature list, platform support, pricing, version 0.6.0 details (verified August 2026)
• TurboTasking: Espanso vs AutoHotkey for Office Productivity — independent third-party comparison referenced for AutoHotkey's real-world automation use cases and search/discoverability gap (verified August 2026)

Explore more comparisons on the FlitKey comparisons hub.