You crank every slider to Ultra, boot into your favorite game, and your frame rate collapses to a stuttery mess. So you start lowering settings at random, hoping something sticks. An hour later the game looks worse and runs exactly the same. If that sounds familiar, you are not alone, forum threads on r/buildapc and Linus Tech Tips are full of gamers stuck in the exact same loop.
The good news is you do not have to guess. There is a systematic way to find which setting is tanking your FPS without guessing, and it takes maybe twenty minutes once you know the steps. This guide walks through a real diagnostic method, ranks the settings that hit frame rate hardest, and shows you how to read the numbers so the culprit is obvious.
We will cover the quick fixes first, then move into the step-by-step process, the per-setting breakdown, and how to tell a software problem from a hardware limit. By the end you will have a repeatable workflow you can run on any game.
Table of Contents
What FPS Actually Means (And Why It Drops)
FPS, or frames per second, is how many complete images your PC pushes to the monitor each second. Higher is smoother, but raw FPS is only half the story. Frame pacing, or how evenly spaced those frames arrive, matters just as much as the total count. A game averaging 60 FPS with wild swings between 40 and 90 feels worse than a locked 55.
Every frame is built by a chain of components. Your CPU handles game logic, AI, and draw calls. Your GPU renders the actual pixels. RAM and VRAM shuttle data between them. When one link in that chain is slower than the rest, you have a bottleneck, and FPS drops follow.
Graphics settings matter because they load different parts of that chain. Shadows and reflections hammer the GPU. Draw distance and NPC count stress the CPU. That is why two different settings can both tank your frame rate for completely different reasons, and why blanket advice like “just lower everything” wastes your time.
Quick Fixes to Try Before Touching Graphics Settings
Before you blame the graphics menu, rule out the boring stuff. A huge percentage of “sudden low FPS” posts on gaming forums trace back to one of the issues below, not the game itself.
Update your GPU drivers. Both NVIDIA and AMD push Game Ready and Adrenalin updates timed to major releases. Running a driver from three months ago can cost you 10 to 20 percent performance in newer titles. Use GeForce Experience, the AMD Adrenalin app, or download directly from the manufacturer.
Kill background processes. Open Task Manager (Ctrl+Shift+Esc) and sort by CPU, then by GPU. Browser tabs with video, streaming software, RGB utilities, and even overlapping game launchers all eat resources. One reddit user on r/buildapc traced a 40 percent FPS loss to a forgotten OBS preview running in the background.
Switch your Windows power plan. On Windows 10 and 11, the default Balanced plan throttles the CPU under light load and sometimes fails to ramp back up. Set it to High Performance or Ultimate Performance. On laptops this matters even more, a quiet fan profile can quietly cap your frame rate.
Disable redundant overlays. Steam, Discord, GeForce Experience, Xbox Game Bar, and the EA app all want to draw an overlay. Each one hooks into the render pipeline. Two or three stacked can cause micro-stutter that looks like a settings problem.
Check your display cable and refresh rate. If your monitor is set to 60Hz in Windows, you will never see past 60 FPS no matter what the game reports. Right-click the desktop, go to Display settings, Advanced display, and confirm the refresh rate matches your monitor.
How to Find Which Setting Is Tanking Your FPS Without Guessing
This is the method most guides skip, and it is the exact thing that separates an hour of frustration from a clean answer in minutes. You need three things: an FPS overlay, a repeatable benchmark, and the patience to change one variable at a time.
Step 1: Install a Monitoring Overlay
You cannot fix what you cannot measure. Install one of these tools before doing anything else.
MSI Afterburner with RivaTuner Statistics Server. The classic combo. Shows FPS, frametimes, GPU usage, CPU usage per core, GPU temperature, VRAM usage, and clock speeds in a corner overlay. Free and works with basically every game.
CapFrameX. A cleaner, more modern alternative built for capturing and analyzing frametime data. Great for spotting stutter patterns Afterburner will not flag. Exports CSV files if you want to graph results.
NVIDIA Frame View (NVIDIA cards only) or the built-in overlay in AMD Adrenalin both work if you want something lighter. The key is having GPU and CPU utilization visible at the same time as FPS.
Step 2: Identify CPU vs GPU Bottleneck
Before testing settings, figure out which component is limiting you. Launch the game, get to a busy scene that produces your normal FPS, and read the overlay.
If GPU usage is sitting at 95 to 99 percent, you are GPU-bound. Lowering graphics settings will help. This is the most common scenario.
If GPU usage is below 85 percent and FPS is still low, you are CPU-bound. Lowering shadows and reflections will barely move the needle. You need to reduce CPU load, which means lower crowd density, shorter view distance, fewer NPCs, or just accepting your CPU is the limit.
This single check saves hours. There is no point turning down eight GPU settings if your CPU is the problem.
Step 3: Find or Create a Repeatable Benchmark
The biggest mistake people make is testing settings while playing normally. Frame rate swings wildly depending on where you look, who is on screen, and what is exploding. You need the same scene every time.
Many games have a built-in benchmark tool in the settings menu. Cyberpunk 2077, Red Dead Redemption 2, Shadow of the Tomb Raider, and Forza Horizon all ship with one. Use it. They run the same cinematic every time and spit out clean min, max, and average FPS numbers.
If your game has no benchmark, pick a fixed spot, face a specific direction, and stand still for 30 seconds while CapFrameX records. Walk the same path each time. It is not perfect, but it is consistent enough to spot big differences.
Step 4: Toggle One Setting at a Time
Now the actual diagnosis. Reset everything to the preset you normally play on. Run the benchmark and log the result. This is your baseline.
Pick the highest-impact setting first, usually shadows. Drop it one notch, run the benchmark again, log the result. If FPS jumps 15 percent, you found a major culprit. If it barely moves, restore it and move to the next setting.
Work down this order: shadows, volumetric lighting, dynamic reflections, ambient occlusion, anti-aliasing, render scaling, post-processing, texture quality, view distance. We will explain why this order in the next section.
One setting per run. No exceptions. Changing two at once means you cannot tell which one mattered. This is the part people skip, and it is the entire reason this method works.
Step 5: Log and Compare
Write down the result after each run. A simple list works.
Baseline: 58 FPS average. Shadows on Low: 74 FPS. Volumetric on Low: 61 FPS. Reflections off: 60 FPS. Suddenly the answer is staring at you. Shadows were costing 16 FPS in this game on this hardware, and nothing else came close.
That is the entire method. Five steps, repeatable, no guessing. Once you have done it once, the same workflow takes ten minutes on the next game.
Settings That Hit FPS the Hardest (Ranked)
Not all settings are created equal. Based on Digital Foundry performance analyses, forum consensus from r/pcgaming and r/OptimizedGaming, and our own testing, here is roughly how much each setting tends to cost on a midrange GPU running a modern AAA game at 1440p.
Actual numbers vary by game and hardware. Treat these as a starting point for which setting to test first, not as guarantees.
1. Shadows and shadow resolution. Usually the single biggest FPS drain. Shadows require the GPU to render the scene again from the light’s perspective. Dropping shadows from Ultra to Medium commonly returns 15 to 25 percent FPS. Shadow resolution has a similar impact and is barely visible in motion.
2. Volumetric lighting and fog. God rays, volumetric clouds, and dense fog are essentially rendering light as a 3D volume. Beautiful, expensive, often the second biggest culprit. Drop from Ultra to Medium for a typical 10 to 18 percent gain.
3. Dynamic reflections (SSR and ray-traced). Screen-space reflections re-render parts of the scene. Ray-traced reflections are far worse. Turning reflections down or off frequently returns 10 to 15 percent, sometimes much more with ray tracing enabled.
4. Ambient occlusion. SSAO, HBAO+, and similar techniques add contact shadows between objects. The visual difference between High and Off is subtle in fast motion, but the FPS cost is real. Expect 5 to 12 percent.
5. Anti-aliasing. MSAA is the old heavy hitter, doubling or quadrupling the render workload. TAA is far cheaper and is the modern standard. FXAA is almost free but blurs the image. If you are on MSAA 4x or 8x, switching to TAA can net 8 to 15 percent.
6. Render scaling and resolution. Running below native resolution (render scaling at 80 or 90 percent) is a brute-force FPS lever. It affects image quality across the board, but it works when nothing else does. Every 10 percent reduction in render scale roughly returns 10 to 15 percent FPS.
7. Post-processing: motion blur, bloom, depth of field. Individually cheap, collectively noticeable. Disabling motion blur also has the bonus effect of making low FPS feel less smear-y. Combined savings of 3 to 8 percent.
8. Texture quality. Surprisingly low impact on FPS on most modern GPUs, because textures live in VRAM, not in the render pipeline. Texture quality mainly affects VRAM usage. If you have enough VRAM, dropping textures from Ultra to High barely changes FPS. If you do not have enough VRAM, you will see stutter from texture streaming instead.
9. View distance and population density. These are CPU settings. They rarely touch the GPU. If your overlay showed low GPU usage in Step 2, these are your targets, not shadows.
Hardware Bottleneck or Bad Setting? How to Tell
Sometimes no setting change helps because the problem is the hardware, not the menu. Here is how to read the signs.
GPU at 99 percent, FPS still low. Your GPU is working as hard as it can. Settings changes will help, up to the point where you run out of GPU horsepower. If you have already dropped shadows, volumetrics, and reflections and you are still at 99 percent GPU at 40 FPS, you need a stronger GPU or a lower resolution.
GPU below 85 percent, FPS stuck. Your CPU, RAM, or storage is the limit. Check CPU usage per core in MSI Afterburner. If one or two cores are pegged at 100 percent, the game is CPU-bound and no graphics setting will fix it. Enabling XMP or EXPO for your RAM in BIOS is a known fix that forum users frequently overlook, running RAM at base JEDEC speeds instead of its rated speed can cost 10 to 20 percent FPS.
Temperatures climbing and clocks dropping. Thermal throttling mimics a settings problem. Check GPU and CPU temps in your overlay. If the GPU is hitting 83 to 90 degrees Celsius and the clock speed is dropping, clean your fans, redo thermal paste, or improve case airflow. On gaming laptops this is the number one cause of “sudden low FPS.”
VRAM maxed out. If VRAM usage is at your card’s limit, the game starts streaming textures from storage, causing stutter that looks like an FPS problem. Lowering texture quality or texture pooling fixes this even though raw FPS looks fine on the overlay.
When to actually upgrade. If you have run the full diagnostic, ruled out settings and thermals, and your GPU is pinned at 99 percent with everything on Low at 1080p, you have genuinely outgrown your hardware. A new GPU will do more than any tweak. But that diagnosis should come after the method above, not before it.
Advanced Diagnostic Tips From the Community
Beyond the core method, these are the lesser-known causes of FPS problems that show up repeatedly in forum threads.
Shader compilation stutter. Many modern engines (Unreal 5 in particular) compile shaders the first time you enter a new area, causing brief FPS drops that look like a settings issue. This settles after the shaders cache. If stutter only happens in new areas and disappears on a second visit, this is the cause, not your settings.
Frame generation and upscaling artifacts. DLSS, FSR, and frame generation can boost the FPS number while introducing latency or visual weirdness that feels worse than raw lower FPS. If your overlay shows 90 FPS but the game feels laggy, check whether frame generation is inflating the number without improving responsiveness.
Per-area FPS drops. If FPS is fine in most of the game but tanks in one specific city or scene, the cause is almost always CPU-bound asset streaming or NPC count. Lower population density, crowd variety, or the relevant world-detail setting. No amount of shadow tweaking will help here.
Config file edits. Some engines expose hidden settings in plain text config files that the menu does not show. Checking the game’s community wiki or the relevant pcgamingwiki page often reveals specific cvars tied to known performance killers in that title.
Dual-channel vs single-channel RAM. Running one stick of RAM instead of two cuts memory bandwidth in half and cripples CPU-bound performance. This is a common mistake in budget builds and prebuilts. If your overlay shows low GPU usage and your CPU looks fine, check whether you are actually running dual-channel.
FAQs
How to figure out what is causing low FPS?
Install an overlay like MSI Afterburner with RivaTuner, run a repeatable in-game benchmark, then toggle one graphics setting at a time and log the FPS result after each change. The setting that produces the biggest jump is the one tanking your frame rate. Checking GPU versus CPU utilization first tells you whether to lower GPU settings like shadows or CPU settings like view distance.
Which settings affect FPS the most?
Shadows and shadow resolution typically cost the most FPS, followed by volumetric lighting, dynamic reflections, ambient occlusion, and MSAA anti-aliasing. Texture quality has surprisingly low FPS impact on most modern GPUs, and view distance is a CPU setting rather than a GPU one.
Is 200 FPS overkill?
For most players on standard 60Hz or 144Hz monitors, yes. You can only see as many distinct frames as your monitor’s refresh rate. 200 FPS matters on 240Hz competitive displays in fast-paced shooters like Valorant or CS2, where lower input latency gives an edge. On a 60Hz monitor, anything above about 75 FPS is wasted.
Is 40 FPS choppy?
Yes, 40 FPS generally feels choppy on a 60Hz monitor because frames arrive unevenly, causing visible judder. On a 120Hz or 40Hz VRR display, 40 FPS can feel smoother because the refresh rate locks to the frame rate. Below 30 FPS, most games become noticeably unplayable for anything but slow-paced titles.
How do I know if it is my GPU or CPU causing low FPS?
Check your overlay. If GPU usage is above 95 percent, your GPU is the limit and lowering graphics settings will help. If GPU usage is below 85 percent while FPS stays low, your CPU, RAM, or storage is the bottleneck, and you should lower CPU-heavy settings like view distance, crowd density, and population variety instead.
Stop Guessing, Start Measuring
The reason most people never figure out which setting is tanking their FPS is that they change everything at once and have no way to tell what worked. The fix is boring and effective: overlay on, benchmark set, one setting at a time, log the numbers. Once you know how to find which setting is tanking your FPS without guessing, the same workflow works on every game you own. Install MSI Afterburner, find your benchmark, and start with shadows.