NVIDIA Control Panel settings for games: what each one does

You open the NVIDIA settings to change one thing and find a long list, many named as if they should make every game faster. Several were written for particular situations, and NVIDIA's own help text says which. This page quotes what NVIDIA says the ones gamers touch actually do, and shows how to decide game by game instead of copying a list.

Control Panel or NVIDIA app, as of October 2026

In its May 2026 driver announcement (610.47), NVIDIA retired the classic Control Panel for Game Ready and Studio drivers. An existing install stays unless you do a clean driver installation, and NVIDIA still offers it in the Microsoft Store, "but we won't be adding features, fixes, or other changes".

The settings moved to the NVIDIA app:

Graphics > Program Settings in the app replaces 3D Settings > Manage 3D Settings in the Control Panel.
Every other setting, display options and G-SYNC included, is in the app's System tab.

The descriptions below quote NVIDIA's help for the Manage 3D Settings page, dated 2005-2023.

Global settings or one game

Both tools split settings in two. Per NVIDIA's help, the global tab is where you "create your own custom settings to use when running 3D applications", and the Program Settings tab holds "a set of 3D settings to use when running a particular game or application".

A global change reaches every game and 3D application on the PC, including the ones it does not suit. A program entry touches one executable and is easy to undo. Change things per game, one at a time.

If w0a has written its NVIDIA profile, cs2.exe already has a program entry with the G-Sync/FreeSync setting at fixed refresh, and V-Sync off unless V-Sync is on in CS2's own settings. To use variable refresh in CS2, change that entry, or use the NVIDIA profile card on the Fix page: it deletes the settings w0a wrote, so the driver defaults apply again, and leaves settings you made yourself alone.

Low Latency Mode

NVIDIA's help: Low Latency Mode "reduces latency by limiting the number of frames the CPU can prepare before the frames are processed by the GPU".

Off (default) "prioritizes render throughput by allowing games to queue frames".
On limits "queued frames to one", the same as the old "Max_Prerendered_Frames = 1".
Ultra is "fully minimizing queued frames": each frame is submitted "just in time for the GPU to pick it up".

A queue builds only when the processor gets ahead of the graphics card, so the setting has something to remove only when the GPU is the slower part. NVIDIA's launch article says the modes "have the most impact when your game is GPU bound, and framerates are between 60 and 100 FPS". If your game waits on the processor instead, GPU not at 100% shows how to tell.

At launch it covered DirectX 9 and 11 ("in DX12 and Vulkan titles, the game decides when to queue the frame"). Driver 551.23, in January 2024, added support for "Ultra Low Latency Mode with DirectX 12 titles", and Blur Busters' settings guide says the setting is not supported in Vulkan.

If the game has NVIDIA Reflex, use that instead. Reflex is built into the game and, per NVIDIA's Reflex article, works by "eliminating the GPU render queue and reducing CPU back pressure"; the driver mode can shorten the queue but "can not remove the increased back-pressure". NVIDIA recommends Reflex over Ultra, and if both are on, Reflex "will take higher priority automatically".

Max Frame Rate

Max Frame Rate sets "the maximum 3D game or application frame rate that the GPU will render", from 20 to 1000 fps. NVIDIA names two uses, "extending battery life or for reducing system latency in certain scenarios", without saying which scenarios. Its Reflex article explains one: latency is "typically higher in GPU-bound cases because of the render queue", and a cap the GPU can always meet keeps the game from being GPU-bound. Should you cap your FPS? covers where to set the number.

Background Application Max Frame Rate limits a game left running while you switch to something else, to "reduce power consumption or fan noise".

Vertical sync and G-SYNC

Vertical sync has these values (names as the current driver shows them, descriptions from the help):

Use the 3D application setting: the game's own V-Sync option decides.
Off, "useful if performance is more important than image quality".
On, "useful for eliminating tearing".
Fast, which "improves latency without introducing tearing", on Pascal and later GPUs in single-GPU systems.
Adaptive and Adaptive (half refresh rate), only when Monitor Technology is set to ULMB or Fixed Refresh.

Monitor Technology picks G-SYNC, ULMB or Fixed Refresh, which the help describes as "the set refresh rate of the display without any variability or adaptation". G-SYNC itself is switched on under Display > Set up G-SYNC in the Control Panel and in the System tab of the app.

Blur Busters tested G-SYNC input lag on a display with a G-SYNC module and recommends G-SYNC on, V-Sync on in the NVIDIA settings for the game, V-Sync off in the game, and a frame rate limit at least 3 below the refresh rate, such as 141 at 144 Hz. They note that G-SYNC Compatible displays "may vary". G-SYNC, FreeSync and V-Sync explains how the pieces fit.

Power management mode

NVIDIA driver-controlled lets the driver decide.
Adaptive lets the driver "reduce GPU performance depending on the needs of the 3D application".
Prefer maximum performance: "Use the GPU only at maximum performance when running most 3D applications."
Prefer consistent performance is "often used to provide reproducible results during software development and tuning".

NVIDIA's Reflex article gives the case for maximum performance: higher clocks "can reduce latency in CPU-bound instances at a tradeoff of higher power consumption". That cost applies wherever the setting does, so a game's program entry is the place for it, not the global tab. As of October 2026, the release notes for driver 617.42 list an open issue: "'Prefer Maximum Performance' Power Management Mode may not be applied correctly."

Texture filtering and antialiasing

Texture filtering - Quality runs from High performance through Performance and Quality, the GeForce default, to High quality, which NVIDIA says "is not necessary for average users who run game applications". Anisotropic filtering "improves image quality at the expense of some performance".

For Antialiasing - Mode, NVIDIA calls Application-controlled "the preferred setting to use for applications that have built-in antialiasing controls". Override any application setting is for a game without its own antialiasing control.

Shader Cache Size

The cache keeps the shaders the driver compiled for your GPU, so later runs of the same game skip that work. The help offers Disabled, Unlimited and sizes from 128 MB to 100 GB, and its guideline is about size: "large enough to cover the set of games you normally use, but not too large that it exceeds your available hard drive disk space". A limit "too small may cause the driver to remove shaders you still make use of and cause game play stutters".

Installing a new driver deletes the cache anyway, and we found no measurement showing that Unlimited beats a large fixed size. Since NVIDIA app 11.0.7, Automatic Shader Compilation (beta) "rebuilds DirectX 12 shaders while your system is idle". Deleting the cache is not a stutter fix; shader compilation stutter explains why.

Threaded optimization

All the help says is that Threaded optimization "allows applications to take advantage of multiple CPUs". NVIDIA gives no guidance on when to change it and we found no measurement either way, so this page does not tell you to change it.

How to decide on your machine

Make the change in the game's program entry, not globally.
Change one setting, play the same scene before and after, and compare frame times and 1% lows rather than the average; reading the benchmark shows how.
Keep it only if the difference shows up in the measurement, and note what you changed.

What does not help: copying a list of global values from a video, Low Latency Mode in a game that has Reflex (Reflex takes priority anyway), and clearing the shader cache to cure stutter.

Did this page help?

What was missing, or what did not work? We read every one of these.

If this page did not solve it, write to us — say which article you read, and we will fix the article.