To install a config in CS2, create a plain text file named autoexec.cfg with your commands, put it in C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg, and add +exec autoexec.cfg to the game's launch options in Steam. From then on the commands run every time CS2 starts, and you can test the setup right away by typing exec autoexec in the console. Below is the full process: writing your own config, installing a downloaded one, resetting to default settings, and the common mistakes that make the game ignore the file.
What a Config Is and Why Settings Reset
Before installing a config, it helps to know where CS2 keeps your settings and why they sometimes reset. CS2 uses two kinds of config files. The first is written by the game itself: everything you change in the menu (mouse sensitivity, binds, crosshair, HUD) is saved to .vcfg files in the userdata folder, such as cs2_user_convars_0_slot0.vcfg and cs2_user_keys_0_slot0.vcfg. In CS:GO, config.cfg played this role. The game overwrites these files on its own, and Steam Cloud sync can replace them with an older copy from the cloud, so after a crash or a reinstall your settings may roll back.
The second file, autoexec.cfg, is one you create yourself. The game never overwrites it, which is why experienced players keep their key commands there: write it once, and your values are applied again on every launch, regardless of patches or reinstalls. For a full breakdown of where the CS2 config file is located and what each folder contains, see our separate guide.
| Property | .vcfg files (menu settings) | autoexec.cfg |
|---|---|---|
| Created by | The game, automatically | You, manually |
| Can the game overwrite it | Yes | No |
| Applied when CS2 starts | Yes | Yes, with the +exec autoexec.cfg launch option |
| Portable to another PC | Yes, by copying or via Steam Cloud | Yes, by copying the file |
| Protected from resets | No | Yes |
In short, menu settings can reset, while autoexec.cfg reapplies your values every time. That is why the rest of this guide focuses on it.
How to Install a Config in CS2 from Scratch
You write your own config in a plain text editor. Notepad works, but Notepad++ is more convenient: it is free and does not change the file encoding. Put one command per line and save the file with the right name and extension. Most problems come down to exactly those two things: the extension and the destination folder.
Step by step:
Open a text editor.
Type your console commands, one per line.
Save the file as autoexec.cfg. In the "Save As" dialog, set the file type to "All Files," otherwise Windows appends .txt.
Move the file to C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg.
In Steam, right-click Counter-Strike 2, open Properties → General → Launch Options, and add +exec autoexec.cfg. If you already use other launch options, separate them with a space.
Once the file is in place and the launch option is set, you can test it immediately. Open the console with the ~ key and type exec autoexec: if everything is right, the commands apply in your current session without a restart. As a check, add the line echo "Autoexec loaded!" at the end of the file, and that message will appear in the console every time the config loads.
A common trap: Windows hides file extensions by default, so autoexec.cfg.txt looks like autoexec.cfg in Explorer while the game cannot see it. Turn extensions on in Explorer via View → Show → File name extensions.
Which Commands to Put in Your Config
A config is simply a list of console commands that run automatically every time the game launches. Players usually put in things the standard settings menu does not offer, or things they would rather not type by hand every session.
A baseline set most players start with:
cl_crosshairsize 3: crosshair size (the full crosshair is easier to build in the menu and import as a code).
cl_righthand 0: weapon held in the left hand.
fps_max 300: frame rate cap.
viewmodel_fov 65: weapon model field of view.
bind "F" "use weapon_flashbang": a quick bind for the flashbang.
bind "MWHEELDOWN" "+jump": jump on mouse wheel down.
host_writeconfig: saves your current settings; it usually goes on the last line.
That is a starting point. Over time players add grenade binds, radar tweaks, and viewmodel settings. Start lean and add only what you actually use in matches. Commands that only existed in CS:GO are ignored in CS2 or throw a console error, so check an old config line by line.
How to Install a Downloaded Config in CS2
Many players want to try pro settings, and configs from well-known players circulate widely. Installing a downloaded config is no harder than installing your own: the process is the same, the file is just already written. Before installing, open it in a text editor and make sure every command makes sense and nothing looks suspicious.
Steps:
Download the .cfg file from a trusted source.
Open it in Notepad++ and read through the commands.
Rename it to autoexec.cfg, or keep the original name and add +exec filename.cfg to your launch options instead.
Copy the file to ...\game\csgo\cfg.
Make sure the launch option is set in Steam.
Launch the game, or run exec autoexec in the console to apply it right away.
Before installing someone else's config, back up yours by copying autoexec.cfg to another folder. It takes seconds and saves trouble if the new settings feel wrong. Note that a config usually does not touch video settings: resolution and graphics options live in a separate file, cs2_video.txt, and are set through the in-game menu.
How to Reset to the Default CS2 Config
Sometimes it is easier to start over. One catch: CS2 has no standalone "default settings" file you can download or drop into a folder. Default values are built into the game, and the settings files are recreated on first launch. So there are two ways to get back to default.
Method 1, in-game settings. Launch CS2, open the settings menu, and reset the sections you need. Best when one specific thing is broken rather than everything.
Method 2, a full reset through the files. This works even when you cannot get into the game or the menu no longer helps. Back up first: rename files rather than deleting them.
Turn off Steam Cloud for CS2: right-click the game → Properties → Cloud tab → uncheck the box.
Go to C:\Program Files (x86)\Steam\userdata\<ID>\730\local\cfg, where <ID> is the short number of your Steam account.
Rename or delete the contents of the cfg folder (renaming is safer, since you can restore the files).
Launch CS2: the game creates new files with default settings.
| Reset method | Difficulty | What gets reset | Risk of data loss |
|---|---|---|---|
| In-game settings | Low | Selected sections | Minimal |
| Through the files | Medium | All settings | High without a backup |
If +exec autoexec.cfg is still in your launch options, your autoexec will apply again on the next start. For completely clean settings, remove that option for a while.
Why Your Config Is Not Working: Common Mistakes
If you followed every step and the config still does not apply, the cause is almost always one of a few typical mistakes. Run through the table before reinstalling.
| Issue | Cause | Fix |
|---|---|---|
| Config does not load on startup | +exec autoexec.cfg is missing | Add it to the game's launch options in Steam |
| The game does not read the file | Extension is .txt instead of .cfg | Show file extensions and rename the file |
| Menu settings keep resetting | Steam Cloud replaces files with the cloud copy | Turn off Steam Cloud for CS2 |
| Config is in the wrong folder | The path has no \game\ segment | Move it to ...\game\csgo\cfg |
| Commands are not applied | Several commands on one line, or CS:GO-only commands | One command per line; test it in the console |
The most common mistake is the wrong folder. When CS:GO became CS2, the folder structure changed: the path now includes a \game\ segment, and a file left in the old csgo\cfg folder is never found. The second most common cause is Steam Cloud replacing your local files with the cloud copy. Turning off sync in the game's properties once is enough.
To confirm the config loaded, use the same echo "Autoexec loaded!" line at the end of the file. If the message shows up in the console after launch, the config was picked up. If not, work through the points above.
Your Config as a Working Tool
Installing a config in CS2 is the first step toward a stable setup, not the last. Over time it gains new binds, crosshair tweaks, and handy aliases for practice. If you want a pro setup as a base, look at all of NiKo's settings, for example, and move into your autoexec only what suits you.
A good habit is keeping a copy of autoexec.cfg in the cloud or on a USB drive, not just on your PC. It is especially handy if you play on several machines or go to LAN events: copy the file into the right folder and you are playing with your own settings.
A well-made config will not raise your rating by itself, but it removes the moments when your settings reset before an important match, your crosshair changes, or your binds stop working.
FAQ
Where do I put a config file in CS2?
Your own autoexec.cfg and any downloaded configs go in C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg. The settings the game saves from the menu live separately, in userdata\<ID>\730\local\cfg.
Do I need +exec autoexec.cfg if the file is already in the folder?
Yes, it is the most reliable option. With the launch option, the game runs your autoexec on every start; without it, the file may not be picked up.
How do I install a pro player's config in CS2?
The same way as your own: download the .cfg, check the commands, put the file in ...\game\csgo\cfg, and add +exec with its name to your launch options. Back up your current config first.
Do CS:GO configs work in CS2?
Partly. Binds and many crosshair and viewmodel commands still work, but some CS:GO commands were removed in CS2. The game skips those lines, so test an old config line by line in the console.
