V-Sync on but tearing at 144Hz: 3 causes that break synchronization

Part of our guide on gaming controllers impact

Your V-Sync toggle isn't broken. Three other settings are quietly undoing it, and only one of them lives in the game's menu.

What screen tearing is and whether V-Sync causes it

Say you're sweeping your view across a wall in a shooter and a horizontal line splits the image: the top half shows one frame, the bottom half the next. That line is the tear, and it means the monitor drew part of a new frame before finishing the old one.

V-Sync does not cause tearing. It exists to stop it. The setting makes the GPU wait for the monitor's refresh cycle before sending a frame, so the display never grabs a frame mid-draw. When it works, the tear line vanishes and stays gone.

The trade-off is latency. Waiting for the refresh cycle adds roughly one frame of delay, which at 144Hz is about 7 milliseconds. On some setups, especially when frame rates dip below the refresh rate, that wait can double. That's the cost you accept for a clean image.

So if tearing appears with V-Sync enabled, the setting isn't doing its job. Something else in the chain, your frame rate, your window mode, or your driver, is stopping the synchronization from reaching the screen. The next three sections cover each one. Before you commit to anything, it is worth looking at how to get started streaming games.

Cause 1: your frame rate runs above 144 fps

Picture an esports title on a strong GPU: the counter reads 250 fps, V-Sync is toggled on in the menu, and you still see tearing when you turn quickly. This is the most common cause, and it's the first one to rule out.

V-Sync only works when the GPU actually waits. Many games and engines treat a V-Sync toggle as a request, and if the frame rate runs well above the refresh rate, frames queue up faster than the monitor consumes them. The display ends up showing slices of two different frames anyway.

The fix is a frame rate cap at or slightly below 144. Use 141 fps, which leaves headroom so a stray frame never arrives early. Cap it in the game's settings if the option exists, or in NVIDIA's app under Max Frame Rate, or AMD Adrenalin's Frame Rate Target Control. RTSS, a free tool, caps frame rates for almost any game. We go through lag despite low ping cloud step by step elsewhere on the site.

Uncapped fps above refresh also fights with G-Sync and FreeSync. Those technologies need the frame rate inside the panel's refresh range, typically 48-144Hz, to hold sync. Above the ceiling, adaptive sync disengages and you're back to plain tearing. Cap first, then judge whether V-Sync is actually failing.

Cause 2: borderless windowed mode bypasses in-game V-Sync

You switch a game to borderless windowed because alt-tabbing is instant, and the tear line returns even though V-Sync is still ticked. The setting didn't stop working. The game stopped owning the display.

In exclusive fullscreen, the game controls the monitor directly and its V-Sync applies cleanly. In borderless windowed mode, the game renders into a window managed by Windows' desktop compositor. The compositor decides when frames reach the screen, so the game's own V-Sync setting can be ignored entirely. Many engines don't even attempt it in this mode. The other half of this decision is how to view fps steam.

Three paths fix it. Switch the game back to exclusive fullscreen if the option exists. Or leave borderless mode and enable V-Sync at the driver level instead, where the compositor respects it. Or use the windowed mode's own presentation setting if the game offers one, sometimes labelled as reduced latency or fullscreen optimizations.

There's a real trade-off here. Exclusive fullscreen gives V-Sync full control but makes alt-tabbing slower and can break overlays. Borderless gives you instant switching and smooth multi-monitor use but hands frame timing to Windows. Pick based on whether you tab out mid-session or sit locked in the game.

Cause 3: the driver override conflicts with the in-game setting

You set V-Sync On inside a game, but your NVIDIA Control Panel or AMD Adrenalin settings say Off, and the driver wins. This override is the cause people miss most, because nothing on screen tells you the two settings disagree. We cover xbox controller troubleshooting in its own article.

The driver-level V-Sync setting has three states that matter: On forces it everywhere, Off disables it everywhere, and Use application setting lets the game decide. If it's set to Off, every in-game toggle you flip does nothing. Some games and utilities also set the override themselves during installation or profile tweaks.

Open the control panel, find Manage 3D Settings on NVIDIA or the Graphics/Display tab in Adrenalin, and set V-Sync to Use application setting. Then choose per game where you want it. While you're there, check whether Fast Sync or Enhanced Sync is enabled, since those reduce tearing by different means and can mask or worsen the behaviour you're diagnosing.

Two settings disagreeing is worse than either alone: you can end up with double buffering, added latency, and tearing all at once. One owner, one decision. Decide at driver level or in-game, and set the other to defer. If that sounds like your situation, read up on how to block inappropriate games on kids pc next.

How to tell if V-Sync is not working properly

Work through one test at a time, because overlapping fixes hide which change did the job. Set up a scene with fast horizontal motion: panning across a striped wall or a fence in any game shows tearing within seconds if it's happening.

Then run this sequence and note where the tear disappears.

1. Open your frame rate overlay, via the GPU app, Steam, or the game itself, and confirm your fps. If it reads above 144, cap it at 141 and test again. Most tearing cases end here.

2. Switch the display mode to exclusive fullscreen and test again. If the tear vanishes, borderless mode was bypassing your V-Sync setting.

3. Open the driver control panel and set V-Sync to Use application setting, then enable it in-game. If tearing stops, a driver override was cancelling your choice.

4. If tearing persists through all three, update the GPU driver cleanly, then check whether G-Sync or FreeSync is enabled on the monitor's own menu as well as in the driver. A mismatch there can produce tearing-like stutter.

A quick tell that V-Sync IS working: tearing gone, but mouse movement feels slightly heavier, by roughly a frame. That lag is the sync cost, not a fault.

1. Check the fps counter; cap at 141 if above 144
2. Switch to exclusive fullscreen and retest
3. Set driver V-Sync to Use application setting, enable in-game, retest
4. Update the GPU driver and verify G-Sync or FreeSync matches on monitor and driver

Does V-Sync hurt performance, and is FreeSync the better deal

The common claim: V-Sync tanks your frame rate. Partly true. V-Sync doesn't lower the fps a GPU can render, but it forces the pipeline into sync with refresh, and when a frame misses its deadline the GPU can drop to half the refresh rate, 72 fps on a 144Hz panel. That stutter is what people blame on the setting.

The standard fix is a frame cap just below refresh, which keeps frames inside the sync window and prevents the half-rate drop. You trade a few frames of input lag for a stable image. Competitive players usually refuse that trade; everyone else rarely notices it once adaptive sync is on.

FreeSync and G-Sync change the math. The monitor refreshes to match the GPU instead of the GPU waiting for the monitor, so tearing disappears without the fixed refresh wait. Latency stays lower than plain V-Sync, and performance is essentially unaffected. They are not bad for performance; the catch is the range, typically 48-144Hz, and the fact that you should still cap fps below the ceiling.

My take: on a 144Hz FreeSync or G-Sync monitor, run adaptive sync on, cap at 141, and leave driver V-Sync off unless a game shows flicker in dark scenes. On a monitor without adaptive sync, V-Sync plus a cap is the only clean option, and the input lag is the price.

• V-Sync myths: it lowers fps itself (no, the half-rate drop does), it always ruins latency (about a frame at 144Hz)
• FreeSync myths: it costs performance (it doesn't), it works at any fps (no, only inside the refresh range)

Questions people still ask

I chased a tear line across two GPUs before finding a driver profile set to Off. Check the override first; it's the five-minute fix nobody mentions.