G-SYNC 101: Optimal G-SYNC Settings & Conclusion

Optimal G-SYNC Settings*

*Settings tested with a single G-SYNC display (w/hardware module) on a single desktop GPU system; specific DSR, SLI, and multi-monitor behaviors, as well as G-SYNC laptop display and “G-SYNC Compatible” display implementation, may vary.

Nvidia Control Panel Settings:

  • Set up G-SYNC > Enable G-SYNC, G-SYNC Compatible > Enable for full screen mode.
  • Manage 3D settings > Vertical sync > On (Why?).

In-game Settings:

  • Use “Fullscreen” or “Exclusive Fullscreen” mode (some games do not offer this option, or label borderless windowed as fullscreen).
  • Disable all available “Vertical Sync,” “V-SYNC,” “Double Buffer,” and “Triple Buffer” options.
  • If an in-game or config file FPS limiter is available, and framerate exceeds refresh rate:
    Set (a minimum of) 3 FPS limit below display’s maximum refresh rate (57 FPS @60Hz, 97 FPS @100Hz, 117 FPS @120Hz, 141 FPS @144Hz, etc).

RTSS Settings:

  • If an in-game or config file FPS limiter is not available and framerate exceeds refresh rate:
    Set (a minimum of) 3 FPS limit below display’s maximum refresh rate (see G-SYNC 101: External FPS Limiters HOWTO).


Nvidia “Max Frame Rate” Settings*:

*Introduced in Nvidia driver version 441.87

  • If an in-game or config file FPS limiter is not available and framerate exceeds refresh rate:
    Set “Max Frame Rate” to “On,” and adjust slider to (a minimum of) 3 FPS limit below display’s maximum refresh rate.

Low Latency Mode* Settings:

*This setting is not currently supported in DX12 or Vulkan.

  • If an in-game or config file FPS limiter is not available, RTSS is prohibited from running, a manual framerate limit is not required, and framerate exceeds refresh rate:
    Set “Low Latency Mode” to “Ultra” in the Nvidia Control Panel. When combined with G-SYNC + V-SYNC, this setting will automatically limit the framerate (in supported games) to ~59 FPS @60Hz, ~97 FPS @100Hz, ~116 FPS @120Hz, ~138 FPS @144Hz, ~224 FPS @240Hz, etc.
  • If an in-game or config file FPS limiter, and/or RTSS FPS limiter is available, or Nvidia’s “Max Frame Rate” limiter is in use, and framerate does not always reach or exceed refresh rate:
    Set “Low Latency Mode” to “On.” Unlike “Ultra,” this will not automatically limit the framerate, but like “Ultra,” “On” (in supported games that do not already have an internal pre-rendered frames queue of “1”) will reduce the pre-rendered frames queue in GPU-bound situations where the framerate falls below the set (in-game, RTSS, or Nvidia “Max Frame Rate”) FPS limit.

Windows “Power Options” Settings:

Windows-managed core parking can put CPU cores to sleep too often, which may increase frametime variances and spikes. For a quick fix, use the “High performance” power plan, which disables OS-managed core parking and CPU frequency scaling. If a “Balanced” power plan is needed for a system implementing adaptive core frequency and voltage settings, then a free program called ParkControl by Bitsum can be used to disable core parking, while leaving all other power saving and scaling settings intact.

Blur Buster's G-SYNC 101: Input Lag & Optimal Settings

Mouse Settings:

If available, set the mouse’s polling rate to 1000Hz, which is the setting recommended by Nvidia for high refresh rate G-SYNC, and will decrease the mouse-induced input lag and microstutter experienced with the lower 500Hz and 125Hz settings at higher refresh rates.


Refer to The Blur Busters Mouse Guide for complete information.

Nvidia Control Panel V-SYNC vs. In-game V-SYNC

While NVCP V-SYNC has no input lag reduction over in-game V-SYNC, and when used with G-SYNC + FPS limit, it will never engage, some in-game V-SYNC solutions may introduce their own frame buffer or frame pacing behaviors, enable triple buffer V-SYNC automatically (not optimal for the native double buffer of G-SYNC), or simply not function at all, and, thus, NVCP V-SYNC is the safest bet.

There are rare occasions, however, where V-SYNC will only function with the in-game option enabled, so if tearing or other anomalous behavior is observed with NVCP V-SYNC (or visa-versa), each solution should be tried until said behavior is resolved.

Maximum Pre-rendered Frames*: Depends

*As of Nvidia driver version 436.02, “Maximum pre-rendered frames” is now labeled “Low Latency Mode,” with “On” being equivalent to MPRF at “1.”

