The keys that stop playback
These keys are the emergency stop, and they are built into the program for exactly this reason.
PauseScrollLockBreak
You do not need to click anything first. You do not need the window in focus. Press the key and the macro ends.
The program tells you this itself. Open Prefs, hover Playback Hotkey, and the hint appears at the bottom of the submenu. It is easy to miss, because it sits under a list of options and looks like a footnote.
This matters, because several sites publish a different stop shortcut. If you have read somewhere that Ctrl+Shift+Alt+S ends playback, it does not. That combination is not in the program. The full list of what is really there is on the TinyTask hotkeys page.
The playback hotkey is not the stop key
These are two different things, and mixing them up is the usual reason people panic.
The playback hotkey starts a macro. By default it is Ctrl+Shift+Alt+P.
The stop keys end a macro that is already running. They are Pause, ScrollLock and Break.
Pressing the playback hotkey again during playback does not stop anything. It is not a toggle. The record button behaves differently, and that difference confuses people. Recording uses one key to start and the same key to stop. Playback does not.
When the keyboard feels stuck
Your keyboard is not stuck. The macro is typing and clicking faster than you can react, so every window you touch changes under your cursor.
Work through these in order.
Press the stop key first. Pause or ScrollLock, once, firmly. Do not hold it down. Do not press it repeatedly, because a fast macro may be stealing focus between presses.
If your keyboard has no Pause key, look for it as a shared function on another key. On many compact and laptop keyboards it sits on Fn plus B, Fn plus P, or on the Insert key row. Check your keyboard's printed legends. Some manufacturers put Break on a different combination than Pause, so try both.
If the key genuinely does not exist, open the Windows On-Screen Keyboard. Press Ctrl+Win+O. It has a ScrLk key you can click. This works because the on-screen keyboard sends a real key event, not a simulated one.
If none of that reaches the program, press Ctrl+Alt+Del. This opens a secure screen that a macro cannot click through, and it stops the macro from doing further damage while you decide what to do. From there, open Task Manager, find the process, and end it.
Ending the process is safe for your computer. You will lose an unsaved recording held in memory, and nothing else. Saved .rec files on disk are untouched, as covered on the rec files page.
How to tell playback has actually stopped
Look at the title bar. During playback the program shows a countdown there. When the countdown is gone and the title reads normally, playback has ended.
This is worth knowing, because a macro that finished on its own and a macro you stopped look identical afterwards. If the countdown is still running, the key did not register. Press it again.
Stopping a looping macro
The stop keys work the same way on a loop. One press ends it.
A loop is not a special mode that needs a special exit. Continuous Playback and Set Playback Loops simply tell the program to repeat, and the emergency stop cuts through both. How each of those settings behaves is covered on the TinyTask loops page.
There is one practical difference. A loop gives you more chances to press the key, because the macro returns to its starting point on every pass. A single long macro at high speed gives you fewer. That is why loop count matters less than speed does, which the playback speed page goes into.
Stopping a compiled macro
The same keys work. Pause and ScrollLock stop a compiled macro exactly as they stop one playing inside the program.
We tested this on a compiled file rather than assuming it. Several sites say nothing about it at all, and a runaway standalone macro is the situation where you most need to know.
There is a second route that always works, and it is worth knowing as a fallback. Press Ctrl+Alt+Del, open Task Manager, find the process by the file name you gave it, and end it. That reaches a macro even in the rare cases where the keyboard is being captured faster than you can press anything.
One habit either way. Test a compiled macro at normal speed, with a loop count of one, before you rely on it or send it to anyone. What compiled files can and cannot do is set out on the compile to EXE page.
What does not work
Escape is not a stop key. The developer avoided it deliberately. Escape is pressed constantly during ordinary work, which means it often ends up inside recordings. Making it the stop key would break the recordings that contain it.
Closing the window does not always help. If the macro is clicking, it may click your close button away, or click somewhere else entirely before your cursor arrives.
Clicking Rec does not stop playback. Recording and playback are separate. Pressing record during playback does not cancel it.
Unplugging the mouse does not stop it. The program is not sending signals through your mouse. It is sending them to Windows directly. A macro plays perfectly well with no mouse connected.
Pulling out the keyboard does not stop it either, and it removes your ability to press the stop key. Do not do this.
How to avoid needing this page
Knowing how to stop TinyTask is useful. Never needing to is better. Four habits remove almost every runaway.
Test at normal speed first. Record the macro, play it once at 1x, and watch it. A macro that misbehaves at normal speed will misbehave far worse at high speed.
Use a loop count instead of continuous playback while you are still testing. Set it to run twice. You get to see the repeat behaviour without committing to an endless one.
Keep the stop key under a finger. Before you press play on anything long, put a finger on Pause. It costs nothing.
Leave the program visible. Turn on Always on Top so you can see the countdown. If the macro hides its own window, you lose the one clear signal that it is still running. Recording and playback basics are covered end to end in the how to use TinyTask guide.
When stopping is not the real problem
Sometimes the macro is not running away. It is going wrong.
A macro that clicks in empty space, opens the wrong menu, or types into the wrong window usually has a coordinate problem, not a speed problem. The program replays screen positions, not buttons. Move a window and the macro misses. That is the most common failure in this tool, and it is covered on the TinyTask not working page.
If playback works on your machine and fails on another, display scaling is the likely cause. The Windows 11 page covers scaling, elevation and multiple monitors.
Frequently asked questions
Press Pause or ScrollLock. Break also works. These are the built-in emergency stops and they do not need the window to be in focus. If your keyboard has no such key, open the On-Screen Keyboard with Ctrl+Win+O and click ScrLk.
Because the playback hotkey only starts a macro. It is not a toggle. Recording uses the same key to start and stop, playback does not. The full hotkey behaviour is listed on the hotkeys reference.
No. The developer left Escape out on purpose, because it appears inside so many recordings that using it as a stop key would break them.
No. You lose an unsaved recording sitting in memory. Files already saved to disk are not affected, and nothing on your system is changed.
The program has no scheduler of its own. If you have scheduled a compiled macro through Windows, you stop it the same way you stop any Windows process, and you disable the task so it does not fire again. This is covered on the scheduling page.