Screen tearing is a visual glitch where the top and bottom of the image no longer line up — a horizontal seam runs across the screen while you move the camera or pan quickly. It happens when your GPU finishes a new frame while the monitor is still drawing the previous one, so you see two frames at once during a single refresh cycle.
Tearing is not a broken monitor or a bad cable. It is a timing mismatch between how fast your graphics card renders frames and how fast your display refreshes. The fix depends on what hardware you have, whether you care more about input lag or visual smoothness, and whether your frame rate sits above, inside, or below your monitor’s variable refresh range.
This guide explains the mechanics, every major fix available in 2026, and a practical order to try settings without guessing.
Quick answer
| Your setup | Best first fix |
|---|---|
| Monitor with VRR (FreeSync, G-SYNC Compatible, HDMI VRR) | Enable VRR in monitor OSD + GPU driver; cap FPS 3 frames below max refresh |
| No VRR, competitive FPS, input lag matters most | Leave VSync off; accept minor tearing or cap FPS with in-game limiter |
| No VRR, single-player, tearing bothers you | Enable VSync or use Enhanced Sync / Fast Sync if FPS is well above refresh |
| FPS often drops below refresh on a VRR monitor | VRR handles it; disable VSync in-game so lows are not doubled to 30 FPS |
| Console on HDMI 2.1 TV | Enable VRR and Game Mode in TV settings; use 40–120 Hz or 48–144 Hz modes |
| Laptop / iGPU on a 60 Hz panel | VSync or 60 FPS cap; most integrated GPUs do not drive high-refresh VRR well |
If you only remember one rule for modern PC gaming: a VRR monitor plus a sensible FPS cap beats VSync for most people in 2026.
What screen tearing looks like
Tearing shows up as one or more horizontal breaks in the image. The line often moves up or down as frame rate and refresh rate drift apart. It is most obvious when:
- You pan the camera quickly in a first-person or racing game
- Vertical edges (poles, door frames, UI bars) cross the tear line
- Your FPS is uncapped and far above your monitor’s refresh rate
- You play on a 60 Hz display where each frame stays on screen longer
On a 144 Hz or 240 Hz panel, tearing can still happen — but each frame is on screen for less time, so many players notice it less than on 60 Hz. That is one reason competitive setups push high refresh even with VSync disabled.
Tearing is not the same as:
| Artifact | What you see | Typical cause |
|---|---|---|
| Screen tearing | Horizontal split; two frames visible at once | GPU and display refresh out of sync |
| Stutter / hitching | Whole frames skip or freeze briefly | FPS drops, shader compilation, disk streaming, CPU spikes |
| Micro-stutter | Regular rhythm of uneven frame pacing | VSync on without triple buffering, bad frame limiter step |
| Judder | Motion looks uneven at fixed 30/60 on 144 Hz | Non-native frame rate on high-refresh display without VRR |
| Ghosting | Blurry trail behind moving objects | Slow pixel response on LCD panel — panel overdrive, not sync |
Fixing tearing will not fix stutter from low FPS. If performance is the bigger problem, tune settings and check VRAM headroom before chasing sync options.
Why screen tearing happens
Displays do not update all pixels at once. They scan out from top to bottom (and back), line by line, at a fixed interval set by the refresh rate — 60 times per second on a 60 Hz monitor, 144 on a 144 Hz panel, and so on.
Your GPU renders complete frames into a back buffer. When a frame is ready, the display reads from the front buffer during scanout. In the simplest double-buffered, unsynchronized path:
- The monitor starts showing Frame A.
- Mid-scanout, the GPU finishes Frame B and swaps buffers immediately.
- The top of the screen still shows part of Frame A; the bottom already shows Frame B.
- You see a tear line where the swap occurred.
The GPU can produce frames faster or slower than the monitor refreshes. Both cases cause tearing:
- FPS above refresh (e.g. 280 FPS on 144 Hz): the GPU may swap buffers multiple times per refresh, producing very visible tears.
- FPS below refresh (e.g. 52 FPS on 60 Hz): tears still appear between uneven frame times; stutter from low FPS usually feels worse than the tear itself.
Higher resolution means more pixels per frame — see 2560×1440 vs 1920×1080 — but tearing itself is about frame delivery timing, not pixel count. A GPU that struggles at 1440p may tear and stutter; fixing sync does not add FPS.
Fullscreen, borderless, and present modes
Exclusive fullscreen often gives the lowest latency and the most reliable sync behavior because the compositor is bypassed.
Borderless windowed routes through the Desktop Window Manager (DWM) on Windows. VRR and VSync still work on modern Windows 10/11 builds, but latency can be slightly higher than exclusive fullscreen. Some games default to borderless for alt-tab convenience — if tearing persists only in borderless, test exclusive fullscreen.
At the API level, games use different present modes:
- Immediate — swap as soon as a frame is ready; lowest latency, tearing allowed
- FIFO (VSync on) — wait for refresh; no tearing, higher latency, FPS capped to refresh
- Mailbox / flip model — triple-buffer style pacing; smoother when implemented well
You rarely pick these in menus; they are why the same “VSync Off” setting feels different between DirectX 11 and Vulkan titles.
How to fix screen tearing (every method)
There is no single universal setting. Each approach trades tearing, input lag, and frame rate stability differently.
Comparison table
| Method | Stops tearing? | Input lag vs uncapped | FPS cap? | Needs special hardware? |
|---|---|---|---|---|
| VRR (FreeSync / G-SYNC Compatible / HDMI VRR) | Yes, within VRR range | ~+1 ms vs uncapped in range | No (cap below max for ceiling) | VRR-capable monitor + compatible GPU |
| VSync on | Yes | Noticeably higher | Yes, to refresh rate | Any |
| Adaptive VSync (NVIDIA) | Yes when FPS ≥ refresh | High when active | No hard cap | NVIDIA GPU |
| Enhanced Sync (AMD) / Fast Sync (NVIDIA) | Mostly, if FPS >> refresh | Lower than VSync, higher than off | No | Recent AMD / NVIDIA GPU |
| In-game or RTSS frame cap | Reduces, does not eliminate alone | Lower than VSync | Yes | Any |
| Cap = refresh − 3 with VRR | Yes, including near max refresh | Low | Soft cap | VRR monitor |
| Triple buffering + VSync | Yes | Lower than double-buffer VSync | To refresh | Game/API support varies |
Variable refresh rate (VRR) — the 2026 default
VRR lets the monitor change its refresh rate to match the GPU’s frame rate within a supported range — for example 48–144 Hz on a common 1440p gaming panel, or 40–144 Hz on many 2026 models with LFC (Low Framerate Compensation) that multiply frames when FPS dips below the minimum.
When your FPS is inside that range:
- Tearing disappears
- Stutter from fixed 60 Hz showing uneven 57 FPS is greatly reduced
- Input lag penalty is typically around 1 ms — far less than traditional VSync
FreeSync (AMD) and G-SYNC Compatible (NVIDIA) both use VESA Adaptive-Sync over DisplayPort or HDMI. In 2026, most new gaming monitors support Adaptive-Sync; dedicated G-SYNC Ultimate modules with proprietary hardware are niche — most “G-SYNC” badges on spec sheets mean G-SYNC Compatible (Adaptive-Sync certified by NVIDIA).
NVIDIA: GeForce GTX 10-series and newer support Adaptive-Sync on certified displays via G-SYNC Compatible mode in the NVIDIA App (formerly GeForce Experience control panel).
AMD: FreeSync works on Radeon GPUs and is the native label for the same VESA standard.
VSync (vertical sync)
VSync forces the GPU to wait until the monitor starts a new refresh before swapping buffers. No tearing, but:
- Input lag increases — the GPU may wait with a finished frame ready
- FPS is capped to your refresh rate (60 FPS on 60 Hz)
- If FPS drops below refresh even briefly, classic double-buffer VSync can halve effective FPS (60 → 30 on a 60 Hz display) — worse than occasional tearing
Use VSync when you have no VRR monitor and tearing distracts you more than added latency — common in story-driven games at 60 Hz.
In competitive shooters, most players leave VSync off and accept tearing or use VRR + FPS cap instead.
Adaptive VSync (NVIDIA)
Adaptive VSync turns VSync on only when FPS is at or above refresh. If FPS drops below, VSync disables and you get tearing instead of harsh 30 FPS stutter. Better than always-on VSync for fluctuating frame rates, but VRR is strictly better when your monitor supports it.
Enhanced Sync (AMD) and Fast Sync (NVIDIA)
These technologies do not cap FPS to refresh. The GPU renders as fast as possible but only displays the latest complete frame at each refresh, discarding partial swaps that would cause tears.
Requirements and behavior:
- Works best when FPS is at least double your refresh rate (e.g. 300+ FPS target on 144 Hz)
- Lower input lag than VSync, but not as low as VSync off
- Does not help much when FPS hovers near refresh — use VRR instead
- Can be combined with VRR: VRR handles pacing in range; Enhanced Sync / Fast Sync can help above max refresh if you refuse to cap FPS
Enable in AMD Software: Adrenalin Edition (Graphics → Enhanced Sync) or NVIDIA App (Manage 3D settings → Fast Sync — where still exposed per driver version).
Frame rate limiting
Capping FPS is underrated:
- With VRR: cap 3 below max refresh (see above)
- Without VRR but high FPS: cap to refresh or refresh − 0.01 via RTSS (Rivatuner Statistics Server) for slightly less tearing than uncapped — some players use exact refresh minus a fraction to stay just below VSync threshold
- Without VRR and near refresh: a stable cap reduces tear frequency even with VSync off
Prefer the in-game limiter when it is frame-pacing aware. Use RTSS when the in-game cap steps in coarse increments (60, 120, 144 only) or causes micro-stutter.
Limiting FPS also reduces GPU heat and power — useful on laptops and when pairing a strong GPU with a 1080p high-refresh monitor.
Triple buffering
Triple buffering adds a third buffer so the GPU can keep working while one frame displays and another waits — smoother VSync with less stutter when FPS dips slightly below refresh. Not all games expose it; DirectX 12 and Vulkan often handle buffering differently than older DirectX 9/11 titles. When a game offers “VSync + triple buffering”, enabling both is reasonable on fixed refresh without VRR.
What to enable: decision guide
Work through this order on PC:
- Confirm monitor VRR range in the manual (e.g. 48–144 Hz). Enable Adaptive-Sync / FreeSync / G-SYNC Compatible in the monitor OSD.
- Windows: Settings → System → Display → Graphics → select display → turn Variable refresh rate On (and Optimizations for windowed games if you play borderless).
- GPU driver: NVIDIA App or AMD Adrenalin — enable G-SYNC Compatible or FreeSync for full screen and windowed as needed.
- In-game: VSync Off when using VRR (in-game VSync can fight driver VRR). Enable FPS limit at max refresh − 3.
- If tearing remains above VRR max: lower cap further or test Enhanced Sync / Fast Sync.
- No VRR: choose VSync on (cinematic) or off + cap (competitive). Avoid Adaptive VSync if you can upgrade the monitor — VRR panels are mainstream at 1440p 144 Hz prices in 2026.
By play style
| Priority | Recommended settings |
|---|---|
| Competitive FPS (CS2, Valorant, Apex) | VRR + cap at refresh − 3; VSync off; consider Reflex / Anti-Lag for latency (does not fix tearing) |
| Single-player AAA | VRR + cap, or VSync on if no VRR; Quality upscaling if GPU-bound |
| Console on TV | HDMI 2.1 VRR + Game Mode; 40 or 48 Hz modes for 30 FPS cinematic titles |
| Handheld PC (Steam Deck, ROG Ally) | Often 60 Hz cap; VRR on supported external displays via USB-C DisplayPort Alt Mode |
| Streaming / recording | Tearing on your monitor does not always appear on stream — OBS captures the game frame; fix tearing for local play, not viewer experience |
Troubleshooting: still tearing?
| Symptom | Likely cause | Fix |
|---|---|---|
| Tears only above 144 FPS on 144 Hz VRR panel | FPS above VRR ceiling | Cap at 141 FPS (or lower) |
| Tears with VRR “on” | VRR disabled in Windows or monitor OSD | Enable both; replug DisplayPort |
| Tears in menus only | Menus uncapped at 300+ FPS | Cap FPS globally or in driver profile |
| Tears in borderless, fine in exclusive | DWM / Game Bar overlay | Exclusive fullscreen or disable overlays |
| Tears on second monitor | VRR often primary display only | Game on VRR monitor; cap secondary |
| Worked until driver update | Reset NVIDIA/AMD 3D settings | Re-enable G-SYNC/FreeSync per game |
| HDMI TV, no VRR | Wrong HDMI port or HDMI 2.0 cable | Use labeled HDMI 2.1 port on TV; ultra high speed cable |
Also verify you are running the native resolution and refresh in Windows — a 144 Hz panel stuck at 60 Hz tears differently and wastes the panel. After changes, use Settings → System → Display → Advanced display to confirm Hz.
Screen tearing on consoles and TVs
PlayStation 5 and Xbox Series X|S support HDMI VRR on compatible TVs and monitors. Enable VRR in system settings and on the display. 40 Hz and 48 Hz modes help VRR cover 30 FPS and 40 FPS targets without judder.
On 120 Hz TVs, VRR range is often 40–120 Hz or 48–120 Hz — similar cap logic applies: if a game offers a 120 FPS performance mode but VRR maxes at 120, uncapped minor overshoot can still tear; use in-game 60 or 120 FPS locks when available.
Nintendo Switch has no VRR; tearing can appear in docked mode at unstable frame rates — a display-side limitation, not something settings fix.
Does refresh rate and resolution matter?
- Higher refresh reduces how long each torn frame is visible — 240 Hz tears bother some players less than 60 Hz tears, but sync is still needed for a clean image.
- 1440p vs 1080p does not cause tearing by itself; higher settings lower FPS, which can push you below VRR minimum — then LFC or frame-gen (DLSS / FSR on modern GPUs) helps more than VSync.
- OLED gaming monitors use the same VRR standards as LCD; burn-in is unrelated to tearing.
For a full list of render targets and streaming sizes, see 16:9 resolutions.
FAQ
Is screen tearing bad for your monitor or GPU?
No. It is a harmless timing artifact. It does not damage hardware. It can cause eye strain or distraction for some players.
Should I turn VSync on or off in 2026?
Off if you use VRR with a proper FPS cap. On if you have a fixed 60 Hz monitor without VRR and hate tearing. Off for competitive latency if you accept minor tearing on high refresh.
Why do pros play with tearing?
Many use 240–360 Hz VRR displays with VSync off and high FPS caps. Tearing is less visible at high refresh, and input lag matters more than a perfect image. Tournament clients also standardize settings across machines.
Does G-SYNC still require an NVIDIA module?
Native G-SYNC modules (hardware scalers) are rare in 2026. Almost all new “G-SYNC” monitors are G-SYNC Compatible — Adaptive-Sync displays certified by NVIDIA. They work with AMD and Intel GPUs too via VESA Adaptive-Sync.
Can I use FreeSync with an NVIDIA GPU?
Yes. Enable G-SYNC Compatible in the NVIDIA App for Adaptive-Sync monitors — including most FreeSync-branded panels.
Does capping FPS at 144 on a 144 Hz monitor remove tearing without VRR?
It reduces tearing but does not guarantee elimination — frame times still drift slightly. VRR or VSync fully removes tearing; a cap alone is a partial fix.
Does screen tearing appear in screenshots?
Usually no — screenshots grab a single completed frame. Tearing is visible only during live motion when scanout catches a buffer swap.
What about Intel integrated graphics?
Recent Intel Core Ultra and Arc iGPU systems support Adaptive-Sync on compatible monitors over DisplayPort. On older 60 Hz laptops, use VSync or a 60 FPS cap. Integrated GPUs rarely drive high-refresh 1440p without upscaling — fix performance first, then sync.
Bottom line
Screen tearing happens when frame delivery and display refresh are not aligned. In 2026, VRR on a gaming monitor or HDMI 2.1 display, plus a frame cap just below max refresh, is the best default for most PC gamers — low latency, no tearing, and smooth pacing when FPS drops.
Without VRR, choose between VSync (clean image, more lag) and uncapped or capped high FPS (responsive, possible tears). Understand which artifact you are fixing — tearing is sync; stutter is performance. Tune the GPU first, then sync.