AT Auto Clicker combines three levels of Windows input automation: a timer for repeated clicks, multiple saved points for stable sequences, and a recorder for mouse-and-keyboard workflows.

This feature guide helps you choose the smallest mode that completes a permitted task.

Platform and use

AT Auto Clicker is designed for Windows 11 and Windows 10. It runs as a desktop utility and sends the mouse or keyboard input you configure.

Appropriate uses include a permitted repetitive desktop task, exploratory interface testing, a local demonstration, or an accessibility workflow. Games, websites, and workplace systems may restrict automation; check their rules first.

Timer mode

Use Timer for the same mouse event at one or more stable points.

Configure:

  • Left, right, or middle mouse button.
  • Single or double event.
  • Hours, minutes, seconds, and milliseconds between clicks.
  • Current pointer or saved positions.
  • Fixed count, duration, or continuous repeat.
  • Start and stop hotkey.

For a first run, choose left single-click, one point, 500 ms, and 10 repetitions. The beginner settings guide explains why this baseline is easy to verify.

Multi-point mode

Add points in the exact order the workflow should use them. This is useful for a stable sequence of buttons that all use the same mouse event and similar timing.

Window position, display scale, and browser zoom must remain consistent. Run one slow cycle before adding repetitions.

Use the multi-point tutorial for coordinate and timing checks.

Script recording

Switch to Script when a workflow includes:

  • Mouse movement.
  • Different mouse buttons.
  • Wheel input.
  • Keyboard actions.
  • Different pauses.
  • A visible demonstration path.

Record one clean cycle at a steady pace. Review the events and replay at 1× before increasing speed.

Do not record passwords or confidential data. The mouse and keyboard macro guide covers preparation and replay.

Save and reuse configurations

Give a saved script or timer a descriptive name that includes the task and version. Keep the last known-good copy while testing a faster variation.

Document the required starting screen, window position, display scale, expected duration, and stop hotkey. Retest after an app or display change.

Choose the right repeat rule

Use a fixed count for a known quantity and for every new test. Use duration after timing is reliable. Use continuous mode only for a proven supervised task with a tested stop shortcut.

A manual hotkey plus an automatic endpoint gives you two ways to stop. Read count versus duration versus continuous mode for examples.

Troubleshooting order

When a setup fails:

  1. Test one point from the on-screen Start button.
  2. Use left single-click at 500 ms for 10 repetitions.
  3. Recapture the point.
  4. Change the hotkey.
  5. Match the target and clicker’s permission levels.
  6. Keep the target focused.
  7. Add original features back one at a time.

This isolates a point, timing, hotkey, permission, or target problem. The complete Windows fixes go deeper.

Safety principles

  • Download from the official site.
  • Keep Windows security enabled.
  • Test with disposable data.
  • Keep destructive actions manual.
  • Do not bypass app or game restrictions.
  • Use a short fixed endpoint.
  • Supervise the first runs.
  • Stop after any screen change.

The software repeats input; it does not understand the meaning of the control below the coordinate.

Frequently asked questions

Does AT Auto Clicker support macOS?

AT Auto Clicker currently targets Windows 11 and Windows 10. Do not download an unrelated file that uses the name while claiming unsupported platforms.

Is the core clicker free?

Core automation features are available in the free plan without ads. Optional paid plans are described on the pricing page.

Does it click a minimized app?

Normal desktop mouse automation is intended for the active visible target. Keep the target focused.

Which mode should a beginner use?

Start with Timer, one point, and a fixed count. Add multiple points, then learn Script only when the workflow requires mixed input.

Bottom line

Begin with the simplest timer, prove one safe action, and add points or recording only when the task needs them. Reliable automation comes from controlled conditions, clear endpoints, and permission.