Monitor Overdrive Tuning Guide? Pixel Response, Overshoot Inverse Ghosting & Refresh-Rate Behaviour.

2026-10-26 ｜ GPU Repair ｜ 21 min read ｜ HK GPU Fix Editorial

重點摘要

Monitor Overdrive changes how fast liquid-crystal pixels transition, not how fast the panel refreshes. Too little leaves motion blur, too much creates inverse ghosting. This guide explains pixel response, overshoot, refresh-rate behaviour, and variable refresh interaction, plus a practical method for separating blur, ghosting, inverse ghosting, and tearing.

What Overdrive Actually Changes

A monitor's refresh rate describes how often it draws a new image, while Overdrive describes how aggressively it drives its pixels from one brightness or colour level to the next. Those are different mechanisms, and confusing them is the source of most Overdrive mistakes. Raising refresh rate gives each frame a shorter time slot on screen. Raising Overdrive applies a stronger voltage impulse to make liquid-crystal molecules rotate faster toward their target position, so the pixel reaches the intended brightness sooner within that slot.

Think of a pixel as needing to travel from its previous value to its new value. Without Overdrive, that travel takes a certain amount of time, governed by the panel's liquid-crystal properties and the voltage normally applied for the target level. With Overdrive, the panel briefly applies a voltage beyond the target level, pushing the molecules harder, then settles back to the correct voltage once the target is approached. Done well, the pixel arrives sooner and the image looks sharper in motion. Done excessively, the pixel overshoots the target, passing the intended brightness and then having to return, which creates a visible artefact in the opposite direction. That artefact is inverse ghosting, and it is the signature of too much Overdrive.

Overdrive settings in monitor menus go by different names depending on the manufacturer, such as Overdrive, Response Time, Overdrive Level, or TraceFree-style labels, and the number of levels and their behaviour vary by model. The labels themselves do not standardise how strong each level is. A middle level on one monitor can be mild, while a middle level on another can be aggressive. Settings must therefore be judged by what appears on screen, not by the label or by assuming that a higher level is always better.

Pixel Response: Grey-to-Grey, Rise, Fall, and What They Miss

Pixel response time is usually quoted as a grey-to-grey figure, meaning the time for a pixel to transition between two grey levels. It is a useful shorthand, but it hides important detail. Different transitions take different amounts of time. A small step between two similar brightness levels is usually fast. A large step between dark and bright, or between bright and dark, can be slower, and the rise time and fall time of a pixel are often asymmetric. A single averaged number does not reveal which transitions are slow, and slow transitions are exactly the ones that leave visible trails behind moving objects.

Motion clarity also depends on more than response time alone. At a fixed refresh rate, each frame is held on screen until the next frame arrives, and the eye tracking a moving object across a held image perceives blur even if the pixel itself transitions quickly. This sample-and-hold blur is separate from pixel-transition blur, and Overdrive does not remove it. Backlight strobing and related motion-clarity features address sample-and-hold blur by a different mechanism, and they interact with brightness and with variable refresh in ways that are outside the scope of a pure Overdrive guide. The practical point is narrower: Overdrive improves the pixel-transition portion of motion blur. It cannot make a held frame behave like an impulsed display, and expecting it to do so leads to disappointment and to pushing the setting far beyond its useful range.

Response time also interacts with refresh rate through a simple time budget. At a higher refresh rate, each frame has less time on screen, so a pixel transition that was fast enough at a lower refresh rate may no longer complete within a frame at a higher refresh rate. Conversely, at a lower refresh rate, the same transition has more time, and an Overdrive level tuned for the highest refresh rate may be unnecessarily aggressive, producing overshoot that would not appear at the higher rate. This is the core reason the correct Overdrive level changes with refresh rate, and it is developed in detail below.

Overshoot and Inverse Ghosting: The Mechanism

