Auto clicker & macro recorder for Windows

Your mouse is about to have a mind of its own.

An auto clicker and macro recorder that watches the screen. Set a trigger — a hotkey, an icon appearing, a colour bar, a sound, a timer — and Polter Click takes it from there: clicking, typing, and waiting in your place.

Open beta — free while it runs, and it needs a free account. Expect rough edges: builds change quickly, and the servers it signs in through are not immune to a bad day. Paid plans come after the beta, and beta accounts hear about that by email first.

// what actually happens when it fires

TRIGGER F6
WAIT UNTIL icon "Fireball" appears in "Hotbar"
THEN press 1 → wait 500 ms

What it is

A macro tool that can actually see and hear.

Most macro recorders replay a fixed sequence and hope the world stayed still. Polter Click is built around the opposite idea: a macro is a set of steps that wait for something — an icon appearing on screen, a bar dropping below a level, a sound playing, a key being held — and only then act.

Wait for the Fireball icon, then press 1 — the moment it lights up, every time, while you keep dodging. 90 seconds, from the empty editor to the macro playing.
How a macro is put together →

Everything a poltergeist needs.

Wire triggers to conditions to actions, and let Polter Click sit in the tray and run the routine — for as long as you need it to.

Keyboard

Press, hold and release any key or combination. Type text at the speed you set.

Mouse

Move to a point, in a direction, or onto an icon it has found on screen. Click, double-click, hold.

Screen

Wait for an icon to appear or vanish, or for a bar to cross a level — on the whole screen or in one area of it.

Sound

Record a sound once. A step can then wait until it plays, even with the window behind another one.

Parallel flows

Several flows in one stage run at the same time, each with its own waits.

Recorder

Record what you do and get back an editable flow — clicks, holds and typing already grouped.

Common setups

Two things people build first.

Before you download

The things people ask first.

Which systems does it run on?

Windows 10 and 11, 64-bit. It installs into your own user folder, so there is no administrator prompt. There is no macOS or Linux build to download today.

What does "beta" mean here?

That it is finished enough to be useful and not finished enough to be quiet about it. Features change between builds, bugs reach you before they reach us, and a build can ask to update itself before it runs again. It also needs our servers: signing in goes through them, and if they are down you cannot sign in — an installation that is already signed in keeps working, but not forever, because it has to reach them at least once a week. When something breaks, the guide explains how to send a report; it is the fastest route to a fix.

Is it free?

It is free while it is in open beta. It needs an account, which is free as well — the app stops at its sign-in screen without one. After the beta there may be free and paid plans, and what each one includes may differ from what the beta allowed; if you have a beta account, we write to you before anything about the price or the limits changes. The terms say it in full.

Am I allowed to use it here?

That depends on the program or the game, and only its rules can answer it. Polter Click — it plays nothing for you and knows nothing about the game; it presses the keys you told it to press. But plenty of programs and online games forbid automated input of any kind, and some ship anti-cheat that looks for it. Read those rules first, and where automation is not allowed, don't use it — that decision, and what follows from it, is yours. We are here to make repetitive things comfortable, not to hand anybody an edge.

Does anything leave my computer?

Your macros, images and settings live in a local database on your machine; screen captures are read in memory to answer a condition and are not uploaded. The app talks to our servers for two things: signing you in — it needs an account, and asks for it on its first screen — and checking whether a newer version has been published. While you are signed in it also tells us, about every half hour, that this installation is alive — nothing about what it runs. The privacy policy lists every field, and who else sees it.

Do I have to write scripts?

No. Every step, condition and timeout is a control in the editor. If you would rather not build at all, record yourself doing the thing and edit the result.

All questions, and the full guide →