← CS2
Walker Bex / Gaming / CS2

CS2 Config Not Saving: Which Settings Keep Resetting?

Find whether CS2 resets keybinds, gameplay preferences, or video settings, and safely identify account files and Steam Cloud conflicts.

Quick answer

Change one setting, leave CS2 normally, and reopen it before editing any files. If the setting resets, check whether the correct Steam account is in use, whether a launch option or custom config re-applies an old value, and whether Steam Cloud shows a sync problem. Back up the account’s CS2 config folder before deeper work.

Identify what actually resets

  • Only keybinds reset: focus on the account-specific key configuration and anything that runs commands at startup.
  • Crosshair, HUD, or other preferences reset: check user configuration and Steam account syncing.
  • Resolution, display mode, or graphics options reset: check the video configuration and whether the selected resolution is supported.
  • All settings revert across machines: check Steam account selection and Steam Cloud status before touching files.

Test only one clearly visible setting at a time. Change it from the CS2 menu, close the game through its normal Exit/Quit action, wait for any Steam Cloud sync, reopen, and check. A crash or forced termination is not a reliable save test.

First look for an override or sync problem

  • In Steam Library > Counter-Strike 2 > Properties > General, copy the Launch Options field to a note and look for any user-added setting or startup commands that could override the menu. Do not delete the text without a copy.
  • If you have a custom config or autoexec that sets the same value, temporarily stop that override for one controlled test. This article does not require rebuilding an autoexec.
  • Check Steam for “Out of Sync” or a Cloud conflict warning. Do not select a cloud or local version before comparing timestamps and identifying which contains the changes you want.
Worth checking

Turning Steam Cloud off is not a universal fix. It changes cross-device synchronization and can create conflicting local and cloud versions; make a backup and understand the consequences first.

Where CS2 settings are usually stored on Windows

Steam documents the parent cloud-data location as Steam\userdata\[account ID]\[game app ID]. Community-documented CS2 Windows installations commonly use Steam\userdata\[account ID]\730\local\cfg. This is account-specific and may differ with custom Steam install locations. Check your own folder before assuming any filename exists.

  • cs2_user_keys_0_slot0.vcfg: commonly contains key bindings.
  • cs2_user_convars_0_slot0.vcfg: commonly contains player preference variables.
  • cs2_video.txt: commonly contains display and graphics preferences.
  • cs2_machine_convars.vcfg: commonly contains machine-related variables; leave it alone unless a specific investigation requires it.
Worth checking

File names and exact assignment are based on CS2 community file inspection rather than an official per-file Valve specification. A future patch could move or rename them.

Back up before inspecting or changing anything

  • Exit CS2 and Steam completely. Open the relevant 730\local\cfg folder for the correct Steam account.
  • Copy the entire cfg folder to a dated backup location outside the Steam userdata directory; do not move the original.
  • Check file modification dates before and after changing one setting through the game. If no file changes, document that before further diagnosis.
  • Do not set config files to read-only, grant broad folder permissions, or delete .vcfg or video files as a routine fix.

File timestamps are diagnostic clues, not proof that one specific file must be responsible. If the problem began immediately after a patch, document the game version before trying invasive edits.

When the reset happens on another PC

Steam Cloud can carry some settings between computers, but each game chooses which files are synchronized. Let the first machine finish syncing before opening CS2 elsewhere. If Steam detects conflicting versions, read its conflict dialog and compare dates with the last known good settings. Keep the backup until you confirm the new state survives a clean restart.

Sources

More CS2