Counter-Strike 2 shifted from the original Source engine to Source 2, and that change has a direct cost on budget hardware. GPUs that delivered 250–350 FPS in CS:GO often produce 60–100 FPS in CS2 at default settings. The gap is almost entirely explained by three settings: Global Shadow Quality, shadow rendering, and MSAA. Disable or minimise those, and GTX 1060-class hardware crosses 100 FPS at 1080p. GTX 1650-class hardware reaches 130–160 FPS. This guide covers the exact settings, in the order that matters most. For a general explanation of what CS2’s video settings do under the hood, see the game settings explained guide. For a universal low-end template across multiple titles, see the universal settings template. For PC-wide optimisation beyond CS2 itself, see the game settings optimisation hub.
What “Low-End” Means for CS2
CS2’s official minimum specification is an Intel Core i5-750 with a GTX 970 and 8GB RAM. In practice, hardware below that floor is still broadly playable — the minimum spec defines the threshold for a stable 60 FPS experience at low settings. This guide covers three tiers:
| Tier | GPU Examples | Expected FPS (Low, 1080p) |
|---|---|---|
| Below minimum | GTX 1050 Ti (4GB), GTX 960, RX 470 | 55–80 FPS |
| At minimum | GTX 1060 6GB, RX 580, GTX 1660 | 95–135 FPS |
| Entry dedicated | GTX 1650, GTX 1650 Super, RX 5500 XT | 120–165 FPS |
Integrated graphics (Intel UHD 620, AMD Vega 8) run CS2 at 25–45 FPS at 1080p low settings — playable for casual matches but not competitive. Drop to 720p and reduce render scale to extract more frames, but a dedicated GPU is the correct fix at that tier.
Squeeze out more FPS with the settings in cities skylines low end pc.
The One Setting That Matters Most
Global Shadow Quality is the single largest FPS lever in CS2. Source 2’s shadow rendering pipeline is substantially more expensive than it was in the original Source engine, and a GTX 1060 at 1080p loses 20–35 FPS purely from moving this setting from Very Low to Medium. Set it to Very Low before touching anything else. The gameplay impact is minimal: character silhouettes, wall edges, and grenade indicators are all unaffected. Ambient occlusion, which contributes to contact shadow detail at the base of geometry, should be Disabled for the same reason — it adds GPU cost and provides no tactical advantage.
Full Low-End Settings Template
Apply all of these via Settings > Video in CS2. Every value has been chosen for maximum FPS on GTX 1060 to GTX 1650-class hardware without compromising competitive readability.
| Setting | Value | Reason |
|---|---|---|
| Resolution | 1920×1080 or 1280×960 (4:3) | See resolution section below |
| Display Mode | Fullscreen | Lowest input latency; borderless adds a frame of delay |
| Refresh Rate | Monitor maximum | Match monitor’s native refresh rate |
| Global Shadow Quality | Very Low | Largest single FPS gain in CS2 — saves 20–35 FPS on GTX 1060 |
| Model/Texture Detail | Low | Reduces VRAM pressure; no gameplay readability impact |
| Texture Filtering Mode | Bilinear | Minimal visual benefit from anisotropic filtering at competitive distances |
| Shader Detail | Very High | See Shader Detail section — counterintuitively boosts stable FPS |
| Particle Detail | Low | Reduces smoke and explosion particle overhead |
| Ambient Occlusion | Disabled | GPU cost with no competitive benefit |
| High Dynamic Range | Quality | Improves enemy visibility in bright/dark contrast areas |
| FidelityFX Super Resolution | Quality (1.5x) or Balanced | Native is fine if GPU can sustain target FPS; FSR adds frames at minimal sharpness cost |
| MSAA Anti-Aliasing Mode | None | 4x MSAA cuts FPS by 25–40% on low-end hardware — never use it |
| FXAA Anti-Aliasing | Disabled | Softens edges slightly; negligible FPS cost but unnecessary |
| Wait for Vertical Sync | Disabled | VSync halves FPS if frames dip below monitor refresh rate and adds input latency |
| Motion Blur | Disabled | Reduces visual clarity; no gameplay benefit |
| Boost Player Contrast | Enabled | Increases enemy silhouette visibility against complex backgrounds |
Resolution and Aspect Ratio Strategy
CS2 supports both 16:9 and 4:3 aspect ratios, and competitive players have used 4:3 stretched since the CS:GO era for two reasons: player models appear wider (easier to hit), and the reduced pixel count increases FPS. At 1280×960 stretched to fullscreen, the GPU renders approximately 40% fewer pixels than at 1920×1080 native, which translates directly into a 30–50 FPS gain on budget hardware.
We cover the exact settings in fortnite low end pc to maximise performance.
For competitive play on a GTX 1050 Ti or below: Use 1280×960 (4:3) stretched to fullscreen. Enable this via the CS2 Video settings Resolution menu — the game handles the stretch natively. FPS gains are significant and enemy models are wider.
For GTX 1060 6GB and GTX 1650: Native 1920×1080 is viable at the settings in the table above, delivering 100–140 FPS. Use FidelityFX Super Resolution at Quality (1.5x) if frames drop in CPU-intensive rounds — it reduces the render resolution to approximately 1270×710 internally while outputting at 1080p. The sharpness cost is minimal at Quality mode.
The Shader Detail Paradox
Setting Shader Detail to Very High is counterintuitive on low-end hardware, but it produces more stable frame times than Low or Medium. The reason is pre-compilation: at Very High, CS2 pre-compiles a more complete set of shader variants during the initial load sequence. At lower Shader Detail settings, some shader variants are skipped during pre-compilation and compiled on-the-fly during gameplay — this is the source of the characteristic frame-rate hitching visible on first encounters with new maps, smokes, and special effects.
Performance issues? starfield low end pc has the settings fix.
The cost of higher Shader Detail is longer initial load times and a larger cached shader footprint on disk. In exchange, mid-game frame-time spikes are significantly reduced. On a GTX 1060 or GTX 1650, the difference in average FPS between Shader Detail Low and Very High is under 3 FPS — but the reduction in stutter is measurable. Very High is the correct choice for any hardware tier covered by this guide.
Launch Options for Budget Hardware
Right-click CS2 in your Steam library > Properties > Launch Options, then add the following:
+fps_max 0 -novid -console
- +fps_max 0: Removes CS2’s default FPS cap, which defaults to 400 FPS. Set to 0 for uncapped, or set to your monitor’s refresh rate plus 10% (e.g.
+fps_max 165for a 144 Hz monitor) to reduce power consumption and heat output on budget hardware during less demanding map sections. - -novid: Skips the Valve intro video on launch, saving 10–15 seconds of load time.
- -console: Enables the developer console (tildes key in-game), allowing real-time stat monitoring via
cl_showfps 1andnet_graph 1.
The launch option -high (Windows high CPU priority) is commonly listed in low-end guides but produces no measurable benefit in CS2 on most systems — CS2’s process already self-elevates priority. Avoid -threads X arguments unless troubleshooting a specific CPU scheduling issue; incorrect thread counts can degrade performance on modern multi-core CPUs.
What Hardware Can Hit 100 FPS in CS2
The GTX 1060 6GB is the practical 100 FPS floor at 1080p low settings. Below this card, 100 FPS requires either a resolution drop to 900p or 720p, or 4:3 stretched 960p as covered above. The table below reflects performance with the settings template applied — not default CS2 settings.
| GPU | FPS at 1080p Low | 100 FPS Target |
|---|---|---|
| GTX 1050 Ti (4GB) | 55–80 FPS | Use 1280×960 (4:3) stretched |
| GTX 1060 3GB | 80–105 FPS | Borderline — 3GB VRAM limits texture streaming |
| GTX 1060 6GB | 95–135 FPS | Yes at 1080p native low settings |
| GTX 1650 | 120–165 FPS | Yes — headroom for FSR Quality instead of native |
| RX 580 (8GB) | 90–125 FPS | Yes — benefits significantly from Very Low shadow quality |
| Intel UHD 770 | 30–48 FPS | No — use 720p + FSR Balanced for casual play |
RAM is a second constraint on low-end systems. CS2 recommends 16GB — running on 8GB with Chrome and Discord open causes background memory pressure that manifests as micro-stutter rather than sustained FPS loss. Close non-essential applications before launching CS2 if total system RAM is 8GB or below.
Frequently Asked Questions
Why did my CS2 FPS drop after the CS:GO migration?
Source 2 places higher demands on the GPU than the original Source engine, particularly for shadow rendering and ambient occlusion. A GPU that delivered 250 FPS in CS:GO may produce 80–120 FPS in CS2 at comparable settings. Applying the low-end template above recovers most of this difference — the default settings are not optimised for budget hardware.
Does CS2 support FSR or DLSS?
CS2 includes FidelityFX Super Resolution (FSR 1.0) as a native option in Video settings. FSR is compatible with all GPUs regardless of manufacturer — it works on NVIDIA GTX cards, AMD RX cards, and Intel Arc. DLSS is not available in CS2. FSR at Quality mode (1.5x) adds 20–40 FPS on GTX 1060-class hardware with modest sharpness reduction. Balanced mode (1.7x) adds more frames with a larger sharpness cost — worth testing if frames are still insufficient after applying all other low-end settings.
What causes CS2 to stutter on low-end hardware?
The most common cause is shader pre-compilation. After a CS2 update, the engine compiles shaders for your GPU on first launch. On budget hardware this can take 15–30 minutes and causes severe hitching if the game is entered before completion. The progress indicator appears on the main menu — wait for 100% before queuing into a match. A second common cause is VRAM overflow on the GTX 1060 3GB: set Model/Texture Detail to Low to keep peak VRAM usage below the 3GB limit.