Overshoot happens when the Overdrive impulse pushes a pixel past its target value. Suppose a pixel needs to move from dark grey to light grey. With a well-judged impulse, it approaches light grey quickly and settles there. With an excessive impulse, it passes light grey, becomes brighter than intended, and then relaxes back. During that excursion, the screen shows a value that was never part of the intended image. When the object that caused the transition is moving, that wrong value appears as a trail that is brighter than the background where a normal ghost would be darker, or darker than the background where a normal ghost would be brighter. In other words, the artefact has inverted polarity compared with ordinary ghosting. That inversion is how an observer distinguishes inverse ghosting from ordinary blur or ghosting.

Inverse ghosting is most visible at high-contrast edges: dark text on a light background, a dark object moving across a bright sky, a bright cursor or crosshair moving across a dark scene, or the edge of a window being dragged. It often appears as a bright halo trailing a dark object, or a dark halo trailing a bright object. It is also most obvious during moderate-speed motion, where the eye can track the edge and the overshoot has time to register as a distinct trail rather than blending into general blur. At very high motion speeds, many artefacts blur together, and at very slow speeds, the pixel has time to settle before the edge moves far, so overshoot is less noticeable. Testing at a single speed therefore risks missing the setting's worst behaviour.

It is also important to understand that overshoot is transition-dependent. An Overdrive level that is clean for most transitions can still overshoot on particular extreme transitions, such as full black to full white or the reverse. Judging a setting by one test pattern alone, especially a low-contrast pattern, can miss the transitions that matter in real content. A good evaluation uses several contrast levels and several motion speeds, and checks both dark-on-light and light-on-dark edges.

Why the Right Level Changes With Refresh Rate

The refresh-rate dependence of Overdrive follows directly from the frame time budget. Each refresh cycle gives the pixel a window in which to complete its transition before the next frame's value is required. At a high refresh rate, that window is short, so the pixel needs a stronger push to arrive in time. At a low refresh rate, the window is long, so the same strong push overshoots, because the pixel arrives early and then has to wait, with the excess impulse still driving it past the target.

Some monitors handle this automatically with variable Overdrive, adjusting the impulse strength as refresh rate changes. Many monitors do not. On a monitor with a single fixed Overdrive level, the level is typically tuned for one refresh rate, often the maximum, and it becomes progressively less appropriate as refresh rate falls. This is not a defect in the usual sense; it is a consequence of a fixed impulse being applied to a variable time budget. The user who changes refresh rate for different tasks, for example a high rate for fast-paced content and a lower rate for desktop work or for power saving, should expect to revisit Overdrive, or accept a compromise level that is tolerable across the range used.

The effect is most noticeable when the refresh rate changes by a large factor, such as dropping from a high gaming rate to a standard desktop rate, or when a frame-rate limiter or a less demanding scene holds the effective rate well below the maximum. In those cases, a level that was clean at maximum refresh can show clear inverse ghosting at the lower rate, and the correct response is to lower Overdrive for the lower rate, not to conclude that the monitor is faulty. Conversely, a level chosen to be clean at a low rate may leave visible blur at a high rate, because the pixel no longer completes its transition within the shorter window.

Variable refresh rate displays add a further complication, because the frame interval itself varies from frame to frame. A fixed Overdrive level cannot be simultaneously optimal for a short interval and a long interval. The next section explains that interaction.

Variable Refresh Rate Interaction

Variable refresh rate technology, in which the monitor's refresh timing follows the graphics card's frame delivery rather than running at a fixed rate, changes the Overdrive problem from a single-rate problem to a range problem. When frame rate is high, intervals are short and pixels need a strong push. When frame rate drops, intervals lengthen and the same push overshoots. A monitor with fixed Overdrive therefore faces an impossible compromise across a wide variable range: tune for the top of the range and overshoot at the bottom, or tune for the bottom and blur at the top.

