Macro Recorder for Windows: Record Mouse and Keyboard, Then Fix the Timing

A macro recorder captures what you do with the mouse and keyboard, then plays it back. If you have a repetitive task in an application with no macro feature of its own, that is usually the shortest path to automating it — you perform the sequence once and hand it back.

This guide covers what a macro recorder can and cannot do on Windows, why the tool most people are still using has one specific flaw, and how to record and edit a macro properly.

The flaw in every 2010-era recorder

The classic Windows macro recorders — TinyTask being the famous one, at 36 KB and largely unchanged since 2010 — record to an opaque blob and replay it. That is fine until something is slightly wrong.

And something is always slightly wrong. You started recording a beat too early. One pause was 200 ms too short and the dialog had not appeared yet. A click landed three pixels off the button. With an unopenable recording, every one of those means shooting the whole take again, and the new take introduces its own small mistake.

A recording you can edit is the entire difference. ClickTray's Macro Recorder drops your capture into a step list with every step's timing in milliseconds and every mouse move's position exposed, both editable in place. A timing fix is a number you change.

Recording a macro

1. Open Macro Recorder and press Start recording.
2. Perform the task once, at your own pace. Mouse movement, clicks, scroll and keystrokes are all captured, with the real gaps between them. (Mouse side buttons, and keys such as Caps Lock and media keys, are left out because they cannot be replayed.)
3. Press Stop recording. ClickTray reports how many steps it captured.

Two things worth knowing about what it does while recording:

• Continuous cursor movement is compressed as it captures, into point-to-point transitions rather than a per-pixel trail. That keeps the macro small and the replay smooth, and it happens on capture rather than on replay, so what you see in the step list is what will run.
• Recordings stay on this PC. A macro is saved in ClickTray's own settings on this PC. It is never uploaded, and ClickTray's anonymous crash and usage reporting is built so it cannot carry one — it sends a module name and a coarse error class, never a key name, coordinate or window title.

Editing the steps

This is the part the old tools do not have. Once a macro exists the Steps list appears. Each row shows its time in milliseconds, counted from the start of the recording, and every mouse move also shows its X and Y. Replay waits the difference between one step's time and the next.

Common fixes, in rough order of frequency:

• Delete the false start. The first two or three steps are usually you moving to the right window. Remove them — and the last few, which usually include your click on Stop recording.
• Lengthen a pause. If the macro races ahead of a dialog, raise the time of the step that comes too early and every step after it by the same amount. Raise only that one step and the pause after it shrinks instead. Guess generously the first time; you can tighten it later.
• Nudge a position. A move that lands on the edge of a button is two numbers.

Steps can be deleted, but not added or reordered — for that, record again.

Then set the replay: Repeat takes a count from 1 up to 100,000, or infinite, Speed runs from 0.1× to 10× the recorded pace, and Timing jitter (ms) varies the gaps slightly on replay for anything that dislikes a perfectly identical repeat.

Macro recorder or scripting language?

The honest comparison, since this is the decision people actually face:

Use a macro recorder when the task is a fixed sequence you can perform once, the windows are always in the same place, and the shape of the work does not change between runs. That covers most repetitive desktop work.

Use AutoHotkey when you need conditions, loops with logic, variables, or behaviour that depends on what is on screen. It is a full scripting language and genuinely more capable — the trade is that you have to learn it, which is why most people looking for a macro recorder are not looking for AutoHotkey. There is a fuller comparison here.

If your only reason for reaching for a script is "run this until the button appears", ClickTray's pixel and image conditions cover that without a language: run only while a color is present, stop when an image appears, or click a captured image wherever it is found.

ClickTray is free, ad-free and code-signed, with no paid tier and no account. It is funded by sharing a slice of your PC's idle bandwidth when it can — and the tools are disabled while that is switched off, which is the trade, said plainly.

The limitation to plan around

Coordinates are absolute. A macro recorded at 1920×1080 at 100% scaling does not survive being replayed at 2560×1440, or at 125% scaling, or on a different monitor. Every target moves.

ClickTray does not check which screen a macro was recorded on, so a change of resolution or scaling will not be flagged — if a replay misbehaves after a display change, that is almost always why. Record again at your current settings, or correct the move steps' X and Y in the step list.

Sharing a macro

In this version you cannot. A recorded macro lives in ClickTray's own settings on the PC that recorded it, with no export or import. What can be shared is an Auto Clicker setup: its guided Review step has Save setup, which writes a .clicktray.json file — captured pictures included — that Open a setup checks before anything runs.

Every macro you play is also kept on the Runs screen, so on your own PC the one you need is always a click away.