How to Fix Screen Tearing (2026): VRR, V-Sync & FPS Caps

By LK Wood IV · 2026-06-29 · ~8 min read · St. Louis County, MO

The old advice was simple: see a tear, turn on V-Sync. In 2026 that advice is mostly wrong. Screen tearing is not something you fix by toggling one checkbox anymore. The real fix is variable refresh rate, which means G-Sync, FreeSync, or the open VESA Adaptive-Sync standard, paired with a frame-rate cap set a few frames below your monitor’s maximum refresh. V-Sync still exists, and it still kills tearing, but it has become the fallback for people without a VRR monitor, not the default. This guide ranks the fixes from best to last resort and gives you exact, copy-pasteable numbers and click paths.

What screen tearing actually is

Tearing comes from a timing mismatch. Your GPU writes a new frame to the framebuffer while the monitor is partway through drawing the previous one, so a single screen scan ends up showing parts of two or more frames at once. That produces the familiar horizontal split or line across the image, usually most visible during fast horizontal camera pans — a line that exists only while the picture is moving, unlike the persistent lines on a monitor that point at a cable, a port, or a dying panel. The key technical detail, explained well by DisplayNinja, is that the GPU and the monitor are simply not synchronized.

There is a common misconception worth clearing up early. Tearing is not only a too-many-frames problem. It can occur both when your frame rate is higher than your refresh rate, which is the most obvious case, and when it is lower than your refresh rate. So capping your frame rate alone does not make tearing go away. The cap has a job, but eliminating tearing is not it. (If your problem is a faint trail following moving objects rather than a clean horizontal split, that’s a different artifact entirely — see how to fix monitor ghosting.)

The best fix: VRR plus an FPS cap

Variable refresh rate flips the relationship between GPU and monitor. Instead of forcing the GPU to wait on a fixed refresh, VRR makes the monitor dynamically change its refresh rate to match the GPU’s frame rate in real time, as long as that frame rate stays within the monitor’s supported VRR range. DisplayNinja gives a clean example: if your game is running at 65 FPS, the panel shifts to 65Hz to match, which eliminates both tearing and stutter with only about a 1ms input-lag penalty. That is a fraction of what V-Sync costs.

There are three flavors. VESA Adaptive-Sync is the open standard, introduced by VESA in 2014 under DisplayPort 1.2a. AMD FreeSync is built on top of Adaptive-Sync, which is why it is open, royalty-free, and needs no proprietary monitor hardware, per AMD’s FreeSync page. NVIDIA’s original G-Sync uses a proprietary scaler module embedded in the monitor and typically supports VRR from 1Hz all the way to the panel’s max refresh.

You do not need matching brands. NVIDIA GPUs can drive FreeSync and Adaptive-Sync monitors through the G-Sync Compatible program — supported since the January 2019 driver on GTX 10-series cards and everything newer — so VRR is no longer locked to one vendor. As RTINGS notes, true G-Sync module monitors historically cost roughly $100 to $200 more than comparable FreeSync panels because of the proprietary chip and licensing. For most people, a certified Adaptive-Sync monitor is the better value.

Enabling G-Sync (NVIDIA)

Per NVIDIA’s own control panel documentation, the steps are:

1. Open the NVIDIA Control Panel.
2. Go to Display, then “Set up G-SYNC.”
3. Check “Enable G-SYNC / G-SYNC Compatible.”
4. Choose “Enable for full screen mode” or “Enable for windowed and full screen mode.”

The prerequisite is a G-Sync-capable or G-Sync Compatible display connected, enabled, and set as your primary display. To confirm it is actually working, turn on “Show indicator for G-SYNC” in the Display menu, which puts an on-screen overlay up in-game when VRR is active.

Enabling FreeSync (AMD)

The AMD path is shorter because, per AMD’s support FAQ, FreeSync is enabled globally by default on systems with a compatible AMD GPU and a FreeSync-certified display. To check or toggle it:

1. Open AMD Software: Adrenalin Edition.
2. Go to Settings (the gear icon), then Display.
3. Confirm or toggle “AMD FreeSync.”

Per game, you can set FreeSync to “AMD Optimized,” which is the default, or “On,” or “Off” in the application profile.

The critical step: cap your FPS below refresh

This is where most people go wrong. Enabling VRR is only half the fix. You also need a frame-rate cap a few frames below your monitor’s maximum refresh so you stay inside the variable-refresh window. Per Blur Busters’ G-SYNC 101 testing, the tested safe target is about 3 FPS below your max refresh:

The minus-3 figure is the tested minimum; some setups need a slightly larger margin depending on the limiter or the game. Whatever you do, do not cap exactly at your refresh rate. Capping 144 on a 144Hz panel pushes you up against the ceiling, which kicks you out of the VRR range and brings tearing or V-Sync lag right back.

The enthusiast combo: G-Sync + V-Sync + cap

