Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
For higher, more consistent FPS in a shooter, first determine whether the GPU or CPU is limiting performance, then change one settings group at a time. If the GPU is near full utilization, use the game’s own DLSS or FSR mode, reduce shadows, volumetrics, reflections and costly anti-aliasing, and keep textures high until VRAM pressure appears. If the GPU is underused while a CPU thread is saturated, lowering resolution may barely help; reduce view distance, simulation and effects that run on the CPU instead. Finish by enabling a supported latency mode such as NVIDIA Reflex, choosing a sensible frame cap, and retesting the same route or map.
A stable frame-time pattern and clear targets are more valuable in a match than a short-lived peak-FPS number. The procedure below gives you a repeatable way to find that balance without making the game unnecessarily blurry.
1. Establish a repeatable baseline before changing anything
Write down your current display resolution, refresh rate, graphics preset, frame cap and upscaling mode. Then use the same map, practice route or replay camera for every test. Record average FPS, a low-percentile result (such as 1% low if your overlay provides it), frame-time behavior, GPU utilization and CPU utilization. A five-minute repeatable run is more useful than comparing two different matches.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallIdentify a GPU-bound system
Your GPU is the likely limit when utilization stays close to full while one or more CPU cores have headroom. In that case, reduce the amount of work each frame asks the GPU to perform: render resolution, upscaling mode, shadows, volumetric lighting, reflections and anti-aliasing are the highest-value places to start.
#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
Identify a CPU-bound system
If GPU utilization is well below its ceiling and one or more CPU threads are saturated, lowering resolution may produce little or no FPS gain. Look instead for CPU-heavy controls exposed by the game, such as view distance, object or crowd density, simulation quality and effects. Close background recording, browser tabs and overlays that compete for CPU time, then retest.
Why low-percentile FPS matters
Average FPS can hide the hitch that you feel when a fight starts. Low-percentile FPS and frame-time graphs reveal whether the game delivers evenly spaced frames. A lower but steady cap is often easier to aim with than a higher average interrupted by large spikes.
2. Change settings in the order that usually returns the most performance
Use this sequence, making one change or one closely related group at a time. Keep a short log of the setting, average FPS, low-percentile FPS or frame-time result, image artifacts and whether distant targets remain easy to see.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitches- Confirm the bottleneck. Check GPU load, per-core CPU load, resolution and frame-time behavior in the same test route.
- Activate the game’s integrated upscaler. Start with a quality-oriented DLSS or FSR mode. Move to balanced or performance only when the GPU is still the limit and target detail remains readable.
- Lower expensive lighting. Reduce shadow quality or shadow distance, volumetric lighting or fog, screen-space or ray-traced reflections, ambient occlusion and heavy post-processing.
- Tune anti-aliasing. Lower the sample count or select a lighter method if edge shimmer is acceptable, but keep enough anti-aliasing to preserve target outlines at your chosen resolution.
- Protect texture quality. Keep textures high when VRAM is comfortable. Lower them only when the memory meter is full, textures pop in, or streaming causes stutter.
- Separate latency tuning from FPS tuning. Enable a supported in-game latency feature such as NVIDIA Reflex and evaluate responsiveness and frame-time consistency independently from average FPS.
- Choose a display mode and cap deliberately. Test exclusive fullscreen or the game’s recommended low-latency mode against borderless mode. Cap FPS at a level the system can sustain with headroom.
- Retest after every meaningful change. Restore the previous value if the visual cost is greater than the measured benefit.
3. Use upscaling without sacrificing target visibility
Native resolution versus upscaling
Native rendering draws every frame at the display resolution, giving the clearest fine detail but the highest GPU workload. An upscaler renders internally at a lower resolution and reconstructs a higher-resolution output. This can deliver a substantial GPU workload reduction while retaining more detail than simply selecting a very low output resolution.
| Option | Strength | Cost or risk | When to choose it |
|---|---|---|---|
| Native resolution | Maximum fine-detail clarity and predictable edges | Highest GPU load | Your GPU maintains the desired cap and distant targets are easiest to read natively |
| Quality upscaling | Lower render cost with relatively small clarity loss | Possible reconstruction shimmer or ghosting | First choice for a GPU-bound system |
| Balanced upscaling | More FPS headroom than Quality | More visible softness and temporal artifacts | Use when Quality still misses your cap |
| Performance upscaling | Largest reduction in internal render cost | Fine target detail and thin geometry can degrade | Only when the GPU remains the bottleneck and visibility is acceptable |
DLSS Super Resolution
In supported games and on compatible NVIDIA hardware, DLSS Super Resolution reconstructs a higher-resolution frame from a lower-resolution render. Select it in the game’s graphics menu rather than forcing a generic driver scale. Start with Quality, compare distant target readability, then try Balanced or Performance only if your measurements show that the GPU is still limiting FPS.
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
FSR integrated in the game
AMD recommends the game’s built-in FSR implementation when available, because game-specific integration and tuning can produce a better result than a driver-level spatial scaler. The same visibility test applies: inspect foliage, thin rails, wires and moving opponents at typical engagement distances before accepting a more aggressive mode.
Radeon Super Resolution (RSR)
Radeon Super Resolution is an in-driver spatial upscaler for games that do not offer integrated upscaling. It requires the game to run below the display’s native resolution and compatible Radeon hardware and software. Use a per-game Radeon profile, select a lower in-game resolution, and let RSR scale it to the display. If the game has FSR, prefer that integrated option instead.
Do not stack incompatible reconstruction features
DLSS Super Resolution, DLSS Frame Generation, DLAA and Reflex are separate features whose availability depends on the game and its implementation. NVIDIA warns against combining native DLSS Frame Generation with Smooth Motion: doing so can reduce performance and introduce visual artifacts. Treat each feature as an independent test variable and record the result.
4. Reduce lighting and post-processing before lowering textures
Shadows and shadow distance
Lower shadow quality or the distance at which high-quality shadows are drawn. These settings can be expensive and often have less impact on target readability than texture detail. Check corners, doorways and outdoor cover after each change; overly low settings can remove useful visual cues.
Volumetric lighting and fog
Volumetric fog, lighting shafts and cloud-like effects require substantial per-pixel work. Move from High to Medium before making larger cuts elsewhere. In NVIDIA’s Control control-panel guide, reducing Volumetric Lighting from High to Medium produced about 9–11 additional FPS on that specific test system; that figure is title- and hardware-specific, not a universal shooter result.
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
Reflections and ambient occlusion
Screen-space reflections and ray-traced reflections can be costly, especially in wet areas or maps with many reflective surfaces. Lower or disable them when they do not help you identify opponents. Ambient occlusion adds contact shading but is another sensible reduction when the GPU is saturated.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Post-processing and motion effects
Lower heavy post-processing and disable motion blur, film grain and chromatic aberration when they obscure movement. These effects may not all be major FPS consumers, but removing them can improve target separation and make the visual cost of other reductions easier to judge.
5. Tune anti-aliasing deliberately
Anti-aliasing reduces jagged edges, but higher sample counts cost performance. AMD describes the trade-off directly: anti-aliasing improves image quality while lowering FPS, with higher levels costing more. Test a lower sample count or lighter method, then inspect thin geometry and moving targets for shimmer. Do not disable anti-aliasing automatically if the resulting crawl makes opponents harder to track; a modestly lower method can be a better compromise than Off.
When using an upscaler, compare its own anti-aliasing and sharpening behavior before adding extra driver-level sharpening. Excessive sharpening can create halos around silhouettes and make compression noise look like movement.
6. Keep textures high until VRAM or streaming becomes the problem
Texture quality primarily consumes video memory and storage bandwidth rather than raw shader throughput. If your VRAM meter remains below its limit and you see no texture pop-in or streaming hitch, leave textures at the highest reliable level. Lower them when memory pressure causes stutter, surfaces appear late, or the game reports that the texture budget is exceeded.
Free tools Windows power users keep installed
One-click scans. No signup required.
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
| Texture symptom | Likely action |
|---|---|
| Sharp textures, stable frame times and unused VRAM | Keep the current texture level; reduce shadows or volumetrics first if GPU-bound |
| Texture pop-in or missing detail during movement | Lower texture quality one step and retest streaming |
| Stutter when entering new areas with a nearly full VRAM meter | Lower textures, close competing GPU applications and retest the same route |
| Low GPU utilization with a saturated CPU thread | Texture changes are unlikely to fix the bottleneck; tune CPU-heavy settings instead |
7. Reduce input latency separately from average FPS
NVIDIA Reflex
NVIDIA Reflex reduces system latency by synchronizing CPU and GPU work so input appears on screen faster, particularly in competitive games. Enable Reflex in the game when supported, then judge mouse response and frame-time consistency in an actual practice session. Reflex is not a guaranteed average-FPS boost; it addresses the path from input to displayed frame.
Frame generation
Frame generation can increase the displayed frame count by inserting generated frames, making camera motion look smoother. It does not replace a sufficiently high base render rate: the generated image still depends on the latency and cadence of the real frames. For a competitive shooter, compare aiming feel and artifact behavior with it off and on rather than selecting it solely because the overlay reports a larger number.
Driver settings and shader cache
Keep driver overrides in a per-game profile. Global overrides can change image quality or latency in other titles. On Radeon software, shader cache stores compiled shaders so games can load faster and use less CPU instead of recompiling them repeatedly. Clearing a shader cache can force a temporary recompilation period; allow the game to rebuild it before judging stutter.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.8. Select display mode, VRR behavior and a sustainable frame cap
Fullscreen versus borderless
Test exclusive fullscreen, when the game offers it, against borderless mode and the game’s recommended low-latency option. Keep the mode that gives the most consistent frame times and reliable alt-tab behavior on your system; the result can vary by game and operating-system configuration.
Recommended Free Tools
Frame-cap method
Set a cap that the system can hold during the heaviest fight, not the peak it reaches in an empty hallway. Leave CPU and GPU headroom for effects and asset streaming. A lower stable cap can reduce heat, fan noise and frame-time spikes while keeping input consistent. The ideal value depends on monitor refresh rate, variable-refresh-rate behavior and available headroom, so measure rather than copying a universal number.
| Cap strategy | Benefit | Trade-off |
|---|---|---|
| Uncapped | Chases the lowest possible render latency when the system is never saturated | Can create heat, noise and uneven frame times |
| High cap near the monitor limit | More responsiveness when the system can sustain it | May oscillate during fights and trigger VRR limits |
| Lower sustainable cap | Predictable frame times and more thermal headroom | Lower peak FPS than an uncapped run |
9. What to lower when FPS is still low
GPU-bound after the first pass
- Move from native resolution to Quality upscaling, then Balanced if necessary.
- Lower shadows, volumetrics, reflections and ambient occlusion.
- Reduce anti-aliasing samples and inspect target readability.
- Lower textures only if VRAM pressure or streaming problems are present.
CPU-bound after the first pass
- Lower view distance, object density, simulation and CPU-heavy effects when available.
- Close background capture, browser and overlay processes.
- Check for a single saturated CPU thread rather than relying on total CPU percentage.
- Keep resolution and GPU quality unchanged if the GPU is waiting on the CPU; those cuts may make the image worse without raising FPS.
Stutter despite a high average FPS
- Use the same route to determine whether spikes occur during shader compilation or asset streaming.
- Check VRAM usage and lower textures if the budget is exceeded.
- Allow the game’s shader cache to rebuild after a driver or game update.
- Use a sustainable cap and compare frame-time graphs, not just the average counter.
10. A practical test worksheet
For each run, record the following in a simple note:
- Resolution, display mode, refresh rate and VRR state.
- Upscaler and mode (Native, Quality, Balanced or Performance).
- Shadow, volumetric, reflection, anti-aliasing and texture levels.
- Frame cap and whether Reflex or frame generation is enabled.
- Average FPS, low-percentile FPS or the worst recurring frame-time spike.
- GPU utilization, busiest CPU-thread utilization and VRAM usage.
- Visibility notes: distant target clarity, edge shimmer, ghosting, pop-in and distracting effects.
Change only one line or one tightly related group between runs. Keep the setting when the measured gain is meaningful and the visual cost is acceptable; otherwise restore the previous value. This process prevents a common mistake: lowering several options at once, gaining FPS, and then being unable to tell which change damaged image quality.
Quick Recap
11. Decision table for common competitive priorities
| Priority | Recommended emphasis | Avoid first |
|---|---|---|
| Maximum target clarity | Native or Quality upscaling, moderate anti-aliasing, high textures, reduced shadows and volumetrics | Performance upscaling and excessive sharpening |
| Highest stable FPS on a GPU-bound system | Quality then Balanced upscaling, lower shadows, volumetrics, reflections and anti-aliasing | Lowering textures while VRAM is not constrained |
| Lowest input latency | High sustainable cap, supported Reflex mode, consistent frame times and a tested low-latency display mode | Relying on frame generation to compensate for a low base FPS |
| Eliminating streaming stutter | Texture level within VRAM budget, shader-cache completion and a cap with headroom | Chasing a peak FPS that leaves no memory or thermal margin |
12. The key principles to keep
- Measure the bottleneck before changing quality.
- Prefer integrated DLSS or FSR; reserve driver-level RSR for games without an in-game upscaler.
- Reduce shadows, volumetrics, reflections and heavy anti-aliasing before sacrificing textures that your VRAM can handle.
- Treat Reflex, frame generation, display mode and frame caps as latency and consistency decisions, not simple FPS toggles.
- Judge success by stable frame times and readable opponents in the same test route, not by one peak number.
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.
