Delay before the picture appears
Input lag is the time between a signal arriving at a display and the corresponding image appearing on the screen. In everyday terms: a game console sends a frame, and some number of milliseconds pass before that frame is visible. The display itself is only one part of what you feel when you press a button, but it is a part you can sometimes influence.
A closely related idea is system latency, the whole delay from pressing a key or button to seeing the result. It includes the controller, the software, the graphics processing and the display. Input lag describes only the display’s share of that chain. Because the terms are often mixed up, reading carefully what a quoted figure actually measures is worthwhile.
How it differs from response time
Input lag is easily confused with response time, but they describe different things.
- Input lag is about when the picture starts to change. It is a delay.
- Response time is about how quickly a pixel moves from one shade to another once it starts. It affects blur and smearing, not when the change begins.
A display could have very fast pixel transitions and still hold each frame for a while before showing it. It could equally show frames promptly while individual pixels change slowly. The two numbers measure separate properties, and a good value for one says little about the other. For more on the latter, see response time and what the numbers leave out.
Where the delay comes from
Several steps can sit between the cable and your eyes.
Image processing. Modern displays often process the picture before showing it. They may scale it to the panel’s native resolution, adjust colors, sharpen edges, reduce noise or insert extra frames to smooth motion. Each step takes time, and some require the display to hold several frames in memory first. Televisions in their default picture modes tend to do more of this than computer monitors.
Refresh timing. Because the screen is drawn from top to bottom at a fixed rate, the bottom of the picture is drawn later than the top. At 60 Hz, a full pass takes about 16.7 milliseconds, so there is a built-in spread of how late different parts of the image appear. A higher refresh rate shortens that, so a higher rate can reduce delay even when everything else stays the same.
Frame buffering. If the display or source holds a frame until it is complete or queues extra frames, a small delay is added. Vsync with extra queued frames is a common example, and variable refresh methods can help by avoiding some of that waiting.
Panel response. Even after the display starts to change a pixel, it takes a moment to reach its target. This is where response time enters, and its effect is felt as part of the total delay.
Connections and extra equipment. Adapters, capture devices, wireless links, audio receivers and switches can add delay if they process the video or re-encode it. A plain direct digital connection usually adds very little.
Why it matters, and for whom
Whether you notice input lag depends on how you use the screen.
- For reading, browsing, watching video and ordinary office work, small delays are typically unnoticeable. Video players can even compensate by delaying the sound to match the picture.
- For fast-paced games and competitive play, delay can be noticeable because you are reacting to what you see. This is a large part of what esports displays are built around.
- For drawing or writing with a pen, delay between pen movement and the line appearing affects how natural it feels, though much of that comes from touch latency in the input system rather than the screen.
- For music and rhythm activities, timing matters, and many games offer a calibration step to compensate for display delay.
There is no universal threshold at which delay becomes a problem. People differ, and the type of content matters. A delay of a few milliseconds is generally hard to perceive, while a much larger one is easier to feel, but where the line sits varies with the person and the task.
How people measure it, in general terms
Measuring it properly is harder than it sounds. A common approach is to feed the same signal to a reference display and the display being tested, then record both with a high-speed camera and compare when each begins to show the change. Because the screen refreshes top to bottom, the result depends on which part of the screen is measured, so published figures may refer to the top, the center or an average. Without knowing the method, comparing figures from different sources is unreliable.
Manufacturers do not always state input lag, and the numbers they publish may not match your setup, since settings change the result. Independent reviews sometimes measure it, but methods differ.
What you can do about it
- Use a game or low-latency mode. Many televisions and some monitors have a mode that turns off extra processing. The effect can be large on televisions.
- Turn off features you do not need, such as motion smoothing and heavy noise reduction.
- Run at the display’s native resolution, so that the display does not need to scale the picture.
- Use a higher refresh rate if the display and source support it.
- Connect directly, without switches, capture hardware or wireless links, when delay matters.
- Check the settings of the source, since vsync and frame queues can add delay.
These steps reduce delay but do not eliminate it. Some of it comes from the way displays work, and the rest from everything before the display. If a setup feels fine to you, there is no need to chase smaller numbers.