Does G-Sync or FreeSync Add Input Lag to Your Monitor?
The Short Answer
No — G-Sync and FreeSync do not meaningfully add input lag. Variable refresh rate (VRR) technology itself adds negligible lag compared to running your monitor at a fixed refresh rate. This is one of the most persistent myths in PC gaming settings, and it sends players disabling a useful feature for no benefit.
The real lag trap is something else entirely: classic V-Sync paired with an uncapped frame rate and a full render queue. That combination is what actually delays your inputs. The good news is that you can have smooth, tear-free gaming and low lag at the same time, by combining the technologies correctly. The exact recipe is further down this page: VRR on, V-Sync on in your GPU driver, V-Sync off in the game, and your frame rate capped about 3 FPS below your monitor’s refresh rate. Here is why that combination works.
What G-Sync and FreeSync Actually Do
On a normal fixed-refresh monitor, the screen redraws on a strict schedule — 144 times per second on a 144Hz panel, whether your game is ready or not. Your game, meanwhile, produces frames at its own uneven pace. When those two rhythms fall out of step, you get screen tearing: the monitor shows parts of two different frames at once, split by a visible horizontal line.
G-Sync (NVIDIA) and FreeSync (AMD) solve this by flipping the relationship. Instead of the monitor refreshing on a fixed schedule, the monitor waits and refreshes when the game delivers a new frame, within a supported range. The display’s refresh rate varies to match the game — that is why it is called variable refresh rate.
Notice what VRR does not do: it does not hold frames in a queue, and it does not wait for anything extra before showing you a frame. The frame is displayed when it is ready. That is the mechanical reason its lag cost is negligible — there is no extra waiting built into how it works. What it removes is tearing, plus the stutter that happens when frame times are uneven.
Where Input Lag Really Comes From
If VRR is not the problem, what is? The classic culprit is traditional V-Sync used the wrong way.
V-Sync synchronizes frames to the monitor’s refresh schedule. When your frame rate is uncapped and the render queue is allowed to fill up, frames wait in line before being displayed. Your mouse input goes into a frame, that frame waits behind others in the queue, and only then reaches your screen. That waiting is input lag you can genuinely feel — the game responds a beat after you act.
This is why older advice said “always turn V-Sync off for competitive games.” That advice was about the queue, not about synchronization itself. The modern low-lag approach does not abandon synchronization — it controls the queue, by combining driver-level V-Sync with VRR and, most importantly, a frame rate cap that keeps the queue from ever filling. Understanding frame delivery also explains why your frame rate matters as much as your panel, as covered in is the jump from 144hz to 240hz actually noticeable.
The Low-Lag Setup Recipe
Follow these steps exactly. Each one has a job, and the combination is what produces tear-free, low-lag output.
- Turn on G-Sync or FreeSync in your GPU control panel (and make sure it is enabled on the monitor itself, if your monitor has a setting for it). This lets the display match your game’s frame rate and removes tearing inside the VRR range.
- Turn V-Sync ON in your GPU driver settings — NVIDIA Control Panel or AMD Software — not in the game. At the driver level, V-Sync acts as a safety net that handles the moments your frame rate reaches the top of the range, without building the laggy queue described above.
- Turn V-Sync OFF in the game’s own settings. In-game V-Sync implementations are the ones typically tied to the full render queue behavior you are trying to avoid. The driver handles this job instead.
- Cap your frame rate about 3 FPS below your monitor’s maximum refresh rate — for example, around 141 FPS on a 144Hz monitor, or around 237 FPS on a 240Hz monitor. Use the in-game frame limiter if it has one, or your GPU driver’s limiter. This cap is the key step: it keeps you inside the VRR range at all times and stops the render queue from filling, which is what keeps lag low.
- Play and check. Inside the VRR range, you should see no tearing and feel no added delay. If your frame rate regularly falls far below the cap, lower your graphics settings until it holds — consistent frame delivery matters more than maximum settings, as explained in best settings for high fps in competitive games.
Here is the same recipe as a quick reference:
| Setting | Where | What to Choose |
|---|---|---|
| G-Sync / FreeSync (VRR) | GPU control panel + monitor | On |
| V-Sync | GPU driver settings | On |
| V-Sync | In-game settings | Off |
| Frame rate cap | In-game limiter or GPU driver | ~3 FPS below max refresh rate |
The One Way Tearing Comes Back
This setup has one condition: your frame rate must stay inside the monitor’s VRR range. VRR only works within its supported range, topping out at your monitor’s maximum refresh rate.
If your FPS climbs above that range — say your game surges past 144 FPS on a 144Hz monitor with no cap in place — the display can no longer sync to the game, and tearing returns. This is exactly why step 4, the frame cap, is not optional decoration. The cap keeps your frame rate a few frames under the ceiling at all times, so you never leave the range where VRR is in control. Brief dips below your cap are fine; VRR handles varying frame rates by design. It is the top end you must guard.
If you are still feeling delay after this setup, the cause is almost certainly elsewhere — an overloaded render queue from an uncapped game, a low frame rate, or a setting in another guide worth auditing, like how to reduce input lag in games.
FAQ
Should I turn off G-Sync or FreeSync for competitive games?
No. Variable refresh itself adds negligible lag versus fixed refresh, so disabling it buys you nothing and brings back tearing. Use the recipe above — VRR on, driver V-Sync on, in-game V-Sync off, FPS capped just below your refresh rate.
Why turn V-Sync on in the driver but off in the game?
Driver-level V-Sync acts as a safety net at the top of the VRR range without the laggy behavior of a full render queue. In-game V-Sync is the implementation typically paired with that queue, which is where real input lag comes from. The frame cap then keeps the queue from filling at all.
What frame rate should I cap at on a 144Hz monitor?
About 3 FPS below the maximum — roughly 141 FPS. The same rule applies at other refresh rates: around 237 FPS on a 240Hz panel. The small gap keeps you safely inside the VRR range at all times.
Conclusion
G-Sync and FreeSync are not the lag problem — variable refresh adds negligible lag compared to fixed refresh, and disabling them only costs you smooth, tear-free motion. The real trap is V-Sync with an uncapped frame rate and a full render queue. Avoid it with the recipe: VRR on, V-Sync on in the driver, V-Sync off in the game, and a cap about 3 FPS below your refresh rate. Set it once, and you get both low lag and no tearing.
