Touch Sampling Rate vs. Display Refresh Rate: The Physics of Input Lag
Smartphone marketing is overflowing with Hertz (Hz) ratings: "120Hz Fluid AMOLED," "240Hz Touch Response," "480Hz Instant Sampling." But what do these numbers actually mean in practice, and how do they impact input responsiveness?
By Ritvik Kudalkar, updated . A 6 minute read.
The Fundamental Distinction: Input vs. Output
While both metrics are measured in Hertz (cycles per second), they describe opposite directions of the user interaction pipeline:
Display Refresh Rate (Hz)
The number of times per second the display panel updates its visual image buffer. Standard screens refresh at 60Hz (once every 16.6ms), while high-refresh screens (Apple ProMotion, Samsung 120Hz) update at 120Hz (once every 8.3ms). Higher refresh rates make animations and scrolling look buttery smooth.
Touch Sampling Rate (Hz)
The frequency at which the touch digitizer hardware scans its electrode matrix to detect finger coordinates. A 120Hz sampling rate polls for touches every 8.3ms; a 240Hz rate polls every 4.16ms; a 480Hz gaming rate polls every 2.08ms. Higher sampling rates minimize input lag.
The Anatomy of Touch Latency
When you tap your finger on a screen to shoot in a mobile game or draw a line in a sketch app, the signal must navigate an entire multi-stage hardware and software pipeline:
- Physical Actuation: Your finger physically touches the glass, perturbing the mutual capacitance field.
- Digitizer Polling (Sampling Interval): The touch controller scans the matrix. At 120Hz, this step takes between 0 and 8.3ms. At 360Hz, it takes just 0 to 2.7ms.
- Controller Coordinate Calculation: The touch controller IC filters noise, calculates centroid coordinates, and asserts a hardware interrupt to the CPU. (Approx. 2–4ms).
- OS Input Dispatcher: The operating system kernel reads the interrupt and dispatches a touch event to the active application window. (Approx. 2–5ms).
- Application Logic & Game Loop: The game engine or browser processes the event and submits a render command to the GPU. (Approx. 4–16ms depending on frame rate).
- Display Scanout: The display panel pushes new pixel data to the screen during its next refresh cycle. (Approx. 8.3ms on a 120Hz display; 16.6ms on 60Hz).
Total End-to-End Latency: On a budget 60Hz screen with 60Hz touch sampling, total touch-to-photon latency often exceeds 65–85 milliseconds. On a flagship device with a 120Hz screen and 360Hz touch sampling, latency drops to 20–30 milliseconds.
Comparison Table: Common Sampling Rates
| Device Category | Display Refresh | Touch Sampling | Polling Interval | Primary Benefit |
|---|---|---|---|---|
| Standard Laptops & Budget Phones | 60 Hz | 60 – 120 Hz | 16.6 – 8.3 ms | General browsing, low power draw. |
| iPhones & Modern Flagships | 60 – 120 Hz | 240 Hz | 4.16 ms | Ultra-responsive typing and smooth UI navigation. |
| Dedicated Gaming Phones (ROG, RedMagic) | 144 – 165 Hz | 480 – 720 Hz | 2.08 – 1.38 ms | Competitive esports reaction speed in FPS titles. |
| Stylus Tablets (iPad Pro, Galaxy Tab S9) | 120 Hz | 240 – 280 Hz (Pen) | 3.5 – 4.1 ms | Zero visible "ink drag" when sketching. |
How to Test Tracking & Sensitivity in the Browser
While a web browser cannot override your operating system's kernel to change hardware polling frequencies, our Sampling Rate Test uses the browser's getCoalescedEvents() API to count the intermediate touch points reported between animation frames. Move one finger in fast circles and it reports the live, peak, and average rate in Hz. Browsers without that API (including some versions of Safari) only deliver one event per frame, so the reading there tops out at the display refresh rate.
Launch our Sensitivity & Tracking Test to draw fast spirals and diagonal zig-zags. If the rendered trail shows straight, even line segments without jitter, your touch digitizer's interpolation filter is operating in prime health.