In late 2023, Counter-Strike's 25th Anniversary update pushed changes to the CS 1.6 client, including networking changes that broke compatibility with a large number of older servers and left some players with worse performance than before. Valve kept the old version available as a public beta branch named steam_legacy. Switching to it takes about a minute in Steam and no password, and for players who cannot connect to their usual servers, or whose ping got worse after the update, it is often the difference between playing and not. This guide shows how to switch and how to decide whether you should.
1. When steam_legacy is the right choice
Roll back if any of these describe you:
- Servers you used to play on now reject you or fail to connect after the anniversary update.
- Your ping, choke or loss got noticeably worse specifically since the update, especially against old servers.
- A plugin-heavy community server you rely on has not updated for the new client.
If your servers work fine on the current build, there is no reason to downgrade — stay current. This is a compatibility escape hatch, not a general "old is better" recommendation.
2. Switch the branch in Steam
- Open your Steam Library.
- Right-click Counter-Strike and choose Properties.
- Go to the Betas tab.
- In the beta-participation dropdown, select steam_legacy.
- Close the window. Steam will download the older build automatically.
There is no access code — steam_legacy is a public branch, so the dropdown selection is all it takes. Wait for the download to finish before launching.
3. Confirm you are on the legacy build
After it downloads, launch the game and open the console:
version
The version command prints the build number and date. On steam_legacy it reports the pre-anniversary build rather than the current one. You can also tell by behaviour: servers that rejected the new client will now accept you.
4. Re-check your rates after switching
The anniversary update raised the usable rate ceiling; the legacy build uses the older limits. After rolling back, set rates appropriate to the old engine:
rate 25000 cl_updaterate 101 cl_cmdrate 101 ex_interp 0.01
A rate of 100000 that worked on the current build may not help on legacy — 25000 was the practical ceiling there. See best client rates for the full picture.
5. Going back to the current build
The switch is fully reversible. Repeat the steps and choose None in the beta dropdown to leave the beta and return to the current release. Steam re-downloads the current build. Nothing about your configs or installed content is lost by switching branches back and forth.
Server operators: the other side of this
If you run a server and anniversary-build players cannot connect, the fix is usually on the server, not asking every player to downgrade. Update your engine and mods; the server-side version of this problem is covered in fixing a server broken by the 25th Anniversary update. Telling your whole player base to roll back is a last resort.
Common errors
- steam_legacy not in the dropdown — you are looking at the wrong game's properties, or Steam is offline. Confirm it is Counter-Strike (1.6) and that Steam is online.
- Selected the branch but nothing changed — the download had not finished, or the game was open. Fully close CS, let Steam finish downloading, and relaunch.
- Still cannot connect after rolling back — the problem was not the client version. Work through the high-ping guide and the server's own status.
- Rates feel wrong on legacy — you kept a high
ratefrom the current build. Drop it to 25000 for the old engine. - Wanted current, stuck on legacy — set the beta dropdown back to None and let it re-download.
Verification
Run version in the console and confirm it reports the pre-anniversary build, then connect to the server that was rejecting you and confirm you get in and can play a full round. If the switch fixed your problem, leave it; if it did not, switch back to None — there is no benefit to staying on an older build once you have ruled it out as the cause.
