Mouse Polling Rate & Interval Calculator

Compare common 125–8000 Hz rates, their theoretical report intervals, and how many reports fit inside a chosen frame interval without pretending this predicts end-to-end input latency.

Polling rate (Hz)

Report interval (ms)

Frame rate for comparison

Mode

1.000 ms1000 Hz theoretical report interval

4.17Reports per 240 Hz frame

4.167 msFrame interval

1000 HzNearest common rate

0.500 msHalf report interval

Common polling intervals

Rate	Interval	Reports / 60 Hz frame	/ 120 Hz	/ 240 Hz
125 Hz	8.000 ms	2.08	1.04	0.52
250 Hz	4.000 ms	4.17	2.08	1.04
500 Hz	2.000 ms	8.33	4.17	2.08
1000 Hz	1.000 ms	16.67	8.33	4.17
2000 Hz	0.500 ms	33.33	16.67	8.33
4000 Hz	0.250 ms	66.67	33.33	16.67
8000 Hz	0.125 ms	133.33	66.67	33.33

This is timing arithmetic: interval = 1000 ÷ Hz. It is not a prediction of total click-to-photon latency. Device firmware, USB scheduling, CPU/game timing, display scanout, browser processing, and other stages add their own behavior.

Current vs target polling timing

Compare two polling rates against the frame rate you actually play at. This separates report interval math from total input latency and shows the theoretical average timing saved by a higher report rate.

Current polling rate (Hz)Target polling rate (Hz)Game / display frame rate (FPS)

—Current report interval

—Target report interval

—Avg theoretical wait saved

—Frame time

Ready.

Metric	Current	Target	Interpretation

This is timing math, not a sensor benchmark. Browser scheduling, game-engine sampling, wireless behavior, CPU load and display scanout can dominate the real end-to-end result.

Convert polling rate to report interval

The theoretical report interval is 1000 divided by the polling rate in hertz. For example, 1000 Hz corresponds to 1 ms and 8000 Hz corresponds to 0.125 ms between reports in the simple arithmetic model.

Not total system latency

The calculation does not include sensor processing, USB scheduling details, CPU/game timing, render queues, display scanout or human response. Use it to understand rate/interval relationships, not to predict click-to-photon latency.