CS2 Autoexec: How to Create the File and Use Basic Commands

Crosshair settings, hand placement, and other game parameters – for an experienced player in Counter-Strike, these are critically important settings. Change the crosshair even a little, and the gameplay won’t be as effective anymore, right? But sometimes these settings change on their own, and that’s damn annoying, isn’t it? How to avoid this? The answer is CS2 autoexec.

Now we’ll tell you what this file is, what it includes, how to make it, so everything works just perfectly 🙂.

What is an Autoexec File in CS2?

Autoexec in CS2 is a special file with your personal commands for the shooter. Someone might ask: what’s the point, if we already have the good old config.cfg? The thing is, the commands in that file can be changed automatically by the game. That’s the situation when gamers say: “oh, my config broke again, I’ll have to set everything up manually again!” CS2 autoexec config is protected from such issues. Here, you are the boss! We mean, changes are made only if the player wants them.

Here are the settings most often included in this file:

• crosshair settings;
• hand placement;
• graphics settings;
• binds;
• sound changes in the game.

Every time you launch the game, no matter which PC you use, the settings will remain unchanged. Isn’t that cool?

How to Create a CS2 Autoexec File

So, here’s a step-by-step guide on how to make autoexec CS2.

• Find the folder where the game saves its settings. The path is: …\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg. Yes, don’t be surprised. Even though we are talking about CS2, the folder is still named Counter-Strike Global Offensive.

• Create a new file for the game. It’s best to use Notepad++, though regular Notepad will work too. But come on, what’s the problem with downloading Notepad++ 🙂?
  Type your commands into it. Examples of CS2 autoexec commands: cl_crosshairsize 3, cl_righthand 0, bind “F” “use weapon_flashbang”, fps_max 300.

• Save the newly created file correctly! Name it “autoexec.cfg”. No “my settings to destroy enemies, haha”. Make sure the file doesn’t have a .txt extension, or it won’t work.

• Bind the autoexec launch option to the game so CS doesn’t ignore all your hard work. Open Steam, find CS2. Right-click and choose Properties. In the launch options section, type “+exec autoexec.cfg”.

Important! Steam Cloud is a tricky thing that can delete your file. Make a backup copy on your computer. Or, in the end, just turn off Steam Cloud, and this bad guy won’t interfere with your plans 🙂.

That’s it. You don’t need to think every time how to run autoexec CS2. The game will be forced to do it automatically.

By the way, there’s an alternative way to create the file – CS2 autoexec generator. These services automate the process and help do everything right. This is especially useful for beginners. But the correctness of the process, of course, depends on each service.

Ensuring Autoexec Loads Automatically

So, here are three factors that guarantee the game won’t ignore your settings.

1. Add +exec autoexec.cfg to the Steam launch options.
2. Turn off Steam Cloud for CS2. As we said, this algorithm likes to act on its own from time to time. How to do it? Open CS2 properties. Go to the “General” tab. Find the “Steam Cloud for Counter-Strike” option. By default, this option is enabled. Uncheck it. Done. The potential troublemaker is neutralized 🙂.
3. Add this phrase at the end of the file: echo “Autoexec loaded!“. After entering the game, press the console button and you’ll see these words. If they appear, everything is working as it should. If not, you made a mistake in one of the previous steps. Double-check everything.

After you set up autoexec CS2, nothing will threaten this file.

Key Commands to Include in Your Autoexec

Let’s take a look at the commands worth adding for the best performance in the game. It’s convenient that you don’t have to experiment and dig through settings. Just copy the time-tested parameters.

Must-Have Binds and Settings

Jumpthrow (simultaneous jump and grenade throw). Without it, some smokes, for example, won’t land where they should. After writing these lines in the file, jumpthrow will work with the V key.

• alias “+jumpthrow” “+jump; -attack”
• alias “-jumpthrow” “-jump”
• bind “v” “+jumpthrow”

Bind for buying armor, AK-47, and a flashbang. Don’t waste extra time. Just press F2.

bind “F2” “buy kevlar; buy ak47; buy flashbang”

Crosshair settings. Below is an example of a minimalist and convenient option.

• cl_crosshairsize 3
• cl_crosshaircolor 5
• cl_crosshairalpha 255
• cl_crosshairthickness 1

Hand placement. Optimization of this parameter will make sure the hands don’t block your view during gameplay.

