Overwatch 2 has a reputation for being one of the better-optimized shooters on PC — a GTX 660 can technically meet the recommended spec, and real-world testing confirms budget hardware punches above its weight here. But “technically playable” and “consistently above 60 FPS in team fights” are two different things. This guide covers every meaningful video setting, the FPS cost of each, and config file edits the in-game menu never exposes.
Settings verified on Overwatch 2, March 2026. Applicable to all maps and modes unless noted.
Quick Start Checklist
The short version before the full breakdown:
- Set Display Mode to Fullscreen (not borderless)
- Set Render Scale to Custom: 75%
- Turn V-Sync Off, turn Reduce Buffering On
- Enable NVIDIA Reflex + Boost (NVIDIA GPUs only)
- Set Antialias Quality to Off
- Set Shadow Detail to Off
- Set Dynamic Reflections to Off
- Set Refraction Quality to Low
- Cap Frame Rate to 600 in-game
- Set Texture Quality to match your VRAM: Low for 2 GB, Medium for 4 GB+
These changes target 60+ FPS on systems with an Intel Core i3/i5 and a GPU in the GTX 1050 to GTX 1060 range, and 40+ FPS on older GTX 900-series hardware.
We cover the exact settings in starfield low end pc to maximise performance.
Can Your PC Run Overwatch 2?
Blizzard’s official minimum bar is genuinely low — a 2012-era GPU and a Core i3. Most of the community reports that the true floor for consistently playable competitive play is a bit higher. Here is what the tiers mean in practice [1]:
| Tier | CPU | GPU | RAM | Expected FPS |
|---|---|---|---|---|
| Minimum (official) | Core i3 / AMD Phenom X3 | GTX 600 series / Radeon HD 7000 | 6 GB | 30–45 at Low |
| Recommended (official) | Core i7 / Ryzen 5 | GTX 1060 / R9 380 | 8 GB | 60+ at Medium–High |
| Budget sweet spot | Core i5 4th gen / Ryzen 3 | GTX 1050 Ti / RX 570 | 8 GB | 60–90 at optimized Low |
If your hardware sits below the minimum tier, apply every setting below before concluding the game is unplayable. Overwatch 2’s engine scales unusually well — the difference between default Low and an optimized Low is often 20–35 FPS on the same hardware.
Overwatch 2 Low-End PC Settings: Full Table
Every meaningful setting in the Video and Graphics Quality menus, the recommended value for low-end hardware, and the reason behind each change. Settings are ordered by FPS impact — highest first so you know exactly where to start.
Getting the right settings makes a big difference — see diablo low end pc for the optimal config.
| Setting | Low-End Value | FPS Impact | Why It Matters |
|---|---|---|---|
| Render Scale | Custom: 75% | Very High | Renders at 75% of output resolution then upscales. At 1080p the GPU renders 1440×810 instead of 1920×1080 — a 44% pixel reduction. 50% is available but blurs enemy outlines enough to cost you gunfights. 75% is the competitive floor. |
| Antialias Quality | Off | High | SMAA is GPU-expensive and OW2’s art style uses clean silhouettes — jaggies are far less noticeable than in photorealistic games. Off delivers the largest per-frame saving in this menu. |
| Shadow Detail | Off | High | Shadows are the most expensive rasterization pass in most games. Off eliminates this entirely — no competitive disadvantage at this quality level. |
| Display Mode | Fullscreen | High (latency) | Exclusive fullscreen bypasses the Windows Desktop Window Manager, cutting input latency by 5–15 ms vs. borderless. On low-end hardware the DWM overhead is proportionally larger — this matters more for you than for a high-end system. |
| Refraction Quality | Low | High | Water surfaces, glass, and ability VFX use expensive refraction sampling. Low eliminates the costly ray-march path [2]. |
| Dynamic Reflections | Off | Medium–High | Calculates real-time reflections on surfaces. Off replaces these with static cube maps — visually minimal difference in fast-paced competitive play. |
| High Quality Upsampling | FSR 1.0 | Medium (quality) | When Render Scale is below 100%, FSR 1.0 sharpens the upscaled image. No ghosting on moving targets (unlike temporal methods) — the safest choice for a shooter. Use DLSS if you have an RTX card; it handles motion better. |
| V-Sync | Off | Medium (latency) | Disabling removes the frame cap and prevents the input latency spike from V-Sync waiting for the next refresh cycle. On low-end hardware this spike is often multiple frames. |
| Reduce Buffering | On | Medium (latency) | Flushes the GPU command queue more aggressively. Reduces input-to-display latency — particularly important on budget systems where the CPU may queue frames ahead of time. |
| Texture Quality | Low (2 GB VRAM) / Medium (4 GB+) | Medium (VRAM) | Exceeding your VRAM triggers asset streaming from system RAM, causing stuttering regardless of average FPS. Match Texture Quality to your card’s VRAM, not your visual preference. |
| Effects Quality | Low | Medium | Controls particle VFX from abilities — explosions, projectile trails, impact flashes. Low halves the particle budget. In 6v6 team fights, this is where low-end hardware gets most stressed. |
| Lighting Quality | Low | Medium | Reduces dynamic light sources per map. Minimal visual change in OW2’s stylized art style; measurable savings during ability-heavy fights. |
| Local Fog Detail | Low | Low–Medium | Volumetric fog rendered at lower resolution and sample count. Fog is rare in competitive play areas — a near-free saving. |
| Model Detail | Low | Low–Medium | Reduces polygon count on heroes at range. Your target silhouette is unchanged — hitbox size is not affected by model quality. |
| Ambient Occlusion | Off | Low–Medium | Screen-space AO adds contact shadows under objects. Visually subtle in OW2’s bright, stylized environments — off costs nothing competitively. |
| Local Reflections | Off | Low | Screen-space reflections on floors and water. Low impact in competitive maps — safe to disable. |
| Texture Filtering Quality | Low (2x bilinear) | Very Low | Affects sharpness of textures at oblique angles. Minimal visual change in OW2’s close-quarters maps. |
| NVIDIA Reflex | On + Boost | Latency only | Reduces system latency by optimizing how the CPU queues GPU work. No FPS change — pure input lag reduction. On low-end hardware, system latency is often the bigger problem than raw FPS. |
| Frame Rate Cap | 600 | Latency | A hard cap prevents FPS spikes that cause frame time variance. 600 is effectively uncapped for most budget hardware. |
The Config File Edge: Settings_v0.ini
Overwatch 2 stores additional parameters in a config file the in-game menu doesn’t expose. Community testing has found specific values that further reduce GPU load, particularly for effects and physics rendering [3].
File location: C:\Users\[your name]\Documents\Overwatch\Settings\Settings_v0.ini
Open with Notepad and confirm or add these values:
MaxAnisotropy = "0"— forces anisotropic filtering off below what the in-game slider allows. Marginal GPU saving on older cards.EffectsQuality = "1"— matches in-game Low; confirm it’s already 1 (some installs don’t write this correctly).ModelQuality = "1"— same for model detail.PhysicsQuality = "1"— reduces cloth simulation and debris physics. Not exposed in the in-game menu.FrameRateCap = "600"— ensures the cap applies even when in-game settings reset.
After saving: right-click the file → Properties → check Read only to prevent the game from overwriting your values. This locks all future in-game setting changes from being saved — uncheck it temporarily if you need to adjust settings, then re-check afterward.
Getting the right settings makes a big difference — see diablo low end pc for the optimal config.
System Tweaks That Don’t Touch Graphics
Once in-game settings are dialed in, these OS-level changes close the remaining gap:
- Close background processes. Browsers, Discord video, and streaming software all compete for the same CPU/RAM. Leave Discord open in text-only mode if you need it.
- Set Windows Power Plan to High Performance. Control Panel → Power Options → High Performance. Prevents CPU clock throttling during sustained frame load.
- Disable Xbox Game Bar and Discord overlay. Each overlay adds 2–5 FPS overhead and measurable input latency.
- Keep GPU drivers current. Blizzard and GPU vendors co-optimize OW2 builds each major season. A two-season-old driver can cost 5–10 FPS on older hardware [4].
- Increase virtual memory if you have 8 GB RAM. OW2 regularly pushes past 8 GB in full team fights. Set paging file to 12,288 MB (System Properties → Advanced → Performance Settings → Virtual Memory) to prevent crash-causing memory exhaustion.
Settings Profiles by Hardware
One-size-fits-all “Low everything” advice ignores that a GTX 1060 can afford quality without sacrificing 60 FPS. Use the profile that matches your GPU:
| Hardware Tier | Render Scale | Texture Quality | Shadows | Expected FPS |
|---|---|---|---|---|
| Intel UHD 630 / AMD Vega 8 (iGPU) | 50% + FSR | Low | Off | 40–55 |
| GTX 950 / RX 470 / 4 GB VRAM | 75% + FSR | Low | Off | 55–70 |
| GTX 1060 / RX 580 / 6 GB VRAM | 75% | Medium | Low | 70–100 |
| GTX 1650 / RX 5500 XT / 4–8 GB VRAM | 100% | Medium–High | Medium | 90–120 |
FPS ranges are community benchmark estimates — exact results vary by CPU speed, map, and ability VFX volume. King’s Row and Numbani consistently run 15–20% heavier than open escort maps on the same settings.
For a framework that applies to any game, see our PC optimization guide and the universal graphics settings template — same methodology, any title in your library.
FAQ
Does Render Scale at 75% affect hitbox or aim accuracy?
No. Hitboxes are server-side calculations independent of visual rendering. Render Scale only changes what your GPU draws — hit registration is identical at 50% or 150%. What it does affect is the sharpness of enemy outlines at distance: 75% is the lowest value that keeps medium-range targets readable without FSR assistance.
Should I use FSR or DLSS in Overwatch 2?
If you have an NVIDIA RTX card, DLSS Super Resolution outperforms FSR 1.0 — it uses AI temporal accumulation for sharper results. FSR 1.0 is the correct choice for AMD GPUs, Intel integrated graphics, and NVIDIA GTX cards that don’t support DLSS. Avoid FSR 2.0+ in a fast-paced shooter — temporal methods introduce ghosting on rapidly moving targets.
Why is Overwatch 2 stuttering but my average FPS looks fine?
Stutter with stable average FPS is almost always a VRAM issue. If Texture Quality exceeds your GPU’s VRAM, assets stream from system RAM over the PCIe bus — this causes frame time spikes even when average FPS is steady. Lower Texture Quality by one tier first. If the stutter persists, check Task Manager for RAM usage above 90% during play and increase virtual memory as described above.
Is Overwatch 2 CPU or GPU bottlenecked on budget hardware?
Primarily GPU-bottlenecked at the settings listed. OW2’s engine distributes hero AI and physics efficiently across CPU cores. The exception is integrated graphics — on Intel UHD or AMD Vega iGPUs, the CPU and GPU share the same memory bus, making them simultaneously both the bottleneck.
Sources
- PCGamesN. Overwatch 2 system requirements — official minimum and recommended specs. PCGamesN
- ProSettings. Overwatch 2 settings and options guide — performance optimization. ProSettings.net
- Steam Community. Potatowatch 2 — low-end PC optimization guide including config file edits. Steam Community Guides
- Dexerto. Overwatch 2 best graphics settings to boost FPS and performance. Dexerto
I've been playing video games for over 20 years, spanning everything from early PC titles to modern open-world games. I started Switchblade Gaming to publish the kind of accurate, well-researched guides I always wanted to find — built on primary sources, tested in-game, and kept up to date after patches. I currently focus on Minecraft and Pokémon GO.