CS2 autoexec generator
Tick the settings you want and get a ready-to-use autoexec.cfg. Every line is a command that exists in CS2 today, with values held inside the game's own limits.
Show
Mouse
Gameplay
Performance
On-screen info
HUD and radar
Audio
Viewmodel
Network
Binds
Need buy binds or more keys? Build them with the bind generator and paste its lines under these.
File
autoexec.cfg
6 lines// autoexec.cfg built with CSGOLuck Tools echo "autoexec.cfg loaded" // Mouse sensitivity 1.25 // Performance fps_max 0 // On-screen info cl_showfps 1 // Audio volume 0.5 host_writeconfig
Save it in game\csgo\cfg inside your CS2 folder, then add +exec autoexec to your launch options.
What an autoexec.cfg does
An autoexec.cfg is a plain text file of console commands, one per line. CS2 runs it when you tell it to, usually at launch, so your settings are applied the same way every time and on any PC you copy the file to. It does nothing that typing the lines into the console would not do, which is also why it is safe: no game files change.
The game does keep your menu settings, in your Steam userdata folder and Steam Cloud. An autoexec is for the rest: values you want written down, kept in one place and easy to move. To make the game run the file, add +exec autoexec to your launch options. The CS2 launch options builder has that entry ticked by default.
What goes in it
The builder offers 36 settings in 8 groups, plus a few single-key binds. Every one is a command or variable that exists in CS2 (checked against the game's data, dated 28 October 2026), and every number is held inside the game's own limits. Defaults and ranges for any of them are in the CS2 console commands list.
| Group | Settings | For example |
|---|---|---|
| Mouse | 2 | sensitivity zoom_sensitivity_ratio |
| Gameplay | 4 | option_duck_method option_speed_method cl_sniper_auto_rezoom |
| Performance | 3 | fps_max fps_max_ui engine_low_latency_sleep_after_client_tick |
| On-screen info | 4 | cl_showfps cl_hud_telemetry_ping_show cl_hud_telemetry_frametime_show |
| HUD and radar | 8 | cl_hud_color hud_scaling cl_radar_scale |
| Audio | 9 | volume snd_menumusic_volume snd_mvp_volume |
| Viewmodel | 5 | viewmodel_fov viewmodel_offset_x viewmodel_offset_y |
| Network | 1 | rate |
A starter file
With the builder's default ticks, this is what you get. It is a real output, not a mock-up:
// autoexec.cfg built with CSGOLuck Tools echo "autoexec.cfg loaded" // Mouse sensitivity 1.25 // Performance fps_max 0 // On-screen info cl_showfps 1 // Audio volume 0.5 host_writeconfig
Three things to notice. Comments start with //, so you can add your own notes. The echo line prints a message in the console, which is how you confirm the file ran. And host_writeconfig at the end saves the result to config.cfg, so the values stay if the autoexec is missing next time.
Mouse, crosshair and viewmodel lines
The first line in the Mouse group is your sensitivity, and the number is the in-game value, not your eDPI. Multiply it by your mouse DPI to get eDPI and see where you stand with our eDPI calculator. If you are coming from Valorant, the Valorant to CS2 sensitivity converter gives you the number to paste.
Two other builders make lines you can paste under the ones here. The CS2 crosshair generator outputs the console commands for a crosshair, and the CS2 viewmodel generator outputs the four viewmodel commands with a preview. Buy keys and grenade keys come from the CS2 bind generator.
Where to put autoexec.cfg
Save the file here, in the cfg folder next to your CS2 files:
C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg\autoexec.cfg
~/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/game/csgo/cfg/autoexec.cfg
Your Steam library may be on another drive. In Steam, right-click CS2, choose Manage, then Browse local files, and open game, csgo, cfg. If there is no cfg folder, create one.
How to use it
- Tick what you want above and adjust the values.
- Click Download autoexec.cfg, or copy the text into a new file with that name.
- Put it in the cfg folder shown above.
- Add +exec autoexec to the CS2 launch options in Steam.
- Start the game and open the console. If you left the echo line on, you will see autoexec.cfg loaded.
Old lines that fail in CS2
If you are carrying an old CS:GO autoexec, these lines do nothing: the commands are not in CS2's command list (checked against files dated 28 October 2026).
| Command | What it was | Use instead |
|---|---|---|
| net_graph | On-screen network and FPS graph | cl_showfps and the cl_hud_telemetry_* cvars |
| cq_netgraph | Often passed around as the net_graph replacement | It is not a CS2 command. Use cl_showfps and cl_hud_telemetry_* |
| cl_cmdrate | Client command rate | Nothing to set. The game manages its own update rates |
| cl_updaterate | Server update rate | Nothing to set. The game manages its own update rates |
| cl_righthand | Left or right hand | cl_prefer_lefthanded |
| cl_bobamt_lat | Sideways viewmodel bob | Nothing. The bob cvars are gone |
| cl_bobamt_vert | Vertical viewmodel bob | Nothing. The bob cvars are gone |
| cl_bob_lower_amt | Weapon lower bob | Nothing. The bob cvars are gone |
| cl_bobcycle | Bob cycle length | Nothing. The bob cvars are gone |
| cl_usenewbob | Switches viewmodel bob style | Nothing. The bob cvars are gone |
| viewmodel_recoil | Viewmodel recoil amount | Nothing. The cvar is gone |
| m_rawinput | Raw mouse input | Nothing to set in the console |
| cl_lagcompensation | Lag compensation toggle | Nothing. It cannot be turned off from the client |
| cl_predict | Client prediction toggle | Nothing. It cannot be turned off from the client |
| voice_scale | Voice volume | snd_voipvolume |
| voice_enable | Voice on or off | voice_modenable |
| cl_crosshaircolor | Preset crosshair colour 0 to 5 | cl_crosshaircolor_r, _g, _b and _a |
| cl_grenadepreview | Grenade trajectory preview | sv_grenade_trajectory_prac_pipreview on a practice server |
FAQ
Where does autoexec.cfg go in CS2?
In the game's cfg folder: Steam, then steamapps, common, Counter-Strike Global Offensive, game, csgo, cfg. The folder is still called Counter-Strike Global Offensive. The quickest way there is to right-click CS2 in Steam, choose Manage, then Browse local files, and open game, then csgo, then cfg.
How do I make CS2 run my autoexec?
Save the file as autoexec.cfg in that folder and add +exec autoexec to your launch options. The launch option is a safety net: if the file already ran at startup, running it again is harmless.
Why do my settings not stick without an autoexec?
CS2 keeps your in-game settings in your Steam userdata folder and Steam Cloud, so they follow the account rather than a file you can see. An autoexec is a plain text file you control, so it re-applies the same values every launch and is easy to copy to another PC.
Why does the generator not offer cl_cmdrate, cl_updaterate or net_graph?
They are not in CS2's command list, so typing them only prints an error. Use cl_showfps and the cl_hud_telemetry commands to see FPS, ping and packet loss. See the removed list below for the full set.
Do I need host_writeconfig at the end?
It saves your current settings to config.cfg so they carry over if the autoexec is missing next time. It is optional, and the generator includes it by default.
Can an autoexec get me banned?
No. A cfg file runs ordinary console commands. Cheat-protected commands will not run on servers where cheats are off, and Valve's rule on binds with several input actions is covered on our bind generator page.
