Overwatch 2 runs on the same engine as the original Overwatch — a custom Blizzard engine based on 2016 technology. This has two sides: it's relatively lightweight for modern PCs, but it also has optimization quirks that many people overlook. If your FPS is below expectations or you get stutters in teamfights, the fix is in the system.
Why Overwatch 2 Can Be Demanding Even on Good PCs
Overwatch 2 is much more CPU-bound than GPU-bound — processing abilities from 10 simultaneous heroes, projectile physics, and network synchronization overloads the CPU even at low graphics settings.
- 5v5 teamfights: peak processing of particles, ability effects, and collision geometry
- Shader compilation stutters: the first time certain effects appear, there's a micro-freeze from compilation
- DPC Latency: like any online game, driver interrupts cause micro-stutters
- Misconfigured Render Scale: 100% render scale on a 1440p monitor is much heavier than it seems
Overwatch 2 Settings for Maximum FPS
Display and Rendering
- Display Mode: Exclusive Fullscreen — always
- Resolution: monitor's native
- Render Scale: 75% is the ideal sweet spot. 100% is heavier without proportional visual gain at high resolutions
- Frame Rate: Custom → set to 3x your monitor's Hz (144Hz monitor → 432 FPS cap)
- VSync: Disabled
- Triple Buffering: Disabled
- NVIDIA Reflex: Enabled + Boost (if available)
Graphics Quality
- High Quality Upsampling: AMD FSR 1.0 or NVIDIA DLSS (if RTX)
- Texture Quality: Low (minimal impact on hero visibility)
- Texture Filtering: 1x Bilinear
- Local Fog Detail: Low
- Dynamic Reflections: Off
- Shadow Detail: Off
- Model Detail: Low
- Effects Detail: Low — important for enemy ability visibility
- Lighting Quality: Low
- Antialias: Off
- Refraction Quality: Low
- Screenshot Quality: 1x
- Ambient Occlusion: Off
- Local Reflections: Off
- Damage FX: Off (improves visibility and FPS)
Windows Tweaks for Overwatch 2
Disable the Battle.net Launcher Overlay
The Battle.net overlay adds hooks to the audio and input system, similar to the Xbox Game Bar. Disable it in Battle.net settings → In-Game → uncheck all overlay options during gameplay.
CPU Affinity
Overwatch 2 benefits from high single-core frequency CPUs. On Intel with E-cores (12th, 13th, 14th gen), set the OW2 process affinity to use only P-cores via Task Manager → Details.
High Priority for OW2
With the game running, set High priority for Overwatch.exe in Task Manager → Details. This ensures Windows prioritizes OW2 in CPU cycle distribution.
Exclusive tips
Want more guides like this?
Leave your email and we'll let you know when a new optimization guide drops. No spam, unsubscribe anytime.
Only optimization guides worth your time. Unsubscribe anytime.
UPBOOST does all of this for you in 20 minutes
Forget tutorials. Our technicians apply all these optimizations, and much more, remotely and live, while you watch every step.
Eliminate Shader Compilation Stutters
Overwatch 2 compiles shaders the first time certain effects appear. To "warm up" the shaders, play in Practice Range with each hero for a few minutes — this forces shader compilation in a safe environment.
Overwatch 2 in Competitive: Why FPS Above 144 Matters
Even on a 60Hz monitor, running above 60 FPS reduces render latency — the time it takes the CPU/GPU to process the frame you see. At 300 FPS on a 144Hz monitor, render latency is 3.3ms. At 60 FPS, it's 16.6ms. For a game where Tracer flanks happen in split seconds, that difference is real.
What UPBOOST Applies for Overwatch 2
Advanced scheduler settings to favor the OW2 process, DPC Latency elimination to reduce micro-stutters in teamfights, and network tweaks for less jitter in ranked matches. Customers report much more stable FPS and elimination of micro-freezes that appear during ultimate combos.
Frequently asked questions
75% is the best value for most players. With upsampling (FSR or DLSS), the visual difference from 100% is minimal but the FPS gain is 20-40%. At native 1080p, 100% is fine. At 1440p or 4K, 75% makes a huge difference.