CS2 FPS Settings & Launch Options
Use this practical checklist to improve FPS, reduce stutter, choose launch options, and diagnose net jitter before blaming your aim or your server.
Recommended launch options
-novid -console -fullscreen +fps_max 0
-novidSkips the intro video and gets you to the menu faster.
-consoleOpens the developer console automatically for quick troubleshooting.
-fullscreenStarts the game in fullscreen mode when your local video settings allow it.
+fps_max 0Removes the in-game FPS cap. Use a fixed cap if your frame times become uneven.
What to change first
Lower shadows, particles, and ambient occlusion before lowering resolution.
Use native fullscreen for the lowest-latency baseline.
Keep NVIDIA Reflex or your GPU latency mode enabled if your system supports it.
Test changes on the same map and server so you compare the same workload.
Prefer stable frame times over peak FPS screenshots.
Disable capture overlays until you finish benchmarking.
Video setting profiles
Pick a profile based on your goal. Start on Competitive Low, then raise detail only while frame times stay stable.
Maximum FPS and clarity for 1v1 fights
- Multisampling: None / CMAA2
- Global Shadow Quality: Low
- Dynamic Shadows: Sun only
- Model / Texture Detail: Low or Medium
- Shader Detail: Low
- Particle Detail: Low
- Ambient Occlusion: Disabled
- High Dynamic Range: Performance
- FidelityFX Super Resolution: Disabled (prefer native)
- NVIDIA Reflex / Low Latency: Enabled + Boost when stable
Smoother image without heavy frame-time spikes
- Multisampling: 2x / 4x MSAA if you still hold high FPS
- Global Shadow Quality: Medium
- Model / Texture Detail: Medium
- Shader Detail: Medium
- Particle Detail: Medium
- Ambient Occlusion: Medium only if FPS stays stable
- High Dynamic Range: Performance
- VSync: Off for competitive play
- Max FPS: Cap slightly under average uncapped FPS
Cleaner look for demo review and content capture
- Multisampling: 4x or 8x if hardware allows
- Shadow / Texture / Shader: High
- Particle Detail: High
- Ambient Occlusion: Medium or High
- FSR: Quality mode only if you need resolution headroom
- Prefer native resolution over heavy upscaling
- Keep overlays minimal while capturing
Stutter and frame drops
- Update GPU drivers and restart after installation.
- Disable overlays you do not need, especially capture and browser overlays.
- Cap FPS slightly below your monitor refresh if uncapped FPS creates uneven frame times.
- Keep shader cache enabled in your GPU control panel.
- Close RGB software, launchers, and browser hardware acceleration during matches.
Net jitter and packet loss
- Use ethernet when possible and avoid WiFi repeaters.
- Close downloads, streams, cloud sync, and browser tabs before queueing.
- Restart Steam and your router if jitter appears suddenly.
- Pick lower-ping servers in the server browser before blaming game settings.
- Test with and without VPN/QoS tools — some routes get worse with them enabled.
Input latency
- Use fullscreen mode and a native refresh rate.
- Disable VSync for competitive play unless tearing is worse than the latency tradeoff.
- Keep mouse polling stable and avoid USB hubs for your mouse.
- Use a simple crosshair and avoid heavy background apps while playing.
- Prefer a fixed FPS cap that your PC can hold over uncapped spikes.
FPS testing routine
Change one setting at a time, run the same deathmatch or offline benchmark route, and judge the result by smoothness and frame-time stability. A stable 240 FPS usually feels better than a wildly fluctuating 360 FPS.
FPS and net jitter FAQ
What are the best CS2 launch options?
Start simple: -novid, -console, -fullscreen, and a tested FPS cap are enough for most players. Add hardware-specific options only when you are testing a clear problem.
How do I improve FPS in CS2?
Lower expensive video settings, update GPU drivers, reduce overlays, keep the game on an SSD, and use an FPS cap that creates stable frame times instead of chasing the highest number.
What causes net jitter in CS2?
Net jitter is usually caused by unstable routing, WiFi interference, background traffic, overloaded home networks, or a bad server route. It is not always fixed by console commands.
Should I use +fps_max 0?
Uncapped FPS is fine if your frame times stay smooth. If you see stutter or GPU power-state swings, cap slightly under your average FPS for more consistent input.
Related tools
Keep practicing with the next highest-impact CS2Hype tools.