Monitors that implement variable Overdrive address this by scaling the impulse with the current refresh interval, so that each frame gets an impulse appropriate to the time available. The quality of that implementation varies. Some implementations track the interval closely and keep artefacts low across the range. Others adjust coarsely, or only within part of the range, leaving overshoot at low frame rates or blur at high frame rates. The practical implication for the user is to test Overdrive not only at the maximum refresh rate, but also at the frame rates actually experienced in variable refresh play, including dips during demanding scenes. A setting that looks clean in a high-frame-rate test scene can overshoot badly when the frame rate falls, and that low-rate overshoot is often what the player notices during a demanding moment.

It is also worth separating this interaction from other variable-refresh artefacts. Variable refresh can be associated with brightness variation or flicker on some panels, particularly at low frame rates or during large frame-time swings, and that flicker has a different mechanism from Overdrive overshoot. A detailed companion discussion of variable-refresh dark flicker covers that mechanism, and it is not repeated here. The diagnostic distinction matters: flicker is a whole-screen or large-area brightness variation that pulses with frame timing, while inverse ghosting is a localised trail attached to a moving edge with inverted polarity. Treating one as the other leads to adjusting the wrong setting.

Similarly, flicker that appears across multiple monitors, or that follows a monitor regardless of content, points to a different family of causes, covered in companion discussion of multi-monitor flicker. Overdrive tuning does not fix a flicker that is present on a static image, because Overdrive artefacts require motion and a transition to appear.

Telling Blur, Ghosting, Inverse Ghosting, and Tearing Apart

Accurate diagnosis starts with separating four artefacts that are often lumped together as "blurry motion." Ordinary motion blur, in the pixel-transition sense, appears as a soft smearing behind a moving object, with the trail having the same polarity as the object: a dark object leaves a darkish smear, a bright object leaves a brightish smear. The edge looks soft and spread, rather than doubled or haloed. Reducing it requires faster pixel transitions, which is what a higher, still-clean Overdrive level provides, up to the point of overshoot.

Ghosting, in the stricter sense, appears as a distinct, delayed copy or trail of the moving object, still with normal polarity. It is what remains when pixel transitions are too slow to keep up with the object's motion, so the previous position of the edge is still visible while the object has moved on. Ghosting and soft blur sit on a continuum: very slow transitions produce a distinct ghost, moderately slow transitions produce soft smearing, and the distinction is a matter of degree and edge sharpness.

Inverse ghosting, as described above, is distinguished by inverted polarity: a bright halo behind a dark object, or a dark halo behind a bright object. It appears when Overdrive is too strong, not too weak, so the corrective action is the opposite of the action for ordinary ghosting. Increasing Overdrive when the artefact is already inverse ghosting makes it worse. This is the most common Overdrive error: seeing a trail, assuming the pixel is too slow, and pushing the setting higher, when the trail is already an overshoot artefact.

Tearing is different again. Tearing appears as a horizontal discontinuity, where the top and bottom portions of a single displayed frame come from different source frames, so a vertical edge appears split or offset at a horizontal line. It is a synchronisation artefact between frame delivery and display refresh, not a pixel-transition artefact, and it appears even on a perfectly fast panel if synchronisation is absent. Overdrive does not cause tearing and does not fix it. A companion discussion of tearing and vertical synchronisation covers its mechanism and remedies, and tearing should not be tuned away with Overdrive. Likewise, ghosting that comes from rendering or upscaling, such as temporal artefacts around moving objects in a rendered scene, has a different origin from panel ghosting, and a companion discussion of rendering ghosting in upscaling technologies addresses that family separately. The panel test in this guide isolates panel behaviour by using simple moving patterns and desktop motion, where rendering artefacts are absent.

A Per-Setting Comparison Method

A reliable Overdrive comparison changes one thing at a time: the Overdrive level. Keep refresh rate, resolution, brightness, and test content fixed for each round of comparison. Changing refresh rate and Overdrive together makes it impossible to tell which change produced an improvement or a regression, and that is how users end up chasing settings in circles.

