Auto Clicker Test
Set your auto clicker going over the box and find out what it actually delivers: clicks per second, the average gap between clicks in milliseconds and how regular that gap is. The regularity score tells a program apart from a finger, which is also how anti-cheat systems spot one. Works with any auto clicker on Windows, Mac, Linux and Android.
- Runs in your browser
- Nothing is uploaded
- Free, no sign-up
Pick a time, move the pointer into the box and start your auto clicker. The timer starts on the first click.
How to test an auto clicker
- Open your auto clicker and set the click interval you want to test, for example 100 ms for 10 CPS or 10 ms for 100 CPS.
- Pick a test length. 10 seconds is enough to measure the rate; 30 or 60 seconds also shows whether the rate holds up.
- Move the mouse pointer into the box and start the auto clicker with its hotkey (often F6 or F8). The timer starts on the first click.
- Leave the pointer in the box until the timer reaches zero. Then stop the auto clicker.
- Read the clicks per second, the measured gap between clicks and the verdict. Compare the gap with the interval you set: if they differ, the box below explains why.
What the results mean
Four numbers describe what the browser actually received:
- Clicks per second: total clicks divided by the test length. This is the rate games and websites see, not the rate shown in the auto clicker's settings.
- Click gap: the average time between one click and the next, in milliseconds. 1000 divided by the gap is the CPS. An auto clicker set to 50 ms should show close to 50 ms here.
- Variation: how much the gap wanders, as a standard deviation and a percentage of the gap. A program typically varies by under 5%; a human finger by 20 to 40%.
- Verdict: Automated when the variation is under 8% over at least 20 clicks, Probably automated under 20%, otherwise Looks human.
| Interval set | Expected CPS | What you usually get |
|---|---|---|
| 100 ms | 10 | 10, accurately. Any auto clicker manages this. |
| 20 ms | 50 | 45-50. Windows timer resolution starts to matter. |
| 10 ms | 100 | 60-100. Depends on the clicker and the browser's event handling. |
| 1 ms | 1000 | Far less, often 100-250. The operating system and browser cap how many events a second get through. |
The graph shows clicks in each second of the test. A flat line means the rate is stable; dips mean the browser or the computer stalled for a moment, which happens when other windows are busy or the auto clicker shares a core with the browser.
Why an auto clicker delivers fewer clicks than its setting
An auto clicker asks the operating system to send a click, waits the interval you set, and repeats. Three things stretch the interval. First, timer resolution: Windows timers tick at about 15.6 ms by default, so a 1 ms setting can become 15 ms unless the program raises the resolution, and many free clickers do not. Second, every click is two events, a press and a release, so the OS has twice the work and may merge or delay them. Third, the browser processes input on the same thread that draws the page, and when clicks arrive faster than it can handle them, some are coalesced. The result is that settings below 10 ms rarely deliver what they promise. If the figure matters, test here and set the clicker by what you measure rather than by the box in its settings.
Auto clickers, games and fairness
Most multiplayer games treat auto clickers as cheating, and the regularity you see on this page is exactly how they get caught: a human cannot produce 100 clicks with 2% variation. Minecraft servers with anti-cheat plugins flag suspiciously regular clicking well before 20 CPS, and many ban for it. Where auto clickers are legitimate, idle games, repetitive form work, accessibility for people who cannot click repeatedly, testing your own software, use the random delay option that most clickers offer and keep the rate within what the task needs. This page measures; it does not provide an auto clicker. For your own clicking speed, try the CPS test and the jitter click test, and to check whether a mouse button is faulty, the double click test.
Common problems and fixes
The counter stays at zero
The auto clicker is clicking somewhere else. Make sure the browser window is in front and the pointer is inside the dashed box when you press the hotkey. Some clickers click at a fixed saved position rather than the current pointer; set the position to the box.
The CPS is much lower than the interval I set
That is normal below about 20 ms: operating system timer resolution and the browser's event handling cap the rate. Try the same interval in another browser; Chrome and Edge usually pass the most clicks.
The verdict says "Looks human" with the auto clicker running
Either the clicker has a random delay enabled, or fewer than 20 clicks reached the page. Turn the random delay off for the test and run at least 10 seconds.
The page or the whole browser froze
Rates above a few hundred clicks a second can overwhelm the page. Stop the clicker with its hotkey, press Reset and use a longer interval. Hotkeys keep working while the page is busy; a mouse click on a Stop button often does not.
My Android tap app is not counted
Accessibility-based auto tappers inject touches, which this page counts as clicks. If nothing registers, the app may be tapping a point outside the box; move its target marker onto the box.
Frequently asked questions
What does the auto clicker test measure?
Why is my auto clicker slower than its setting?
How does the test know it is an auto clicker?
Can games detect my auto clicker?
Does the test work on a phone?
Does this page provide an auto clicker?
Last updated