How to Save and Back Up a Dota 2 Configuration

Dota 2 saves normal settings automatically and can synchronize many controls through Steam Cloud. A separate configuration backup is still useful before reinstalling Windows, changing accounts, testing console commands, or moving to another computer.

The safest backup includes the Steam user configuration and any custom autoexec.cfg file. Do not replace the entire cfg folder with an unknown download. Old commands can break current controls or produce errors after a patch.

Let Dota save the normal settings first

Change the required options and hotkeys inside the client. Close the settings menu and exit Dota normally. Wait for Steam to finish synchronization before closing Steam or turning off the computer.

Check that Steam Cloud is enabled for Dota 2 in the game’s Steam properties. Cloud synchronization can preserve many settings and control groups. It is not a replacement for a manual backup when several people use the same computer.

Launch Dota again and confirm the controls. A setting that disappears immediately may have a conflicting bind, a read-only file, or a Cloud conflict.

Know the important folders

The game installation usually contains the folder steamapps/common/dota 2 beta/game/dota/cfg. This is the common location for autoexec.cfg and other local engine configuration files.

Account-specific Steam data is normally stored under Steam/userdata/your Steam ID/570. The remote and local configuration folders inside that path can contain synchronized Dota settings.

Steam may be installed on another drive. Open Dota 2 properties, choose Installed Files, and use Browse to find the real game folder instead of assuming that it is on drive C.

Create a clean autoexec.cfg

Open a plain text editor and create a file named autoexec.cfg in the game/dota/cfg folder. Confirm that Windows did not add .txt to the end. Add one tested console command per line.

Use autoexec for commands that the client does not save through its normal menus. Do not duplicate ordinary hotkeys without a reason. Add a short comment above an unusual command so you remember its purpose later.

Restart Dota and open the console to check the values. If the client does not execute the file, enter exec autoexec in the console and inspect any error message.

Save a named configuration

The console command host_writeconfig followed by a simple name can write a named configuration on supported builds. For example, host_writeconfig practice creates a configuration that can later be loaded with exec practice.

Use letters, numbers, and underscores in the file name. Avoid spaces and quotation marks. The generated file may contain many engine values, so review it before treating it as a portable personal config.

A named config does not replace Steam Cloud and may not include every interface setting. Keep a manual folder backup as well.

Make a manual backup

Close Dota and Steam before copying active configuration files. Create a dated folder and copy autoexec.cfg plus the account-specific 570 configuration folder. Keep the original folder structure in the backup.

Store the backup outside the Steam installation. A reinstall can remove files inside the library. A second drive or a private cloud folder provides better protection.

Do not share a full userdata folder publicly. It can contain account-related data and personal settings. Share only the specific harmless config lines needed for troubleshooting.

Restore without creating a Cloud conflict

Install Dota and launch it once. Close the game and Steam. Back up the newly created files before copying the older configuration into the matching folders.

Start Steam and resolve any Cloud conflict carefully. Choose the copy with the correct modification date. Open a bot match and test hero selection, abilities, items, camera, chat, and control groups.

If the client behaves incorrectly, restore the fresh files and add custom commands one at a time. This identifies the old line that caused the problem.