Choose test content that covers the transitions that matter. A moving high-contrast pattern, such as dark bars or text moving across a light background and light bars moving across a dark background, reveals both normal and inverse ghosting. A moving photographic or game-like scene reveals whether artefacts visible on a synthetic pattern matter in real content, but synthetic patterns are more sensitive and should be used for the initial judgement. Dragging a window with sharp text, scrolling a document with high-contrast headings, and moving a cursor across contrasting backgrounds are useful everyday checks that complement a dedicated motion pattern, because they reproduce the edges the user actually looks at.

Test at several speeds. A single speed can hide overshoot that appears at moderate speeds, or hide blur that appears only at high speeds. If the test method allows speed selection, run slow, medium, and fast motion at each Overdrive level before judging it. At each level, check both polarities: dark-on-light and light-on-dark. Note the lowest level at which smearing disappears, and the lowest level at which inverse ghosting appears. The correct level, if one exists, lies between those two points: high enough to complete transitions, low enough to avoid overshoot. If no level satisfies both conditions at a given refresh rate, the panel's Overdrive implementation does not have a clean setting for that rate, and the choice becomes a compromise: favour the level with the least objectionable artefact for the content most often viewed, or change refresh rate to a range where a clean level exists.

Repeat the comparison at each refresh rate actually used. A level chosen at maximum refresh should not be assumed clean at a lower rate, and a level chosen at a desktop rate should not be assumed sufficient at a gaming rate. For variable refresh use, repeat the test at representative frame rates, including low-rate moments, or at least check demanding scenes where frame rate dips, because that is where fixed-Overdrive overshoot is most likely to appear. Record the chosen level per refresh rate in plain notes, so that a later change of refresh rate does not silently leave an inappropriate level in place.

Take care with test conditions. Viewing distance, ambient light, and brightness affect how visible a trail is, so keep them reasonably constant across levels. Judge with the same eyes and the same content, and avoid deciding on the basis of a single glance at a single edge. If two adjacent levels look identical, choose the lower one, because it leaves more margin against overshoot on transitions not covered by the test, and because the difference in blur between adjacent levels is often smaller than the difference in overshoot risk.

Common Mistakes and How to Avoid Them

The most common mistake is the one already described: treating every trail as slow pixels and raising Overdrive, when the trail is already inverse ghosting. The polarity check prevents this. Before raising Overdrive, ask whether the trail is brighter than the background behind a dark object, or darker than the background behind a bright object. If so, lower Overdrive instead.

The second mistake is judging Overdrive from a still image. A still image has no transitions, so Overdrive has nothing to do, and a still screenshot cannot show blur, ghosting, or inverse ghosting. Any judgement must use motion. A related mistake is judging from a photograph of a moving screen taken with a long exposure, which blends multiple positions and exaggerates blur in ways that do not match what the eye sees. Judge by eye, in motion, on the actual panel.

The third mistake is copying a recommended level from another monitor, or even from the same model with different firmware or panel revision, and assuming it transfers. Overdrive strength is not standardised across models, and even the same menu label can behave differently across revisions. Another user's ideal level is a starting point for testing, not a prescription.

The fourth mistake is setting Overdrive once and forgetting it after changing refresh rate, enabling variable refresh, or changing the frame-rate limit. Each of those changes alters the time budget or the interval distribution that Overdrive was tuned for, and the setting should be re-checked. This is especially true after switching between a high-refresh gaming profile and a standard desktop profile.

The fifth mistake is conflating panel artefacts with rendering or synchronisation artefacts, and tuning Overdrive for tearing, for upscaling ghosting, or for whole-screen flicker. The table above and the diagnostic distinctions in this guide exist to prevent that waste of effort. If an artefact is visible in a still frame, in a screenshot, or on a static image, it is not an Overdrive artefact, and Overdrive tuning will not fix it.

A Practical Decision Framework

