Response time and refresh rate get borrowed from gaming-monitor marketing more often than they get properly explained — which leaves most display buyers unsure which one actually matters for their product, or whether either does at all.
Two different things, often confused
Refresh rate is how often the panel redraws the entire image, measured in Hz. Response time is how fast an individual pixel can change from one color to another, measured in milliseconds. A panel can have a high refresh rate and slow response time, or the reverse — they're independent specs, not two ways of describing the same thing.
How response time is measured (and why the number flatters)
Datasheets usually quote one of two things: black-white-black (Tr + Tf), the time for a pixel to go fully dark to fully bright and back, or gray-to-gray (GtG), the time to move between intermediate shades. GtG numbers tend to look much better, and real content mostly lives in intermediate shades, so GtG is closer to what you see — but it is also easier to flatter with overdrive settings. When two datasheets are compared, check that both quote the same measurement method before concluding one panel is faster. Temperature matters too: LCD liquid crystal gets sluggish in the cold, and response time at -20°C can be several times worse than at 25°C.
Technology matters more than the headline number
| Panel technology | Typical response | Notes |
|---|---|---|
| TN LCD | Fastest of the LCD family | Narrow viewing angle (see our TN vs IPS comparison for that trade-off) |
| IPS LCD | Moderate (10–35ms typical in tablet class) | Wide viewing angle, good color |
| OLED / AMOLED | Well under 1ms | Pixels switch almost instantly; motion looks crisp, though low-brightness flicker behavior needs a separate check (see our backlight dimming guide) |
Refresh rate: when 60Hz is plenty and when it isn't
60Hz is the default for almost every industrial and tablet-class panel and is more than enough for forms, menus and dashboards. Higher rates (90Hz, 120Hz) mostly show up on phones and premium tablets, where smooth scrolling and stylus tracking are part of the product experience. Higher refresh rate also costs: more power, more demanding interface bandwidth (see our interfaces guide), and a more capable GPU or SoC. Don't pay that cost for content that doesn't change.
When response time actually matters
- Video or fast-moving UI content — slow response time shows up as visible ghosting or blur trailing behind moving elements
- Touch-and-drag interactions — a cursor or drawn line can visibly lag behind the input if response time is too slow relative to touch sampling rate
- Anything with rapidly changing data — live sensor readouts, countdown timers, scrolling text
- Cold-environment devices — outdoor kiosks and vehicle displays where the slowdown at low temperature is the real spec
When it mostly doesn't
- Static or slow-changing content — a status display, an instrument panel showing steady readings, signage that updates every few seconds — response time in the tens of milliseconds is imperceptible here
- Most industrial HMI applications — menu navigation and parameter entry don't stress response time the way video does
What the numbers actually mean in practice
| Response time | What it feels like |
|---|---|
| Under 10ms | No perceptible lag even in fast content |
| 10–25ms | Fine for most UI and moderate video; occasional trailing on fast motion |
| 25–35ms | Acceptable for general use, static/semi-static content, standard touch interaction |
| Over 35ms | Noticeable lag if your application involves fast-moving content |
Most of the panels you'll encounter in the 8"–16" tablet-class range fall in the 15–35ms band — perfectly fine for the drawing pads, portable monitors, and control panels that size class is typically used for.
A quick way to test it yourself
Request a sample, play a scrolling-text or moving-grid test pattern, and also drag a finger or stylus across a drawing app. If you can't see trailing at normal viewing distance, the spec is good enough for your product. Do it at the lowest temperature your product will see, not just on the bench.
The question to ask yourself before worrying about this spec
Does your product display content that changes faster than a person can read it? If yes (video, live camera feed, fast animation), response time deserves real attention. If no (status panels, menus, forms, most industrial and consumer UI), the response time numbers you'll see across normal-quality panels are already fast enough — spending extra budget chasing a lower number won't produce a noticeable improvement.
Not sure if response time matters for your specific application? Request a quote and describe your content — we'll tell you honestly whether it's a spec worth prioritizing.