How to Set Auto Clicker Click Intervals on Mac: Milliseconds, Seconds, and CPS Explained
I set my auto clicker to 1 click per second for a Notion data-entry job and watched the script silently desync after 4 minutes because I forgot to account for page-load lag. The clicks kept firing on schedule. The page just stopped catching up. By minute six I had 23 clicks landing on the wrong rows.
I’ve spent the last year tuning intervals on a free Mac auto clicker across Roblox, Hypixel, Cookie Clicker, web scraping scripts, and a few accessibility setups. The pattern repeats. People grab the default 100 ms, run it on whatever they’re doing, then wonder why the bot got banned or the Mac fan started screaming.
I wrote this guide as the conversion table I wish I had two years ago. Real numbers for real use cases. The CPS limits Apple Silicon actually hits. And the App Nap and Low Power Mode gotchas that quietly mug your timing.
Click interval is the time between two clicks. Mac auto clickers accept it in milliseconds (ms), seconds (s), or CPS (clicks per second). For most use cases, 50 to 200 ms covers gaming, 1 to 3 seconds covers data entry, and 30 to 90 seconds covers Mac-awake idling.
The hard ceiling on any Mac is around 100 to 150 sustained CPS due to event-loop limits. Random intervals always beat fixed ones for anti-cheat. App Nap and Low Power Mode silently slow your interval after 4 to 6 minutes if you don’t disable them.
Click Interval vs CPS: Which Units to Use
Three units, one underlying value. Every Mac auto clicker stores the interval as milliseconds internally and just shows you the unit you picked. The question isn’t which unit’s “correct,” it’s which one matches how you think about the task.
I think in milliseconds for anything under one second. I think in seconds for productivity work. I think in CPS when I’m reading a Reddit thread that says “use 20 CPS for Roblox,” because that’s how gamers talk. The math: interval (ms) = 1000 / CPS. So 20 CPS is 50 ms. 100 CPS is 10 ms. 1 CPS is 1000 ms.
| Milliseconds | Seconds | CPS | Real-world use case |
|---|---|---|---|
| 1 ms | 0.001 s | 1000 CPS | Theoretical max, never achievable on Mac |
| 10 ms | 0.01 s | 100 CPS | Cookie Clicker speed runs, Mac max ceiling |
| 20 ms | 0.02 s | 50 CPS | Aggressive idle gaming, fan noise zone |
| 50 ms | 0.05 s | 20 CPS | Roblox safe zone, Hypixel tolerance |
| 100 ms | 0.1 s | 10 CPS | Default for most tasks, Minecraft AFK |
| 200 ms | 0.2 s | 5 CPS | Slower farming, casual auto-clicking |
| 1000 ms | 1 s | 1 CPS | Form fills, slow data entry |
| 5000 ms | 5 s | 0.2 CPS | Web scraping click-through |
| 30000 ms | 30 s | 0.033 CPS | Video player auto-advance |
| 60000 ms | 60 s | 0.017 CPS | Mac-awake nudge |
I see this trap weekly in forums: someone types 100, leaves the unit on CPS, then wonders why the Mac is screaming. Always check the unit dropdown before you press Start.
How Do You Set the Interval in Auto Clicker for Mac?
I’ll walk through the click-by-click for the free Mac auto clicker on this site. Other Mac apps (OP Auto Clicker, MurGaa, MaClicker) follow nearly identical flows.
Open the auto clicker
I launch Auto Clicker for Mac from the Applications folder, or hit Spotlight and type its name. The main window opens with the click pattern panel visible. If you see “permission required,” grant Accessibility in System Settings first.
Open the Click Pattern panel
Click the Click Pattern tab. You’ll see fields for click type (left, right, middle), interval value, unit dropdown, and click count.
Enter your interval value
Type the value into the interval field. Use whole numbers. Common starting points: 100 for a 100 ms gaming click, 1000 for a 1-second productivity tick, 60 for a 60-second Mac-awake nudge.
Pick the unit
Open the unit dropdown next to the value. Pick Milliseconds, Seconds, Minutes, or CPS. Always confirm this before pressing Start because mismatched units cause 90% of “why is it clicking so fast” complaints.
Start the click loop
Press Start in the toolbar, or press your configured Start hotkey. I’d recommend you set a Start/Stop hotkey first because clicking the Start button at the same time you have an auto clicker firing at 100 CPS gets messy fast.
Quick tip: Type the value first, then the unit. If you change the unit while a value is already there, some builds re-interpret the number (10 ms becomes 10 seconds), which is the kind of surprise nobody wants.
Recommended Intervals by Use Case
I use these values myself. Each one came out of either a successful session or a banned account, so treat them as battle-tested.
Roblox combat games
40 to 80 CPS, 12 to 25 ms. I run 50 CPS with 5 ms jitter as my safe zone. Pure 80 CPS fixed gets flagged inside an hour. See the auto clicker for Roblox on Mac guide for the per-game safe-CPS table.
Minecraft AFK farm
100 to 300 ms, 3 to 10 CPS. Iron golem farms, fish farms, raid funnels. Slower interval keeps you under Hypixel’s Watchdog. Pair with the Minecraft AFK clicker setup for hold-mode farms.
Cookie Clicker
50 to 100 ms, 10 to 20 CPS. No anti-bot at all, so push it. I’ve gone up to 50 CPS without issues. Above that, the in-game cursor animation can’t keep up and visually breaks.
Notion / Airtable data entry
1 to 3 seconds. The Notion API has internal rate limits and the page needs render time. I default to 2 seconds. Faster than 1 second hits the save-indicator race.
Web scraping click-through
3 to 5 seconds. Has to wait for the page to load. Faster than 3 seconds skips the hover-load triggers most modern sites use.
Video player advance
15 to 30 seconds. For YouTube auto-skip, slideshow advance, photo viewer auto-progress. Long enough to watch, short enough to feel hands-free.
Mac-awake idle nudge
30 to 90 seconds. Mac sleeps after 5 minutes of input idle by default. A 60-second click on empty desktop keeps Slack green and Teams active.
QA / software testing
500 ms to 2 seconds. Long enough for the UI to settle, short enough to hammer through a test scenario. I drop to 200 ms for known-fast UIs.
Why “Human-Like” Intervals Beat Fixed Millisecond Timers
I tested this myself. Set the interval to a flat 100 ms, run for 30 minutes, then graph the click timestamps. You get a perfect straight line. Nobody clicks like that. Any anti-cheat system looks at click timestamp distribution as one of its first signals.
Real human clicking has natural variance. Even spamming as fast as possible, gaps bounce between 60 and 140 ms because micro-tremors, fatigue, and reaction reset times add variance. Standard deviation on human intervals is around 15 to 25 ms. A bot at exactly 100 ms has standard deviation under 2 ms. That’s the smoking gun.
I rely on Random Interval mode for every gaming session now. Set min and max, and each click waits a random duration in that window. I run min/max at roughly 80% and 130% of target. So a “100 ms” effective interval becomes “random 80 to 130 ms” with mean still ~105 ms. CPS stays the same. Detectability drops by an order of magnitude.
Pro tip: For Roblox, use min/max of 30 ms and 70 ms (effective ~50 ms or 20 CPS) and add the optional Gaussian distribution toggle if your clicker has one. Real human variance follows a bell curve, not a flat distribution.
I’d take 20 CPS randomized over 50 CPS fixed any day. Random interval is the biggest safety knob on a modern auto clicker.
The 100 CPS Myth
I roll my eyes whenever an auto clicker advertises “up to 10,000 CPS.” Technically true, the value field accepts those numbers. Functionally meaningless. The Mac can’t actually fire clicks that fast and the target app can’t receive them.
Heads up: macOS posts mouse events through Core Graphics → WindowServer → target app event queue. Each hop is 1 to 4 ms. The screen also redraws at 60 to 120 Hz max. So even on the fastest M3 Pro, the practical CPS ceiling for clicks that actually register is around 100 to 150 CPS sustained. Bursts can hit 200 to 300 CPS for a few seconds, then the OS event queue saturates and starts dropping clicks.
Server-side caps it even lower. Roblox’s tick rate is around 20 Hz, so clicks above 20 CPS get batched. Hypixel and most Minecraft servers run 20 TPS, same logic. Your 1000 CPS fires locally but the game “sees” 20 of those per second anyway.
I almost never go above 50 CPS for gameplay. Past 50, you pay CPU heat for clicks that don’t matter and trigger anti-cheat for clicks that don’t help. The “100 CPS for Roblox” advice in YouTube thumbnails is bait.
Apple Silicon vs Intel Timing Differences
I’ve benchmarked this on three Macs across the last year (M2 MacBook Air, M3 Pro 14-inch, late-2018 Intel i7 Mac mini). The differences are real.
M-series Macs hit higher CPS more consistently than Intel. On my M2 Air, 100 CPS sustained holds for hours without drops. On the Intel mini, sustained 100 CPS starts dropping clicks after about 90 seconds because the older WindowServer path has more overhead. Practical Intel ceiling: 60 to 80 CPS. Practical Apple Silicon ceiling: 100 to 150 CPS sustained.
I trust my interval on M-series even under load. Intel’s different. Once the chassis hits ~95°C, Intel CPUs throttle clock and that throttling shows up as drift. A 50 ms target stretches to 70 ms after 10 minutes on my Intel mini. M-series barely moves. So on Apple Silicon, your interval is solid. On Intel, build in a 10 to 15% buffer.
Battery state matters too. Plugged in: full clock, accurate timing. Unplugged with Low Power Mode on: throttled, intervals stretched 30 to 60%. I always plug in for any session over 10 minutes.
Troubleshooting: Why Are My Clicks Dropping at High CPS?
I see this constantly. You set 80 CPS, the first 30 seconds feel fine, then the actual click count starts lagging the counter. Classic high-CPS drop pattern. Here’s the order I work through fixes.
- Lower the CPS to 80 or below. If you were at 150 CPS, you’re hitting the OS event queue ceiling. Drop to 80. If drops stop, the problem was just headroom.
- Check Activity Monitor CPU. Sort by CPU. If WindowServer is over 40% or the auto clicker is over 60%, you’re pushing the OS too hard. Close other apps.
- Close Chrome tabs and event-tap installers. Apps using NSEvent.addGlobalMonitorForEvents (1Password, Magnet, Rectangle, Hammerspoon, password managers) intercept every mouse event before it reaches the target. Each adds 1 to 3 ms.
- Disable App Nap on the auto clicker. Right-click the app in Finder → Get Info → check Prevent App Nap. macOS aggressively naps any app whose window isn’t focused, silently halving your CPS after a few minutes. This is the single most common cause of “clicks slowing down after 5 minutes.”
- Re-enable Input Monitoring permission. System Settings → Privacy & Security → Input Monitoring. Make sure the auto clicker is checked. Sequoia 15.1 has a bug where Input Monitoring grants stop applying after a sleep cycle until you re-toggle.
I’ve worked the full list and still seen drops. When that happens, the issue is the target app, not the auto clicker. Roblox especially caps how fast its input handler reads from the OS queue. Drop CPS to 20 to 30 and the game keeps up. If the auto clicker itself won’t open after a Sequoia update, fix that first.
Setting Infinite vs Limited Click Count With Intervals
Interval is half the picture. The other half: how many clicks total. Mac auto clickers usually offer infinite (clicks until you Stop) and limited (clicks until a target count).
I default to infinite for gaming because session length is unpredictable. A Cookie Clicker run, a Minecraft AFK farm, a Roblox idle game; you don’t care how many clicks fired, you care that it kept clicking. Hit your hotkey when you’re done.
I switch to limited mode when I know the work upfront. 1000 form fills, 50 video advances, 200 test cycles. The auto-stop hands control back without me having to remember.
| Mode | Best for | Stopping |
|---|---|---|
| Infinite | Gaming, AFK, Mac-awake, ongoing tasks | Manual hotkey or window close |
| Limited (count) | Form fills, test cycles, scraping, batch jobs | Auto-stops at count target |
| Limited (time) | Timed sessions, “click for 1 hour” | Auto-stops at time target |
I combine limited count with a slow interval for batch ops where the count is exact. 1000 clicks at 2-second intervals = 2000 seconds = 33 minutes. Cleaner than relying on yourself to remember Stop.
Frequently Asked Questions
Common interval and CPS questions I get from readers tuning auto clickers on macOS.
What’s the fastest CPS I can hit on M2?
Around 100 to 130 CPS sustained on an M2 MacBook Air, with short bursts higher. Past that the macOS event loop drops clicks because Core Graphics can’t post events faster than the compositor processes them. Practical ceiling for game inputs stays 100 to 150 CPS even on M3.
How do I make the interval random?
Open the Click Pattern panel and toggle on Random Interval. Set min and max. Each click waits a random duration in that range. Use 80 to 130 ms for gaming jitter. Constant intervals are the easiest way for anti-cheat to flag you.
Can I set sub-millisecond intervals?
No, and you don’t want to. Core Graphics has a realistic floor of 5 to 10 ms before clicks merge or drop. The interval field accepts whole milliseconds. Anything under 7 ms is unreliable on most Macs.
Why do my clicks slow down after 5 minutes?
App Nap is the usual culprit. macOS throttles background apps after a few idle minutes. Right-click the app in Finder, Get Info, tick Prevent App Nap. Also turn Low Power Mode off. That combo causes the silent 4 to 6 minute desync most users hit.
Does Roblox detect 50 CPS as a bot?
Roblox doesn’t have client-side click detection in 2026, but individual games run their own scripts. Blade Ball, Pet Simulator 99, and Anime Defenders flag fixed intervals above 30 CPS. Use 18 to 25 CPS with jitter to stay under detection.
What’s a safe interval for Hypixel?
Watchdog allows up to 20 CPS on average but flags sustained bursts above that. For SkyBlock dungeons, 12 to 16 CPS with 20 to 40 ms random jitter is the sweet spot. For AFK farms, drop to 4 to 8 CPS to blend with normal player rates.
Can the interval drift?
Yes. macOS uses non-realtime scheduling, so a 100 ms interval can fire at 102 to 115 ms under load. Drift compounds. After an hour at 100 ms target, actual count is usually 1 to 3% under expected. Use Click Count limits and shorter runs for exact timing.
Does battery saver affect interval timing?
Yes, significantly. Low Power Mode throttles CPU clock and suspends background apps. A 50 ms target can stretch to 80 to 120 ms in Low Power Mode. Plug in and turn Low Power Mode off in System Settings, Battery for accurate timing.
How do I set hour-long intervals for AFK?
Pick Minutes from the unit dropdown, or use Seconds and enter 3600 for one hour. The longest interval most apps support cleanly is 24 hours. Mac-awake-keepers only need 30 to 90 second intervals though, because the Mac sleeps after 5 minutes of inactivity by default.
Why is 1 ms not actually 1 ms?
Core Graphics events go through WindowServer, then the target app’s event queue, then any event tap filters. Each hop adds 1 to 4 ms. A 1 ms interval ends up 8 to 15 ms in practice. The clicker fires in 1 ms; registration lags.
What interval do esports players actually use?
Competitive Minecraft PvP runs jitter clicking at 8 to 12 CPS natively, around 80 to 125 ms. Roblox fighting-game players cap at 20 CPS for safety. Cookie Clicker speed runs use 50 to 100 CPS. For tool comparisons see the best Mac auto clickers compared.
Should I match interval to my monitor refresh rate?
Only for visual feedback. A 60 Hz display refreshes every 16.7 ms, ProMotion 120 Hz every 8.3 ms. Clicks faster than refresh still register but you can’t see each one. Matching refresh (16 ms on 60 Hz, 8 ms on 120 Hz) gives the cleanest visual feel.
Related Guides
If you’re tuning intervals you’ll probably want these other configuration and use-case guides too.