Auto clicker, free and open source

This auto clicker is published by Blur009 as Blur009/Blur-AutoClicker, with a Windows homepage at autoclicker.blur009.com. Source, LICENSE, and README live on that repo, and Releases hold the x64 setup plus the portable zip. The same product is in Windows Package Manager as Blur009.BlurAutoClicker, and safe fetch rules sit on the download-safe notes, and repo layout sits on the GitHub notes.

How an auto clicker sends clicks on Windows

The auto clicker sends input to the window in front, on the machine you already control. Simple mode is the daily path: pick a mouse button or a keyboard key, set a rate, bind a hotkey, then choose hold or toggle. Hold fires while the hotkey is down, and toggle starts on one press and stops on the next, which is the whole loop for most jobs. Keyboard detail, including case control, is on the keyboard notes.

An auto clicker interval is not only a raw CPS number, and you can count per second, per minute, per hour, or per day, which is how a slow periodic click differs from a fast burst. Duty cycle on this auto clicker shapes how long the button stays down inside each click; Random CPS draws a rate from a range so the timing is not a flat metronome. The project homepage is explicit that speed variation does not save anyone from a game ban, and that this is not a tool for cheating in videogames. These notes describe foreground clicks, not a game workaround.

Advanced mode on this auto clicker adds limits and geometry, so a run can stop after a count or a duration instead of going forever. Double clicks on this auto clicker fire two presses per step, and position clicking aims at a fixed screen point instead of the cursor. Edge or corner stop ends the run if the pointer hits a screen edge, which is the fast off switch when a window is not the one you wanted. Sequence and click-point notes live in the project homepage and in release notes; delay between separate click points is a GitHub feature request, not a shipped README claim. How-tos for interval and coordinates sit on the interval guide and the position-click guide.

Install command for this auto clicker

One install path covers this auto clicker on a PC you administer: Windows 10 1809 or later, or Windows 11, with App Installer providing winget. The README command is the line to paste into PowerShell or Windows Terminal; GitHub Releases is the file host if you would rather run the setup exe or unpack the portable zip. There is no brew, snap, flatpak, apt, or Docker auto clicker install in the official README, and these notes do not mint those URLs.

winget install -e --id Blur009.BlurAutoClicker --source winget --silent

Windows auto clicker walkthroughs sit on the Windows install guide and portable versus setup, and if App Installer is missing, get it from Microsoft App Installer, then run the same command. Chris Titus Tech winutil maps blurautoclicker to the same winget id; that is a community list pointing at the README package, not a second vendor. The current release is the GitHub tag, injected on the stamp, not a number typed into a blog.

First hour with an auto clicker

The first hour with an auto clicker is one real job on a window you can waste, not a tour of every control. Pick left, right, or middle, then set an interval you can see, such as a few clicks per second, not a thousand. Bind a hotkey you will remember, then choose hold or toggle; Hold is safer when you want the run to die the moment you lift the key, and toggle is better when you need both hands on something else. Hotkey steps sit on the hotkeys guide.

If the auto clicker job is a key instead of a mouse button, switch to keyboard mode and set case the way the README describes. If the job is a pixel that never moves, use position clicking rather than hoping the cursor stays put. If you only need a recorded mouse path, you may want a macro tool instead; TinyTask is that kind of recorder, compared on the TinyTask comparison. Scripts that branch belong in AutoHotkey, compared on the AutoHotkey comparison.

Keep originals of anything the auto clicker clicks through, and the auto clicker can minimize to the tray, and the homepage lists a start-with-Windows option. Duplicate tray icons have shown up in GitHub issue threads, so restart the app if you see two. Click statistics stay locally under AppData; Default CPS is capped at 500 in the project FAQ, and settings can raise the cap to 1000. That is a product limit, not a promise that every game or form will accept it.

Compared with other auto clicker tools

A four-way auto clicker view is about source, install, and what the tool actually sends, not a rank. GS is freeware on SourceForge; TinyTask is a tiny recorder; AutoHotkey is a scripting language. MurGee sells a Windows clicker after a short trial, and the GPL-3.0 project these notes install is the one with a public repo and a winget id. Competitor prices below were checked on 2026-09-02; open each vendor page before you budget.

GS Auto Clicker is the incumbent already compared on the GS comparison, and use the SourceForge project at sourceforge.net/projects/gsautoclicker as the catalog listing. Fan mirrors exist; Goldensoft hosting is discontinued, and a random dot-net mirror is not the vendor. TinyTask at tinytask.net is a 36 KB recorder, not a CPS clicker; AutoHotkey lives at autohotkey.com. MurGee Auto Clicker at murgee.com/auto-clicker is a 20-use trial, then about USD 6.54 to unlock one Windows PC for up to six months, and it needs admin. Compare MurGee on the MurGee comparison, and switching from GS settings is on the GS switch guide.

Common auto clicker mistakes

The expensive mistakes with an auto clicker are almost always fetch, duplicates, and old folders. Take the auto clicker setup or the zip from GitHub Releases or from winget, not from Softonic, CNET, or a search-ad wrapper that uses the project name. The safety checklist is the safety guide and the download-safe notes, and do not run latest.json or a .sig file. Do not treat an unofficial AI-made macOS port as an official package; GitHub issue 285 is open, and the author says it is not endorsed.

If both a portable auto clicker folder and a winget install are running, pick one for the job in front of you. If SmartScreen appears, read the project trust doc rather than fetching a verified-looking exe from some other domain. If you still have a version 2 exe, delete it before the version 3 install so old configs are not a surprise. A borrowed laptop that blocks winget is a bad target unless you use the setup exe from GitHub. The current release is the GitHub tag, not a third-party mirror.