Free Auto Clicker

Create Hotkey Macros for Clicks, Workflows and Recordings

Give a specific task its own shortcut. Choose what the shortcut runs, how it starts and stops, and whether it applies to every profile or only the active one.

Current guide: Free Auto Clicker 9.0.1 · Windows x64 · Updated November 17, 2026

Download for Windows
Macros showing shortcut, trigger behavior, scope and automation target settings.
Free Auto Clicker 9.0.1 · English · Dark theme. Example configuration.

Start small: use a harmless visible target, test once, and keep F8 available.

In this guide
  1. Choose the Task First
  2. Choose the Trigger Behavior
  3. Set Scope Separately from the Target
  4. Enable and Test One Macro
  5. Understand Background Listening
  6. Frequently asked questions

Choose the Task First

Test the task manually before binding a key. Use a finite Quick click configuration, a checked Task flow or one Recording with deliberate playback settings.

  1. Open Macros and click Add. Give the macro a recognizable name.
  2. Under Automation target, choose Quick click, Task flow or Recording and select its actual target.
  3. Use Capture key combination and press an available shortcut. Esc cancels capture. Avoid the reserved control keys.

You can also start from a recording with Create playback macro, then review the resulting macro rather than assuming its defaults fit your task.

Choose the Trigger Behavior

  • Press once: a physical key press starts one task.
  • Toggle start/stop: the first press starts it; a later press stops it.
  • Hold: holding the shortcut runs the task; releasing it cancels that macro's task.

Operating-system key repeat is not a new physical press. Leave Allow concurrent runs of this macro off for the first test.

Set Scope Separately from the Target

Scope → All profiles makes the binding available independently of the selected click profile. For Profile scope, choose Enabled for active profile; the binding is active only while that profile is selected.

A profile is a local task configuration, not an online account. Scope decides when a binding is available; Automation target decides what it runs. Selecting a flow target does not by itself make the macro active in every profile.

Enable and Test One Macro

  1. Check the macro's own Enabled setting.
  2. Use Enable macros, or the default F9 macro switch, to turn on the macro system.
  3. Prepare the visible target and press the captured shortcut. For Hold, release it to check cancellation; for Toggle, press again to stop.
  4. Press F8 if anything unexpected happens. Review the task before enabling macros again.

A duplicated macro starts disabled. Use Save all to keep changes. Check scope, the individual Enabled box and the master switch if a binding appears to do nothing.

Understand Background Listening

Global key listening lets the shortcut be noticed while another window has focus. It does not provide input inside arbitrary hidden or minimized windows, bypass permissions or override every system/app shortcut conflict.

Prepare the target before triggering a macro: macros do not use the manual Start button's ordered minimizing/countdown path. For timed starts, use Schedules. For a failed trigger, follow the hotkey checks.

Frequently Asked Questions

How is a macro different from F6?

F6 starts or stops the selected mode. An independent macro has its own key combination, automation target, scope and trigger behavior.

Why does my shortcut work in one profile only?

Check Scope. A Profile-scoped macro works only when its selected profile is active; All profiles makes the binding independent of the selected profile.

Why does it stop responding after F8?

F8 stops tasks and turns off the macro system and scheduling. Review the task and use Enable macros or F9 when ready; also check the macro's individual Enabled setting.

Try the Task on Windows

Quick clicks, mouse and keyboard recording, and editable local workflows. All existing local features are free.

Download for Windows

Windows 10/11 x64 · Free Auto Clicker 9.0.1 · Online setup requires an internet connection and WebView2 Runtime. Setup may show an optional partner invitation; local features do not require it.