copypaster vs AutoHotkey

What each tool actually is

AutoHotkey is a free, open-source scripting language for Microsoft Windows, released under GPLv2. Keystroke emulation is one feature among many: it also does hotkeys, key remapping, text replacement, window manipulation and GUI creation. Version 2 is the current line. It has been around since 2003 and has an enormous script ecosystem.

copypaster is a closed-source desktop app for Windows 10+, macOS (Apple Silicon and Intel) and Linux that does exactly one thing: it takes text you paste into it and types that text into whatever window has focus, at 20-250 WPM, with a timing model built to look like human typing. Free trial of 5 pastes, then from €4.99/mo or a €49 lifetime founders licence.

These are not the same category of product. AutoHotkey is a language. copypaster is an appliance.

Side by side

The AutoHotkey auto typer script, honestly

People searching "autohotkey auto typer" usually want this, so here it is. In AutoHotkey v2, binding Ctrl+Alt+V to type your clipboard into the focused window is one line:

^!v::SendText(A_Clipboard)

That works. It sends the characters as keystrokes, so it lands in fields that reject Ctrl+V. If your goal is "get this text in there and I do not care how it looks", you are done, for free, and you can stop reading.

The catch is the delivery profile. SendText fires at machine speed with uniform gaps. Slowing it down means looping character by character with a Sleep in between, and a fixed Sleep still produces a metronome. To get output that reads as a person typing you end up writing, and tuning:

1. A skewed interval distribution rather than a uniform random one. Real inter-keystroke intervals cluster tight with a long right tail.
2. Bursts. People type several words quickly and then stop, rather than typing at a steady rate.
3. Structural pauses at clause, sentence and paragraph boundaries, which are much longer than the between-character variation.
4. Per-character adjustment: same-hand versus alternating-hand digraphs, word-initial keys, shift usage.
5. Speed drift across a page, plus a slow fatigue trend.
6. Optional typos, which need to be adjacent-key slips, noticed a character or two late, then backspaced and retyped.
7. Timer resolution handling. Windows timers land on roughly 15.6 ms boundaries, so naive sleeps overshoot and your effective WPM drifts well below the number you asked for.

That is a real project. It is a perfectly enjoyable one if you like this sort of thing, and the AHK forums have partial versions of it. It is also precisely the work copypaster packages, which is the entire argument for paying for it.

When you should use AutoHotkey instead

• You want it free. That is a completely legitimate reason and AutoHotkey is genuinely excellent.
• You want source you can read. GPLv2, on GitHub, auditable.
• You need more than typing. Remap Caps Lock, automate a window, drive a legacy app, build a small GUI. copypaster does none of this.
• You need conditional logic. Type different text depending on which window is active, read from a file, loop over rows. That is scripting, and scripting is what AutoHotkey is for.
• You want it embedded in an existing automation. If you already have an AHK setup, adding typing to it is easier than bolting on a second app.
• You enjoy the tinkering. Not a joke. Half of AHK's value is that building the thing is the fun part.

When copypaster is the better tool

• You are on a Mac or Linux. AutoHotkey does not run there. See auto typer for Mac.
• You want the timing model without building it. Bursts, structural pauses, drift, corrected typos, WPM-aware scaling, all shipped.
• You want to see what is happening. A floating pill with a progress bar, live ETA, pause and stop. A script gives you none of that unless you write it.
• You are typing long text, repeatedly. Paste, set WPM, click into the target, 3-2-1 countdown, go. See form filling and screencasts.
• You cannot install a scripting runtime. Some managed machines allow a signed app but flag script interpreters.
• You want it for code. Indentation and bracket-pair handling in editors is fiddly to get right in a script. See auto typer for code.

Can you use both?

Yes, and it is a sensible setup. AutoHotkey handles remapping, window management and everything conditional. copypaster handles the "type this long block of text into that field" case where you want the output to look typed. They do not conflict; they hook different things.

What neither of them does

Both send real OS-level keystrokes, so both work in applications where clipboard paste is blocked, stripped or length-capped. That is a mechanical fact about keystrokes, not a claim about defeating anything. Neither tool bypasses a security control, neither makes text undetectable to a content-level AI detector, and neither changes what your employer, school or client permits. If pasting into a system is disallowed by policy, typing into it is the same act. Background on the mechanism: why paste does not work in some apps and clipboard not working in Citrix.