CS2 Autoexec / Config Generator

Build a clean Counter-Strike 2 autoexec.cfg with the settings that matter — viewmodel, sensitivity, radar, HUD, audio and net — start from a preset, then copy or download the finished file. Save multiple configs in your browser and reload them any time.

Aim & viewmodel

Radar

HUD & audio

Your autoexec.cfg

Save & load configs

Stored locally in your browser — nothing is uploaded.

How to install your autoexec

1. Download the file (or paste the text into a new file named autoexec.cfg).
2. Put it in …\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg.
3. Add +exec autoexec.cfg to your launch options, or type exec autoexec in the console.

Pair it with the crosshair generator and bind generator, and read best launch options for the rest.

What is an autoexec.cfg and why use one?

An autoexec.cfg is a plain text config that CS2 runs automatically at launch. Instead of re-typing console commands every session, you write your settings once and the game applies them every time. It's the reliable way to lock in crosshair, viewmodel, radar, network and bind settings so an update or reinstall never wipes them.

It also keeps everything in one place: if you swap PCs or reinstall, you copy a single file and you're back to your exact setup. Pros and semi-pros all run one — it's the difference between "my settings randomly reset" and a config you never think about again.

What to put in your CS2 autoexec

• Crosshair — your full cl_crosshair* block so it's identical every launch (build one with the crosshair generator).
• Viewmodel & HUD — viewmodel_fov, hand position, and HUD scale so weapons and UI sit where you expect.
• Radar — cl_radar_always_centered 0, scale and rotation for a bigger, more readable map.
• Network rates — max rate and interp settings for the smoothest connection your bandwidth allows.
• Binds — jumpthrow, buy binds and grenade keys (or exec a separate binds file). Build them in the bind generator.
• A confirmation line — end with something like echo "autoexec loaded" so you can see in console that it ran.

Make sure it actually runs

The single most common mistake is the config loading once but not on every launch. Two fixes: add +exec autoexec.cfg to your launch options, or end the file with host_writeconfig. If your settings still reset, double-check the file is named autoexec.cfg (not autoexec.cfg.txt) and sits in the game\csgo\cfg folder.

A minimal autoexec example

You don't need hundreds of lines. A solid starting autoexec is your crosshair block, a couple of quality-of-life settings, your network rates and a confirmation echo — for example a readable radar (cl_radar_always_centered 0, a larger scale), a comfortable viewmodel_fov, your rate settings, then echo "autoexec loaded" on the last line so you can confirm it ran in console. Build it up over time as you find settings you like, and keep a backup copy somewhere safe so a fresh install is a 10-second fix instead of an evening of re-tweaking.

Autoexec FAQ