The CS2 config lives in two places. Settings you change through the menu are stored in Steam\userdata\[your account ID]\730\local\cfg (files cs2_user_convars_0_slot0.vcfg, cs2_user_keys_0_slot0.vcfg, cs2_machine_convars.vcfg and cs2_video.txt). Your own configs and autoexec.cfg go into the game folder, steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg. The quickest way to open it: in Steam, right-click Counter-Strike 2, choose Manage, then Browse local files, and go to game\csgo\cfg. Below are the exact paths for Windows and Linux, what each file does, and how to edit and back them up.
These files are the foundation of every personal setting, from mouse sensitivity and graphics to binds and console commands. If you want to install a pro's config rather than just find the folder, follow our step-by-step guide on how to install a config in CS2.
What Is a Config in CS2
A config (configuration file) in CS2 is a text file that stores game settings. It can hold basic parameters (graphics, controls, sound) as well as more advanced things such as binds, aliases and individual console commands.
In CS2 there are a few kinds of config files:
.vcfg files in the userdata folder: the game writes everything you change in the menu here automatically (in CS:GO, config.cfg played this role);
autoexec.cfg: a file you create yourself, with commands that run every time the game starts;
any custom .cfg (for example practice.cfg or userconfig.cfg): extra configs you run with the exec command when needed.
Players who want precise control over their setup use these files all the time. A config lets you set your binds, radar and FPS limit once instead of redoing them after every reinstall.
Where Is the Config Located in CS2
One of the most common questions is where the CS2 config is stored. The answer depends on your operating system and on which file you need.
Windows
Menu settings (your user config) are here:
C:\Program Files (x86)\Steam\userdata\[your account ID]\730\local\cfg
The folder for autoexec.cfg and your own configs (global, inside the game folder):
C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg
If Steam is installed on another drive, the start of the path changes, for example D:\SteamLibrary\steamapps\common\... The folder is still called Counter-Strike Global Offensive because CS2 installs into the same place CS:GO did.
Linux
User settings:
~/.steam/steam/userdata/[ID]/730/local/cfg
Game folder for autoexec.cfg:
~/.steam/steam/steamapps/common/Counter-Strike Global Offensive/game/csgo/cfg
macOS
CS2 has no official macOS client, so the path ~/Library/Application Support/Steam/userdata/[SteamID]/730/local/cfg only applies to old CS:GO installs. CS2 runs on a Mac only through workarounds, and file locations depend on the method you use.
The account ID in the userdata path is a short number (the same as your Steam friend code), not the 17-digit SteamID64. If you see several folders in userdata, several accounts have signed in on this PC; you need the one that contains a 730 folder.
If you are still unsure where the CS2 config is, open Steam, right-click Counter-Strike 2, choose Manage, then Browse local files, and go to game\csgo\cfg.
Main Config Files and What They Do
cs2_user_convars_0_slot0.vcfg: created automatically, holds menu settings such as sensitivity, crosshair and HUD;
cs2_user_keys_0_slot0.vcfg: your key bindings;
cs2_machine_convars.vcfg and cs2_video.txt: settings tied to your PC, including graphics;
autoexec.cfg: created by you, for commands that should run at launch.
To lock in sensitivity, binds or your own commands, use autoexec.cfg. To keep what you set up in the menu, copy the .vcfg files from userdata.
Creating and Editing an autoexec.cfg
Any plain text editor works, though Notepad++ is more convenient than Notepad because it highlights text and keeps the encoding intact. Typical lines look like this:
sensitivity 2.2: mouse sensitivity;
bind "mouse4" "+voicerecord": voice chat bind (see how to make a bind in CS2);
fps_max 300: FPS cap;
cl_radar_scale 0.4 and viewmodel_fov 68: radar and weapon view settings.
Save the file as autoexec.cfg (make sure it does not end up as autoexec.cfg.txt) in game\csgo\cfg. To make sure it runs at launch, add this to your CS2 launch options in Steam:
+exec autoexec.cfg
Old CS:GO configs often contain cl_cmdrate 128, cl_updaterate 128, cl_interp_ratio 1, mat_queue_mode 2 or cl_forcepreload 1. CS2's subtick netcode and the Source 2 engine work differently, so these lines do nothing and can be dropped. For commands that do work, see our list of CS2 console commands. Graphics are set under Settings, Video and saved to cs2_video.txt; the main performance line left for a config is fps_max, and you can check the result with our guide on how to enable FPS in CS2.
Backing Up and Restoring Your CS2 Config
Copy both cfg folders (userdata\[ID]\730\local\cfg and game\csgo\cfg) to cloud storage or a flash drive, and put them back after reinstalling the game or Windows. Steam Cloud may sync some settings between PCs, but do not rely on it fully: in some cases it overwrites local files with an older version. If you play on several accounts, back up each account's userdata folder separately.
Tips for Safe Config Editing
Editing configs is a powerful tool, but it should be used carefully. Here are some practical tips:
Make a copy of the original file before making changes. It is better to keep a config_backup than to restore settings from memory later.
Do not download configs from unverified forums or channels. They may contain stray binds or commands that break your setup.
Do not use binds banned by server or league rules. In CS2, Valve restricted binds that perform several actions with one key, so old aliases such as +jumpthrow may no longer work.
Study the commands you add. You can look them up on the Valve Developer Community wiki and in dedicated guides.
Check that a command works in CS2: some CS:GO settings were removed or changed.
Moving a Config from CS:GO or to Another PC
If you still have a config from your CS:GO days, part of it carries over to CS2. Tips:
Move only universal commands such as sensitivity, bind, cl_radar_* and viewmodel_*.
Remove commands tied to the old engine and netcode, such as cl_interp_ratio, cl_cmdrate and mat_queue_mode.
Keep versions with clear labels, for example cs2_autoexec.cfg and csgo_autoexec_old.cfg.
Use cloud storage to move them between devices.
This approach is especially useful if you play tournaments or switch PCs often.
Frequently Asked Questions
Where is autoexec.cfg in CS2?
In the game folder: steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg. If it is not there, create it yourself and add +exec autoexec.cfg to your launch options.
Where can I get a pro player's CS2 config?
Pro settings are published on Liquipedia (on player pages), HLTV and by the players themselves on streams and social media. Do not copy a config blindly: first understand why each command is there.
How do I find my CS2 config if it is lost?
Check userdata\[account ID]\730\local\cfg first, since menu settings live there. Steam Cloud may restore some of them. A custom autoexec.cfg without a backup cannot be recovered.
What happens to the CS2 config when I uninstall the game?
The userdata folder sits in the Steam directory, not in the game folder, so it usually survives an uninstall. The game\csgo\cfg folder with your autoexec.cfg is deleted with the game, so copy it first.
Now you know where to find the CS2 config, what each file does, and how to edit, back up and move it. A tidy autoexec.cfg and a backup of both cfg folders will save you from setting everything up by hand after any reinstall.
