Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesFor higher FPS in a shooter, first determine whether the GPU or CPU is limiting performance, then change one setting group at a time. If the GPU is near 100% utilization, use the game’s built-in DLSS or FSR, reduce shadows, volumetric effects, reflections and costly anti-aliasing, and keep textures high until VRAM becomes a problem. If a CPU thread is saturated, lowering resolution may barely help; reduce view distance, simulation and effects instead. Judge every change by sustained frame time, target visibility and input response—not by a single peak-FPS reading.
What higher FPS actually requires
A shooter feels faster when it produces frames at a consistent interval and presents your input promptly. A high average with frequent stalls can feel worse than a lower, steady result. Track average FPS together with a low-percentile FPS reading or a frame-time graph, GPU and CPU utilization, and whether distant targets remain easy to identify.
As an Amazon Associate I earn from qualifying purchases.
Graphics options do different kinds of work. Render resolution, upscaling, shadows, volumetric lighting, reflections and anti-aliasing primarily change GPU load. View distance, effects, simulation and background activity can keep a CPU thread busy even when overall CPU utilization looks moderate. Texture quality usually consumes video memory and affects streaming more than raw shader throughput. That is why lowering every slider is rarely the best competitive preset.
Build a repeatable baseline before changing settings
- Choose a fixed test. Use the same map, practice route, camera movement and approximate match conditions each time. A busy fight is useful for a second test, but it is not a controlled baseline.
- Record the starting state. Note display resolution, refresh rate, graphics preset, upscaler mode, frame cap, average FPS, low-percentile FPS or frame-time behavior, GPU utilization and CPU utilization. Record temperatures and clock speeds if your monitoring overlay provides them.
- Watch utilization during the slowest moments. A GPU running close to full utilization while frame rate falls indicates a render bottleneck. If the GPU is not busy but one or more CPU threads are saturated, you have a CPU-side limit.
- Change one setting group. Apply a change, restart the game when it requests it, and repeat the identical route. Log the new performance and any visual artifact before making another change.
This method prevents a common mistake: changing resolution, shadows, textures and the driver profile at once, then being unable to tell which choice helped or caused a visibility problem.
#1 Best Overall
- AI Performance: 767 AI TOPS
- OC mode: 2632 MHz (OC mode)/ 2602 MHz (Default mode)
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Axial-tech fan design features a smaller fan hub that facilitates longer blades and a barrier ring that increases downward air pressure
- A 2.5-slot design maximizes compatibility and cooling efficiency for superior performance in small chassis
Diagnose the bottleneck first
| Observed behavior | Likely limit | First settings to test |
|---|---|---|
| GPU utilization stays near full and frame time rises in complex scenes | GPU rendering | Built-in DLSS or FSR, render resolution, shadows, volumetrics, reflections and anti-aliasing |
| GPU utilization is well below full while one or more CPU threads are saturated | CPU throughput | View distance, simulation, effects, crowd or object detail controls, and background processes |
| Performance is acceptable until textures stream, then stutters or shows pop-in | VRAM capacity or streaming | Lower texture quality one step, close other GPU-accelerated applications, and retest the same route |
| Average FPS is high but frame-time spikes occur | Driver or shader compilation, background load, thermal limits or an unstable cap | Allow shader compilation to finish, check temperatures, reduce background load and set a sustainable cap |
Total CPU usage can be misleading: a game thread may be the limit while other cores are idle. Likewise, a GPU that briefly reaches full utilization does not prove it is the only bottleneck; observe the slowest portion of the test repeatedly.
Use the game’s own upscaler before lowering image quality elsewhere
When the GPU is the limit, render fewer pixels and reconstruct the output. NVIDIA defines DLSS Super Resolution as reconstructing higher-resolution frames from a lower-resolution render. AMD recommends integrated FSR when a game provides it, because game-specific implementation and optimization can produce better results than a driver-level substitute.
DLSS Super Resolution
DLSS Super Resolution is available only in games and on hardware that support it. Start with a quality-oriented mode so fine target detail and weapon edges remain readable. Move to balanced, then performance, only if the GPU remains the limiting component. Check foliage, thin geometry, particle edges and motion for reconstruction artifacts after each change.
FSR integrated in the game
Built-in FSR follows the same decision: begin with its quality mode and lower the internal render scale only as far as necessary. Keep the game’s sharpening control moderate; excessive sharpening can make distant geometry shimmer and does not restore detail lost by a very low render resolution.
Radeon Super Resolution
Radeon Super Resolution (RSR) is an in-driver spatial upscaler for games that lack integrated upscaling. It requires the game to run below the display’s native resolution and compatible Radeon hardware and software. Set the game to a lower resolution, enable RSR in the per-game driver profile, and let the driver upscale the result. If the title has built-in FSR, use that integrated option instead of RSR.
| Option | Use it when | What to check |
|---|---|---|
| Native resolution | The GPU has headroom and maximum fine-detail clarity is important | Frame-time stability during fights, not only the training area |
| DLSS Super Resolution | A supported game is running on compatible NVIDIA hardware | Quality mode first; inspect moving edges and distant targets |
| Integrated FSR | The game supports FSR and you need more GPU headroom | Quality, balanced and performance modes at the same route |
| Radeon Super Resolution | The game has no integrated upscaler and compatible Radeon hardware is in use | Below-native game resolution and per-game driver profile |
Upscaling is a GPU-load control, not a CPU fix. If lowering resolution changes FPS very little while a CPU thread remains saturated, restore the clearer resolution and work on CPU-heavy options.
Lower expensive lighting and post-processing in the right order
These settings often deliver a better performance-to-visibility trade-off than reducing textures.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #2
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Powered by GeForce RTX 5060
- Integrated with 8GB GDDR7 128bit memory interface
- PCIe 5.0
- WINDFORCE cooling system
Shadows and shadow distance
Reduce shadow quality or distance one step and test corners, doorways and indoor-to-outdoor transitions. Shadows can improve spatial awareness, so disable them completely only as a diagnostic test or when their competitive benefit is negligible. Riot Games’ support guidance specifically recommends lowering quality options and disabling shadows and anti-aliasing as a strong performance test.
Volumetric lighting and fog
Volumetrics can become expensive in smoke, fog, god rays and large outdoor scenes. Lower volumetric quality before sacrificing texture clarity. Watch smoke edges and bright-to-dark transitions for distracting banding or loss of contrast.
Reflections
Screen-space reflections and ray-traced reflections can consume substantial GPU time while adding little target information. Reduce the quality or disable ray tracing for competitive play, then verify that reflective floors or water are not hiding enemy silhouettes in the maps you play.
Ambient occlusion and post-processing
Lower ambient occlusion and heavy post-processing when the previous changes are insufficient. Motion blur, depth of field, film grain and chromatic effects can reduce clarity even when they do not dominate the frame-time cost; disable them if the game allows it. NVIDIA’s control-panel reference warns that High or Ultra settings can increase lag and may be unsuitable for first-person shooters or competitive gaming.
Free tools Windows power users keep installed
One-click scans. No signup required.
NVIDIA’s 2019 Control guide illustrates why results must be treated as title-specific: on its test system, reducing Screen Space Reflections from High to Medium produced approximately 9 additional FPS, while reducing Volumetric Lighting from High to Medium produced approximately 9–11 additional FPS. Those figures are not universal shooter gains.
Tune anti-aliasing without hiding targets
Anti-aliasing (AA) reduces jagged edges but costs performance; AMD notes that higher AA levels cost more FPS. Lower the sample count or choose a lighter method when edge shimmer is acceptable. Do not remove AA automatically: at a reduced resolution, completely disabling it can make wires, railings and enemy outlines flicker, making targets harder to track.
- Keep your chosen resolution or upscaler mode fixed.
- Test the next-lower AA level in a practice area with thin geometry and distant targets.
- Move while observing fences, foliage and weapon sights.
- Keep the lowest level that preserves readable silhouettes without distracting shimmer.
Keep textures high until VRAM, not taste, says otherwise
Texture quality commonly changes memory use and streaming behavior more than shader throughput. If the GPU has adequate VRAM and the game does not stutter, retaining high textures can preserve surface and material detail while you lower shadows or volumetrics. Lower textures when you see VRAM pressure, texture pop-in, hitching during traversal or sudden drops as new areas load. Change one texture step at a time and repeat the same route.
Rank #3
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Powered by GeForce RTX 5070 Ti
- Integrated with 16GB GDDR7 256bit memory interface
- PCIe 5.0
- WINDFORCE cooling system
Closing browsers, recording tools or other applications that reserve GPU memory can also prevent streaming stalls. A texture setting that is visually acceptable in a menu may still fail in a long match, so include a full-map traversal in your test.
Reduce CPU-heavy settings when resolution is not the answer
When the GPU is not busy and a game thread is saturated, lowering resolution leaves that thread almost unchanged. Look for controls named view distance, object distance, world detail, simulation, effects, physics, crowds or foliage distance. Lower the most CPU-oriented option one step, then retest a scene with many players or moving objects.
- Reduce view or object distance only as far as needed; excessively short distances can make cover and opponents appear late.
- Lower simulation, physics or crowd density if those controls exist and the game’s competitive rules do not depend on them.
- Reduce effects quality when combat particles cause the frame-time spike.
- Close background CPU workloads and overlays that capture, index or synchronize during play.
Separate latency controls from FPS controls
NVIDIA Reflex
NVIDIA describes Reflex as synchronizing CPU and GPU work to reduce system latency, so input appears on screen faster, especially in competitive games. It is a latency feature, not a guarantee of higher average FPS. Enable Reflex in a supported shooter, then evaluate mouse response and frame-time consistency during the same test route. If the game offers a Reflex mode such as “On” or “On + Boost,” use the label exposed by that game and monitor temperatures and sustained clocks.
Frame generation
Frame generation can raise the displayed frame count by inserting generated frames, but it does not replace a sufficiently high base render rate. A low base rate can still produce delayed input, and generated frames can show interpolation artifacts around fast-moving targets or effects. Test it separately from upscaling and judge responsiveness, not only the counter.
NVIDIA lists DLSS Super Resolution, Frame Generation, DLAA and Reflex as separate features whose availability depends on the game and implementation. NVIDIA also warns against combining native DLSS Frame Generation and Smooth Motion, because doing so can reduce performance and create visual artifacts.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Shader cache
AMD explains that shader cache stores compiled shaders so games can load faster and use less CPU instead of recompiling them each time. Keep shader caching enabled where the driver exposes it. After a driver or game update, the first run may stutter while shaders compile; allow that process to complete before judging a new setting.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choose display mode and frame caps deliberately
Test exclusive fullscreen or the game’s recommended low-latency mode against borderless windowed mode. Use the mode that gives the most consistent frame time on your system; do not assume the label alone determines performance.
Rank #4
- Powered by the NVIDIA Blackwell architecture and DLSS 4 OC mode: 2640MHz/Default mode: 2610MHz (Boost Clock)
- Military-grade components deliver rock-solid power and longer lifespan for ultimate durability
- Protective PCB coating helps protect against short circuits caused by moisture, dust, or debris
- 3.125-slot design with massive fin array optimized for airflow from three Axial-tech fans
- Phase-change GPU thermal pad helps ensure optimal thermal performance and longevity, outlasting traditional thermal paste for graphics cards under heavy loads
Set a cap the system can sustain in the heaviest repeatable scene. A lower stable cap can feel better than an uncapped counter that repeatedly hits a peak and falls into visible spikes. The appropriate number depends on monitor refresh rate, variable-refresh-rate behavior and available CPU/GPU headroom. Change only the cap, repeat the route and compare the frame-time graph.
| Cap strategy | Benefit | Trade-off |
|---|---|---|
| Uncapped | Highest possible instantaneous rate when the system has ample headroom | More heat, noise and uneven frame times when load varies |
| Cap near a sustainable rate | Predictable frame pacing and lower power use | Peak FPS is lower than the counter’s maximum |
| Cap matched to a VRR display’s practical range | Helps keep output inside the variable-refresh window | Requires testing the monitor, game and driver combination |
A practical competitive tuning order
- Record the baseline in the same route and note GPU and CPU utilization.
- If GPU-bound, enable the game’s built-in DLSS or FSR in its quality mode.
- Lower shadow quality or distance, then volumetrics, reflections and expensive post-processing.
- Reduce anti-aliasing one level while checking thin geometry and distant target readability.
- Lower textures only when VRAM pressure, pop-in or streaming stutter appears.
- If CPU-bound, adjust view distance, simulation, effects and background load instead of render resolution.
- Enable Reflex separately when supported and evaluate input response.
- Test fullscreen versus borderless and establish a sustainable frame cap.
- Retest after every meaningful change and keep the setting that improves frame time without harming visibility.
Why FPS can stay low after lowering settings
You lowered the wrong bottleneck
A CPU-limited game will show little improvement from lower resolution, AA or texture quality. Confirm utilization during the slow section and switch to view-distance, simulation or effects controls.
Recommended Free Tools
The cap, refresh mode or background software is limiting output
Check the in-game cap, driver cap, display refresh setting and any capture or overlay software. Test with one cap active so two different limits are not fighting each other.
Thermal or power limits appear after several minutes
A short benchmark can look fast before clocks fall. Repeat a long enough route to reach steady temperature, then compare sustained clocks and frame time. Improve cooling or use a stable cap if heat is the cause.
Shader compilation or streaming causes hitches
Let shader compilation finish after updates, keep shader caching enabled, and check whether stutter occurs when entering new areas. If VRAM is full, lower textures one step and close other GPU-using applications.
Visual quality fell without a useful gain
Restore the last change, not the entire preset. Prioritize shadows, volumetrics, reflections and heavy post-processing before sacrificing textures or resolution that keep targets readable.
Maintain a settings log
A short log makes optimization reproducible when a game patch or driver changes behavior. Record the date, game version, display resolution, upscaler and mode, key quality settings, frame cap, average FPS, low-percentile FPS or representative frame time, utilization, temperatures, and notes about shimmer, ghosting, pop-in and target visibility. Re-run the baseline after major updates instead of assuming an old result still applies.
The best shooter settings are therefore a measured compromise: enough render resolution and anti-aliasing to identify targets, reduced effects that do not aid aim, textures that fit comfortably in VRAM, and a frame cap the system can hold through the worst fight. That combination produces more useful responsiveness than chasing a brief peak number.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
