A high refresh rate and VRR get sold as the same upgrade, but they solve different problems. A high-refresh display increases how often the screen can update. Variable Refresh Rate lets the screen’s update timing actually match what your GPU is delivering, instead of updating on a fixed schedule regardless of what’s ready to show. You can own a 240Hz monitor with VRR turned off and still see tearing; you can own a modest 75Hz monitor with VRR working correctly and see none. They’re related, but one doesn’t substitute for the other.

Refresh rate vs. FPS vs. VRR

Three things are happening at once, and it’s worth separating them before anything else makes sense.

Refresh rate is how often your display is physically capable of drawing a new image. Our refresh rate explainer covers what that number actually changes as it climbs. Frame rate (FPS) is how often your GPU actually finishes rendering a new frame, and it moves constantly based on what’s happening on screen: a quiet hallway and a crowded firefight can produce very different numbers in the same game. On a fixed-refresh display, the screen updates on its own rigid schedule no matter what the GPU has ready. A variable refresh rate display can instead adjust its update timing to line up with each frame as the GPU delivers it, within a supported range.

The mismatch between a fixed schedule and a constantly-changing frame rate is exactly what causes the two visual problems VRR exists to address.

Why screen tearing happens

A display update happens on a timer. If a new frame from the GPU arrives partway through that timer’s cycle, a fixed-refresh display doesn’t wait. It draws part of the old frame and part of the new one in the same pass, producing a visible horizontal split, most obvious during fast horizontal motion. That’s screen tearing, a timing mismatch between when a frame is ready and when the display happens to be updating, not a defect in the rendering itself.

The traditional fix, V-Sync, makes the GPU hold each finished frame until the display’s next fixed update instead of showing it immediately. That stops tearing, but it can introduce its own added delay and stutter if the frame rate doesn’t line up cleanly with the fixed refresh rate. VRR takes a different approach entirely.

What VRR actually changes

Instead of holding the display to a fixed schedule, a Variable Refresh Rate display updates exactly when a new frame is ready, within its supported range. That principle is the same behind every VRR brand name, whether it’s NVIDIA’s G-SYNC, VESA’s Adaptive-Sync or AMD’s FreeSync. Because the display is no longer drawing a frame that arrives mid-update, tearing caused by that mismatch is eliminated within the supported range, and frame-rate changes tend to look and feel more coherent than they would on a fixed-refresh display forcing every frame into the same rigid timing.

VRR does not fix bad performance

This is the part marketing tends to skip, and it matters more than the feature itself: VRR changes when a finished frame gets displayed. It does nothing to how fast that frame gets finished in the first place.

VRR will not fix a CPU bottleneck, GPU performance that’s genuinely insufficient for the settings you’re running, shader-compilation stutter (the brief freeze many games show when a new visual effect appears for the first time), network latency in an online game, or poor frame pacing built into a game’s own engine. It also doesn’t universally reduce input lag. Synchronization technologies can affect latency, but the actual result depends on your specific frame rate, your display’s behavior, and how the game itself is configured, not a blanket rule that VRR always makes things more responsive. If a game feels bad because your hardware can’t sustain the frame rate you want, VRR makes that experience look and feel somewhat more coherent while you’re in it. It doesn’t raise your actual frame rate, and it isn’t a substitute for addressing the real bottleneck. Our guide to smooth PC gaming without chasing Ultra settings covers the settings side of that problem, and Monitor or GPU first covers the hardware side.

Why the VRR range matters

Every VRR display supports variable refresh only within a specific range. For example, a display might operate its VRR behavior somewhere between roughly 48Hz and its maximum refresh rate. That’s an illustrative example, not a universal number; the real range is set by the specific panel and its certification, not by the underlying standard, so always check the actual specification for the display in question rather than assuming a number.

Inside that range, VRR works as intended. Above the range, meaning a frame rate higher than the display’s maximum refresh rate, the display simply can’t show every frame the GPU produces. Behavior falls back to how the display and driver are configured for that case, commonly capping or otherwise limiting frames past the ceiling. Below the range is the more interesting problem: once frame rate drops under the display’s minimum supported refresh, the mismatch VRR was designed to prevent can start to reappear.

What LFC does

Low Framerate Compensation is a feature, documented as part of AMD’s FreeSync ecosystem, built specifically to handle that below-range case. When the frame rate falls under the display’s normal minimum, LFC keeps things within the usable range by displaying each finished frame multiple times, at a multiple of the actual frame rate, rather than by generating new frame content. That keeps the display’s effective refresh rate inside its supported window even when the GPU itself is producing frames too slowly to do that on its own.

LFC isn’t available on every VRR display, and where it is available, it isn’t a fix for the underlying low frame rate. It’s frame repetition, not frame generation, so it keeps the presentation smoother without doing anything about the performance problem that pushed the frame rate below the range in the first place.

Adaptive-Sync, FreeSync and G-SYNC

