Valorant Patch 8.05 FPS Drops: How to Fix (2026 Guide)

Valorant's Episode 8 Act 5 patch dropped on September 10, 2026, and within hours Reddit lit up with reports of sudden frame drops, micro-stutters, and input lag that weren't there the day before. Players running stable 300+ FPS pre-patch saw dips into the 180–220 range on identical hardware, some with new hitching on certain maps.

The culprit isn't your GPU degrading overnight. Riot's 8.05 update includes shader recompilation for the new Ascent visual updates and backend anti-cheat hooks that conflict with certain driver versions and cached data. The good news: most drops reverse in under ten minutes with the right fixes. Here's the methodical breakdown, in priority order.

Quick Fixes First (Do These in Order)

Start here before touching settings. These address the most common 8.05-specific issues — corrupted shader cache and file integrity problems introduced during the patch install.

1. Close Valorant completely, then navigate to `%LocalAppData%\VALORANT\Saved` and delete the entire `ShaderCache` folder. This forces the game to rebuild shaders with the new Episode 8 Act 5 data instead of using stale pre-patch cache that now causes hitching.
2. Open the Riot Client, click the Valorant icon, hit the gear icon, and select 'Repair'. This verifies all game files and replaces any corrupted by the patch process — typically takes 2–4 minutes.
3. Restart your PC. Riot Vanguard (the anti-cheat kernel driver) updated in 8.05 and sometimes holds onto old hooks until a full reboot clears memory.
4. Update your GPU driver to the latest version released after September 10, 2026. NVIDIA 566.14+ and AMD Adrenalin 26.9.1+ both include Valorant 8.05 optimizations. Older drivers conflict with the new Vanguard signature checks.

If those four steps don't restore your FPS, the problem is deeper — either a settings conflict introduced by the patch's auto-config changes, or a hardware bottleneck that 8.05's heavier anti-cheat overhead now exposes. Move to the next section.

Settings Riot Changed Without Telling You

Patch 8.05 silently reset two video options for some users during install: `Multithreaded Rendering` flipped back to OFF, and `Anti-Aliasing` bumped from MSAA 2x to 4x. Both tank frames if you didn't catch them. Open Video settings and verify these match your pre-patch config.

The new Ascent rework also defaults `Material Quality` to High instead of Medium for players who had auto-graphics enabled. Ascent's updated geometry is roughly 18% more polygon-heavy than the old version, and High material settings now pre-load more texture mipmaps into VRAM. On GPUs with 8GB or less, this causes micro-stutters as the engine swaps textures mid-round. Drop Material Quality back to Medium or Low if you're on an RTX 4060 / RX 7600 tier card.

Driver & Software Conflicts (NVIDIA vs AMD)

NVIDIA users on driver 565.xx (released mid-August) report sporadic frame pacing issues with Valorant 8.05 specifically — the average FPS looks fine, but frame time spikes every 4–6 seconds create perceived stuttering. NVIDIA acknowledged this in a support thread and pushed 566.14 on September 12 to address Vanguard signature verification overhead. Update through GeForce Experience or manually from nvidia.com.

AMD RX 9000-series and RX 7000-series cards had a different bug: Adrenalin 26.8.2 conflicts with Vanguard's new kernel-mode hooks, causing intermittent black-screen flickers during agent select and round start. AMD patched this in 26.9.1 (released September 11). If you're still on 26.8.x, the driver update alone can eliminate the drops.

Third-party overlays — Discord, Medal, NVIDIA GeForce Experience in-game overlay — also interact badly with Vanguard's 8.05 memory scanning. Disable all overlays, restart Valorant, and test. If FPS returns, re-enable them one at a time to isolate which one conflicts.

When 8.05 Exposed a Hardware Bottleneck

Sometimes a patch doesn't break your config — it just reveals a limit that was already there. Vanguard's new kernel driver adds roughly 2–4ms of CPU overhead per frame for integrity checks. On a CPU already running near capacity (one or two cores pinned at 95%+), that extra 3ms pushes you over the edge into frame drops.

Open Task Manager, go to Performance → CPU, right-click the graph and select 'Change graph to Logical processors'. Play a match and watch individual cores, not the aggregate percentage. If you see one core at 98–100% while others sit at 30–50%, you're CPU-bound. The fix isn't settings — it's either upgrading the CPU or lowering your target frame rate cap to match what your CPU can deliver.

GPU bottlenecks are rarer in Valorant, but the new Ascent lighting pushes VRAM harder. If you're on an 8GB card (RTX 4060, RX 7600) and seeing texture pop-in or stuttering only on Ascent, that map now exceeds 8GB at high settings in some scenarios. Drop Texture Quality to Low and Material Quality to Medium — this cuts VRAM usage by 1.2–1.5GB and eliminates the stutter.

Nuclear Option: Clean Reinstall & Config Reset

If all of the above fails, you're likely dealing with a corrupted user profile or Windows registry conflict that survived the Repair tool. This is the last-resort fix, but it works when nothing else does.

1. Uninstall Valorant and the Riot Client completely through Windows Settings → Apps. Reboot.
2. Navigate to `%AppData%\..\Local\VALORANT` and delete the entire folder (this wipes all settings and cached data).
3. Run `regedit`, go to `HKEY_CURRENT_USER\Software\Riot Games`, right-click the Valorant key, and delete it (backs up first if you're cautious).
4. Reinstall Valorant fresh from playvalorant.com. Let it auto-detect settings the first time, then manually configure only the essentials (resolution, refresh rate, Multithreaded ON).
5. Play one match, close the game, then run a playbook for your GPU to apply tested optimizations without guessing.

This process takes about 20 minutes including the download. It strips out any configuration corruption from prior patches and gives you a clean baseline to work from. Most users who reach this step report FPS returning to pre-8.05 levels immediately.

What FPS Should You Expect After the Fix?

Context matters — 'good FPS' depends on your hardware and settings tier. Here's what independent testing shows for 2026 hardware on patch 8.05, measured by ProSettings.net and Dodge.gg after the shader cache bugs were resolved.

At 1080p with low competitive settings, an RTX 5070 hits 800 FPS average (measured by ProSettings.net) — identical to the RTX 5080 at the same settings, since Valorant's lightweight engine doesn't stress high-end GPUs differently at low detail. The RX 9070 XT lands at 780 FPS on low, also measured by ProSettings.net. At 1440p low, the RTX 5070 delivers 700 FPS average (ProSettings.net), and stepping up to high settings at 1440p drops that to 650 FPS — still well above the 240 Hz threshold most competitive players target.

For reference, the RTX 5070 Ti at 1080p competitive settings averages 590 FPS with 480 FPS 1% lows (measured by Dodge.gg), and the flagship RTX 5090 pushes 800 FPS average with 650 FPS 1% lows at the same config (Dodge.gg). The 1% low figure matters more than average for perceived smoothness — if your 1% lows drop below your monitor refresh rate, you'll feel stuttering even if the average looks high.

Patch-induced FPS drops are frustrating because they feel random and out of your control, but most 8.05 issues trace back to shader cache corruption, silent settings resets, or driver conflicts that reverse in minutes once you know where to look. If you've worked through this list and FPS is still below baseline, generate a free playbook for your exact GPU — the tool auto-detects your hardware and builds a patch 8.05-tested config that accounts for Vanguard overhead and the new Ascent geometry. For users who want every patch automatically handled, Patch Watch regenerates your playbook whenever Riot updates the game, so you never lose frames to a Tuesday patch again.

Frequently asked questions