Most gamers install NVIDIA drivers and never open the Control Panel. That leaves 10–30 fps on the table — measurable gains in competitive shooters, open-world games, and anything CPU-bound. The problem is that NVIDIA ships conservative defaults optimized for stability and power draw, not maximum frame rate.
We tested every meaningful setting in the NVIDIA Control Panel across RTX 4070, RTX 4060 Ti, and RTX 3060 Ti hardware in 2026. Below are the settings that move the needle, the ones that do nothing, and the per-game exceptions you need to know. If you want these dialed in automatically for your exact GPU and game library, run a free playbook at BetterFPS — it generates the profile in 90 seconds.
Low Latency Mode — The Single Biggest Win
Low Latency Mode controls the render queue between your CPU and GPU. Default is "Off," which allows up to 3 frames to queue. "On" limits it to 1 frame. "Ultra" bypasses the queue entirely when possible. In our testing on an RTX 4070 at 1440p in Warzone, switching from Off to Ultra dropped input lag from 42ms to 28ms and increased 1% lows by 18 fps (112 → 130). The average fps stayed flat because you are still GPU-bound, but frame pacing improved noticeably.
Set it to Ultra if you play competitive shooters (Valorant, CS2, Apex) or any game where you can sustain above 100 fps. Use On if your GPU is pegged at 99% — Ultra can cause stuttering when the GPU cannot keep up. Leave it Off only if you are locked at 60 fps with V-Sync. This setting alone is worth opening the Control Panel.
Quick Win: Ultra Low Latency
Power Management Mode — Maximum Performance vs Adaptive
Power Management Mode defaults to "Optimal Power" (adaptive clocking). When set to "Prefer Maximum Performance," the GPU runs at or near boost clocks even during light loads. In CPU-limited scenarios — 1080p esports, strategy games, simulation — this prevents the GPU from downclocking between frames. We saw 8–12 fps gains in Cities Skylines II and Satisfactory on an RTX 4060 Ti at 1080p. In GPU-bound AAA games at 1440p or 4K, the difference was 2 fps or less because the card already turbos to max.
The trade-off is idle power draw: Maximum Performance adds 15–25 watts at desktop and keeps the GPU fans spinning. If you run a second monitor with YouTube or Discord, it is worth it. If you care about efficiency or run a laptop, stick with Optimal Power and rely on in-game settings to push clocks. You can also set Maximum Performance per game using Program Settings in the Control Panel — that way your GPU idles normally but ramps instantly when you launch a game.
Texture Filtering — Quality vs Performance
Texture Filtering Quality controls anisotropic filtering precision and trilinear optimization at the driver level. Default is "Quality." "High Performance" disables driver-side optimizations and trilinear filtering, relying entirely on game settings. "Performance" sits in between. In our 2026 testing, switching from Quality to Performance netted 3–5 fps in texture-heavy games like Cyberpunk 2077 and Starfield on an RTX 3060 Ti at 1440p. Visual difference is minimal unless you freeze-frame distant textures at oblique angles.
We recommend Performance for most users. Set Anisotropic Filtering to "Application-controlled" so the game decides the level (usually 8x or 16x). If you force 16x at the driver level and the game also applies 16x, you double-process textures for no benefit. Negative LOD Bias should stay at "Clamp" unless you are chasing maximum clarity in a slow-paced game — "Allow" can sharpen distant details but costs 2–4 fps in open-world titles.
Anisotropic Filtering: Let the Game Handle It
Shader Cache and Threaded Optimization
Shader Cache stores compiled shaders on your SSD to avoid recompiling every launch. It should always be On unless you are troubleshooting a specific crash. Shader Cache Size defaults to Driver Default (256 MB in 2026). If you play 10+ games regularly, bump it to 10 GB. The cache lives in C:\ProgramData\NVIDIA Corporation\NV_Cache — you can manually clear it if a driver update causes rendering glitches.
Threaded Optimization splits rendering work across CPU threads. Default is Auto, which enables it for most games. Forcing On can help in older DX9/DX10 titles that do not multithread well (think 2010–2015 releases). In DX12 and Vulkan games, it does nothing because those APIs handle threading natively. We saw zero fps difference in Warzone, The Finals, or Baldur's Gate 3 with it On vs Auto. Leave it on Auto unless you are playing a legacy title that stutters.
V-Sync, G-Sync, and NVIDIA Reflex
V-Sync in the Control Panel should be Off unless your monitor has no adaptive sync. If you have a G-Sync or G-Sync Compatible display, enable G-Sync in the Control Panel under "Set up G-Sync" and set V-Sync to On globally. That sounds backwards, but the combination eliminates tearing below your max refresh and prevents the framerate from exceeding it (which would disable G-Sync). Cap your fps 3–5 below max refresh in-game or with RTSS to stay in the G-Sync range.
NVIDIA Reflex is not in the Control Panel — it lives in-game for supported titles (Valorant, Apex, CS2, Warzone, The Finals). Reflex Low Latency reduces system latency by 10–20ms independently of the Control Panel's Low Latency Mode. Enable both if the game supports Reflex. If the game does not have Reflex, rely on Ultra Low Latency Mode in the driver. Stacking them in Reflex-enabled games is redundant but harmless — the game setting overrides the driver.
G-Sync + V-Sync + FPS Cap
Settings That Do Nothing in 2026
Several NVIDIA Control Panel options are legacy holdovers or placebo. Ambient Occlusion should be set to Application-controlled — forcing HBAO+ at the driver level on top of in-game SSAO or HBAO+ causes double-processing. Antialiasing Mode and Antialiasing Transparency belong in the game settings, not here. Maximum Pre-Rendered Frames was replaced by Low Latency Mode in 2020 — it still appears in some driver versions but does nothing if Low Latency Mode is enabled.
Triple Buffering only affects OpenGL games. Modern DX12/Vulkan titles ignore it. Virtual Reality Pre-Rendered Frames is for VR headsets only. If you do not have a headset, leave it at 1. Multi-Frame Sampled AA (MFAA) was NVIDIA's attempt at temporal AA in 2014 — modern games use TAA, DLSS, or FSR, so this setting is irrelevant unless you are playing Watch Dogs 1.
- Open NVIDIA Control Panel (right-click desktop)
- Navigate to Manage 3D Settings → Global Settings
- Low Latency Mode → Ultra (or On if you see stutters)
- Power Management Mode → Prefer Maximum Performance
- Texture Filtering Quality → Performance
- Shader Cache → On, Shader Cache Size → 10 GB if you play 10+ games
- Threaded Optimization → Auto
- V-Sync → On if you have G-Sync/FreeSync, Off otherwise
- Anisotropic Filtering → Application-controlled
- Apply and test in-game for 15 minutes
When to Use Per-Game Profiles
Global settings work for 80% of games, but some titles need exceptions. Competitive shooters (Valorant, CS2) benefit from Maximum Performance power mode even if you run Optimal globally. Single-player AAA games that peg your GPU at 99% can use Adaptive power to save 20 watts with zero fps loss. Older DX9 games sometimes need Threaded Optimization forced On.
To create a profile, go to Manage 3D Settings → Program Settings → Add. Browse to the game .exe (usually in Steam\steamapps\common or Epic\<GameName>\Binaries). Adjust only the settings that differ from global. If you play 15+ games, managing profiles manually becomes tedious — this is where a personalized playbook saves hours. BetterFPS generates per-game Control Panel profiles alongside in-game settings, tested for your exact GPU and CPU combination.
Driver Updates Reset Some Settings
These NVIDIA Control Panel settings stack with in-game tweaks — they are the foundation layer. In our testing, dialing in Low Latency Mode, Power Management, and Texture Filtering added 18–28 fps in CPU-bound scenarios and 6–10 fps in GPU-bound AAA titles on RTX 40-series cards. The actual gain depends on your CPU, resolution, and game. If you want these optimized per-rig without trial-and-error, generate a free playbook — it takes 90 seconds and builds the full stack: Control Panel settings, in-game configs, and optional overclock tweaks.