A game can be running perfectly well right up until the image decides to split into horizontal slices. A character’s upper half shifts sideways from the lower half. A tree crown no longer quite lines up with its trunk. The camera moves, and the whole scene briefly resembles a badly shuffled deck of landscapes.
That visual artifact is screen tearing. It is especially familiar in PC gaming, though it can also affect console play. The reassuring part is that it is not usually evidence that a display is dying or that a GPU has suddenly developed a taste for cubism. Tearing is principally a timing problem: the graphics processor and the monitor are not agreeing on when one complete image should replace the next.
The modern answer is generally a combination of variable refresh rate technology and sensible frame-rate limits. But the terms around the subject can make a straightforward issue sound more mysterious than it is. Here is the practical version of what the hardware is doing, why older fixes carried trade-offs, and how to avoid letting a powerful PC outrun its own screen.
The mismatch behind the split image
A GPU, or graphics processing unit, creates the individual images that make up a game’s motion. Those images are frames, and its output speed is expressed in frames per second, usually shortened to FPS or fps.
A monitor has the separate job of presenting those frames. Its refresh rate is the number of times per second it refreshes the displayed image, measured in hertz (Hz). A conventional display may run at 60Hz, meaning 60 refreshes each second. Gaming monitors often offer 144Hz or higher; 240Hz is increasingly common in the middle of the gaming-monitor market, and displays rated as high as 1,000Hz are available.
The crucial detail is that a display updates on its own schedule. If the GPU finishes a fresh frame while the screen is partway through drawing the prior one, the displayed result can contain a portion of each frame. Because a monitor scans the frame buffer from top to bottom, the division typically appears as one or more horizontal discontinuities. One strip of the screen belongs to the older image; another belongs to the new one.
That is why tearing has such a distinctive look. It is not simply blur, and it is not necessarily a lower frame rate. It is two moments in a game being visible on different horizontal bands at once. It can be particularly obvious while panning a camera across scenery, because edges that should remain continuous—walls, roads, character models, trees—are suddenly offset.
Fast hardware can still tear
It is tempting to assume tearing is only what happens when a PC cannot keep up. In fact, an extremely fast GPU can create it just as readily. If a graphics card produces frames much faster than a fixed-refresh monitor can show them, it may submit a new frame mid-refresh. A 240Hz display, for example, cannot physically display more than 240 whole refreshes per second merely because the game is rendering above that figure.
Related coverage includes How to Fix Screen Tearing on PC and Console.
At the opposite end, a demanding scene can push GPU output very low. Frame-time variation is part of why the issue can feel inconsistent: a game may seem fine in a quieter area, then exhibit distracting artifacts when the workload changes. The basic cause remains the same—the GPU’s delivery of frames is not coordinated with the display’s refresh timing.
V-Sync: the original traffic light
V-Sync, short for vertical synchronization, is the long-standing software approach to preventing the GPU from handing a new image to the display at the wrong moment. It makes the graphics hardware wait until the monitor is ready for another frame rather than submitting completed frames without regard to the refresh cycle.
In simple terms, V-Sync is a traffic light. It reduces the chance of a mid-refresh handoff and therefore prevents the screen from combining parts of two different frames. For a fixed-refresh display, that is a direct solution to tearing.
The cost is that waiting introduces its own compromises. If a completed frame has to sit until the next permitted moment, player input can take longer to appear onscreen. This is called input lag: the delay between an input and its visible result. It matters most in fast, reactive play, where the appeal of a high frame rate is not purely cosmetic.
There is another consequence when performance dips. If the GPU does not finish a frame in time for the next refresh, the monitor can repeat a frame. That repetition can appear as stutter, uneven motion caused by an irregular sequence of displayed frames. V-Sync therefore removes one visual problem while potentially exchanging it for lag or judder when the frame rate cannot remain consistent.
That does not make V-Sync obsolete. It just means it is best understood as one piece of a broader display-synchronization setup, rather than a universal button to press without considering the rest of the system. For a deeper look at that balance, see what V-Sync does to FPS, screen tearing and input lag on a gaming PC.
Variable refresh rate changes the monitor’s schedule
Variable refresh rate, or VRR, takes a more flexible approach. Rather than forcing GPU output to fit the monitor’s unchanging cadence, VRR allows the monitor to adjust its refresh timing to the rate at which the GPU is completing frames. When the frame is ready, the display can refresh for that frame.
This substantially reduces the conditions that create tearing while also avoiding much of the stutter associated with a fixed timing schedule. It is useful because game performance is rarely perfectly flat. A game may render one frame quickly and the next more slowly; VRR lets the display follow those shifts within its supported operating range.
The major PC-gaming names are NVIDIA G-Sync and AMD FreeSync. Traditional G-Sync implementations used a dedicated hardware module in officially supported displays to coordinate the monitor and GPU. Newer monitors branded G-Sync Compatible can provide the relevant functionality without that dedicated module. NVIDIA’s next G-Sync generation is also intended to address motion blur with a feature named Pulsar.
FreeSync pursues the same anti-tearing goal using the VESA Adaptive-Sync protocol rather than a dedicated monitor module. From a player’s perspective, the important shared concept is VRR: the display is no longer rigidly refreshing at one rate regardless of the frames it receives.
VRR has a ceiling, not superpowers
Variable refresh rate is not a way to turn a 144Hz monitor into a 300Hz monitor. It works within the display’s native VRR window. Once the GPU’s frame rate rises beyond the monitor’s maximum refresh capability, the monitor cannot simply accelerate forever. Above that ceiling, the conditions for tearing return.
This is the point that can surprise players who have bought a high-refresh VRR screen and still occasionally see a horizontal split. The display may be properly synchronized for most of a game, but a lightweight menu, older title, or suddenly easy-to-render scene can push FPS above the refresh-rate limit. The GPU has then run past the range in which VRR can keep the pairing coordinated.
Likewise, a high refresh rate alone does not mean a system is synchronized. Faster refresh cycles can make artifacts less conspicuous to some eyes, but they do not change the underlying rule: a GPU and a fixed display schedule can still disagree about which complete frame should be shown at a particular moment.
A practical anti-tearing configuration
For a PC with a compatible GPU and monitor, the source-supported approach is to pair VRR with V-Sync and set a frame cap just below the monitor’s top refresh rate. Each component has a distinct job:
- G-Sync or FreeSync/Adaptive-Sync lets the monitor match the GPU’s changing frame output while the frame rate is in the display’s VRR range.
- V-Sync provides the guardrail at the upper edge, keeping the GPU from exceeding the display’s capabilities and escaping that VRR window.
- A frame-rate cap placed slightly below the maximum refresh rate gives the system room to stay inside the range rather than repeatedly colliding with its ceiling.
The recommended place to enable V-Sync in this arrangement is the computer’s global NVIDIA or AMD graphics settings, rather than a game’s own V-Sync setting. Then set the game’s frame limit just under the display maximum. On a 240Hz monitor, the provided example is about 235 fps. The exact purpose is not to chase an arbitrary number; it is to prevent brief spikes above the refresh-rate ceiling while retaining the benefits of VRR.
That combination also has a practical stability benefit. A cap prevents the GPU from constantly pushing for frames the monitor cannot present, which can make output steadier in addition to removing the most obvious tears. Players should not expect every game to land on a perfectly fixed number of frames—game workloads vary—but the display pipeline has a clearer set of boundaries within which to operate.
What to check before blaming the game
When tearing appears, separate the observations from the diagnosis. A horizontal split that moves or appears during camera motion points toward synchronization. A generally slow or choppy game may involve performance limitations too, but that is not automatically the same issue. Tearing specifically describes the mixed-frame image created during display scanning.
- Identify the monitor’s maximum refresh rate and whether it supports VRR.
- Confirm that the appropriate VRR option—G-Sync, FreeSync, or Adaptive-Sync as applicable—is enabled through the graphics setup.
- Enable V-Sync through the global NVIDIA or AMD graphics settings.
- Set the game’s FPS cap slightly beneath the display’s maximum refresh rate. For a 240Hz screen, around 235 fps is the provided reference point.
- Observe whether the artifact disappears during the movement that made it most visible.
The central lesson is refresh-rate literacy, not superstition. A monitor’s Hz rating describes its refresh capability; FPS describes the GPU’s production rate. Neither figure is meaningful in isolation if their timing is unmanaged. VRR lets the screen follow changing performance, while V-Sync and a modestly lower cap stop the GPU from sprinting beyond the display’s finish line.
Screen tearing can look dramatic precisely because it literally shows two different moments of the game at once. Fortunately, it is a known problem with established tools. A correctly configured VRR display, paired with V-Sync and a cap below the monitor maximum, turns the horizontal jigsaw back into the single, continuous image the game meant to show.
