Where do I put autoexec.cfg in CS2?

In the cfg folder of your CS2 install. On a default Steam library on Windows that is C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg; on Linux it is ~/.steam/steam/steamapps/common/Counter-Strike Global Offensive/game/csgo/cfg. If CS2 is in another Steam library, right-click Counter-Strike 2 in Steam → Manage → Browse local files, then open game\csgo\cfg.

How do I make CS2 load my autoexec?

Add +exec autoexec to the launch options (Steam → right-click Counter-Strike 2 → Properties → General → Launch options) so it runs on every start. To load it once without restarting, open the developer console and type exec autoexec.

Why doesn't a pro's config include their viewmodel, binds or video settings?

Because we only write what the player's own source states — their stream chat-bot command, channel panel, video or post, or Liquipedia citing an official match. Those sources give sensitivity, DPI, sometimes zoom sensitivity and a crosshair share code. Anything else would be a guess, so it stays out; every pro line in the file is commented with its source URL and date.

Do older crosshair commands still work after CS2 1.41.8.2?

CS2 1.41.8.2 (September 2026) moved crosshairs to whole-pixel sizes (cl_crosshair_length, cl_crosshair_screen_height …). A crosshair saved in that format gets those commands; an older share code keeps the legacy cl_crosshairsize / cl_crosshairgap commands it was made with — there is no exact formula between the two. If your client ignores the legacy lines, paste the share code from the file's comment into the crosshair settings instead.

What does host_writeconfig do at the end of the file?

It saves the values the file just set into CS2's own config, so they stay even if the autoexec stops running. It is optional — untick it in the generator to leave it out.

Is SensLab really free?

Yes — the core converter, crosshair generator, pro presets, and pro comparison tables are permanently free. We use Vercel's cookieless analytics to count page views; no ads, no sign-up, no personal data collection.

CS2 Config Generator

Turn a pro’s sourced settings — or your own — into a ready autoexec.cfg. 218 CS2 pros with a citable sensitivity or crosshair.

From a pro’s sources

Search a CS2 pro

Your choice

My sensitivity

My crosshair share code

Echo a line when the file runsecho "autoexec.cfg loaded"

Save to CS2's config at the endhost_writeconfig

autoexec.cfg

11 lines

// autoexec.cfg - Counter-Strike 2, generated with SensLab (https://senslab.pro/cs2-config)
// Put it in ...\game\csgo\cfg\ and add "+exec autoexec" to CS2's launch options.

// ============================================================
// Your choice - not from any pro
// ============================================================

echo "autoexec.cfg loaded"

// Save these values to CS2's own config, so they stick even without this file.
host_writeconfig

Pick a pro or add your own sensitivity or crosshair — the file has no settings yet.

In short: save the file as autoexec.cfg in CS2’s game\csgo\cfg folder and add +exec autoexecto the launch options. A pro’s config holds only what their own source states — sensitivity, zoom sensitivity when stated, crosshair — each line commented with the source URL and date.

How do I install a CS2 autoexec.cfg?

Pick a pro or your own settings. Search a CS2 pro to start from their sourced sensitivity and crosshair, or enter your own sensitivity, DPI and crosshair share code.
Choose what goes in. Tick the sections you want. Pro values are commented with their source and date; your own picks go under "Your choice".
Download autoexec.cfg. Download the file or copy its text, and save it as autoexec.cfg in CS2's cfg folder (game\csgo\cfg).
Load it on every start. In Steam, add +exec autoexec to Counter-Strike 2's launch options — or type exec autoexec in the console to load it once.

Where is the CS2 cfg folder?

Default CS2 cfg folder by operating system
System	Folder (default Steam library)
Windows	C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg
Linux	~/.steam/steam/steamapps/common/Counter-Strike Global Offensive/game/csgo/cfg

Installed CS2 in another library? In Steam, right-click Counter-Strike 2 → Manage → Browse local files, then open game\csgo\cfg. Make sure the file ends in .cfg, not .cfg.txt.

What goes into a pro’s config?

Only values the player’s own source states: the sensitivity from their stream chat-bot command, channel panel, video or post (zoom sensitivity only when that same quote states it), and the crosshair share code they publish or Liquipedia records from an official match. DPI is a mouse setting, so it appears as a comment, and m_yawis left at its default. Viewmodel, binds, radar and video settings are never added for a pro — no source we accept lists them. A source that is old or undated is marked “may be outdated” in the file, just like on the pro player pages.

Which crosshair commands does the file use?

The ones that match the crosshair’s format. A crosshair made in CS2 1.41.8.2 or later uses the pixel commands (cl_crosshair_length, cl_crosshair_screen_height); an older share code keeps the legacy ones (cl_crosshairsize, cl_crosshairgap). The share code is always in a comment above them. To tweak a crosshair first, use the CS2 crosshair generator — the config page can load it from there — and pick your sensitivity with the CS2 sensitivity converter.