Turn a .vcfg into a config, and run it

From the files the game wrote to an autoexec.cfg you can read, edit and carry to another machine.

  1. 01Drop the files onto the converterDrag all three .vcfg files onto the Convert page at once — settings, binds and machine. Nothing is uploaded: the parsing happens in your own browser and the files never leave it.
  2. 02Pick how much of it you wantClean is the default and is what most people want: the settings, without the cached menu state that makes up most of a real .vcfg. Everything gives you the raw dump, and essentials cuts it to the lines that change how the game plays.
  3. 03Read what it dropped, and whyEvery removed line is listed with its reason. This is worth one look, because it is where you find out that something you thought was a setting is actually a record of a popup you dismissed in 2023.
  4. 04Save it as autoexec.cfgDownload it into Counter-Strike Global Offensive\game\csgo\cfg\. That is inside the game install, not the userdata folder you took the originals from — they are two different places and putting it in the wrong one is the single most common reason a config does nothing.
  5. 05Run it and check the console said soOpen the console and run exec autoexec. The last line of every config from here is an echo, so the console prints a confirmation — if you do not see it, the file is not where you think it is.
  6. 06Put it back on next launchCS2 does not run autoexec.cfg by itself any more. Add +exec autoexec to the game's launch options in Steam, or run it by hand each session.

The tools this uses

  • Convert — CS2 .vcfg files into autoexec.cfg, or cs2_video.txt into readable video settings
  • Check — The lines in your config that stopped working and nobody told you

All tutorials