Best VALORANT PC Settings for FPS and Visibility (2026)
A full VALORANT 13.10 settings pass for PC: video and graphics values with the reason behind each, sensitivity and eDPI, crosshair, minimap, HRTF audio, default and remapped keybinds, plus Reflex, Anti-Lag 2 and system tweaks that stay inside the rules. Includes per-tier picks for low-end and high-end machines and a repeatable way to test your own numbers.
VALORANT moved to Unreal Engine 5.3 with patch 11.02 in July 2025, and the newer renderer still asks more of your CPU and your eyes than of your GPU. A mid-range card already sits above your refresh rate in a quiet round; the frames you actually feel disappear are the ones lost inside ability-heavy fights. This guide gives you the values to enter, the reason behind each one, and a test loop that proves they hold on your machine. Everything here reflects patch 13.10, released November 10, 2026.
Quick Settings Cheat Sheet
Understanding VALORANT's Performance
- Engine and API. VALORANT has run on Unreal Engine 5.3 since patch 11.02 (July 29, 2025), after years on 4.27. The official system requirements still list DirectX 11 support only, so there is no DX12 or Vulkan switch to hunt for in the menu.
- You are usually not GPU-bound. The minimum spec is an Intel HD 4000, which tells you how light the renderer is. On a modern card the limiting factor is more often CPU headroom, background load and frame pacing than raw shading power.
- Stutter shows up in fights, not in the range. Ability effects, overlapping smokes and stacked particles are where frame time spikes; a clean empty corridor tells you almost nothing about your real 1% low (the frame rate at your worst moments).
- Low settings are a visibility choice first. Flatter lighting and fewer glow effects make silhouettes easier to read, which is why the competitive profile is also the cheapest one to run.
With a discrete GPU you also need at least 1 GB of VRAM on the minimum tier, and the CPU must support SSE 4.2 or AVX. For a rough sense of 1080p output on the low settings below, manufacturer estimates put a GTX 1660 or RTX 3050 at around 144 to 180 FPS, an RTX 4060 or 4060 Ti at roughly 200 to 300+, and an RTX 4080, 4090 or 50-series card at 300+ consistently. Those are vendor figures, not per-setting measurements, so treat them as a ceiling to verify rather than a promise.
Best Video and Graphics Settings
The approach is simple: start from the floor, then add back only the rows you can name a reason for. For a tactical shooter, most visual options cost frames and add noise at the same time, which makes the competitive pick and the cheap pick the same pick.
Pro Tip: the row players regret leaving on is Distortion. It is not a cosmetic filter you notice in the menu — it warps your view during the exact seconds you are holding an angle through an active ability. Turn it off before you tune anything else.
Key Setting Deep Dives
Material Quality: The One Row Worth Grieving
Material Quality controls how much shading work goes into every surface in the level. It has the heaviest impact on overall performance of the quality rows, which makes it the first thing to drop and the last thing to raise. Low is the competitive answer on essentially any card.
The exception is real but narrow: on a high-end GPU at 4K you can hold a high average frame rate with Material Quality high, and the game does look better. The condition is that your 1% low stays above your refresh rate. If it does not, the extra detail is costing you exactly the frames that decide a fight. Check it by watching frame time in a busy round, not by reading the average in the menu.
Multithreaded Rendering: Check the Threshold First
This toggle spreads rendering work across CPU threads. Riot's official threshold is 8 GB of RAM, 2 GB of VRAM and a CPU with at least 8 threads counted physical plus virtual — which means most modern 4-core chips qualify. Above the line it reduces the load on your main thread; below it, gains are not guaranteed and stutter is possible.
If you enable it and the game feels worse, look at RAM usage before anything else. A 4 GB machine already sits at the minimum spec, and pushing rendering work into a memory-starved system trades smoothness for throughput you cannot use.
Reflex, Anti-Lag 2, and When to Cap Frames
NVIDIA Reflex is the one latency setting with no downside: On + Boost keeps the render queue short and does not touch image quality. Reflex 2 with Frame Warp had not shipped in VALORANT as of September 2026, so do not expect it in the menu.
AMD's equivalent, Anti-Lag 2, arrived in patch 12.09 on May 12, 2026, and is off by default. It requires an RDNA card (RX 5000 series or newer) and a driver dated March 9, 2026 or later. Run one latency layer per GPU vendor — you will not see both toggles on the same machine anyway.
Frame caps are where opinions split, and the split is really about hardware. On a strong rig, leaving Limit FPS Always off avoids any added delay. On a laptop or a machine that runs hot, cap at your refresh rate minus three (141 on a 144 Hz panel, 237 on 240 Hz) so the GPU is not pegged at 100% for no visible benefit. Do not stack two cap sources at once; pick the in-game cap or the driver cap and leave the other off.
Controls, Audio and Visibility
Mouse and Sensitivity
Start at 800 DPI and 0.35, which is 280 eDPI, then adjust in small steps after a week rather than after one bad match. Some pros sit well above 320 eDPI, so treat the band as a starting point, not a rule.
Crosshair
If you are new, leave Movement Error and Firing Error on for a few weeks — they teach you when your shots are actually inaccurate. Turn them off once the habit is there.
Minimap and HUD
Audio
Riot's own position is that neither HRTF nor an external spatial layer has shown a competitive advantage beyond personal preference, so pick the one that makes positions easier for you to place and stop tuning.
Default binds are worth knowing before you remap: C and Q for the two basic abilities, E for the signature, X for the ultimate, 4 for the Spike, F to use an object, V for team voice and M for the map. The most common change is moving Ability 1 and Ability 2 to mouse buttons 4 and 5, which keeps your left hand on movement. Keybinds are stored per agent, so a change made on one agent does not carry to the next — check for conflicts after each edit.
Launch Options and Config File Tweaks
There is nothing to add here, and that is the honest answer for this game. VALORANT has no supported launch-parameter workflow, and editing game files or configs sits directly against Vanguard's rules. No third-party "optimizer" is verified as safe, and several are known to trip the anti-cheat.
Latency and Input Optimization
- Reflex On + Boost keeps the CPU and GPU frame pipeline short. Boost holds clocks higher while the setting is active, which is why it costs a little power for a little less latency.
- Anti-Lag 2 on RDNA cards does the same job from the driver side, but only with a driver from March 9, 2026 or newer; on older drivers the toggle will not appear.
- Refresh rate is the hard ceiling. On a 60 Hz panel every other setting is fighting a 16 ms frame. Competitive play starts at 144 Hz; in the pro sample, 47% use 360 Hz or higher and 33% use 240 Hz.
- Your mouse does not need a high DPI. A lower DPI with a higher in-game multiplier and a higher DPI with a lower multiplier can produce the same eDPI, so tune the product, not the number.
System and Driver Tweaks
- Update your GPU driver before you touch a single menu row. Driver-side fixes resolve stutter that no in-game option can reach.
- Set Windows 11 up properly. Vanguard requires TPM 2.0 and UEFI Secure Boot; without both, the game will not launch at all.
- Switch the power mode to Best Performance. Laptops on a balanced or saver profile throttle CPU clocks mid-match, which shows up as stutter rather than a lower average.
- Confirm the Windows refresh rate. Some systems default to 60 Hz regardless of the panel, so check the display settings, not just the in-game value.
- Close what you are not using. Browsers, capture software and overlays compete for the same CPU time and memory bandwidth the game needs.
How to Test Your Settings
- Pick one map and one repeatable scenario, such as a site take in a custom game, and run it the same way each time.
- Record your average FPS and your 1% low with the in-game performance overlay. The average flatters you; the 1% low is what you feel.
- Drop every graphics row to its lowest value and play a round. That is your machine's ceiling.
- Raise one row at a time, replaying the same scenario, and keep only the rows whose cost you cannot see in the 1% low.
- Match the result to your display: stable 60 FPS at 60 Hz, 120 to 144 FPS at 144 Hz, 200+ at 240 Hz. If you cannot reach the target after step 4, drop resolution one step before you drop your refresh rate.
