Keyboard Latency: Where Input Lag Really Comes From
Between your finger starting to press a key and a character appearing on screen lies a pipeline of a dozen delays — mechanical travel, debounce, matrix scanning, USB polling, operating system queues, application processing, and display refresh. Marketing focuses on one or two of these numbers. This guide walks the whole pipeline, with realistic magnitudes, so you know what is worth optimizing and what is noise.
Start the Performance TestThe input pipeline, stage by stage
A keypress travels through these stages, each adding delay: physical key travel to the actuation point (highly variable — this is where switch choice matters), switch debounce (the firmware waits a few milliseconds to confirm a clean contact, typically 1–10 ms), matrix scanning (the controller sweeps the key grid, adding roughly 0.1–1 ms), the connection hop (USB polling or a wireless link), and finally the operating system and application, which queue and process the event before anything reaches the screen.
End to end, a good wired gaming keyboard contributes somewhere between 2 and 15 ms from actuation to USB report. For context, a 60 Hz monitor adds up to 16.7 ms per frame just in refresh, and game rendering pipelines typically add several frames more. The keyboard is usually a minority share of total input lag — which is exactly why measuring, rather than assuming, is worthwhile.
Polling rate: what 1000 Hz really buys
For an ideal periodic USB polling schedule, 125 Hz means an 8 ms interval and 1000 Hz means 1 ms. If a report becomes ready uniformly within that interval, average waiting time is 4 ms versus 0.5 ms: a 3.5 ms difference in this stage only, not in total keyboard or display latency.
At 4000 and 8000 Hz the nominal intervals are 0.25 and 0.125 ms. A smaller polling interval alone does not establish end-to-end latency or a perceptible benefit. Evaluate the device, application and independently measured latency; browser key-repeat events cannot confirm the polling rate.
Switches, actuation and debounce
Switch choice affects latency mainly through actuation distance: a switch that actuates at 1.0–1.2 mm (speed switches) fires measurably earlier in the press than one actuating at 2.0 mm — at typical press speeds, roughly 5–10 ms earlier. This is one of the larger levers in the keyboard itself, though it comes with more accidental presses.
Analog hall-effect and optical switches take this further with adjustable actuation points and rapid-trigger behavior (re-arming the key the instant it starts moving up), which meaningfully tightens repeated presses in games. Optical switches also skip traditional debounce, saving a few more milliseconds; conventional switches depend on the firmware's debounce algorithm, which ranges from about 1 ms in good implementations to 10+ ms in sloppy ones — a bigger spread than most switch differences.
For typing rather than gaming, none of this is perceptible. Latency optimization is a gaming concern; typists should choose switches for comfort and accuracy.
Wired vs. wireless: the honest comparison
Modern 2.4 GHz dongles from major gaming brands achieve latency statistically indistinguishable from their wired mode — the good ones poll at 1000 Hz over the air. A quality wireless gaming keyboard is no longer a compromise.
Bluetooth is a different story: connection intervals commonly add 10–20 ms and can spike under interference or when the radio power-saves. Bluetooth is fine for productivity and unsuitable for competitive play. If your keyboard offers both modes, this is one of the few settings changes that produces a genuinely measurable improvement: use the dongle or cable for gaming.
Beware of battery-saving modes on wireless boards — some raise effective latency when idle to stretch battery life, making the first keypress after a pause noticeably slower.
Measuring what you actually have
These tests observe your tapping rhythm and operating-system key repeat in the browser. They do not measure physical keyboard latency or USB polling rate, and do not assign a hardware score. Measuring physical latency requires a known physical trigger and an independent timing reference, such as a suitable high-speed-camera or hardware setup.
Changes in these results can come from finger rhythm, OS repeat settings or browser scheduling. They do not identify wireless latency, USB faults or a damaged switch. Keep the setup consistent for practice comparisons; investigate suspected hardware problems with independent measurements.
What actually reduces your input lag
- Use a wired connection or a 2.4 GHz dongle, never Bluetooth, for competitive play — saves 10–20 ms over Bluetooth.
- Plug the keyboard directly into the PC, not through an unpowered hub or a monitor's USB passthrough.
- Check the supported polling setting in the manufacturer's software. The OS-repeat test cannot verify USB polling rate or show that an upgrade is needed.
- If your board supports it, reduce actuation distance or enable rapid trigger for games — one of the few genuinely felt keyboard-side changes.
- Attack the bigger delays outside the keyboard: a high-refresh monitor, exclusive fullscreen, and capped-but-stable frame rates each save more milliseconds than any keyboard upgrade.
- Close background software that hooks keyboard input (some RGB suites, macro tools, and overlays add measurable delay).
Observe your key timing
Record tapping intervals and OS repeat in the browser. Read the sampling method and limits alongside each result.
Start the Performance TestFrequently Asked Questions
Can humans even feel a few milliseconds of input lag?
Not as isolated events — blind tests show most people cannot distinguish single-digit millisecond differences. But delays add up across the pipeline, and consistency is perceptible: irregular timing feels 'floaty' even when the average is low. Cutting 10–20 ms of total system lag is noticeable; chasing 0.5 ms on one component is not.
Do optical switches make a keyboard faster?
Slightly and genuinely: they eliminate debounce delay (a few milliseconds) and often actuate on shorter travel. Whether that is felt in play is doubtful, but combined with rapid-trigger features they do tighten fast repeated inputs. Their bigger practical advantage is switch longevity — no metal contacts to wear and chatter.
Why do my browser test results vary between runs?
Changes in these results can come from finger rhythm, OS repeat settings or browser scheduling. They do not identify wireless latency, USB faults or a damaged switch. Keep the setup consistent for practice comparisons; investigate suspected hardware problems with independent measurements.
Can these results tell me which keyboard to buy?
Browser observations document the keys and combinations you tested. They do not certify every advertised feature or provide a hardware score for an upgrade or return decision. Measuring physical latency requires a known physical trigger and an independent timing reference, such as a suitable high-speed-camera or hardware setup.
Related guides
All guidesGaming Keyboard Buying Guide: What Matters, What's Marketing
Which gaming keyboard specs actually matter — rollover, polling, switches, rapid trigger — which are marketing, and how to verify claims after buying.
Keyboard Ghosting Explained: Why Keys Vanish When You Press Many at Once
Why keyboards drop or invent keystrokes when you press several keys at once, what NKRO and anti-ghosting really mean, and how to test your own rollover.
How to Test Your Keyboard: A Complete Step-by-Step Guide
Learn to test every keyboard key in your browser, read key codes, spot dead or chattering keys, and decide if a keyboard needs cleaning or replacing.