How to gain 20-30 FPS in Valorant and CS2 with the NVIDIA Control Panel: the settings that actually work, the Reflex trap, and the myths you should ignore.
I picked up around 20-30 FPS in Valorant and CS2 by tweaking the NVIDIA Control Panel. But half of what you'll read out there does absolutely nothing in these games, and nobody tells you that.
I'm running a 3060 Ti and mostly play Call of Duty, Valorant, CS2, and League of Legends. I've spent a lot of time fighting with the NVIDIA Control Panel chasing frames, and after testing everything on my own rig, the conclusion is uncomfortable: most of the "47 magic settings" that top Google searches are pure fluff in modern competitive games, because the game itself overrides the driver and stomps whatever you touch in the panel.
The real gains do exist. In my case it was around 20-30 FPS and, more noticeably, much more stable frametimes. But those gains come from four or five specific settings and one step that almost every guide skips. Not from blindly checking thirty boxes.
The Step Zero Everyone Skips: Clean Install
Before touching a single panel setting, I install drivers using the clean install option (CleanInstall / "Perform a clean installation" in the NVIDIA installer). This wipes your previous config and the leftovers from older versions instead of just layering on top.
Why does it matter so much? Because old drivers leave garbage behind. Corrupted profiles, settings you've been dragging along from three versions ago without knowing it, configurations that fight each other. I've seen stutter and FPS drops that no panel tweak would fix — drops that vanished with a clean install. If you want to go nuclear, there's DDU (Display Driver Uninstaller) in safe mode to leave your system graphics-wise like a fresh format, but for 90% of cases the clean install checkbox in the NVIDIA installer itself is enough.
This is the equivalent of checking your connection before putting your card in: a boring step nobody talks about that saves you hours chasing ghosts. Optimizing the panel on a dirty install is building on sand.
The Settings That ACTUALLY Give You FPS and Stability
All of this is in the classic NVIDIA Control Panel under "Manage 3D Settings." My baseline advice: make your serious tweaks in the "Program Settings" tab for each specific game, not in "Global Settings." That way you're not hammering the GPU all day on the desktop and you can fine-tune game by game.
Low Latency Mode. The one that actually matters for input lag. Off queues up to 3 frames and maximizes average FPS but adds latency. On queues 1 frame and is the recommended balance. Ultra forces the absolute minimum frames in queue but cuts some peak FPS. Ultra is only worth it if you're running well above your monitor's refresh rate in frames. HEADS UP: this one has a catch, and I'll explain it below.
Power Management Mode. Clean gains here: "Prefer Maximum Performance." This stops the GPU from dropping clocks at bad moments. Downclocking causes micro-stutters and inconsistent frametimes that feel like "lag" even when the FPS counter looks fine. This setting helped my stability more than almost anything else. Set it per-game, not global, so you're not running your card at max clocks while browsing.
Vertical Sync (Vsync). For competitive, off in most cases. Vsync adds latency. If tearing drives you crazy, a frame cap or Fast Sync (depending on the game) is a better move, but don't enable Vsync in both the panel and the game at the same time — that's how you spike your latency.
Frame Rate Limiter. Counterintuitive but real: capping FPS a bit below your refresh rate keeps frametimes stable and, paradoxically, makes the game feel more consistent than letting it run uncapped. On GPUs like the 3060 Ti, it also stops the card from slamming 100% load and heating up for no reason.
Resolution and Scaling. The single biggest FPS lever isn't buried in some obscure driver setting: it's the resolution you're rendering at. I'm saying this because a lot of people hunt for the magic driver trick when the big gains are sitting right in front of them.
The Trap Nobody Mentions: Reflex Overrides the Panel
This is the part almost no guide explains, and it's why half the NVIDIA panel optimization advice for CS2 is wasted effort.
Of my four games, three (CS2, Valorant, and Call of Duty) have NVIDIA Reflex built in natively. And when a game has native Reflex, Reflex takes priority and overrides the panel's "Low Latency Mode." Translation: if you spend half an hour setting Ultra Low Latency in the NVIDIA panel for CS2 because you read it in some listicle, you're not doing anything. Reflex is already managing the frame queue from inside the game.
So what should you do? In CS2, Valorant, and COD, enable Reflex inside the game (On or On + Boost) and leave the panel's Low Latency Mode at Off, because it won't apply anyway. Reflex does a better job than the driver override because it integrates directly with the game engine and aligns CPU and GPU work just in time, eliminating the render queue from the inside. The panel can only do that blindly, from the outside.
This is the Steam Wallet bait-and-switch of this guide: the price you see isn't the real price. The setting you think is doing something isn't, because another system with higher priority already took control.
The Placebos and Myths That Waste FPS or Do Nothing
One concrete example from my own testing before the list: toggling anti-aliasing in the panel did not change a single FPS in CS2 or Valorant — the game engine manages AA itself and ignores the panel option. What did give me frames was switching "Texture Filtering - Quality" from "Quality" to "Performance": that setting the panel does respect, and you feel it directly in-game. Simple rule: if a panel change doesn't show up in the game's graphics menu, it's usually smoke; if it touches something the game doesn't expose (texture filtering, low latency, sync), it usually matters.
Things you'll see recommended like they're gold that are either useless in competitive or actively counterproductive:
"Set texture filtering to High Performance and gain FPS." The difference in modern competitive games is statistical noise. You're trading image quality for a margin-of-error FPS change. It's not the lever they're selling it as.
Image Sharpening / panel sharpness. It's cosmetic. You might like how it looks sharper, but it's not a performance optimization. Don't put it in the "this gives me frames" column because it doesn't.
Threaded Optimization as a universal fix. Leave it on Auto and forget it. Forcing it to On or Off rarely changes anything measurable in these games and sometimes introduces problems. The myth that it's a free FPS toggle doesn't hold up.
Stacking thirty AA overrides in the panel "just in case." Modern competitive games manage their own AA. Overriding from the panel usually doesn't apply or fights with the game. Less is more.
General rule: if a setting doesn't touch latency, GPU clock speed, sync, or resolution, it's probably not giving you the FPS you think it is.
The Special Case of League of Legends
Of my four games, League is the only one without native Reflex (while Riot has been working on low-latency integration, don't assume it's active the same way as in CS2). And this is where the panel actually does real work.
Since there's no Reflex overriding the setting, the panel's "Low Latency Mode" actually applies. Here, On (or Ultra — because League runs well above what a 3060 Ti needs to sweat over) has a real effect on input lag. It's the exact opposite of CS2: what was useless in the shooter is the right tool in League. League is also lightweight, so the GPU isn't the bottleneck; "Prefer Maximum Performance" still helps prevent micro-stutters during heavy team fights.
The takeaway: the same panel setting can be useless in one game and essential in another, depending on whether the game has Reflex. There's no universal "optimal config." That's exactly why I configure per-game, not globally.
The "Don't Break Anything" Protocol
Like anything where you can make a mess, there are three rules that never fail.
First: write down the default values before you touch anything. Or just trust the panel's "Restore" button. If you make ten changes at once and something gets worse, you won't know which one caused it. Change, test, measure. One at a time if you have to.
Second: configure per-game, not global, for aggressive settings like maximum performance. You don't need the GPU pegged at max clocks while watching a video. That's heat and power draw for nothing.
Third: actually measure, don't just believe. Enable the FPS counter and, better yet, the frametime/latency counter. A lot of "magic settings" that people swear by are placebo: they changed ten things, one did something, and they credit a different one. If you don't measure it, you don't know.
Conclusion
If you want the short version: do a clean driver install, enable Reflex inside the game in CS2/Valorant/COD, set "Prefer Maximum Performance" per-game, leave the panel's Low Latency Mode at On (Ultra only if you have frames to spare), cap frames a bit below your refresh rate, and ignore half the settings you see in bloated guides.
On my 3060 Ti that was 20-30 FPS and, more importantly, much more stable frametimes. Not from checking thirty boxes, but from understanding what each setting actually does and, more importantly, what things DON'T do anything because another system with higher priority is already running the show.
The NVIDIA Control Panel isn't a chest of free FPS. It's a box with five levers that matter and twenty there to waste your time. Count the real effect, not the one the guide promises.
Frequently Asked Questions
Does tweaking the NVIDIA Control Panel actually gain FPS in Valorant and CS2?
Yes, but only if you touch the right settings. The author gained 20-30 FPS and improved frametime stability in Valorant and CS2 by changing four or five specific settings. Most guides that list dozens of changes are fluff, because the game itself overrides what you set in the panel.
What does NVIDIA's Low Latency Mode do and which one should I use?
Off queues up to 3 frames and maximizes average FPS but adds latency. On queues 1 frame and is the recommended balance. Ultra forces the minimum frames in queue but cuts some peak FPS; it's only worth it if you have frames to spare well above your monitor's refresh rate.
What happens to the NVIDIA panel's Low Latency Mode if I have Reflex enabled in CS2 or Valorant?
When a game has native Reflex — CS2, Valorant, and Call of Duty all do — Reflex takes priority and overrides the panel's Low Latency Mode. Setting Ultra Low Latency in the panel for those games does nothing. The right move is to enable Reflex inside the game and leave the panel setting at Off.
Why should I do a clean NVIDIA driver install before optimizing the panel?
Old drivers leave residue: corrupted profiles and settings from previous versions that can cause stutter and FPS drops that no panel setting will fix. The clean install checkbox in the NVIDIA installer itself is enough for 90% of cases.
