Macro Detector | Check Controller, Keyboard & Mouse Timing

A macro detector looks at the timing pattern of your button presses, key presses, or clicks and checks whether that pattern looks like natural human input or like something mechanically repeating itself. It does not read the contents of any script or program, it only measures how consistent your input rhythm is over time.

As you press buttons, keys, or the mouse target, this page records the exact time of each press and measures the gap between one press and the next. Human presses naturally vary by a noticeable amount even when someone is trying to be consistent, while a hardware or software macro tends to repeat almost the exact same gap every time. The tool compares that variation against typical human ranges and shows you where your input falls.

Timing variation describes how much the gap between presses changes from one press to the next, shown here as a percentage. A high percentage means your presses are naturally uneven, which is normal for a person. A very low percentage means the gaps are almost identical every time, which is difficult to do by hand and is the clearest signature of a macro or turbo function.

No. This tool reports a timing pattern, not a verdict. Skilled players can produce very fast and fairly consistent input on their own, and some games or connections introduce timing artifacts that can look unusual even from a normal controller. Treat a flagged result as something worth a second look, not as proof on its own.

It depends on how consistent the mashing is, not just how fast it is. A fast masher whose gaps still vary by a reasonable amount will land in the natural range. Only presses that are both fast and extremely uniform in timing will read as a possible macro signature.

A hardware macro is built into a modified controller, keyboard, or mouse, often through a turbo switch, a mod chip, or a device made for input conversion. A software macro is a script or driver feature running on the computer that simulates presses through the operating system. See the comparison table above for how each one typically behaves in a timing analysis.

Often, yes. Turbo functions repeat a press and release cycle at a fixed rate while a button is held, and that fixed rate shows up as unusually low timing variation on this tool. The faster and more mechanical the turbo cycle, the more clearly it stands out from natural input.

Sometimes. These devices convert or remap input before it reaches the game, and many produce a timing signature that looks different from manual play. Some include settings meant to add randomness to their output specifically to look more human, which can make detection less reliable. A clean result here is not a guarantee that no device is being used.

Yes. Switch to the Keyboard tab and press any key repeatedly. This works with any keyboard connected to your computer, including keyboards with dedicated macro keys.

Yes. Switch to the Mouse tab and click the target area repeatedly. This measures the timing of clicks the same way the other tabs measure button and key presses.

Yes. A laptop built in keyboard and trackpad send the same signals to the browser as an external keyboard and mouse, so the Keyboard and Mouse tabs work on a laptop without any extra setup.

A touchscreen tap cannot be measured through these tabs directly, but any Bluetooth controller, keyboard, or mouse paired to a phone or tablet is read the same way through a mobile browser that supports the Gamepad API or standard input events.

Most fight sticks are recognized by the browser as a standard gamepad, so the Gamepad tab reads their buttons the same way it reads a regular controller, which makes it useful for checking mash and combo timing.

In most competitive online games, yes. Automating inputs through hardware or software typically violates the game's terms of service even when the macro is hard to detect, and many tournament rule sets ban turbo and macro devices outright. Rules vary by game and by event, so check the specific terms that apply to you.

Small sample sizes are the most common cause, since a handful of presses does not average out the way dozens of presses do. Fatigue, a change in grip, or pressing more carefully partway through a test can also shift your numbers between attempts.

Yes. A weak or congested Bluetooth connection can add small, irregular delays to when a press is actually reported to the browser, which can add noise to the timing data in either direction. A wired connection gives the most reliable reading if you want to rule that out. See Connection Stability for a focused check.

No. Every press is timed and analyzed locally in your browser tab. Nothing is transmitted anywhere, and closing or refreshing the page clears everything.

No. This tool runs entirely in your browser using standard web input events. There is nothing to download and no account to create.

Any modern Chromium based browser such as Chrome or Edge, along with Firefox, supports the input events this tool relies on. The Gamepad tab specifically depends on the Gamepad API, which has more limited support on Safari.

This tool is built to check input on the device in front of you, not to remotely analyze someone else's controller. If you suspect another player in a match or tournament, report it through that game or event's official channels, since they can apply their own rules and evidence standards.