Begin by resetting Overdrive to the monitor's default or to a middle level, and test at the refresh rate used most often, using the method above. Find the range between the disappearance of smearing and the appearance of inverse ghosting, and choose a level inside it, preferring the lower end when two levels look equivalent. Then repeat at any other refresh rate regularly used, and note a per-rate choice where the monitor allows it. For variable refresh, test at representative frame rates including dips, and favour a level that remains acceptable at the low end of the experienced range, because low-rate overshoot during demanding moments is more distracting than a small amount of blur at high rates.

If no level is clean at a given refresh rate, decide by content priority. For fast-paced content where edge sharpness matters most, a slightly higher level may be tolerable if inverse halos are faint. For text-heavy work where halos around letters are distracting, a slightly lower level is usually preferable, because reading involves tracking many high-contrast edges. There is no universally correct compromise; there is only the compromise that disturbs the actual work least.

Re-check after any change to refresh rate, variable refresh settings, frame-rate limits, or monitor firmware, and after moving the monitor to a very different ambient temperature environment, since liquid-crystal behaviour is temperature-sensitive in principle, even though everyday indoor variation rarely justifies frequent re-tuning. Keep notes of the chosen levels, so that a future reset to factory defaults does not silently discard a tuned configuration.

Related boundaries, briefly: tearing and vertical synchronisation are a separate synchronisation topic; rendering ghosting from upscaling technologies is a separate rendering topic; variable-refresh dark flicker is a separate brightness topic; and multi-monitor flicker is a separate multi-display topic. Each is covered in its own discussion and should not be conflated with Overdrive tuning.

FAQ

What does Overdrive actually do?

Overdrive applies a brief voltage impulse beyond the target level to make liquid-crystal pixels rotate to their new brightness faster. It shortens pixel transition time within a frame. It does not change refresh rate, resolution, or the number of frames delivered.

How do I know if my Overdrive is too high?

Look for inverted-polarity trails: a bright halo behind a dark moving object, or a dark halo behind a bright moving object. That halo is overshoot. Lower Overdrive one level and re-test the same edge, speed, and refresh rate.

How do I know if my Overdrive is too low?

Look for soft smearing or a normal-polarity trail behind moving edges, where the trail matches the object's brightness direction. Raise Overdrive one level and re-test, stopping before inverse halos appear.

Why does a setting that looks good at maximum refresh look bad at a lower refresh rate?

At a lower refresh rate, each frame has a longer time window, so the same strong impulse overshoots. A fixed Overdrive level tuned for the maximum rate is often too aggressive at lower rates. Lower the level for the lower rate, or use variable Overdrive where the monitor provides it.

Does Overdrive fix tearing?

No. Tearing is a synchronisation artefact where parts of one displayed frame come from different source frames. It appears as a horizontal split in an edge. Overdrive affects pixel transitions, not frame synchronisation, and cannot fix tearing.

Why does Overdrive behave differently under variable refresh?

Under variable refresh, frame intervals vary, so a fixed impulse cannot be optimal for both short and long intervals. A level tuned for high frame rates can overshoot when frame rate dips. Test at representative frame rates, including dips, and consider variable Overdrive if the monitor offers it.

Can I copy someone else's Overdrive setting for the same monitor model?

Only as a starting point. Overdrive strength is not standardised, and behaviour can vary across firmware and panel revisions. Test the recommended level with the method in this guide, at the refresh rates actually used, before adopting it.

Conclusion

Overdrive is a tuning control for pixel transition speed, not a general motion-clarity switch. Its job is to help pixels arrive at their target brightness within the frame window, without passing that target. Too little leaves smearing and ghosting; too much creates inverse ghosting with inverted polarity. The correct level depends on refresh rate, because the frame window changes with rate, and on variable refresh behaviour, because the interval itself varies. A disciplined per-setting comparison, changing only Overdrive at a time, testing both polarities at several speeds, and repeating at each refresh rate used, will find the clean range for the panel in front of you. Judge by polarity, not by label, keep notes per refresh rate, and re-check whenever refresh rate or variable refresh settings change. That method turns a confusing menu setting into a predictable, repeatable adjustment.