Counter Strike 2GuideYour CS2 server runs perfectly well without a token, and friends can join it by address at any time. A Game Server Login Token (GSLT) is only needed for…
Your CS2 server runs perfectly well without a token, and friends can join it by address at any time. A Game Server Login Token (GSLT) is only needed for one thing: making the server appear in the in-game Community Server Browser. Tokens are free from Steam. Paste one into the Game Server Login Token (GSLT) field in your server's Details tab, save, and restart.
Private server for friends: no token needed.
You want strangers to find your server in-game: you need a token. Without one, your server never gets listed with Steam's public server list, so it cannot show in the browser. That is a Valve rule, not something we control.
Sign in at steamcommunity.com/dev/managegameservers.
Create a new game server account with App ID 730 (that is Counter-Strike 2) and any memo you like, for example your server name. The memo is just a label for you.
Copy the login token that Steam generates. It is a long string of letters and numbers.
Two Steam requirements to know before you start:
The Steam account needs a verified phone number and must not be a limited account. If the page refuses to make a token, that is almost always why.
Each server needs its own token.
On My Servers, press Detail view on your CS2 server.
In the Overview card, open the Details tab.
Paste your token into Game Server Login Token (GSLT), the second field in the Details tab, directly under RCON Password. The field is hidden like a password; the eye icon reveals it if you want to check the paste.
Press Save changes in the popup at the bottom of the page.
Restart the server. The token is handed to CS2 when the server starts, so it does nothing until the next power-up. See start, stop, and restart your server.


Once the server is back Online, open CS2, go to Play, then the Community Server Browser, and search for your server name. Give it a couple of minutes after the restart.
To go private again, clear the field, save, and restart. Nothing else changes: your settings, config, and plugins are untouched.
All of these work whether or not a token is saved:
The address on your server card. This is what you send to other people. The Join button next to it is your own shortcut, on desktop while the server is Online; friends get the same button on your server's public page if you set one up.
The in-game console. In CS2, turn on Settings, Game, Enable Developer Console, press ~, and type connect your-address:port using the address from your server card. With a server password set, use connect your-address:port; password yourpassword.
Steam favorites. In the Steam client: View, Game Servers, Favorites, Add a Server, then paste the address.
Work down this list before anything else:
Did you restart after saving? This is the number one cause. The token only applies on a fresh start.
Is the server Online right now? Browser listing needs the server online, so a stopped or sleeping server is not listed. A direct connection attempt still wakes a sleeping server, so anyone with the address is unaffected.
Did CS2 just update? Out-of-date servers drop off the browser until they restart onto the new build. See CS2: server out of date after an update.
Is the server failing to start instead of running unlisted? A mistyped, retired, or banned token stops CS2 from starting. The server card goes red and reads "Server failed to start" with either "Invalid Game Server Login Token (GSLT)" or "Game Server Login Token is banned". Steam can retire tokens that sit unused for a long time, and it revokes tokens belonging to an account with a game ban, so generate a fresh token on the same Steam page and replace the old one. Clearing the field and restarting also gets the server running again, as a private server.
Treat the token like a password: anyone holding it can run a server under your Steam account. Do not paste it into Discord or leave it visible in a screenshot. The dashboard hides it for that reason.
Message us in Discord or at support@haptic.gg with your server name and what you see in the browser search. Never include the token itself.