A text expander watches for a short trigger you've typed — ;sig, addr, brb — and swaps it for a longer block of text you saved earlier. On Windows, the tools that do this split into four categories that differ enormously in setup cost and hardly at all in what they can produce. Every one of them expands text you already wrote down. None of them help with the sentence you're writing for the first time.

That distinction is the reason "which text expander should I use?" threads never really converge. People are answering from inside different categories, and each category is genuinely the right answer for a different person.

The Four Categories

1. Scripting tools

AutoHotkey is the archetype. A hotstring is one line — ::brb::be right back — and the same script can also remap keys, move windows, and automate whole workflows. Enormous ceiling, and you maintain a script file forever.

2. Config-file expanders

espanso is the best-known: cross-platform, open source, and configured by editing YAML files. Free and dependable if you're comfortable in a text editor, and a wall if you aren't.

3. GUI snippet managers

PhraseExpress, Beeftext, FastKeys, Breevy and GagarinSoft's own Text Replacements. You add snippets in a window, organize them in folders, and never touch a config file. This is what most people actually want.

4. Cloud, subscription-based

TextExpander and similar services sync snippets across machines and teams, with shared libraries and usage reporting. Billed monthly per seat, and your snippet library lives on someone else's server.

Picking a Category

The honest selection rule is short. If you already write scripts, category 1 costs you nothing you weren't paying anyway. If you want free, open source, and don't mind YAML, category 2. If you want to add a snippet in ten seconds without learning anything, category 3 — and this is the correct default for most people. Category 4 only earns its subscription when a team needs one shared, governed snippet library across several machines.

Category Setup cost Best for
Scripting (AutoHotkey) High — you write and maintain a script People automating far more than text
Config file (espanso) Medium — YAML, per machine Free, open source, cross-platform needs
GUI snippet manager Low — add a snippet in a window Almost everyone else
Cloud subscription Low, but recurring per seat Teams sharing one governed library
Windows itself offers no category at all. macOS has had system-wide text replacement in System Settings for years; Windows has never shipped an equivalent, which is why every option above is third-party software. Why Windows still has no system text replacement goes into the history.

What Every Category Shares

Here's the part the comparison articles skip. Whichever category you land in, the mechanism is identical: you decide in advance what text you'll need, you write it down, you give it a trigger, and you remember the trigger later. The tool contributes matching and pasting. Everything that made the snippet useful — the wording, the decision that this phrase was worth saving — was your work, done ahead of time.

That model is excellent for text that must come out identical every time: an email signature, a mailing address, a support macro, a legal disclaimer, an onboarding paragraph your team agreed on. Predictability is the feature. You would not want a signature that varies.

But look at what you actually type in a day. A handful of blocks genuinely repeat verbatim. The rest are messages that rhyme without repeating: the same apology worded slightly differently, the same explanation shaped around a different customer's problem, the same status update with this week's details. No trigger fits them, because you'd have to have written each one down first — and if you could have, you'd have needed only one.

The gap in one sentence: a text expander can only give back the sentences you already saved, which means the typing it can't help with is, by definition, most of it.

The Other Half: Predicting Instead of Expanding

The complementary tool works the opposite way round. Instead of matching a trigger against a saved list, it reads the sentence you're currently writing and proposes how it ends — no trigger, no prior setup, nothing written down in advance.

Typeahead is that tool for Windows. It runs from the system tray and shows an inline grey suggestion at your caret in almost any desktop app — WhatsApp, Telegram, Slack, Chrome, Edge, Firefox, Outlook, Thunderbird, Word, Notepad, Notepad++, and VS Code's chat and text panes, with code buffers off by default so it doesn't compete with a dedicated code completion tool. Press Tab or the right arrow to accept it, or keep typing and it disappears.

Suggestions come from a local LLM (Qwen 3.5 via llama.cpp) running entirely on your PC. Nothing you type is transmitted anywhere: no account, no text telemetry, and password fields and financial apps are excluded automatically. Before you've downloaded a model at all, custom snippets and dictionary-based autocomplete still work.

Note what the prediction half asks of you: nothing. No trigger to define, nothing written down in advance — it reads the sentence you're already writing and proposes an ending. Typeahead does also carry its own snippets for exact-match text, but they're the smaller half of what it does.

Do You Need Both?

Often, yes — and they don't conflict, because they fire on different things. An expander fires on an exact trigger you typed; Typeahead offers a suggestion you accept with Tab or the right arrow. If your repeated text is mostly fixed blocks, a dedicated expander alone is enough, and Text Replacements is GagarinSoft's take on category 3: a GUI snippet manager for Windows, one-time purchase, no config files. If your repeated text is mostly variations on a theme, an expander will feel like it never quite fits, and prediction is the piece you were missing.

Run them together and the split is clean: triggers for the paragraphs that must be identical, prediction for everything else.

Frequently Asked Questions

Does Windows have a built-in text expander?
No. Windows has no system-wide text replacement feature comparable to the one in macOS System Settings. Individual apps sometimes have their own — Word's AutoCorrect entries, Outlook's Quick Parts — but they only work inside that app.
Is AutoHotkey still the best option?
It's the most powerful and it's free, but it's a scripting language, not an app. If text expansion is all you want, a GUI snippet manager gets you the same expansions without a script to maintain. If you're already automating other things with AHK, adding hotstrings costs you nothing extra.
What's the difference between a text expander and autocomplete?
An expander replaces a trigger you defined with fixed text, always identically. Autocomplete predicts how your current sentence continues from context, and the suggestion differs each time. Autocomplete vs. autocorrect vs. text expansion covers all three side by side.
Can I use a text expander and Typeahead at the same time?
Yes. They respond to different events — an expander to an exact trigger string, Typeahead to the sentence context plus a Tab or right-arrow press — so they can run together without competing for the same keystrokes.
Do any of these work offline?
AutoHotkey, espanso and most GUI snippet managers work fully offline; cloud services need a connection to sync. Typeahead is offline too — the language model runs locally, so suggestions keep working on a plane or a locked-down network.

Get Typeahead

One-time purchase, no subscription. Windows 10 / Windows 11. 7-day free trial.

 Get it on Microsoft Store