Input Lag vs Response Time

Response time and input lag are two different things that get used interchangeably, and confusing them leads to bad buying decisions. Pixel response time is how fast a pixel physically changes from one colour to another, measured in milliseconds (usually grey-to-grey); when it is too slow you see ghosting and smearing trails behind moving objects. Input lag(system latency) is the total end-to-end delay from your action — a mouse click or a stick move — to the moment the result appears on screen, the “click-to-photon” time. A monitor can have a blisteringly fast response time and still add meaningful input lag, because they measure different links in the chain. Knowing which one a spec refers to is the difference between chasing sharp motion and chasing low latency.

Marketing makes this worse by throwing “1 ms” on a box and letting buyers assume it means the screen is instant end-to-end. It does not. That number is one narrow measurement of one stage. To buy well and to actually feel more responsive in game, you need to separate the two ideas cleanly, understand what feeds into each, and know that improving one does not automatically improve the other. Here is the honest breakdown.

Pixel response time: how fast the pixels change

What it measures

Response time is how long a pixel takes to transition from one shade to another, measured in milliseconds. The common figure is grey-to-grey (GtG)— the time to shift between two grey levels, which represents the transitions that happen most in real content. You will also see MPRT (moving picture response time), a related but different figure tied to how long a frame is visible and often improved with backlight strobing. The critical point: response time is purely about the display panel's ability to repaint its pixels quickly. It says nothing about how long it took your input to reach the screen in the first place.

What slow response time looks like

When response time is too slow relative to the refresh rate, pixels have not finished changing colour before the next frame arrives, and you see ghosting— a faint trailing smear behind moving objects — or smearing, especially in dark scenes on some panels. This is a pixel-transition problem, and it is exactly what our monitor response time guide and our ghosting fix guidedig into, including how the overdrive setting speeds pixel transitions up and how pushing it too far causes inverse ghosting (a bright “corona” artefact) instead. Independent labs such as RTINGS publish measured grey-to-grey figures per monitor because the advertised “1 ms” rarely matches real-world behaviour across all transitions.

Input lag: the end-to-end delay

What it measures

Input lag, better called system latency, is the total time from an input to the corresponding change on screen — the full click-to-photonjourney. When you fire a shot, the signal travels from mouse to PC, through the game engine and CPU, to the GPU which renders the frame, out over the cable, into the monitor's processing, and finally onto the panel as emitted light. Input lag is the sum of all of that. It is what actually determines how instantly the game feels like it responds to you, and it is measured end-to-end — NVIDIA's documentation on Reflex and system latency describes this click-to-photon pipeline and how it is measured.

What contributes to it

Because input lag is a sum, many things feed it. The big contributors:

• Peripheral latency: your mouse or controller polling rate and its own processing.
• PC and game latency:the CPU/GPU render pipeline, frame queue depth, V-Sync, and how many frames are buffered before display — often the largest and most variable chunk.
• Frame rate: a higher, more stable frame rate generally lowers latency, because frames are produced and shown sooner.
• Display processing:the monitor's own internal signal processing before it lights the pixels — scalers, image processing, and any “game mode” that bypasses them.
• Refresh rate: a higher refresh rate shortens the wait for the next frame to be drawn, trimming latency.

Notice that the monitor appears here only as its processingand refresh contribution — not as its pixel response time. That is the crux of the confusion.

Why the two terms get mixed up

The confusion is understandable, because both are measured in milliseconds, both feel like “how fast the screen is,” and both get lumped together in reviews and store listings under vague words like “responsiveness.” But they describe different stages that happen to sit next to each other at the end of the chain. Response time is about the lastphysical step — a pixel changing colour once the frame has already been sent to it. Input lag is about the wholejourney that got the frame there, from your hand to that pixel lighting up.

A useful way to hold the two apart: response time answers “does moving content look clean or smeared?” while input lag answers “when I act, how quickly does the world react?” You can have crisp motion that feels laggy, and slightly smeary motion that feels instant. They are not the same axis, and a good monitor listing reports a separate measured figure for each precisely because one number cannot stand in for the other.

Why a fast response time does not guarantee low input lag

Here is the key idea stated plainly: response time and input lag measure different links in the chain, so one can be excellent while the other is poor.A monitor might change its pixels in a fraction of a millisecond (superb response time, no ghosting) yet still run heavy internal image processing that adds a chunk of display latency before those fast pixels ever light up — giving it good motion clarity but sluggish input lag. Conversely, a monitor with a modest response time can have very low processing latency and feel snappy to play on, just with slightly softer motion.

They can even trade against each other. Some motion-clarity features — certain overdrive implementations, and especially backlight strobing(marketed as blur reduction) — can add a little latency in exchange for sharper motion. So “1 ms” on the box tells you the panel can repaint quickly; it does not promise the screen responds to you quickly. Response time is about how clean the motion looks; input lag is about how instantly the game reacts. Judge a monitor on measured numbers for both, from testers like Blur Busters and RTINGS, rather than a single headline spec.

How to reduce each

Because they are different problems, they have different fixes. To improve response time (sharper motion, less ghosting): enable and tune the monitor's overdrive/ response-time setting to the level that speeds transitions without causing inverse-ghosting coronas; run a higher refresh rate; and, on panels that support it well, consider a backlight-strobing mode for motion clarity (accepting it may cost a little brightness and latency). Our ghosting guide covers the overdrive sweet spot in detail.

To reduce input lag(snappier response to your actions): raise and stabilise your frame rate; enable a low-latency mode such as NVIDIA Reflex where a game supports it; be cautious with V-Sync, which can add latency (pairing a high-refresh panel with a variable-refresh technology and a frame cap just below the max is a common low-latency setup); turn on the monitor's Game Mode to bypass extra image processing; and use a high-polling-rate mouse. Our reduce input lag guidewalks through the full checklist. The takeaway: to fix smeary motion, work on response time; to make the game feel instant, work on input lag — and do not assume a great number for one has done anything for the other.

One last practical note on measuring, since you cannot improve what you cannot see. Response time is a panel property you effectively read from reviews rather than measure yourself; the grey-to-grey figures from an independent lab are your source of truth. Input lag, by contrast, you can partly observe on your own machine — frame rate and latency overlays, and vendor tools that report system latency, let you watch numbers move as you change settings, which is the honest way to confirm a tweak actually helped rather than assuming it did. Treat the monitor's advertised response-time number as a starting hint, verify motion clarity with measured reviews, and judge input lag by what your own latency readout does when you turn a setting on or off.