Blur Auto Clicker

An accuracy and performance focused auto clicker

Why I made it:

A lot of the most popular auto clickers, like OP Auto Clicker and Speed Auto Clicker, are pretty inaccurate at higher speeds. Setting CPS to 50 might give you 40... or 60. Technically this is not an issue since they are still clicking fast, but I am a perfectionist and I wanted something that could actually click at the CPS I set it to, even at higher speeds. So I made this.

Additionally, many auto clickers have 1 good feature but are missing the other features I want. My auto clicker combines all the features I have seen in other auto clickers, and even adds some of my own ideas.

Performance is also a heavy focus of this. While version 3 and onwards run on a web-based UI, The total RAM usage is around 50mb and I intend for it to never go above 100mb.

---

Features

Blur Auto Clicker reaching 500 CPS steadily (windows limit¹)

Simple Mode:

• On / Off Indicator (blur logo turns green when active)
• Individual mouse button settings (left, right, middle)
• Hold / Toggle activation modes
• customizable hotkeys

Advanced Mode (includes all simple mode features plus):

• adjustable click timing (duty cycle)
• Speed Range Mode (randomizes CPS within a range)
• Corner and edge stopping (turns off when mouse is in corners or near edges of the screen)
• Click and Time limits (stop after certain amount of clicks or time)
• Double clicks
• Position Clicking (you can pick a position where the mouse will move to and click.)
• Clicks can be adjusted to per Second, Minute, Hour, or even Day

Other Features:

• click stats (total clicks, clicks per second, etc)

---

Installation

By default, the program is stored in %localappdata%/BlurAutoClicker/BlurAutoClicker.exe.

Config and stats are stored in %appdata%/BlurAutoClicker.

Info: If you are on version 2.1.2 or below, delete the old executable (the installer will not delete it for you). The old Config and Stats files will unfortunately not be compatible with the new versions (3.0.0 and above), so they will be deleted upon launching the application.

Windows trust / signing

Unsigned GitHub-downloaded Windows installers can still show a SmartScreen warning. Tauri updater signing is separate from Windows Authenticode signing. See docs/windows-release-trust.md for build commands, signature checks, and the release-trust checklist.

---

Building From Source

This project is currently Windows-first. The maintained desktop build path is the Rust x86_64-pc-windows-msvc toolchain plus Node.js.

Requirements:

• Node.js 20 or newer
• Rust via rustup
• Microsoft C++ Build Tools / Visual Studio Build Tools

Setup:

git clone https://github.com/Blur009/Blur-AutoClicker.git
cd Blur-AutoClicker
npm install
rustup default stable-x86_64-pc-windows-msvc

Run the app in development:

npm run dev

Build a release bundle:

npm run build

Useful validation commands:

npm run lint
npm run frontend:build
cargo test --manifest-path src-tauri/Cargo.toml

The built Windows installer is written to src-tauri/target/release/bundle/nsis/.

---

Support the project!

You can also support the project by starring the repository and sharing it with your friends :). Thank you for your support!

License

This project is licensed under the GNU General Public License v3.0.

Other Info

1. Windows has a limit of around 500 CPS for mouse events. This is because Windows timer resolution is limited to about 1ms at minimum (1000cps) but windows also needs to do other things, so the practical limit is around 800cps, but since I can not guarantee that performance on every computer, I set the limit to 500cps.