Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteOverwatch 2 on Windows PC is often CPU-limited when you target high frame rates at 1080p with competitive settings, but it can become GPU-limited at higher resolutions, render scales, and visual quality. There is no permanent answer for every PC: the useful question is whether your CPU or GPU is taking longer to prepare each frame on your settings, in the scenes where performance drops.
Which component is more likely to limit Overwatch 2?
Use this as a starting point, not a diagnosis. Your hardware, live game build, settings, frame cap, and the scene all matter.
| Situation | More likely constraint | What to check |
|---|---|---|
| 1080p, low settings, uncapped play aimed at 144–360 Hz | CPU or game/render thread | Whether lowering resolution changes FPS; CPU and GPU frame times |
| 1080p with high visual settings and an older graphics card | GPU or mixed | GPU frame time, utilization, temperature, and VRAM |
| 1440p or 4K at high settings | GPU or mixed | Whether lowering resolution or render scale substantially raises FPS |
| Frame drops in busy team fights at low settings | CPU/engine is plausible; effects may also load the GPU | Compare frame times and repeat the test in the same scene |
| Low GPU utilization with FPS fixed at a precise ceiling | Frame cap or synchronization may be limiting first | Check the in-game cap, V-Sync, driver limiter, and overlays |
Blizzard’s published system requirements name a Core i7 or Ryzen 5-class CPU and GPUs such as the GTX 1060/GTX 1650, Radeon R9 380/RX 6400, or Intel Arc A770 as recommended options. They do not promise 144-, 240-, or 360-FPS performance. See Blizzard’s Overwatch 2 system requirements.
What CPU-bound and GPU-bound mean
The CPU handles work such as game simulation, player and ability logic, visibility, physics, and preparing commands for the graphics card. The GPU renders the scene. In a simplified pipeline, the slower side sets the pace:
#1 Best Overall
- Powered by Radeon RX 9070 XT
- WINDFORCE Cooling System
- Hawk Fan
- Server-grade Thermal Conductive Gel
- RGB Lighting
Frame time = max(CPU frame time, GPU frame time)FPS ≈ 1000 ÷ frame time in milliseconds
If CPU frame time is 8 ms and GPU frame time is 4 ms, the system is limited to roughly 125 FPS by the slower CPU side. If both take about 4 ms, the rough ceiling is 250 FPS. These are illustrative calculations, not Overwatch benchmarks; actual performance also depends on pacing and other system constraints.
At high refresh rates, a few milliseconds matter. Total CPU usage can look modest on a many-core processor even when one important game thread is heavily loaded. Likewise, a powerful GPU can show less than full utilization when it is waiting for the CPU to submit work. Utilization percentage alone does not identify the bottleneck.
Why Overwatch 2 can be CPU-limited
Competitive settings often reduce the GPU’s rendering workload. At 1080p and low quality, the processor may have to prepare frames faster than the GPU can render them, especially when the target is a very high uncapped frame rate. Crowded fights and ability-heavy scenes can also increase game simulation, animation, visibility, and rendering-submission work.
A CPU-side limit is more plausible when reducing resolution makes little difference, the GPU is not consistently busy, or drops cluster around busy scenes. It is not proven by those symptoms alone: a cap, driver issue, thermal or power limit, or patch-specific problem can look similar.
Rank #2
- NVIDIA Ampere Streaming Multiprocessors: The all-new Ampere SM brings 2X the FP32 throughput and improved power efficiency.
- 2nd Generation RT Cores: Experience 2X the throughput of 1st gen RT Cores, plus concurrent RT and shading for a whole new level of ray-tracing performance.
- 3rd Generation Tensor Cores: Get up to 2X the throughput with structural sparsity and advanced AI algorithms such as DLSS. These cores deliver a massive boost in game performance and all-new AI capabilities.
- Axial-tech fan design features a smaller fan hub that facilitates longer blades and a barrier ring that increases downward air pressure.
- OC Mode : 1500 MHz (Boost Clock)/Default Mode : 1470 MHz (Boost Clock)
Players have reported low GPU utilization and little FPS change after reducing resolution on Blizzard’s technical-support forums. These are individual reports, not controlled benchmarks or official diagnoses: one report about reduced FPS and GPU utilization and one report of performance degradation after Season 20.
When the GPU is more likely to be the limit
Higher output resolution, render scale above 100%, demanding anti-aliasing, lighting, shadows, effects, and post-processing increase graphics work. High-resolution or ultrawide displays can do the same. Laptop GPUs may also be constrained by cooling or power limits. If lowering resolution or render scale substantially improves FPS and GPU frame time is dominant, the GPU is a stronger suspect.
VRAM is a separate concern from raw rendering speed. Near-capacity VRAM can contribute to stutter, lockups, or crashes, not just lower average FPS. Blizzard warns that performance problems can occur when the game’s VRAM use approaches the amount available on the GPU; consult its performance and network diagnostics.
Run a repeatable bottleneck test
- Remove avoidable variables. Restart the PC and close unnecessary applications, browsers, recording tools, launchers, and overlays. Keep the same driver, power mode, and background conditions across test runs.
- Choose a repeatable scene. The Practice Range is convenient but may not represent a match. A replay or repeatable custom-game scenario is more useful for comparisons; include a busy fight if that is where your drops happen.
- Record a baseline. Note average FPS, 1% lows or a frame-time graph, GPU utilization and clock, per-core CPU load, temperatures, VRAM and system RAM use, and whether an FPS cap or V-Sync is active. Use the same tool and scene for each run.
- Change resolution or render scale substantially. Keep other settings and the test scene unchanged. If FPS rises substantially, the GPU was likely doing a meaningful share of the limiting work. If FPS barely moves, investigate CPU-side work, caps, and software or engine issues.
- Change graphics quality separately. Raise or lower quality while keeping resolution and the cap fixed. A predictable FPS change suggests the GPU workload matters; no change can mean another limit is reached first.
- Compare frame times, not just percentages. The higher CPU or GPU frame time is generally the more direct clue to the slower side. Repeat runs if results vary, and judge frame-time consistency as well as the average.
Blizzard’s built-in performance display is toggled with Shift + Ctrl + R by default on PC. Blizzard documents FPS, GPU temperature, VRAM, simulation time, latency, interpolation delay, and command-queue information in its diagnostic guide.
Interpret the result without mistaking symptoms for causes
| Observation | Likely interpretation | Next test |
|---|---|---|
| Lower resolution barely changes FPS; GPU is below sustained full load | CPU/game-thread limit is possible, but not confirmed | Compare CPU and GPU frame times; check caps, clocks, thermals, and background load |
| One CPU thread is heavily loaded while total CPU use is moderate | A CPU-side limit can exist without 100% total CPU usage | Check whether the same scene has elevated CPU frame time |
| Lower resolution yields a large FPS gain; GPU stays near its sustained maximum | GPU limit is likely | Check GPU frame time, temperature, power behavior, and VRAM |
| FPS stops at a precise value and both CPU and GPU use look low | A cap or synchronization setting may be active | Check game, driver, and third-party limits, plus V-Sync |
| Average FPS is high but motion feels uneven | Frame-time spikes can undermine smoothness | Inspect 1% lows, frame-time spikes, shader compilation, VRAM, and background recording |
| FPS is acceptable but ping, interpolation delay, or command-queue indicators are abnormal | Network symptoms may be separate from rendering performance | Use Blizzard’s network diagnostics rather than treating every hitch as a GPU or CPU problem |
Network delay, simulation performance, and rendering performance are different things. High ping or interpolation delay can make play feel unresponsive without showing that the GPU is too slow; FPS drops and frame-time spikes need their own measurements.
Rank #3
- Powered by the NVIDIA Blackwell architecture and DLSS 4. System Requirements: Minimum 850W PSU with 16-pin 12V-2x6 (12VHPWR) connector required. Verify before purchasing.
- Military-grade components deliver rock-solid power and longer lifespan for ultimate durability. Compatibility: 348mm (13.7") length, 3.6 slots, 4.3 lbs. Confirm case clearance and slot spacing. GPU bracket included.
- Protective PCB coating helps protect against short circuits caused by moisture, dust, or debris
- 3.6-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
Settings and system factors to check
Settings that commonly raise GPU work
- Output resolution and render scale, especially a scale above 100%.
- Anti-aliasing, shadows, lighting, effects, fog, model detail, local reflections, and post-processing. Their impact varies by scene and system; no setting affects only one component in every case.
- Dynamic Render Scale is intended to adjust resolution within minimum and maximum scales to help when GPU performance is constrained. Its current label and behavior can vary with the live build; Blizzard described the feature in its beta patch notes.
Settings and conditions that can hide the result
- V-Sync, the in-game FPS limit, driver-level limiters, and third-party overlays can cap the output. The documented V-Sync path is Main Menu > Options > Video > VSync.
- Laptop battery operation, a quiet or restrictive power profile, overheating, or incorrect selection of the integrated GPU can reduce performance.
- Low system RAM, nearly full VRAM, background recording, and overlays can cause stutter or inconsistent results.
- Drivers, shader compilation, a recent patch, or the game’s graphics API can change frame times. A before-and-after result from a different build is not directly comparable.
DirectX 11 or DirectX 12?
Blizzard identifies DirectX 11 as the lead API and DirectX 12 as a beta option. DX12 may help some systems, but Blizzard warns it can reduce performance or introduce stutter on others; newer does not automatically mean faster. To compare, use the same scene, settings, and measurement method for each API, restart as prompted, and keep the one that performs more consistently on your PC.
The documented path is Options > Video > Graphics API, then select DirectX 12 and restart. Blizzard’s DX12 announcement lists a DirectX 12 Ultimate Feature Level 12_2-compatible GPU and Windows 10 version 1909 or later as requirements; meeting them does not guarantee a performance improvement. See Blizzard’s DirectX 12 beta announcement.
Should you upgrade the CPU or GPU?
Choose a CPU upgrade when measurements support it
- Your goal is high refresh-rate play, particularly at 1080p or low settings.
- Lowering resolution barely improves FPS, and CPU frame time is the higher one.
- Busy fights hurt 1% lows or frame pacing more than quiet scenes.
- Your existing GPU is not already the limiting component.
Before choosing a processor, check motherboard compatibility, BIOS support, memory, cooling, and the cost of changing platforms. A CPU purchase is poor value if a frame cap or GPU limit is what holds performance back.
Choose a GPU upgrade when measurements support it
- You play at 1440p or 4K, use a high render scale, or want higher visual quality.
- GPU frame time is higher, utilization remains near its sustained maximum, and reducing resolution brings a meaningful FPS gain.
- VRAM capacity or GPU-side thermal or power limits are part of the problem.
Match the graphics card to your resolution and image-quality target, and check power supply and case compatibility. A stronger GPU is unlikely to fix a confirmed CPU-side frame-time limit.
Troubleshoot before spending money
- Check for caps. Confirm the in-game limit, V-Sync, driver software limits, and overlay settings. For a test, disable V-Sync through Main Menu > Options > Video > VSync and set a cap above the FPS you are measuring.
- Check power, clocks, and temperatures. On a laptop, test while plugged in and confirm the game uses the intended GPU. Look for clock drops or thermal and power limits during the same scene.
- Reduce background interference. Test without recording, overlays, and unnecessary applications. If monitoring overlays appear to change the result, record a baseline with them disabled.
- Check drivers and game settings. Update or, if a problem started after a driver change, test a known-good driver. Blizzard’s documented reset path is Main Menu > Options > Reset All Defaults; its technical troubleshooting guide also includes driver and background-program checks.
- Compare graphics APIs carefully. Test DX11 and DX12 under the same conditions; keep DX11 if DX12 adds stutter or lowers performance.
- Consider a patch-specific change. Blizzard continues to publish live updates; its live patch notes show the game changes over time. A reproducible drop after an update may be game-build-specific, so avoid treating one old benchmark or one unusually bad match as a hardware verdict.
If the game crashes or locks up, check VRAM use, driver stability, overheating, and game files as well as performance. Near-capacity VRAM is one documented risk factor, but the symptom alone does not identify the cause.
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.
