FPS vs Refresh Rate in CS2 (+ CS 1.6 Comparison)
Introduction
Counter-Strike has always been a game where performance matters, but in Counter-Strike 2 the topic has become even more important. Players constantly compare FPS, refresh rate, input lag, and monitor smoothness, yet many still confuse these terms or assume they mean the same thing. In reality, FPS and refresh rate are connected, but they are not identical, and understanding the difference can help you build a smoother and more responsive CS2 experience.
This guide explains how FPS works in CS2, what monitor refresh rate (Hz) actually changes, and whether running higher FPS than your screen’s refresh rate still makes sense. It also covers FPS vs refresh rate in CS2, launch options such as -freq, -refresh, and -refreshrate, as well as settings like VSync, G-Sync, and FreeSync.
I’ll also compare how these mechanics behave in CS 1.6 and CS2, since the older GoldSrc engine and modern Source 2 do not handle performance in the same way. If you want to understand the real relationship between FPS, Hz, smoothness, and input delay - without myths, outdated advice, or random forum claims - this guide will walk you through it clearly.
How FPS Works in CS2 and CS 1.6 Engines
Both versions of Counter-Strike handle frames differently because each runs on a completely different engine. Understanding this is key to knowing why FPS limits exist in CS 1.6 - and why CS2 benefits from as many frames as your system can push.
GoldSrc (CS 1.6)
The old GoldSrc engine ties game physics directly to frame rate. Movement, recoil, and even grenade bounces depend on how many frames are rendered per second. Because of that, FPS should stay around 100 for the simulation to remain stable.
Many players still use the old command fps_max 101, but that’s more of a tradition than a real setting. People copied it from early pro configs without realizing why it was there. In reality, the GoldSrc engine internally runs at about 100.5 FPS and gains no advantage from "101" at all. A value of 100 fits perfectly with the engine’s internal timing - anything significantly higher can cause physics desyncs, jittery movement, or animation bugs.
Source 2 (CS2)
CS2’s Source 2 engine works very differently. It separates rendering from physics, using a modern sub-tick system where the game tracks player actions between ticks. The more frames your PC renders, the faster the engine processes your inputs and visual updates. That’s why CS2 scales almost linearly with FPS - smoother motion, lower input latency, and tighter aiming feedback.
To sum it up, CS 1.6 needs 100 (maximum 120 for a clear picture) frames per second for a stable and responsive game, while CS2 gameplay improves with each additional frame.
Why Refresh Rate (Hz) Matters in CS2
Your monitor’s refresh rate decides how many frames it can actually show each second. A 60 Hz screen can only display 60 FPS - even if your GPU renders 300 FPS. That means every extra frame beyond 60 is wasted and never reaches your eyes.
When you switch to a 144 Hz, 240 Hz, or 360 Hz display, the difference becomes clear: motion looks smoother, mouse tracking feels tighter, and the overall response time drops. You see movement more precisely and react a little faster - not because the game runs differently, but because your screen updates more often.
In CS 1.6, however, the engine itself limits what you can gain from high-refresh monitors. Since it can’t simulate more than about 100 FPS, running the game at 120 FPS can make the image look slightly sharper and more pleasant to the eye, but raising it further - to 130, 150, 250, or even 500 FPS - won’t change how it looks. What it will do is break the game’s internal physics. You can easily feel it after any jump: CS 1.6 has a short recovery time before your next movement frame begins (roughly a tenth of a second). At extremely high frame rates, this recovery period scales incorrectly, causing sluggish post-jump movement and inconsistent physics - something completely unacceptable for a competitive shooter.
CS2 is a different story: its modern rendering pipeline and sub-tick netcode take full advantage of higher frame rates, reducing input delay and making aiming feel more connected and consistent. The higher your FPS, the faster the game reacts to every mouse input, movement, and shot. At 300 FPS and beyond, you get ultra-low latency and crystal-smooth animation - every frame translates almost instantly into in-game action, giving a true sense of one-to-one control.
-freq, -refresh, and -refreshrate Launch Options in CS2 and CS 1.6
The -freq, -refresh, and -refreshrate launch options are used to force a specific monitor refresh rate. This behavior is officially documented in Valve’s command line options reference. The -freq parameter belongs to the older GoldSrc engine, while -refresh and -refreshrate are used in the Source engine family.
CS 1.6 (GoldSrc)
By default, CS 1.6 uses the refresh rate currently set in your operating system. You can check or change it in Windows under: System -> Display -> Advanced Display Settings -> Choose a refresh rate. If you have more than one monitor, select the correct one first.
You can also manually override this setting with the -freq launch parameter. For example, if your monitor supports 240 Hz but you start the game with -freq 100, it will try to run as if the monitor were limited to 100 Hz. In practice, high-refresh monitors (120, 144, 240+) work perfectly fine with fps_max 100 or even fps_max 60. Forcing a lower refresh rate won’t improve anything - it can actually cause micro stutters or frame pacing issues. Use -freq only if you have a specific reason to test or troubleshoot refresh rate behavior.
CS2 (Source 2)
CS2 handles display modes completely differently. The game automatically detects your monitor’s real refresh rate and adjusts accordingly - regardless of what’s set in Windows. If there’s a mismatch, CS2 will even notify you in the console.
Launch options like -freq, -refresh, or -refreshrate do not affect CS2, as the Source 2 engine manages display timing internally.
The sys_info command entered in the CS2 console displays your computer’s detected hardware specifications.
Best FPS Settings for CS2 and CS 1.6
Getting the right FPS setup in Counter-Strike depends on which engine you’re running. Both games benefit from stable frame pacing, but the limits and behavior are completely different between CS 1.6 and CS2.
CS 1.6 (GoldSrc)
For the classic engine, stability is everything. The game’s physics are locked around 100 FPS, so going higher offers no benefit and can even cause timing issues. A simple, clean configuration looks like this:
fps_override "0" // developer "0" for non-Steam client
fps_max "100"Many guides include rate commands together with FPS tweaks, but they’re not directly related. These parameters control network communication, not frame rendering:
rate 25000
cl_cmdrate "101"
cl_updaterate "102"
ex_interp "0.01" // for ping <10; for 20+ use 0.03-0.04, etcThe link between FPS and rates is only indirect - FPS handles visuals and performance, while rates manage how often data is sent to and from the server. If your ping is too high (for example 140 ms), you can reduce it to 90 by limiting your network rates:
rate 5000
cl_cmdrate "28"
cl_updaterate "30"
ex_interp "0.09"Just don’t cap your FPS to 30 - that only makes things worse. However, if your game actually runs at 30 FPS, then yes, you physically can’t send 100 updates per second; your commands are tied to each rendered frame. The real fix is to get your FPS back up to 100, not to lower rates.
This setup keeps your frame rate smooth, physics stable, and networking consistent across almost all servers.
Related Guides You May Find Useful
If you're adjusting your FPS, here are a few guides that will help you polish your setup even further:
- CS2 Console Commands 2026: Best Practice, Gameplay & FPS Settings
- How to Fix FPS Drops, Stuttering, and Input Lag in Counter-Strike 2
- How to Show FPS in Counter-Strike 2 | Full 2026 Guide
- How to Boost FPS in Counter-Strike 2: Full Performance & Optimization Guide
CS2 (Source 2)
CS2 doesn’t have a fixed FPS limit. The higher your frame rate, the lower your input latency and the smoother your aiming feels. It’s usually best to leave FPS uncapped by setting it to automatic mode (0):
fps_max "0"
fps_max_ui "120"
If your system struggles to stay consistent, set fps_max slightly below your average FPS for steadier frame pacing. For example, if your frame rate jumps between 120-250 FPS, try fps_max 150 and see if it feels smoother.
CS 1.6 vs CS2 - FPS Settings
| Game | Engine | Recommended fps_max |
Monitor | Notes |
|---|---|---|---|---|
| CS 1.6 | GoldSrc | 99-100 | 60+ Hz | Physics bound to 100 FPS; higher values cause instability |
| CS2 | Source 2 | 0 or stable 144+ | 144+ Hz | No hard cap; higher FPS reduces latency and improves input response |
VSync, G-Sync, and FreeSync in CS2 - Should You Use Them?
Display synchronization technologies can drastically change how your game feels - especially when FPS and refresh rate don’t perfectly match. Here’s what each one does and how it behaves in Counter-Strike.
VSync (Vertical Sync)
VSync locks your frame output to your monitor’s refresh rate to prevent screen tearing. While it keeps the image clean, it also adds noticeable input delay - especially in CS 1.6, where every millisecond matters. It’s best to keep VSync disabled in all versions of Counter-Strike.
G-Sync and FreeSync
These adaptive-sync technologies from NVIDIA and AMD dynamically adjust your monitor’s refresh rate to match the game’s current FPS. The result is a smoother image with no tearing or noticeable lag. They work especially well in CS2, where frame rate can vary depending on maps and visual effects.
Real-World CS2 Example 🙂
My current PC runs CS2 at a stable 400+ FPS, while my monitor refreshes at 240 Hz. In this case, the monitor simply can’t adapt to such high FPS, so G-Sync or FreeSync don’t provide any benefit - there’s no need to enable them.
However, when I use the same 240 Hz monitor on an older PC that averages around 170 (±30) FPS, G-Sync (GTX 1060 3 GB) makes a clear difference. It automatically syncs each frame with the monitor’s refresh cycle, eliminating tearing and stutter. Honestly, I never had visible frame drops or screen tearing before, but with G-Sync the game felt smoother and more effortless.
Some guides recommend setting a fixed FPS slightly below your monitor’s refresh rate - for example, fps_max "238" on a 240 Hz display - when using G-Sync and lower frame rates. Personally, I don’t see a need for that: the CS2 console and the Source 2 engine are already well optimized, and with fps_max "0" the game adjusts everything automatically.
My Recommended FPS and Refresh Rate Setup
- For CS 1.6: Disable all sync options - the engine is too old to benefit from them.
- For CS2: Use G-Sync or FreeSync if your average FPS is lower than your monitor’s refresh rate (Hz). Of course, you can always test the game with or without G-Sync and FreeSync. Try both options yourself and choose the one that suits you best.
Common FPS and Refresh Rate Myths in CS2
Counter-Strike has always been surrounded by all kinds of "FPS wisdom" - some of it true, some of it pure myth. Let’s clear up the most common ones once and for all.
Myth #1 - More than 101 FPS gives you an advantage in CS 1.6
False. The GoldSrc engine is physically locked to around 100.5 FPS. Going higher doesn’t make you move faster or aim better - it only breaks game physics and can cause desync on servers.
Myth #2 - VSync makes the game smoother
Not really. VSync removes screen tearing but adds input delay, especially noticeable in shooters like Counter-Strike. You’ll get a prettier picture but slower reactions - a bad trade-off for competitive play.
Myth #3 - Higher FPS always improves accuracy
Partially true. Higher FPS reduces input latency and makes aiming feel tighter, but it doesn’t change bullet spread or recoil patterns. Your shots just feel cleaner because the game reacts faster.
Myth #4 - Limiting FPS improves performance
Only in specific cases. In CS2, capping FPS slightly below your average can smooth frame pacing on weak systems, but generally, letting the engine run freely (fps_max "0") provides the lowest input lag.
Myth #5 - G-Sync or FreeSync increase input lag
Not true. Both G-Sync and FreeSync are designed to reduce tearing without the delay caused by VSync. When used properly, the added latency is almost negligible - and in most cases, gameplay feels smoother and more consistent.
Conclusion
Counter-Strike has always been sensitive to performance, but FPS and refresh rate do not work the same way in every version of the game. In CS 1.6, stable 99-101 FPS matters because the GoldSrc engine ties important parts of movement and physics to frame rate. In CS2, the logic is different: higher FPS improves responsiveness, reduces delay, and helps the game feel cleaner on the high FPS PCs and high refresh rate monitors.
That is why there is no single universal rule for both games. In CS 1.6, consistency is the priority. In CS2, the priority is usually to get as much stable FPS as your system can realistically hold, then pair it with the highest refresh rate your monitor supports and sensible sync settings.
If you understand how FPS, Hz, frame pacing, and sync technologies interact, it becomes much easier to choose the right setup for your hardware instead of copying random settings from old guides or forum posts.
CS2 FPS and Refresh Rate FAQ
Why is FPS capped at 100 in CS 1.6?
Because the GoldSrc engine ties physics directly to frame rate. The simulation runs correctly only around 100 FPS - going higher breaks movement, jump timing, and grenade physics.
Is there any reason to use fps_max "101" in CS 1.6?
Not really. It became a community tradition copied from old pro configs. In reality, the engine runs at about 100.5 FPS internally and gains no benefit from "101".
Does monitor refresh rate affect gameplay in CS 1.6?
Only visually. The game can’t simulate more than 100 FPS, so a 240 Hz or 360 Hz monitor just looks smoother but doesn’t change game physics or reaction timing.
Should I use fps_override "1" (developer "1") in CS 1.6?
Yes and no. If you want to slightly improve image quality, you can set fps_override 1 and fps_max 120, then test your movement, jumps, and grenade throws to see if it feels comfortable compared to fps_max 100. However, I strongly advise against it - the difference is minimal, and it can make the game feel less consistent.
What about in CS2 - does a 360 Hz monitor help?
Yes. CS2’s Source 2 engine fully supports high-refresh displays. The higher your FPS, the lower your input latency and the more responsive moving and aiming feel.
Should I limit FPS in CS2?
Only if your frame rate constantly fluctuates or your GPU runs at 100% for long periods. Otherwise, leave fps_max "0" and let the engine manage it automatically.
Do VSync, G-Sync, or FreeSync affect performance?
VSync adds input lag - avoid it. G-Sync and FreeSync reduce tearing and stutter without delay, but they’re only useful if your FPS is lower or unstable compared to your monitor’s Hz.
Can high FPS improve hit registration?
Indirectly. Higher FPS reduces input delay and makes your shots register faster, but the actual hit calculation still depends on server tickrate and your connection quality.
Should I change refresh rate with -freq or -refresh?
Only in CS 1.6, and only if your system isn’t using the right display rate by default. CS2 ignores those launch options and handles refresh rate automatically.
Why does my FPS drop on certain CS2 maps?
Different maps have different lighting, reflections, and geometry complexity. Lower your shadow quality and anti-aliasing settings - they have the biggest impact on FPS without hurting visibility.