• viewmodel_fov 68
• viewmodel_offset_x 2
• viewmodel_offset_y 2
• viewmodel_offset_z -2

Visual Optimization

Performance Settings. FPS, dynamic effects, and all that.

• fps_max 300
• cl_showfps 1
• r_dynamic 0

Performance and Net Settings

Network Settings. Help avoid lags, high ping, and freezes.

• rate 786432
• cl_interp 0
• cl_interp_ratio 1
• cl_updaterate 128
• cl_cmdrate 128

Important point! If after a game update some function stops working, reconfigure it. It happens. Earlier, we talked about where is CS2 autoexec, so there should be no problem finding it.

How to Use and Test Someone Else’s CFG

You can make it even easier. No need to look at any guide, no need to configure anything manually. Just copy a ready-made config.

Where is the best place to find ready, actually working files:

• websites of professional players;
• large YouTube channels with a reputation;
• forums like Reddit (here you need to be more careful);
• HLTV.

Important! Never download .exe files, even if they promise instant automatic installation. This is a scam that will most likely steal your account data.

We already know where to put autoexec CS2. Let’s remind the path:
…\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg.
A mistake in file location will lead to the file (surprise!) not working.

How to test someone else’s config? Open the console during the game and simply type the name of the file you got. Again, everything will work if you copied the config to the correct CS2 autoexec location. Otherwise, the console will simply ignore your request.

Maintaining and Editing Your Config File

It’s not enough just to create the file. You need to maintain it. We mean you have to make changes regularly.

Again, the simplest and most effective tool for this is Notepad++. For advanced users, VSCode is suitable. It’s more complex but gives more control. It’s better not to use basic Notepad, as it can change the formatting or encoding. The file will simply stop working.

Important! Before making any changes, always create a backup copy – for example, autoexec_backup.cfg. This way, if you break something during editing, you can always return to the original settings.

To make it easier to navigate the config, add comments. For example, before crosshair settings write: // === Crosshair Settings ===. The file does not read such additional symbols. So, lines with them will just remain convenient notes for you.

Watch your syntax, meaning the correctness of the text. Use the correct quotation marks (“), don’t forget the “;”symbol. It may seem like a small thing, but when it comes to a config file, it’s extremely important.

Also, make sure there are no conflicts between binds. Simply put, don’t assign multiple binds to the same key. Otherwise, none of them will work.

How to Safely Edit and Backup Config

Let’s summarize. How to do everything so that nothing breaks?

• Use Notepad++ or VSCode. A default Notepad is a risky tool.
• Before each edit, make a backup copy. It takes just a few seconds.
• Check your binds for duplicates.
• Check the syntax. It takes a little time, but it guarantees correct formatting.

And one more thing. To avoid confusion and unnecessary problems, structure your file with comments. Here’s an example.

// === Mouse Settings ===

• sensitivity 1.8
• m_rawinput 1

// === Crosshair ===

• cl_crosshairsize 3
• cl_crosshaircolor 4

Agree, it’s much easier to understand a config like that. Just in case, a reminder: the symbols // === are not read by the config. They’re just comments for you.

Pro Tips to Get the Most from Your Autoexec

Below, we will look at simple recommendations on how to make an autoexec CS2 without mistakes, so you don’t waste a ton of time later searching for errors and editing.

Start Simple, Grow Gradually

Start with basic settings. For example, first pay attention to your crosshair and key binds. Only then move on to more complex settings.

If you immediately throw a bunch of lines into the config and it doesn’t work, you won’t even know where to start or what to fix. Build your config gradually.

Test After Every Change

After each change, launch an empty server and check if everything is working correctly. If there are problems, fix them. Joining a regular match with a new config may cause problems for you and your team.

Keep It Clean and Updated

Don’t clutter the file with hundreds of lines. Don’t add functions just for fun. Include only those settings that will really help you in a match. And of course, add new parameters if you notice a useful feature somewhere. But only if it’s really useful!

FAQ: CS2 Autoexec Questions Answered

How to run autoexec in CS2?

Go to the following path: …\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg. Here you can find it, run it, and make changes if needed.

Where to store autoexec CS2?

Store your file only here: …\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg. Otherwise, the game simply won’t be able to find it, and nothing will work.

Where is the CS2 autoconfig file?

To find it, just go to this path: …\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg. Unless you previously saved this file somewhere else or, for example, on an external drive.