These labels aren’t really different technologies competing for the same job. They’re overlapping ways of describing and certifying the same underlying idea, and none of them is simply “the best one.”

VESA Adaptive-Sync is the underlying capability built into the DisplayPort specification itself, vendor-neutral and not tied to a specific GPU brand. Separately, VESA also runs an Adaptive-Sync compliance test and logo program; a display can support the underlying DisplayPort capability without necessarily carrying that specific certification logo, so the two aren’t quite the same thing.

AMD FreeSync is AMD’s branded implementation and certification built on that same open foundation, with three officially defined tiers: standard FreeSync, FreeSync Premium (which raises the minimum refresh-rate and resolution requirements over the baseline tier), and FreeSync Premium Pro (which adds HDR-specific requirements on top of Premium). The tier printed on the box tells you which of those performance requirements a specific display actually meets. It isn’t just a marketing label. Whether LFC specifically is present is worth confirming for the exact model rather than assumed from the tier name alone, since AMD’s own current requirements for it aren’t presented identically everywhere.

NVIDIA G-SYNC historically meant a monitor built around a dedicated NVIDIA hardware module, matching refresh rate to GPU frame rate to eliminate tearing and reduce stutter. NVIDIA’s current G-SYNC lineup has continued to evolve beyond that original approach, though, so check what a specific display actually includes rather than assuming one fixed architecture. G-SYNC Compatible is a separate, more common certification: NVIDIA validating that a standard Adaptive-Sync display, including displays also sold as FreeSync, works properly with NVIDIA GPUs. NVIDIA itself positions it as the entry tier, validated for a “good, basic” VRR experience, while G-SYNC and G-SYNC Ultimate displays use an NVIDIA G-SYNC processor. For many players a G-SYNC Compatible display is all they need, but check the specific certification, not the brand name alone. Some FreeSync displays are also G-SYNC Compatible, but that isn’t automatic or universal. “FreeSync means AMD-only” and “every FreeSync display is G-SYNC Compatible” are both assumptions worth verifying against the specific display.

VRR support also depends on the cable/port standard involved: DisplayPort has supported Adaptive-Sync since it was added to the spec, and HDMI added its own VRR feature starting with HDMI 2.1, with the interface standard continuing to evolve since. Not every port on a given device supports it at every resolution and refresh rate the display is otherwise capable of, so checking the actual port in use is worth doing before assuming VRR will work end to end.

VRR and V-Sync are not the same thing

VRR and V-Sync solve a related problem in different ways, and it’s worth being clear that VRR isn’t simply “V-Sync but better.” V-Sync locks frame delivery to the display’s fixed schedule; VRR lets the display’s schedule adapt to frame delivery instead. That’s why behavior above the VRR range specifically matters. Once frame rate exceeds what the display can variably refresh at, some setups combine VRR with a frame-rate cap or V-Sync specifically for that above-range case, rather than relying on VRR alone to handle every situation. There isn’t one universal combination that’s correct for every game or every display; it depends on your frame rate relative to your specific display’s range.

What to check before buying a monitor

  • What is the display’s actual supported VRR range, not just “has VRR,” but the specific minimum and maximum.
  • Does it support LFC, and is that documented for the specific model rather than assumed from the brand?
  • Which certification tier applies (plain Adaptive-Sync, a specific FreeSync tier, native G-SYNC, or G-SYNC Compatible), and what does that tier specifically guarantee?
  • Which port does VRR actually work through on this display, and does your GPU support that same standard over that same port?
  • Does your GPU generation and driver version meet the stated requirements for the certification in question?

Three real-world scenarios

A. A high-refresh monitor with frame rate fluctuating inside its VRR range. This is the situation VRR is built for. The display adapts smoothly as frame rate moves around within its supported window, and tearing and sync-related judder are minimized without any further tuning needed.

B. A high-refresh monitor paired with a GPU that consistently sits below the performance the display is capable of. VRR still helps presentation stay coherent, but it isn’t solving the actual limitation. The GPU is the bottleneck here, not the display, and no sync technology changes that.

C. A very high frame rate competitive game where frame rate frequently exceeds the display’s VRR ceiling. Here, the priority often shifts toward frame-rate capping or other configuration choices for the above-range case specifically, rather than assuming VRR alone is handling everything at every frame rate the system can produce.

Final decision checklist

  1. Do I understand my display’s actual VRR range, not just whether it has the feature?
  2. Is my frame rate typically inside that range, or does it regularly fall below or above it?
  3. If it falls below the range, does this display support LFC?
  4. Am I checking the certification tier and port requirements, rather than assuming one brand name guarantees a specific outcome?
  5. Am I treating VRR as a smoothness feature, not a fix for a GPU, CPU, or engine problem it was never designed to solve?

VRR makes a variable frame rate look and feel more coherent. It doesn’t make your frame rate higher, and it doesn’t replace the hardware or settings work that actually determines how fast your GPU delivers frames in the first place.

Sources

Facts in this guide were checked against these pages in October 2026: