Counter Strike 2 Autoexec Guide: How to Create and Set Up Your Config File (2026)

The Counter Strike 2 autoexec file is the most reliable way to keep your settings permanent. Without it, CS2 can reset your crosshair, binds, radar, and network settings after game updates or when you play on a different PC. With it, every command you care about loads automatically the moment CS2 starts — every single time. This guide walks you through creating the file, placing it correctly, verifying it works, and filling it with a complete ready-to-use config.

• TL;DR
• An autoexec.cfg is a text file that runs your console commands automatically when CS2 launches
• It must be saved in: ...\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg\
• The file must be named exactly autoexec.cfg — not autoexec.cfg.txt
• Add +exec autoexec.cfg to your CS2 Steam launch options to guarantee it loads
• Disable Steam Cloud for CS2 or it may overwrite your file after updates
• Use echo "AUTOEXEC LOADED" at the end of the file to confirm it is working
• Video settings are NOT saved by autoexec — those must be set manually in-game
• Every professional CS2 player uses an autoexec to maintain consistent settings across PCs

What Is a CS2 Autoexec File?

An autoexec.cfg is a plain text file that CS2 reads at startup. Every line inside it is treated as a console command — exactly as if you typed it manually into the developer console. The name stands for auto-execute: the game executes the file automatically so you never have to type commands again after a fresh install or a game update.

The most common things players store in their autoexec are crosshair settings, viewmodel commands, mouse sensitivity, radar configuration, network rates, keybinds, and performance tweaks. Think of the autoexec file as a storage of your best settings in Counter-Strike 2. It removes annoying obstacles on your way to winning by making sure your setup is exactly right every session.

There is a difference between the autoexec and the regular config.cfg file. CS2 can overwrite config.cfg automatically during updates or when the game detects a settings conflict. The autoexec config is protected from such issues — changes are only made when you want them. You are in full control.

The autoexec is completely VAC-safe. You are only using Valve’s own built-in console commands. Professional players have used autoexec files for years in CS:GO, and the practice continues in CS2. There is no risk of a ban from using one.

What Autoexec Cannot Do

Before creating your file, it is important to know one key limitation. Video settings — resolution, display mode, refresh rate, graphics quality — are stored in a separate file called video.cfg and are not affected by autoexec. If you want those to persist, set them manually inside CS2 each time you reinstall, or find the video.cfg file and back it up separately.

Everything else — crosshair, binds, sensitivity, radar, network, audio, viewmodel, HUD — can be saved and loaded through autoexec.

Step-by-Step: How to Create Your CS2 Autoexec

Step 1: Navigate to the Correct Folder

Open File Explorer on Windows and navigate to:

C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg\

If your Steam library is on a different drive, the path will start with that drive letter instead of C:. The folder name is cfg and it sits inside the csgo folder, which itself is inside the CS2 game directory. This is the only location CS2 checks for config files — putting it anywhere else will not work.

If the cfg folder does not exist, you can create it manually. Right-click inside the csgo directory, select New → Folder, and name it cfg.

Step 2: Create the autoexec.cfg File

Inside the cfg folder, right-click on an empty area and select New → Text Document. Before typing any name, make sure Windows is showing file extensions. Go to the View menu in File Explorer and check File name extensions.

Name the file exactly: autoexec.cfg

It is very important to select All Files in the Save as type field when saving. Otherwise, Windows will automatically save the file as .txt and CS2 will not be able to read it. The name must be exactly “autoexec.cfg” with no other characters or spaces allowed.

To be safe, after creating the file, right-click it and select Properties. The file name shown should end in .cfg — not .cfg.txt or .txt. If it says .txt, rename it and remove the .txt extension entirely.

Step 3: Open and Edit the File

Right-click the autoexec.cfg file and choose Open with → Notepad. For a better experience, use Notepad++ or VS Code if you have them — they handle formatting and encoding better than basic Notepad and are less likely to silently break the file.

Each command must be on its own separate line. Do not paste them all onto one line. The format is exactly the same as typing into the CS2 console — one command per line, with the correct spacing and quotation marks.

Here is a simple example of what the inside of the file looks like:

sensitivity 1.2
cl_crosshairsize 2
cl_crosshaircolor 4
bind "mwheeldown" "+jump"

