Short answer: clicks per minute (CPM) is clicks per second (CPS) multiplied by 60, and CPS is CPM divided by 60. 5 CPS is 300 CPM; 450 CPM is 7.5 CPS. The multiplication is exact, but what the result means depends on how long you actually clicked: a CPM figure from a 5 or 10 second run is a rate scaled up to a minute, not a minute of clicking that was measured.
What CPM is
CPM states the same click rate as CPS, in a larger unit. A minute has 60 seconds, so every CPS value becomes 60 times larger when written per minute. The two numbers describe one rate; neither is a more accurate version of the other. Which one a page shows is a matter of convention, so always check the unit and the test duration before comparing two results.
The conversion, both ways
- CPS to CPM: CPM = CPS × 60. Example: 6.4 CPS × 60 = 384 CPM.
- CPM to CPS: CPS = CPM ÷ 60. Example: 240 CPM ÷ 60 = 4.00 CPS.
- From raw counts: CPM = clicks ÷ seconds × 60. Example: 52 clicks in 10 seconds is 52 ÷ 10 = 5.2 CPS, which is 5.2 × 60 = 312 CPM.
The CPS values in the table below are arithmetic, not results measured from anyone:
| CPS | CPM (CPS × 60) |
|---|---|
| 2 | 120 |
| 3 | 180 |
| 4 | 240 |
| 5 | 300 |
| 6 | 360 |
| 7.5 | 450 |
| 8 | 480 |
| 10 | 600 |
Why a short run scaled to a minute overstates
The scaling step assumes the pace stays the same for the whole minute. A 5 or 10 second run says nothing about the other 50 seconds. The article on endurance clicking shows why a longer average usually falls as slower seconds join it; scaling a short run up skips that effect altogether. The invented numbers below show the gap:
| Invented run | Calculation | CPM |
|---|---|---|
| Fast 10 second burst: 80 clicks | 80 ÷ 10 × 60 | 480 |
| Same person, full 60 seconds: 350 clicks | 350 ÷ 60 × 60 | 350 |
Both rows are correct arithmetic and they differ by 130 CPM. The 480 is a projection of a burst; the 350 is a counted minute. Quote the duration next to any CPM figure so a reader can tell which kind it is.
Short tests make one click worth more
Since CPM multiplies the rate by 60, the value of a single click depends on the test length: one click is worth 60 ÷ seconds CPM.
| Test length | One click is worth |
|---|---|
| 1 s | 60 CPM |
| 5 s | 12 CPM |
| 10 s | 6 CPM |
| 30 s | 2 CPM |
| 60 s | 1 CPM |
In a 5 second run, a single extra click moves the CPM by 12; in a 60 second run it moves it by 1. That is why short-run CPM jumps around between attempts and a 60 second figure is steadier. For the same reason in CPS terms, see why 1-second bursts read higher and what a 10-second run tells you.
What CPSKit’s CPM test does
The clicks-per-minute test offers 5, 10, 15, 30 and 60 second presets on its full page. At the end of a run it takes counted clicks divided by the selected duration, multiplies by 60 and rounds to a whole number. While a run is in progress, the displayed figure is the clicks so far divided by the time elapsed, times 60, so it is a live projection that can swing early in a run. Only the final figure is the result. For example, 37 clicks in 5 seconds is 7.4 CPS, and 7.4 × 60 = 444 CPM.
If you want the unrounded rate, the CPS test reports clicks divided by seconds with two decimals. Results are kept on your device only; there is no account or leaderboard.
What a browser CPM cannot tell you
- Not a hardware speed. The test counts click events your browser reports, so it reflects you, your input device and the browser together. It does not isolate the mouse switch or its polling rate; see what a browser reports when you think it is measuring polling rate.
- Not comparable across input types. CPSKit counts mouse, touch, pen and keyboard separately, so a touch CPM and a mouse CPM are different measurements.
- Not proof of a sustained minute unless the duration was 60 seconds, as shown above.
- Double-click chatter can change the count. A switch that registers one press as two events adds counted clicks; check with the double-click test if a number looks too good. The open double-click input behavior dataset next to this article documents browser double-click events; it contains no CPM or CPS benchmark runs.
CPSKit has no dataset of real people’s CPM, so this article gives no average and no “good score”. For reading scores in CPS terms, see how to read CPS scores and averages; for comparing your own runs, see how to track click speed over time and compare fairly. To pick a different test, see the full CPSKit toolbox.
Frequently asked questions
How do I convert CPS to CPM?
Multiply by 60. 5.5 CPS is 5.5 × 60 = 330 CPM.
How do I convert CPM to CPS?
Divide by 60. 270 CPM is 270 ÷ 60 = 4.50 CPS.
Is CPM more accurate than CPS?
No. It is the same rate in a different unit. A CPM value from a short run is less steady than a CPS value from a long one, because the rate is scaled up from fewer seconds.
Which duration should I use for CPM?
Use 60 seconds if you want a counted minute. Shorter presets are fine for quick comparisons, as long as you compare only runs of the same duration and say so when you share the number.
Why does my CPM change a lot between 5 second runs?
One click is worth 12 CPM in a 5 second run, so a single click more or less moves the number visibly.
These tools record real events observed in your browser. Results differ by browser, operating system and connection type, and a result does not certify the device or measure your hand beyond what the test page counts.