I bought a new monitor, went straight into the OSD, and cranked the overdrive setting to its highest option before playing a single game β faster pixel response sounded like a strictly-better setting, so why not max it out. Within an hour of playing a fast-paced shooter I noticed pale, almost glowing outlines trailing behind enemy models and my own crosshair during quick turns. My first assumption was a defective panel. It wasn’t. I’d pushed the overdrive so far past what the pixels needed that they were overshooting their target color and snapping back, which is a completely different artifact from the blur I was trying to fix in the first place, and most monitor settings menus don’t explain the difference at all.
What Overdrive Is Actually Doing to the Pixel
LCD pixels don’t change color instantly β they physically shift how much light passes through the panel, and that transition takes measurable time, which is where motion blur and standard ghosting come from. Overdrive (sometimes called response time compensation) fixes this by applying extra voltage to push the pixel to its target state faster. Done correctly, this reduces the trailing smear behind fast-moving objects. Pushed too far, the extra voltage doesn’t just speed up the transition β it overshoots the target color entirely, the pixel briefly displays the wrong shade, and then corrects back to where it should have landed in the first place. That overcorrection is inverse ghosting, also called overshoot or a corona, and it looks nothing like the problem overdrive is supposed to solve.
Telling the Two Artifacts Apart
Standard ghosting reads as a soft, dark, blurry trail dragging behind a moving object β it looks like the image is smearing because the pixels are too slow to keep up. Inverse ghosting looks like the opposite: a pale halo, a bright or reverse-colored outline, or a “corona” effect tracing the edge of the same moving object, because the pixels are now overshooting rather than lagging. If you’re chasing a fix and can’t tell which one you’re looking at, the direction of the artifact is the tell β dark and trailing behind means your overdrive is too low or off, bright and outlining means it’s too high.
Why the Right Setting Depends on Your Actual Frame Rate, Not Your Monitor’s Spec
The detail that made my situation click was that overdrive strength is tuned by the panel manufacturer around a specific pixel transition window, which corresponds to a specific refresh rate. A 240Hz panel’s aggressive overdrive setting is calibrated assuming a new frame arrives roughly every 4.2ms. If your actual frame rate is dropping to 100fps during demanding scenes, each frame is now staying on screen for close to 10ms β nearly two and a half times longer than the overdrive curve was tuned for β which gives the overshot pixel far more time to sit in its wrong, overcorrected state before the next frame arrives, making inverse ghosting far more visible exactly when your performance dips, not when it’s running at its peak refresh rate.
This is why the practical fix isn’t “find the number that looks best in a static test screen,” it’s tuning for your realistic lowest sustained frame rate during actual gameplay, not your monitor’s advertised peak. If your frame rate swings between 100 and 240fps depending on the scene, a middle or “balanced” overdrive preset usually avoids visible haloing during the lower end of that range while still keeping acceptable clarity at the top, whereas the most aggressive preset β the one that looks most impressive in a manufacturer’s marketing screenshot running at a locked high frame rate β is often the exact setting that produces the coronas you’re trying to eliminate the moment your frame rate dips in a real game.
FAQ
Is inverse ghosting a sign my monitor is defective?
Almost never β it’s a setting problem, not a hardware fault. Lowering the overdrive/response time setting one or two steps in the OSD resolves it in the vast majority of cases.
Should I just turn overdrive off completely to avoid the problem?
Not usually β turning it off entirely brings back standard ghosting (the slow, blurry trailing effect), which is what overdrive exists to fix. The goal is finding the middle setting that avoids both artifacts, not eliminating the feature.
Why does inverse ghosting only show up sometimes and not constantly?
Because it’s tied to the mismatch between your overdrive’s tuned refresh window and your actual frame rate in the moment β it tends to appear specifically during frame rate dips, fast camera pans, or scenes with high contrast edges in motion, not during steady, high frame rate gameplay.
Do OLED monitors have this problem too?
Much less often β OLED pixels change state far faster than LCD pixels natively, so most OLED monitors need little to no overdrive compensation in the first place, which removes the overshoot risk almost entirely. This is primarily an LCD (IPS/VA/TN) issue.
