spacebar clicker
2 Player Spacebar Clicker
Share one device for a synchronized 5, 10, or 30 second keyboard or touch battle, with rebindable controls, ties, rematches, and optional best-of-three scoring.
Player 1
0
0.00 CPS
Player 2
0
0.00 CPS
Ready on one shared device
Best of 3: 0–0
This is local shared-device play, not network multiplayer. Touch and physical-keyboard rounds are not public leaderboard results. Some keyboard matrices cannot register simultaneous key combinations (ghosting).
spacebar cps test
Open the related tool with a different measurement purpose.
Spacebar Clicker home
Open the related tool with a different measurement purpose.
How the local battle works
Player 1 uses Space and Player 2 uses Enter by default. A shared 3–2–1 countdown opens one timer for both players, and input locks at the same deadline. Controls can be rebound to safe event.code values; selecting the same code for both players is blocked. Results show clicks, average CPS, difference, round score, and an honest tie when totals match.
Local play is not network multiplayer
Both players must use the same browser and device. There is no remote room, matchmaking service, account, prize, or global champion claim. Best of three means the first player to win two local rounds; a tied round awards neither side. Rematch preserves controls, Swap controls exchanges them, and New match clears the round score.
Keyboard and touch controls
Physical-key input excludes repeat events and counts only a new keydown after release. Mobile users can use two separate large touch pads, but that mode is described as a touch battle and is not mixed with keyboard leaderboard records. The pads use touch-manipulation styling to reduce accidental zoom and remain separated from all result and navigation controls.
Ghosting and simultaneous input
Some keyboard matrices cannot report particular simultaneous combinations. This limitation, often described as ghosting or key rollover, can make one player’s press disappear even when the page code is correct. Try a different safe key pair or an external keyboard before assuming the game favored one side. The tool cannot override hardware matrix limits.
Fair start and privacy
The countdown prevents either player from accumulating an early score, and input stops at the shared performance.now deadline. Results stay in the current page and do not enter the ordinary Spacebar Counter leaderboard. No names, text, continuous input stream, or remote opponent data are stored. The game is a casual shared-device comparison under visible rules.
Getting a repeatable rematch
Keep both players on the same input type, avoid changing bound keys between comparison rounds, and place the device on a stable surface. If the key positions or switch feel differ, swap controls and play another round to see whether the layout influenced the result. On touch screens, use one finger per pad and avoid browser navigation. These steps do not make players or devices scientifically identical, but they make the local battle easier to reproduce and explain.
Choose five seconds for a quick introduction, ten seconds for a compact comparison, or thirty seconds when both players want to manage a longer pace. Do not compare a five-second keyboard round with a thirty-second touch round. The click difference is an absolute total, while the CPS difference normalizes that total by the common duration. Best-of-three round wins summarize local outcomes and do not erase the underlying score or a tied round. If either player was interrupted, start a new round instead of assigning a winner from partial input.
A local result should be described with its duration, controls, and input type. “Player 1 won a ten-second Space-versus-Enter keyboard round” is meaningful; “Player 1 is globally faster” is not supported. The game performs no identity verification and has no remote referee. Treat the live totals as shared-screen feedback and use the per-round controls to resolve a setup issue before the next countdown.
Frequently asked questions
Is this online multiplayer?
No. It is a two-player local battle on one shared device.
What if both players use the same key?
The binding is rejected because separate event.code values are required.
Why can simultaneous presses be missed?
The keyboard matrix or rollover limit may not report that key combination to the browser.