Overwatch 2 refreshed the original with an engine update focused on larger maps and better lighting, while maintaining excellent optimization. The shift to a 5v5 format slightly reduced the visual clutter, helping with frame rate stability. NVIDIA Reflex is essential for reducing latency, supported on GTX 900 series and up. While minimum specs are low, competitive play at 144Hz+ requires a reasonably modern CPU (Intel Skylake / Ryzen Zen 1 or newer) to handle the fast-paced physics and game state updates.
Actual FPS may vary based on RAM speed, background processes, and other system factors
Performance Report
At 1080p, all quality settings exceed 182 FPS, suitable for 144Hz+ monitors. At 1440p, all settings exceed 119 FPS. At 4K, frame rates range from 36 to 79 FPS.
The GeForce RTX 3060 is 69% above the recommended GPU (GeForce GTX 1060) for Overwatch 2. The Ryzen 5 5600X is 141% above the recommended CPU (Core i7-4770).
At lower resolutions (1080p low, all 4k settings), the Ryzen 5 5600X sets the FPS ceiling. As graphical load increases at (all 1440p settings), the GeForce RTX 3060 becomes the FPS-limiting side. The FPS ceiling is closely matched at 1080p (medium/high/ultra).
Approximated average price on current market:
Combo price: $424. At 1080p Ultra, this combo delivers 182 FPS, equivalent to 0.43 FPS per dollar.
| Resolution | Low | Medium | High | Ultra |
|---|---|---|---|---|
| 1080p | 0.743 fps/$ | 0.634 fps/$ | 0.545 fps/$ | 0.429 fps/$ |
| 1440p | 0.495 fps/$ | 0.408 fps/$ | 0.335 fps/$ | 0.281 fps/$ |
| 4k | 0.186 fps/$ | 0.142 fps/$ | 0.106 fps/$ | 0.085 fps/$ |
* Table values represent FPS per Dollar (higher is better)
This section is based on estimated CPU/GPU FPS ceilings, not utilization percentages.
At 4k low, the Ryzen 5 5600X sets the ceiling at about 98 FPS, while the GeForce RTX 3060 could reach 186 FPS. In this scenario, the CPU limits the GPU potential by 47% (FPS gap: 88 FPS). Overall distribution: CPU limits 5/12 cells, GPU limits 4/12, balanced 3/12.
Your Ryzen 5 5600X is the limiting side in the heaviest mismatch. This means part of the GeForce RTX 3060 rendering potential remains unused in those settings.
| Resolution | Low | Medium | High | Ultra |
|---|---|---|---|---|
| 1080p (Full HD) | CPU Limits GPU 8% | Balanced | Balanced | Balanced |
| 1440p (2K QHD) | GPU Limits CPU 16% | GPU Limits CPU 23% | GPU Limits CPU 26% | GPU Limits CPU 27% |
| 4K (Ultra HD) | CPU Limits GPU 47% | CPU Limits GPU 40% | CPU Limits GPU 24% | CPU Limits GPU 26% |
We estimate the maximum FPS the processor can sustain and the maximum FPS the graphics card can sustain in each setting, then compare those limits directly.
Limit Factor formula: (stronger - weaker) / stronger. Example: if CPU ceiling is 200 FPS and GPU ceiling is 140 FPS, then GPU limits CPU by 30%.
CPU Limits GPU means the processor ceiling is lower. GPU Limits CPU means the graphics ceiling is lower. Balanced means the FPS ceilings are close enough that the gap is negligible.
A component can still be the FPS limiter without reaching 100% utilization. The displayed percentages are derived from FPS ceilings, not generic utilization heuristics.
| Resolution | Low | Medium | High | Ultra |
|---|---|---|---|---|
| 1080p (Full HD) | CPU35% - 61% <> GPU74% - 84% <> | CPU33% - 61% <> GPU81% - 87% <> | CPU33% - 61% <> GPU81% - 87% <> | CPU30% - 60% <> GPU95% - 100% <> |
| 1440p (2K QHD) | CPU41% - 66% <> GPU71% - 86% <> | CPU40% - 66% <> GPU78% - 89% <> | CPU40% - 66% <> GPU78% - 89% <> | CPU36% - 66% <> GPU89% - 100% <> |
| 4K (Ultra HD) | CPU42% - 71% <> GPU71% - 86% <> | CPU40% - 71% <> GPU78% - 89% <> | CPU40% - 71% <> GPU78% - 89% <> | CPU37% - 71% <> GPU90% - 100% <> |
The Ryzen 5 5600X + GeForce RTX 3060 pairing runs this title with CPU utilization between 30% and 71% and GPU utilization between 71% and 100%. Ryzen 5 5600X keeps significant headroom across presets, while GeForce RTX 3060 carries most of the graphics load at heavier visual settings. As resolution scales, average GPU load rises from 86% at 1080p to 85% at 4K, while CPU averages move from 47% to 56%.
From a utilization perspective, this is a GPU-heavy load profile. At 1080p (Full HD) Ultra, the GeForce RTX 3060 averages 98% usage (95-100%), while the Ryzen 5 5600X stays at 45% (30-60%). This shows the graphics pipeline is carrying most of the workload, but utilization alone does not define the FPS limiter.
At 1080p, averages sit around CPU 47% and GPU 86%. At 1440p, that shifts to CPU 53% and GPU 85%, and at 4K it reaches CPU 56% and GPU 85%. This shows that workload scaling is present on both components, with stronger pressure on the GPU.
1080p (Full HD) Medium is the most balanced preset based on this dataset. It runs around CPU 47% (33-61%) and GPU 84% (81-87%), which keeps GeForce RTX 3060 well utilized without constant max-out behavior while Ryzen 5 5600X remains stable for consistent frame delivery.
Upgrade priority should be the GPU. The GeForce RTX 3060 reaches 98% average load at 1080p (Full HD) Ultra while the Ryzen 5 5600X still has headroom, so a faster graphics card would deliver the largest uplift.
Understanding Hardware Utilization: These percentages represent how much of your component's maximum processing power is actively being used during gameplay. They describe hardware load, but they do not directly tell you which component sets the FPS ceiling.
Important: a CPU or GPU can still be the FPS limiter without reaching 100% utilization. Two processors can both show 40% usage and still deliver very different frame rates, depending on per-core speed, cache, engine threading, driver overhead, and frame preparation efficiency.
Data generated by our Machine Learning engine trained on real-world benchmarks. Shows the approximate average utilization at each setting.
See how your processor and graphics card compare against the game official minimum and recommended system specs. The placement of your hardware is calculated using relative synthetic performance scores to help you gauge overall playability.
Your CPU is 141% above and your GPU is 69% above the recommended specs. Ultra settings at 1080p, or High at 1440p/4K.
+141%vsrecommended
+69%vsrecommended
+1230%vsminimum
+795%vsminimum
Yes, the Ryzen 5 5600X paired with the GeForce RTX 3060 can run Overwatch 2 smoothly up to 1440p achieving around 119 FPS at Ultra quality. Your GPU is 69% above the recommended specs, and your CPU is 141% above the recommended requirements.
This CPU + GPU combo costs approximately $424 ($135 CPU (Rank #39 Value) + $289 GPU (Rank #30 Value)). Your build is already very cost-efficient, but if you want even more FPS, the next good option is upgrading the CPU. For example, the Ryzen 9 9950X is a great upgrade option for around $649 (Rank #5 for value).
For Overwatch 2, upgrading the CPU would have the biggest impact on performance. The Ryzen 5 5600X is currently the limiting factor — the GeForce RTX 3060 has extra headroom that a faster processor could take advantage of. This is especially noticeable at 1080p where CPU performance matters more. CPU-limited at: 1080p low, 4k low, 4k medium, 4k high, 4k ultra. GPU-limited at: 1440p low, 1440p medium, 1440p high, 1440p ultra.
Overwatch 2 does not currently support Frame Generation technologies like DLSS 3 or FSR 3. Your performance is based entirely on native rendering. If the game adds support in a future update, newer GPUs will benefit the most.
Overwatch 2 requires at minimum a Core i3-560 (CPU) and GeForce GTX 600 series (GPU) with 6 GB RAM and 50 GB storage. For the recommended experience, you need a Core i7-4770 and GeForce GTX 1060 with 8 GB RAM. Your Ryzen 5 5600X and GeForce RTX 3060 both exceed the recommended specs, so you're well-positioned for a great experience.
These Overwatch 2 FPS results are not arbitrary numbers. They come from calculations informed by thousands of real gaming benchmarks, and the typical accuracy range is around 10% to 15%. That makes them far more useful than generic FPS calculators that simply invent values without a benchmark foundation. Actual in-game performance can still vary with drivers, updates, RAM configuration, cooling, and the exact scene being rendered.
Performance estimates are based on synthetic benchmarks and hardware capabilities.
Results may vary based on drivers, OS, and background processes.
