Why 60 FPS Can Look Worse Than It Should

By Walter Jobs, Technology writer and editor · Published 9 October 2026

You played at 60 fps for years and it was fine. Then you used a 144 Hz monitor, went back, and 60 looked wrong. Not slower in a way you could put a number on, just wrong: juddery when the camera pans, smeary when you turn quickly, slightly late when you aim.

Those are three separate faults with three separate causes, and almost every answer to this question treats them as one. Worse, the most common explanation given for it is about television motion interpolation and has nothing to do with games at all. This article separates the three, explains which one you are seeing, and gives the fix for each.

First, the explanation that is wrong

Search this question and the answer you will most often get is the soap opera effect. That effect is real, and it is not this.

The soap opera effect happens when a television takes 24 frames per second of film and manufactures intermediate frames to fill a higher refresh rate. The invented frames are interpolations, they carry artefacts around fast motion, and the result reads as cheap video rather than as film. It is a consequence of frames that were never shot.

A game rendering 60 frames per second has rendered 60 real frames. Nothing was interpolated, nothing was invented, and the comparison does not transfer. If you have been told your 60 fps gameplay suffers from the soap opera effect, you have been given a television answer to a computer question.

While we are here, two more claims worth discarding. Higher frame rates do not increase input lag; a shorter frame time means a shorter path from your mouse to the screen, and the exceptions are frame generation, which inserts frames and does add latency, and V-Sync, which can queue them. And game engines do not have a general inability to handle high frame rates. Specific engines have specific frame caps, and a handful have physics bugs above a certain rate, but that is a list of named cases rather than a rule.

Fault one: it judders, and the maths explains why

This is the most common cause and the one nobody shows the arithmetic for.

A monitor refreshes at a fixed rate unless variable refresh is doing something about it. Each rendered frame is held on screen for a whole number of refreshes. So if your frame rate does not divide evenly into your refresh rate, frames get held for different lengths of time, and that unevenness is what you are seeing.

Look at the 144 Hz row. A frame shown for two refreshes is on screen for 13.9 ms. The next, shown for three, is on screen for 20.8 ms. Your frame rate counter says a steady 60 and your eyes are being handed a 14, 21, 14, 21 millisecond pattern. The counter is averaging away the thing that is bothering you.

This is also the answer to the question people ask next, which is why 60 fps felt fine on the old 60 Hz screen and bad on the new 144 Hz one. Nothing about the game changed. The division changed.

How to fix the judder

• Leave variable refresh on and let the monitor match 60. G-Sync and FreeSync exist precisely to make the refresh rate follow the frame rate, which removes the division entirely. If you have it, this is the fix, and switching it off to solve choppy 60 fps, which is advice you will see, is backwards.
• Or set the refresh rate to 120 Hz instead of 144. You give up 24 Hz you were not using and 60 then divides exactly. On a 165 Hz panel, 120 Hz is likewise available and divides cleanly where 165 does not.
• Or stop capping at 60. If the hardware can do more, an uncapped frame rate inside a variable refresh window is smoother than a capped one outside it.
• If you must cap, cap at 58 or 59 inside the variable refresh range rather than at the ceiling, which keeps the monitor in the sync window instead of bouncing off the top of it.

Fault two: it smears, and that is your display holding still

The second complaint is different: the image is not uneven, it is blurred while moving, and it sharpens the instant you stop. This has nothing to do with frame rate division and everything to do with how modern panels emit light.

An LCD or OLED is a sample-and-hold display. Each frame is lit continuously for the whole time it is on screen. Your eye, meanwhile, is tracking a moving object smoothly, so it sweeps across a static image that is being held in place for 16.7 ms. The result is that the object is smeared across your retina. The display is perfectly sharp; the blur is produced by the mismatch between your moving eye and the still frame.

This is the reason 60 fps looked acceptable on a CRT and looks smeary on a flat panel. A CRT lit each phosphor briefly and then let it decay, so there was no long hold for your eye to smear across. The frame rate was the same; the persistence was not.

The amount of blur is set by how long each frame is held, which means the only real cure is a shorter hold: a higher frame rate, or backlight strobing, which blanks the backlight between frames to shorten the lit period artificially. At 60 fps on a sample-and-hold panel you are near the worst case, and no setting inside the game changes it.

How to reduce the smear

• Raise the frame rate. 120 fps halves the hold time and halves the blur. This is the honest answer and it is a hardware answer.
• Or turn on backlight strobing if your monitor has it, often sold as ULMB, ELMB, DyAc or 1 ms Motion Blur Reduction. It genuinely works and it costs brightness, usually cannot run at the same time as variable refresh, and introduces flicker some people find uncomfortable.
• Do not expect response time to fix it. Pixel response and persistence are different things. A 0.5 ms OLED still smears at 60 fps, because the pixel transition being instant does not shorten the time the frame is held.

Fault three: it feels late, and that is latency rather than smoothness

The third version of the complaint is about control rather than appearance. The image looks fine; aiming feels like it is arriving a moment after you asked for it.

At 60 fps a frame takes 16.7 ms to produce, and your input can only be reflected in the next one, so the frame rate alone puts something in the region of 16 to 33 ms between your hand and the screen. At 144 fps the same arithmetic gives 7 to 14 ms. That difference is small in absolute terms and large relative to the thing you are comparing it to, which is why it is noticeable in aiming and invisible in a driving game.

On top of that sits whatever the pipeline adds. V-Sync queues completed frames and waits, which can add a full frame or more. Pre-rendered frame queues add their own. Frame generation adds latency by definition, because a generated frame has to sit between two real ones.

How to reduce the lateness

• Cap slightly below your refresh rate rather than letting the frame rate hit the ceiling with V-Sync on. This is what NVIDIA Reflex and AMD Anti-Lag are automating.
• Use variable refresh instead of V-Sync where you have the option, since it removes the wait rather than managing it.
• Be wary of frame generation for this specific complaint. It raises the number on the counter and does not reduce the delay; if lateness is what bothers you, it is the wrong tool.

Which one are you seeing? A short diagnosis

That last row is worth dwelling on, because it is the one people misfile most often. A 60 fps average with a 38 fps 1% low feels nothing like a steady 60, and a frame rate counter will not show you the difference. Turn on a frame-time graph rather than an fps readout. Use the overlay in your GPU software, or a tool like CapFrameX or PresentMon, and look at whether the line is flat or spiky. A flat line at 60 is one of the three faults above. A spiky line is a different article, and usually comes down to memory, storage or a processor that cannot keep up in crowded scenes. Our bottleneck calculator will tell you which of your two parts is setting the ceiling.

The uncomfortable part: adaptation is real

None of the above is in your head, but one thing is, in the sense that it is a change in you rather than in the hardware. Smoothness is judged against what you are used to. Having spent time at 144 Hz, your baseline moved, and 60 is now being measured against a different reference than it was last year.

This matters for a buying decision because it runs one way. People who move to high refresh rarely go back happily, and the honest framing is that you are not fixing a fault in 60 fps, you are noticing it for the first time. That is a reason to be deliberate about the upgrade rather than a reason to avoid it.

What to actually do

1. Check the division first, because it is free. If your refresh rate is 144 or 165 and you are capped at 60, either enable variable refresh or drop the desktop refresh to 120.
2. Look at a frame-time graph, not a frame rate counter, to rule out the fourth row of that table before you blame the display.
3. If it is smear, accept that it is a hardware answer. Either more frames or backlight strobing. No in-game setting addresses persistence.
4. If it is lateness, cap below your refresh and turn off anything that queues frames. And leave frame generation off while you are judging it.