A somewhat contentious setting with very elusive consistent documentable effects, Nvidia Control Panel’s “Maximum pre-rendered frames” dictates how many frames the CPU can prepare before they are sent to the GPU. At best, setting it to the lowest available value of “1” can reduce input lag by 1 frame (and only in certain scenarios), at worst, depending on the power and configuration of the system, the CPU may not be able to keep up, and more frametime spikes will occur.

The effects of this setting are entirely dependent on the given system and game, and many games already have an equivalent internal value of “1” at default. As such, any input latency tests I could have attempted would have only applied to my system, and only to the test game, which is why I ultimately decided to forgo them. All that I can recommend is to try a value of “1” per game, and if the performance doesn’t appear to be impacted and frametime spikes do not increase in frequency, then either, one, the game already has an internal value of “1,” or, two, the setting has done its job and input lag has decreased; user experimentation is required.


Much like strobing methods such as LightBoost & ULMB permit “1000Hz-like” motion clarity at attainable framerates in the here and now, G-SYNC provides input response that rivals high framerate V-SYNC OFF, with no tearing, and at any framerate within its range.

As for its shortcomings, G-SYNC is only as effective as the system it runs on. If the road is the system, G-SYNC is the suspension; the bumpier the road, the less it can compensate. But if set up properly, and run on a capable system, G-SYNC is the best, most flexible syncing solution available on Nvidia hardware, with no peer (V-SYNC OFF among them) in the sheer consistency of its frame delivery.

Feel free to leave a comment below, resume the discussion in the Blur Busters Forums, or continue to the Closing FAQ for further clarifications.

1620 Comments For “G-SYNC 101”

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Sort by:   newest | oldest | most liked

Hello again Jorimt, hope you’re having a great day.

I have a question less related to gsync and more to do with render latency. I’ve noticed as I turn the resolution down, the render latency reduces even at the same fps. In fact I have found that @60fps capped the render latency is around 11.5ms at 1080p compared to 16-18ms latency when capped at 60fps 1440p. At 720p the render latency dropped even further.

As far as I understand, render latency is linked to input latency. Does this mean that for example with console games that are capped at 60fps @4k, the input latency is much higher than it could be if the game was instead rendered at 720p? Since the GPU is doing less work per frame?


Hi, this was exactly what I was looking for, but I still have one unanswered question in my mind.
I’m going to buy a 165hz G-sync monitor, and the game that I play runs around 200 fps. Will I necessarily get screen tear if I don’t cap at 162 ? and do you suggest capping the fps at 162, or playing it on higher graphic settings of the game to stay below the monitor’s refresh rate? like 150 fps or so. Since I play FPS games input lag really matters to me.


After reinstalling windows recently, my G-Sync behaviour has changed.

As far as I can remember, my usual set up was:
League of legends played in Windowed Borderless Mode.
v-sync: disabled – in-game
v-sync: enabled (set to “Fast”) – in NVCP
g-sync: enabled for both windowed and full-screen – in NVCP
preferred refresh rate: Highest available – in NVCP
power management: Prefer maximum performance – in NVCP
Monitor technology: G-SYNC – in NVCP
frame rate: uncapped – in game

With these settings, my frame rate was capped by the fast v-sync to 1 frame below my monitors max refresh rate 164 (down from 165).

However, after reinstalling windows and reapplying these same settings the frame rate is no longer capped to 1 below the monitors refresh rate. Instead I get FPS anywhere from 200-600 and I notice stutters and tearing.

Is there any way for me to get back my previous system behaviour?

PS I know the recommended way to set up a system is for full-screen g-sync but I prefer windowed borderless for the rapid alt tabbing, as I do that frequently.


I am looking to buy a 1440p 144hz monitor and from what I have read, I should set my FPS at 141 using nvcp, set vsync on in nvcp and off in game. However, many sources have told me to turn on null on and others have told me to completely turn it off. Should I put it on ultra, on or off? I play league of legends fyi and my cpu is usually around 16% usage and my gpu is around 30% uncapped 1080p. Sorry, I am new to th this subject .


I have a System with a Geforce 3080 and as display I use a LG c9 OLED TV with 120Hz and GSync.

In Nioh 2, which can easily perform over 120 fps with DLSS on 4k with that System if I limit the game to 117 fps with RTSS I get Micro Stutter when just looking around. If I disable the RTSS limiter and let the game limit the fps to 120 (in game there is only an option to lock at 30/60/120) the game is buttery smooth. Is there any way to get the game running smooth with a limit to 117 fps?