Here is the counterintuitive part. Blur Busters’ G-SYNC 101 testing found that the lowest tear-free latency comes from running G-Sync ON, V-Sync ON in the NVIDIA Control Panel (not in-game), keeping your frame rate inside the refresh range, and keeping GPU usage below about 99 percent. The reason this works is subtle but important. When V-Sync is on, G-Sync reverts to V-Sync behavior above its range, so there is no tearing at the ceiling. When V-Sync is off, G-Sync disables above its range and tearing returns display-wide.

So the combination of G-Sync + V-Sync On + an FPS cap gives you tear-free output across the entire range. The cap, not V-Sync, is what keeps latency low, because the cap keeps you out of the V-Sync region in normal play. V-Sync only ever activates at the very top edge as a safety net. One more detail from the Blur Busters forums: turn in-game V-Sync off while leaving driver V-Sync on, and disable every in-game “Vertical Sync” or “Triple Buffering” option so the game does not quietly enable its own higher-latency sync path. The game should think it is running with V-Sync off.

Add NVIDIA Reflex when the game supports it

NVIDIA Reflex reduces system latency by aligning game engine work to finish just in time for rendering, which eliminates the GPU render queue and reduces CPU back-pressure in GPU-bound scenes. Per NVIDIA, it cites up to about a 33 percent responsiveness improvement on a GTX 1660 Super, and it works best when you are GPU-bound. Importantly, when you enable Reflex alongside G-Sync and V-Sync, Reflex automatically caps your frame rate just below the refresh rate, so you do not need a manual cap in Reflex-supported games.

The community-recommended modern setup follows from this: if a game supports Reflex, enable G-Sync, V-Sync (driver), and Reflex, then run uncapped in-game and let Reflex’s built-in limiter handle the cap. For games without Reflex, set the cap yourself at about 3 FPS below refresh, preferring the in-game limiter when one exists.

The non-VRR options: Fast Sync, Enhanced Sync, and plain V-Sync

If you are stuck on a fixed-refresh monitor with no VRR, you still have choices. NVIDIA Fast Sync and AMD Enhanced Sync are a different class of fix. Per DisplayNinja, they let the GPU render uncapped above the refresh rate while still showing only the most recently completed full frame, which eliminates tearing without V-Sync’s hard wait. The catch is that they work best when your FPS is well above refresh, ideally around twice your refresh or more, so there are spare frames to drop. Below refresh they do not help and can stutter. That makes them a fit for very-high-FPS esports titles on a non-VRR display, and a poor fit for everything else.

Plain V-Sync is the last resort. It stops tearing by forcing the GPU to hold each finished frame until the monitor’s next refresh, but per TechSpot, double-buffered V-Sync at 60Hz adds roughly up to 33ms of input lag, about one to two frames. Worse, with plain double-buffered V-Sync, if your frame rate drops below your refresh rate the GPU misses the refresh window and V-Sync drops you to the next divisor. As DisplayNinja describes, that essentially halves you from 60 to 30 FPS at 60Hz, producing stutter that can feel worse than the tearing you were trying to fix. Triple buffering softens this by giving the GPU a second back buffer so it does not have to stall.

Common mistakes to avoid

• Capping AT your refresh rate instead of below it. Cap below, around minus 3, to stay inside the VRR window.
• Turning V-Sync off with G-Sync. Backwards. Driver V-Sync on plus an FPS cap below refresh is the low-latency, tear-free setup.
• Doubling up in-game and driver V-Sync. Use driver V-Sync on and in-game V-Sync off.
• Expecting a frame-rate cap alone to fix tearing. Per a community guide, a cap with no VRR or sync mode only reduces how often and how severely tearing shows up, because the GPU and monitor are still unsynchronized. The cap’s real job is to keep you inside the VRR range.
• Thinking frame generation fixes tearing. It does not. Frame generation and upscaling raise smoothness, not synchronization.

A quick note on frame generation, since people conflate it with sync. DLSS 4 on the RTX 50 series and AMD’s FSR 4 line are performance and smoothness features, not tearing fixes. AMD itself ships them alongside, not instead of, VRR, and as PC Gamer reports, FSR 4.1 reached the RX 7000 series on June 22, 2026 as an FPS feature. If you want to understand how that interpolation works and why it still needs VRR underneath it, read our breakdown of frame generation explained.

Where to go from here

Screen tearing is one of the few PC problems with a clean answer in 2026: turn on VRR, cap a few frames below your refresh, and leave driver V-Sync on as a ceiling. If you are still figuring out whether your GPU and CPU are well matched for the frame rates you are targeting, run the numbers through our PC bottleneck calculator so your cap targets are realistic for your hardware. And if your tearing only shows up in certain games, your render path may be part of the story, which is why it is worth reading how DX12 and DX11 differ for FPS before you blame the monitor.