The Steam console is a text-based tool built into Steam that lets you run commands to fix game problems, change settings, or test features

The Steam console is a hidden command window inside the Steam client itself. It does not appear in your menus by default — you have to open it through a keyboard shortcut or by launching Steam with a special flag. Once open, you can type commands to restart services, clear cache, force updates, or diagnose why a game won't start. Most players never need it, but when a game crashes or won't launch, the console often shows you why.

The console is not the same as the in-game console that some games have (like the developer console in Valve games). This is Steam's own console, separate from any individual game. It runs behind the scenes and controls how Steam itself behaves.

Key Takeaways

  • Open the Steam console by pressing Ctrl+Alt+B while the Steam client is open, or by launching Steam with the -console flag from your computer's command line.
  • Common commands include clear (to clear the console), exit (to close it), and restart_app_cache (to fix corrupted game files).
  • The console shows error messages and logs that explain why a game failed to launch or crashed, which you can copy and share with support.
  • You do not need the console for normal gaming — use it only when a game won't start or Steam support asks you to run a specific command.

Opening the console with a keyboard shortcut

The fastest way to open the Steam console is to press Ctrl+Alt+B while the Steam client window is in focus. The console appears as a black text box at the bottom of the Steam window. You can type commands directly into it and press Enter to run them.

If the shortcut does not work, make sure the Steam window is active (click on it first) and that you are not in a game. The shortcut only works when you are in the Steam client itself, not when a game is running.

Opening the console by launching Steam with a flag

If the keyboard shortcut does not work on your system, you can launch Steam with the -console flag instead. On Windows, right-click the Steam shortcut on your desktop or in your Start menu and select Properties. In the Target field, add a space and then -console at the very end, so it reads something like C:\Program Files (x86)\Steam\steam.exe -console. Click explore and then OK.

The next time you launch Steam using that shortcut, the console window will open automatically at the bottom of the Steam client. You can also open a command prompt on your computer, navigate to your Steam folder, and type steam.exe -console to launch it that way.

Common console commands and what they do

You do not need to memorize commands — you only run them when Steam support tells you to or when you are trying to fix a specific problem. Here are the ones you are most likely to see:

CommandWhat it does
clearClears all text from the console window so you can see new messages more easily.
exitCloses the console window.
restart_app_cacheRestarts Steam's app cache service, which can fix games that won't launch or update.
force_install_dir [path]Forces Steam to recognize a game installed in a non-standard location.
set_launch_options [options]Adds custom launch parameters to a game (rarely needed unless support tells you to).

If you type a command incorrectly, the console will usually tell you it does not recognize it. There is no harm in trying — wrong commands straightforward do not execute.

Reading error messages in the console

When a game fails to launch, the console often displays error codes or messages that explain why. These messages can be cryptic, but they give you and Steam support real information about what went wrong. Common errors include missing files, permission problems, or conflicts with other software.

If you are troubleshooting a game that will not start, open the console, try to launch the game, and watch what appears. Copy the error message (you can select and right-click to copy text from the console) and paste it into a search engine or share it with Steam support. The specific error is much more useful than saying "the game won't start."

When to use the console and when not to

Use the console only when you have a real problem — a game that will not launch, an update that is stuck, or when Steam support specifically asks you to run a command. Do not type random commands into the console just to experiment. Most commands are harmless, but some can change settings in ways that are hard to undo.

If a game is running fine, you do not need the console at all. It is a troubleshooting tool, not something you need for normal play. Close it when you are done by typing exit or pressing Ctrl+Alt+B again.

Frequently Asked Questions

Can I break Steam by typing the wrong command in the console?

Unlikely. Most wrong commands straightforward will not run, and Steam will tell you the command is not recognized. The commands that actually do something are usually safe — they restart services or clear cache, which is what you want when troubleshooting. Avoid typing commands you do not understand, but a typo will not damage your installation.

Why does my game still not launch even after I ran a command?

The console can fix some problems (like corrupted cache files) but not all. If a command does not work, the problem may be outside Steam — a missing driver, a firewall blocking the game, or a conflict with antivirus software. Copy the error message from the console and search for it, or contact Steam support with the exact text.

Is the Steam console the same as the in-game console?

No. The Steam console controls Steam itself. Some games (like Half-Life 2 or Counter-Strike) have their own in-game console that you open with a different key, usually the tilde (~) or backtick key. That console runs commands inside the game, not in Steam.

Do I need to restart Steam after running a console command?

Usually not. Commands like restart_app_cache restart the service without closing Steam. If Steam support tells you to restart, they will say so explicitly. You can close the console and continue using Steam normally after running a command.