After adding your commands, save the file with Ctrl + S. Close it.

Step 4: Add the Launch Option in Steam

Creating the file is not enough on its own. You also need to tell CS2 to execute it at startup. Open Steam, find CS2, right-click and choose Properties. In the launch options section, type +exec autoexec.cfg.

This launch option tells CS2 to find and run your autoexec file every time the game launches. Without this step, CS2 may or may not load the file depending on the game version. Adding it guarantees the file always runs.

Step 5: Disable Steam Cloud for CS2

Steam Cloud can silently overwrite your local config files with older versions stored in the cloud — especially after game updates. Steam Cloud is a tricky thing that can delete your file. Make a backup copy on your computer, or turn off Steam Cloud for CS2.

To disable it:

1. Right-click CS2 in your Steam Library and select Properties
2. Go to the General tab
3. Find Steam Cloud and uncheck the option that says Keep game saves in the Steam Cloud for Counter-Strike 2

This makes your local autoexec.cfg the permanent authority. Steam can no longer overwrite it.

Step 6: Verify the File Is Working

Add this line at the very bottom of your autoexec.cfg before saving:

echo "AUTOEXEC LOADED!"

The next time you launch the game, open the console with the tilde key and check if the message “AUTOEXEC LOADED!” appears. If you see it, the autoexec is enabled correctly and all commands within the file are applied automatically.

If the message does not appear, check these things:

• The file is named exactly autoexec.cfg with no hidden .txt extension
• The file is in the correct cfg folder path
• You have added +exec autoexec.cfg to your Steam launch options
• The file is saved and not empty

You can also manually trigger the file at any time by opening the console and typing exec autoexec.

How to Use Comments in Your Autoexec

