Spacebar Counter

Count spacebar presses with no timer or against a 5, 10, 30 or 60 second window. Auto-repeat does not count, and best scores stay on your device.

🌐 Español

Mode:
Elapsed: 0s
0Press Space to start

Counts genuine spacebar presses in your browser. Holding the key down does not add extra counts, and nothing is uploaded — your best scores are saved only in this browser.

🔒 Private by design: everything runs locally in your browser and never uploaded to any server.

Written and maintained by Last updated

One press, one count

A spacebar counter is trivially easy to build badly. Listen for key events, add one each time, show the number. That version can be beaten by holding the key down, because the operating system will happily send hundreds of events a second while a key is depressed.

Auto-repeat events arrive with a flag saying exactly that, and they are rejected here before anything is counted. So the number on screen is a count of physical presses, and holding the bar down adds precisely nothing after the first.

The other half of a trustworthy counter is knowing which key was pressed. Three different properties can identify the spacebar depending on browser vintage, and any of them is accepted, so an older browser is not silently counting nothing.

Running a timed test

  1. Choose a Mode from the buttons. The options are free with no timer, or windows of 5, 10, 30 and 60 seconds.
  2. Press the spacebar. The first press starts the run, so there is no separate start button and no reaction time penalty.
  3. Keep pressing. The large number is your live count and the pad label tells you the run is in progress.
  4. In a timed mode the run ends automatically when the window elapses. A result panel appears with your count, the window length and your presses per second.
  5. In the free mode there is no automatic end. Press Reset to stop and clear.
  6. Your best count for the current mode is shown alongside the timer once one exists.

Mode buttons are disabled while a run is in progress. Reset first, then switch.

Free counting against a timed challenge

The five modes serve two different purposes and it is worth being clear which you want.

The timed windows are a test. A fixed window makes counts comparable, both against your own previous attempts and against anybody else running the same window, and the presses per second figure is then a straightforward division by a known number. Five and ten seconds measure burst speed; thirty and sixty measure whether you can sustain it, which for most people is a very different number.

The free mode is a tally. It never stops, the rate is computed against however long you have actually been going, and it is genuinely useful away from any competitive framing. Counting people through a door, counting repetitions, counting anything where a big obvious number and a key you can hit without looking is what you want.

What the presses per second figure divides by

In a timed mode the divisor is the window length, not the time you spent pressing. Fifty-five presses in the ten second test is 5.5 per second even if you stopped after eight seconds, because the test was ten seconds long and you chose not to use two of them.

In the free mode there is no window, so the divisor is the time elapsed since your first press. That figure updates live, which makes it a reasonable pacing indicator, and it drifts downward the moment you pause.

Both use the same rounding to two decimals, and both return zero rather than an arithmetic error when there is nothing to divide.

Scores that stay on your machine

Each mode keeps its own best count. That separation matters, because a sixty second record and a five second record are not comparable achievements and merging them would make the number meaningless.

Storage is this browser’s local storage, under a key belonging to this tool alone, so there is no chance of collision with any other tool on the site that stores a score. Nothing is transmitted, there is no leaderboard, and no account exists.

The stored value is parsed defensively. A missing, corrupt or hand-edited entry degrades to no record at all rather than breaking the widget, and any individual entry whose value is not a real number is dropped.

For mouse clicks rather than key presses, CPS Test is the direct equivalent and shares the same rate arithmetic. For measuring how fast you respond to a signal rather than how fast you can repeat an action, Reaction Time Test is the one you want.

Keyboard Tester checks whether every key on a keyboard registers at all, which is the diagnostic to run first if a key seems to be missing presses. And Typing Speed Test measures the thing all of this is a proxy for. The rest is on the testers hub.

See it in action

Screenshot of the Spacebar Counter tool with a spacebar counter with a free mode or timed rounds of 5, 10, 30 and 60 seconds, counting genuine key presses and started by pressing Space itself
Spacebar Counter mid-process: a spacebar counter with a free mode or timed rounds of 5, 10, 30 and 60 seconds, counting genuine key presses and started by pressing Space itself.
Diagram: where the work happens on a SysFenix page that has no file input at all: the tool arrives as ordinary JavaScript inside the page, works the answer out on your own device and renders it in place, so the upload, queue and server-side record a typical online tool needs never happen
Where the work happens on a SysFenix page that has no file input at all: the tool arrives as ordinary JavaScript inside the page, works the answer out on your own device and renders it in place, so the upload, queue and server-side record a typical online tool needs never happen.

Frequently asked questions

Can I cheat by holding the spacebar down?

No. Holding a key makes the operating system fire a continuous stream of key events, each one flagged as an auto-repeat, and those are rejected before anything is counted. One physical press is one count. That single filter is the difference between a counter that means something and one that rewards leaning on the key.

When does the timer start?

On your first press, not when the page loads and not on a separate start button. There is no reaction time penalty built into the score, so the clock and the count begin at the same instant. In a timed mode the window then runs to its end and stops accepting presses.

What happens in the free mode?

Nothing stops. The count rises for as long as you keep pressing and the elapsed time keeps climbing, with a live presses per second figure shown alongside. It ends only when you press Reset. That mode is for warming up, for settling an argument, or for counting something with the spacebar as a tally button.

How is presses per second worked out?

Count divided by seconds, rounded to two decimals. In a timed mode the divisor is the full window, so 55 presses in the ten second test is 5.5 per second. In the free mode the divisor is the time actually elapsed since your first press. Zero presses or a zero length window give zero rather than an arithmetic error.

Are my best scores kept separately for each mode?

Yes, one record per mode. A ten second best is stored separately from a sixty second best, and the free mode keeps its own all-time high. The raw press count is what is stored, since within a fixed window a higher count is always a higher rate too.

Where are the scores saved?

In this browser's local storage on this device, under a key belonging only to this tool, so it can never collide with any other tool's saved data. Nothing is uploaded and there is no account. Clearing site data erases the record, and a corrupted or hand-edited value is discarded rather than crashing the widget.

Why can I not change mode mid-run?

The mode buttons are disabled while a run is in progress, because switching would either invalidate the count or silently discard it. Press Reset first and the buttons come back. The reset control itself only appears once a run has started, so an untouched page has nothing to reset.

Related tools