Text Expanders and Clipboard Managers

Most productivity software asks you to change how you work. These two ask you to change nothing, and then quietly remove a few hundred keystrokes a week from your day.

A text expander watches for a short trigger and replaces it with something longer. A clipboard manager remembers what you copied before the thing you just copied. Neither is clever. Both are the sort of tool you notice only when you sit at a machine that does not have them, at which point you notice constantly.

What each one actually does

The expander is the one with a learning curve, and it is short. You define a trigger — say :sig — and the text it becomes. Type the trigger anywhere, in any application, and the text appears. Better tools go further: fill-in-the-blank forms, the current date computed at expansion time, the output of a shell command dropped into place.

The clipboard manager has no learning curve at all. It keeps a list of the last few hundred things you copied and gives you a keyboard shortcut to search it. That is the whole product, and it fixes the specific, daily annoyance of copying something over the thing you were about to paste.

The options, and what they cost

Published rates at the time of writing.

Tool	Platforms	Cost	Best when
Espanso	Windows, macOS, Linux	Free, GPL-3.0	You want snippets as files you control
Raycast	macOS, Windows, iOS	Free; Pro $10/month, $8 annually	You want launcher, clipboard and snippets in one
TextExpander	macOS, Windows, iOS	Free for five snippets; $6/user/month annually	A team needs one shared, maintained library
Alfred	macOS	Powerpack, £34 one-off	You prefer buying a licence once
PowerToys	Windows	Free, open source	You are on Windows and want the basics covered

Two things are worth pulling out of that table. Raycast's free plan already includes clipboard history — three months of it — and snippets, so on a Mac you can have both tools working before lunch without paying anything. And Alfred is one of the last pieces of desktop software still sold as a one-off licence rather than a subscription, which for some people settles it on principle alone.

Why we keep coming back to Espanso

Espanso is free, runs on all three desktop platforms, and stores its configuration as YAML files in a folder. That last detail is the one that matters more than it sounds.

Snippets in a text file can go in a git repository. They can be reviewed, copied to a new machine in one command, and diffed when something changes. Every commercial expander stores its library in a proprietary sync service, which is fine until you leave, and a nuisance the day you want your snippets somewhere else. Plain files sidestep the whole question.

It also does the advanced things: forms that prompt for values before expanding, shell command output, regex triggers, and a package hub for shared sets. If you already keep a set of dotfiles, this belongs beside them — the same instinct we described in our piece on terminal setups that are actually faster.

Give every trigger a prefix that never occurs in normal writing. A leading colon costs one keystroke and saves you from an expansion firing in the middle of a word for the rest of your life.

The twenty minutes that pays for itself

Do not build a library. Notice one instead. For one week, every time you catch yourself retyping something, write it down. At the end of the week you will have between eight and fifteen items, and that list is your snippet set.

Ours, for what it is worth, has settled on roughly this shape:

• Identity. Email address, postal address, phone number, company registration details.
• Replies. The polite decline, the "can we move this to email" line, the availability paragraph.
• Structure. A meeting-notes skeleton, a bug report template, a pull request description with the headings already in place.
• Fiddly strings. The date format your team uses, a currency symbol your keyboard hides, the em dash.

Fifteen entries, expanded a few times each per week, is a few thousand keystrokes a year that you no longer type or mistype. The mistyping is the real gain. A snippet is correct every time, and an address typed from memory is not.

The two mistakes worth avoiding

The first is the enormous library. Someone builds a hundred snippets in an afternoon, remembers eleven of them, and abandons the tool a month later because it felt like homework. Add snippets when you notice the need, never in advance.

The second is forgetting what the clipboard history contains. It holds whatever you copied, and what you copied includes passwords, one-time codes and API keys. Every serious tool can exclude specific applications, or expire entries after an hour — turn that on when you install it, not after an incident. Keep the history local rather than synced unless you have a specific reason not to.

What we would do

On a Mac, install Raycast, use the free clipboard history immediately, and add Espanso for expansion if you want your snippets as files. On Windows, PowerToys plus Espanso covers everything without spending anything. On Linux, Espanso and whatever clipboard manager your desktop environment already ships.

Pay for TextExpander only when the snippets need to be shared and maintained by a team, because that is the problem it solves that the free tools do not. For one person, the free options are not a compromise. They are the answer.