You can add comments to your autoexec file to organize sections and remind yourself what each command does. Comments start with two forward slashes (//) and are completely ignored by CS2 — they are only for you to read.

Example:

// ===== CROSSHAIR =====
cl_crosshairstyle 4
cl_crosshairsize 2

// ===== MOUSE =====
sensitivity 1.2
m_rawinput 1

Using comments becomes very useful once your file grows longer. Labelling each section means you can find and update specific commands quickly without reading through everything.

Complete Ready-to-Use CS2 Autoexec Config (2026)

Below is a complete, paste-ready autoexec.cfg designed for competitive play in 2026. Every section is commented. Review each value and adjust to your own preferences before saving. Replace sensitivity, crosshair, and bind values with your own where noted.

Open your autoexec.cfg file and paste the following:

// ============================================
// CS2 AUTOEXEC CONFIG — GAMINGPROMAX 2026
// Replace values marked with [ADJUST] to suit your setup
// ============================================

// ===== MOUSE AND SENSITIVITY =====
sensitivity 1.2                     // [ADJUST] Your in-game sensitivity
m_rawinput 1                        // Always on — bypasses Windows mouse settings
m_mouseaccel1 0                     // Disable mouse acceleration (low speed)
m_mouseaccel2 0                     // Disable mouse acceleration (high speed)
zoom_sensitivity_ratio 1.0          // Scoped sensitivity multiplier. Most pros use 0.8–1.0

// ===== NETWORK RATES =====
rate 786432                         // Maximum data rate to servers. Lower to 262144 on poor connections
cl_interp_ratio 1                   // Use 2 on unstable/high packet loss connections
cl_interp 0                         // Let CS2 calculate interpolation automatically
cl_cmdrate 128
cl_updaterate 128

// ===== FPS AND PERFORMANCE =====
fps_max 0                           // Remove FPS cap. Use your monitor Hz x1.5 without Reflex
cl_forcepreload 1                   // Preloads map assets to reduce mid-round stutter
engine_low_latency_sleep_after_client_tick true   // Reduces input latency with NVIDIA Reflex
r_drawtracers_firstperson 0         // Hides your own bullet tracers
r_show_build_info false             // Removes game version watermark from bottom left

// ===== CROSSHAIR =====
cl_crosshairstyle 4                 // 4 = Classic Static (recommended for competitive)
cl_crosshairsize 2                  // [ADJUST] Line length. Pro range: 1–2.5
cl_crosshairgap -2                  // [ADJUST] Gap between lines and center. Negative = tighter
cl_crosshairthickness 0.5           // [ADJUST] Line thickness. Pro range: 0–1
cl_crosshairdot 0                   // 0 = no center dot, 1 = dot enabled
cl_crosshaircolor 4                 // 4 = cyan (most visible), 1 = green
cl_crosshair_drawoutline 0          // 0 = no outline, 1 = black outline around lines
cl_crosshairalpha 255               // Always 255 — fully opaque

// ===== VIEWMODEL =====
viewmodel_fov 68                    // Maximum value — pushes gun furthest from screen center
viewmodel_offset_x 2.5              // Maximum right offset — clears center sightline
viewmodel_offset_y 0                // Forward/back position. 0 is standard
viewmodel_offset_z -1.5             // Lowers the gun. Negative = lower
viewmodel_presetpos 3               // 3 = Classic preset as base
cl_righthand 1                      // 1 = right hand, 0 = left hand

// ===== RADAR =====
cl_radar_scale 0.35                 // Zooms out radar to show full map. Range 0.25–1
cl_radar_always_centered 0          // 0 = map stays fixed, you move on it (better awareness)
cl_radar_rotate 1                   // Radar rotates with your view direction
cl_radar_icon_scale_min 0.6         // Makes player icons on radar easier to read
cl_hud_radar_scale 1.15             // Slightly increases the radar widget size on screen
cl_radar_square_with_scoreboard 1   // Square radar shape when scoreboard is open

// ===== AUDIO =====
volume 1                            // Always at maximum — control loudness via hardware
snd_musicvolume 0                   // Mutes in-game music during play
snd_roundstart_volume 0             // Mutes round start music
snd_roundend_volume 0               // Mutes round end music
snd_deathcamera_volume 0            // Mutes death camera music
snd_tensecondwarning_volume 0.15    // Keep this audible — it tells you the round is ending
snd_mixahead 0.05                   // Reduces audio delay for more immediate footstep feedback
voice_scale 0.7                     // Slightly reduces teammate voice volume

// ===== HUD =====
hud_scaling 0.85                    // [ADJUST] HUD element size. Range 0.5–0.95
cl_hud_color 0                      // Default HUD color
cl_hud_playercount_showcount 1      // Shows player count numbers instead of avatars
r_show_build_info false             // Removes version number from bottom left

// ===== GENERAL GAME SETTINGS =====
cl_autowepswitch 0                  // Disables auto weapon switch when picking up a new gun
cl_showfps 1                        // Shows FPS counter in corner (set to 0 to hide)

// ===== KEYBINDS =====
bind "mwheeldown" "+jump"           // Scroll down to jump (bhop scroll)
bind "mwheelup" "+jump"             // Scroll up to jump (optional)
bind "mouse5" "r_cleardecals"       // Side mouse button clears blood and bullet holes
bind "mouse3" "player_ping"         // Middle mouse button pings location

// Grenade binds — [ADJUST] keys to match your preference
bind "f" "use weapon_flashbang"
bind "z" "use weapon_smokegrenade"
bind "x" "use weapon_molotov; use weapon_incgrenade"
bind "c" "use weapon_hegrenade"

// Jumpthrow bind — works in all competitive modes
alias "+jumpthrow" "+jump;-attack"
alias "-jumpthrow" "-jump"
bind "v" "+jumpthrow"

// Quick switch to last weapon slot
bind "q" "use weapon_knife; slot1"

// ===== CONFIRMATION =====
echo "AUTOEXEC LOADED — GAMINGPROMAX 2026"

After pasting, adjust any values marked with [ADJUST] to match your own settings. Then save the file and launch CS2. Open the console with ~ and look for the echo message at the bottom to confirm everything loaded correctly.

Multiple Config Files: Practice vs Competitive

Your autoexec is not the only cfg file you can create. You can make separate config files for different situations and load them on demand using exec [filename] in the console.

A good setup is:

• autoexec.cfg — Your permanent competitive settings. Loads every time CS2 starts.
• practice.cfg — Practice server setup with sv_cheats, infinite ammo, grenade trajectories, and bot controls. Only loaded when you want it.
• awp.cfg — Optional. AWP-specific sensitivity or zoom settings if you want them separate.

To load a file manually during a session, open the console and type:

exec practice

This runs every command in your practice.cfg file instantly. No need to retype everything. Keep your practice commands separate from your autoexec so they do not run in competitive matches automatically.

Autoexec Troubleshooting: Common Problems and Fixes

Autoexec Is Not Loading

Check these in order:

• File is named exactly autoexec.cfg — no hidden .txt extension. Enable file extensions in File Explorer to verify.
• File is in the correct folder: ...\Counter-Strike Global Offensive\game\csgo\cfg\
• Steam launch options contain exactly: +exec autoexec.cfg
• Steam Cloud is disabled so it cannot overwrite the file
• The file is not empty — open it and confirm your commands are there

Settings Keep Resetting After Updates

Steam Cloud can delete or overwrite your file. Disable it and make a backup copy of your autoexec on a flash drive or cloud storage of your own. After any major CS2 update, open the console and type exec autoexec to manually reapply your settings, then check if everything still looks right.

Some Commands Are Not Working

A number of CS:GO autoexec commands no longer work in CS2. If a command is not applying, check whether it is a Source 2-compatible command. Common ones that are broken or changed include net_graph (replaced by cq_netgraph), -tickrate (does nothing online), and several thread management flags. Refer to our CS2 all console commands guide for a verified list of what works in 2026.

File Has Wrong Encoding

If you notice strange characters or commands not running despite correct syntax, the file may have been saved in the wrong encoding. Open the file in Notepad, go to File → Save As, and set the encoding to UTF-8 without BOM. Save it again as autoexec.cfg (selecting All Files in the type dropdown). Notepad++ handles this more reliably than basic Notepad.

Jumpthrow or Alias Commands Not Working

Alias commands must be defined before the bind that uses them in the file. If your jumpthrow bind is not working, make sure the two alias lines appear above the bind line in your autoexec. Order matters for aliases.

Keeping Your Autoexec on Other PCs

One of the main reasons pros use autoexec files is consistency across different computers. Autoexec gives you a significant advantage especially if you have several computers or decide to visit a LAN tournament. Download your autoexec config on a flash drive or place it online. After that, you can use it on a new computer. All settings except video will be automatically applied by autoexec. Video setup should be manually adjusted.

To use your autoexec on a new PC:

1. Copy your autoexec.cfg to a USB drive or upload it to Google Drive, Dropbox, or similar
2. On the new PC, navigate to the CS2 cfg folder: ...\Counter-Strike Global Offensive\game\csgo\cfg\
3. Paste your autoexec.cfg into that folder
4. Add +exec autoexec.cfg to the CS2 Steam launch options on that PC
5. Launch CS2 and verify the echo message appears in the console

Video settings still need to be set manually on each new PC, but everything else — your crosshair, sensitivity, binds, radar, and network rates — will load automatically in under a minute.

Do Professional CS2 Players Use Autoexec?

Yes, almost all professional Counter-Strike 2 players use autoexec.cfg. At each tournament, players on professional teams play on different computers. To ensure that all their crosshair, sensitivity, radar, and other settings remain consistent, they use their own CS2 autoexec configs.

This is the real reason the autoexec matters at any skill level. Even if you never go to a LAN event, your home PC can reset settings after Windows updates, driver installations, or CS2 patches. The autoexec is your insurance against all of that.

How the Autoexec Connects to the Rest of Your Setup

The autoexec is the file that locks in every other setting you have configured. For the full list of commands to include, our CS2 all console commands guide has every command organized by category with values and explanations. For your audio settings and the commands to make footsteps clearer, our Counter Strike 2 best audio settings guide covers everything in detail. For your crosshair import codes and commands, our CS2 crosshair settings guide has pro configs ready to paste. For your viewmodel commands, see our Counter Strike 2 best viewmodel settings guide. For sensitivity and mouse configuration, our Counter Strike 2 best sensitivity settings guide has the full breakdown. And for the Steam launch options that run before the autoexec itself, our CS2 launch options guide covers every working command for 2026.

You can also check the official Counter-Strike 2 page on Steam to track updates that may add or change console commands affecting your config.

Frequently Asked Questions