Every guide on how to increase FPS in CS2 opens with a block of console commands to paste. The problem is that several of the most commonly recommended ones do not exist in CS2 at all. The game accepts nothing, changes nothing, and says nothing, so you conclude the machine is the problem.
Ghost commands still being recommended
| Command from an FPS guide | Status in CS2 |
|---|---|
| cl_forcepreload | does not exist |
| r_drawparticles | does not exist |
| mat_queue_mode | does not exist |
| cl_disablehtmlmotd | does not exist |
| cl_showfps | exists, shows the counter |
| fps_max | exists, sets the cap |
We checked these against the game’s own command and variable dumps rather than against other articles. The first four are leftovers from the previous game, still being republished as current advice.
That matters beyond the wasted minute. Pasting a list of dead lines and seeing no improvement is how people talk themselves into buying hardware they do not need.
The four settings that actually move frames
Almost all of the achievable gain lives in the video options rather than in the console.
Resolution. The single biggest lever. Every pixel costs work, and dropping a step down is worth more than every console line combined.
Shadow quality. The most expensive individual setting relative to what it adds. Also the one worth thinking about twice, since shadows carry information about players you cannot see.
Effect and particle detail. Cheap to lower and mostly invisible during a fight.
Multisampling. Edge smoothing costs a great deal on weaker hardware and changes nothing about whether you hit anything.
Change these one at a time, not all at once. Otherwise you have no idea which of them did the work and you end up playing on unnecessarily ugly settings.
What you can realistically gain
Worth an honest number, because guides promising to double your frame rate are selling something.
On a machine that already runs the game acceptably, going through the video settings sensibly buys somewhere in the region of twenty to forty percent. Noticeable, and not transformative.
The bigger gains almost always come from somewhere else: a background application eating the processor, an overlay hooked into the game, or a power profile throttling the machine.
Check those before touching graphics settings. A browser with thirty tabs and a chat client with hardware acceleration on can cost more than every video option combined.
Settings that cost more than they give
A short list of things people disable and then wonder why they keep dying.
Shadows at the lowest setting remove a source of information. Seeing a shadow around a corner is a genuine advantage and you are trading it for a handful of frames.
Dropping the resolution too far makes distant players smaller and harder to distinguish from the background. There is a point where the extra frames do not compensate for not seeing the target.
Turning off the game’s own frame counter is fine. Turning off every visual cue you use to read the game is not, and that is the trap in guides written as if only the number mattered.
Commands worth having in the config
Two exist and both are useful, which is a short list compared with what the average guide offers.
The frame counter tells you what any change actually did, and without it you are guessing based on feel, which is unreliable in exactly the situations you care about.
The frame cap is the more interesting of the two. Set slightly above your monitor’s refresh rate, it stops the card rendering frames nobody will ever see, which lowers heat and, on laptops, keeps the machine from throttling mid match.
Both belong in a file that reloads at every launch, so an update cannot quietly reset them. How to build one is in our guide to the CS2 autoexec.
How to measure whether anything changed
- Turn on the counter and note the number in a fixed spot on a map you know.
- Change one setting. One, not five.
- Return to the same spot and compare.
- Test through smoke and in a firefight, since that is where drops actually hurt.
- Keep whatever helped and put the rest back.
An empty server makes this considerably easier, because nothing else is moving and the numbers are comparable between runs. The setup takes two commands and is covered in our walkthrough of the CS2 practice server config.
The number that matters is not the average
Two machines showing the same average frame rate can feel completely different to play on, and this is why.
What breaks aim is not a low average, it is a sudden drop at the moment something happens: a smoke lands, four players enter your view, a flash goes off. The average absorbs those moments and hides them.
So the useful measurement is the worst moment in a round rather than the number sitting on screen while you stand in spawn. If the counter reads two hundred and dips to sixty when a smoke deploys, that dip is what you are actually playing on.
Which changes what is worth adjusting. Effects and particles matter more than they appear to, because they are precisely what is being drawn during those dips.
Launch options, and how few of them matter
The second half of most FPS guides is a string of launch options, and that list has shrunk far more than the articles admit.
The options that genuinely do something now are unglamorous: forcing a refresh rate the game did not detect, or pointing the game at your config file. Neither of those adds frames, they simply stop the game from behaving unexpectedly.
The rest of the usual string, the memory flags and the threading switches, comes from an engine that no longer runs this game. Steam accepts anything you type, and that is why those lines survive: nothing ever tells you they were ignored.
A short launch line is easier to debug for the same reason a short config is. When something breaks after an update, you want a field you can read at a glance rather than forty characters you copied in 2019.
Frames and how the mouse feels
An unstable frame rate rarely gets blamed for what it actually causes, because the symptom shows up somewhere else entirely.
When the picture stutters, the same hand movement lands differently on screen, and that reads as a mouse problem rather than a performance one. People then start changing sensitivity, which makes an already inconsistent situation worse.
The tell is where it happens. Sensitivity behaves identically everywhere on the map. Frame drops cluster in specific places and specific moments, usually the busy ones.
Fix the picture first and only then touch the mouse, using the measurement in our guide to CS2 sensitivity. Tuning aim on an unstable frame rate means tuning against a moving target.
Where settings stop and hardware starts
The part nobody can fix with a config, and it is worth recognising it rather than chasing settings forever.
CS2 leans on the processor harder than the previous game, so on older machines that is the bottleneck rather than the graphics card. The symptom is characteristic: lowering graphics settings changes almost nothing, because the constraint is elsewhere.
You can recognise it easily. If your frame rate is roughly the same on lowest and on medium settings, going lower buys nothing and costs you image quality for free.
In that situation the only thing that genuinely helps, short of new hardware, is taking load off the processor: closing what runs in the background and disabling overlays. Everything else is decoration.
Monitor and refresh rate
Frames your screen cannot display do not exist as far as your eyes are concerned, and they still cost the card work.
If the screen refreshes sixty times a second and the game renders three hundred frames, you see sixty. The rest turns into heat. That is the argument for a cap set a little above the refresh rate rather than at maximum.
The exception applies to players who feel the difference in input latency at very high frame rates. That effect is real and applies to a minority, so treat it as something to test rather than as a rule to follow.
Frequently asked questions about increasing FPS in CS2
Which commands actually increase FPS?
Essentially none. The frame counter and the frame cap exist and are useful. The classic list of optimisation commands mostly does not exist in CS2.
Does lowering resolution help most?
Yes, it is the single largest lever, and also the one that most affects how easily you can see distant players.
Should I turn shadows off completely?
Only if you need the frames badly. Shadows carry information about players you cannot see directly.
What should I set the frame cap to?
Slightly above your monitor’s refresh rate. Rendering far beyond it produces heat rather than visible frames.
Why did nothing change after I pasted a config?
Most likely because the commands in it do not exist in CS2 and were silently ignored.
Are drops in smoke normal?
Common, yes. Effects and particle settings are the ones that affect those moments most directly.
How do I know if my processor is the bottleneck?
If lowest and medium settings produce roughly the same frame rate, the graphics settings are not what is limiting you.
Last updated: September 2026
The list of commands that do not exist comes from comparing common guides against the game’s own command and variable dumps, checked in September 2026. Valve changes both between builds, so verify in the console before keeping any line.
