CS:GO didn't die. It moved to a branch.

01The state of play

Three facts orient everything else. First: CS2 took over CS:GO's AppID — 730 is now Counter-Strike 2, and the merge also swallowed the dedicated server (the servers hub covers that side). Second: Valve did something they almost never do — they kept the old game officially available, as a beta branch of 730 called csgo_legacy, holding the final CS:GO build. Third, and this is the part that matters for this site's recurring theme: because csgo_legacy is an active branch, its manifests still get request codes reliably. The doctrine from the status page — "branches are the downgrade path that still works" — has no better poster child.

02The legacy client

One prerequisite: the account you log in with needs CS2 in its library. The game's free, so this costs nothing — but it does mean logged in, not anonymous. Then:

That pulls the complete final CS:GO for your platform — plan for roughly 30 GB, most of it the shared asset depot. On my last check, June 2026, this branch was still handing out request codes without complaint — which is more than I can say for the older historical builds further down. The same branch is what you'd get by opting into "csgo_legacy" in CS2's beta properties in the Steam client, with the crucial difference that the client route installs it alongside CS2 and keeps it hostage to the updater, while the DepotDownloader copy is yours: a standalone folder Steam won't touch, ready for archiving or the keep-Steam's-hands-off workflow.

03Binaries-only & asset mining

App 730's depot layout makes selective pulls worthwhile, because the weight is wildly uneven: depot 731 is the platform-agnostic content (the ~30 GB), while the per-OS binaries are small — the Windows binaries depot 732 is well under half a gigabyte. Two practical recipes fall out of that split. Refreshing just the executables against an asset folder you already have:

And the reverse — depot 731 alone — is the asset-mining route: Source modders mounting CS:GO content in other games' SDKs want the materials, models and maps, not the binaries. If you only need a handful of files out of that 30 GB (one map, one model set), don't download the depot at all — that's exactly what filelist filtering exists for.

04The legacy server: app 740 still answers

The classic CS:GO dedicated server was never merged away — it still lives at its own AppID, 740, and unlike the client it downloads anonymously:

The community-server scene this serves is quietly healthy: surf, KZ, retakes, 1.6-style pubs — people who never asked for CS2's changes and run the final CS:GO build indefinitely. Players reach those servers from the csgo_legacy branch client, which closes the loop: branch client, app-740 server, both still officially served. The operational side — cron updates, -validate cautions on modded servers — is identical to every other server and lives in the hub.

05Builds older than legacy — the honest part

The legacy branch is one specific build: the last CS:GO. The other decade of versions — the 2014 build with the old M4A1-S sound, the pre-Panorama UI, whatever your nostalgia or your demo archive points at — are ordinary historical manifests on SteamDB, and they're subject to everything the status page documents: unreferenced by any branch, they're in coin-flip-to-dead territory for request codes, with per-account variance to boot. Worth knowing before you try: old CS:GO demos generally need the matching old build to play back, which is precisely why the demo-archiving crowd got hit hardest by the 2025 tightening. If a specific historical manifest still answers for your account, the advice is the site's refrain by now: archive it today — when I went looking for a couple of pre-Panorama builds, some answered and some didn't, and I'd rather you grab the one you want while it's still in the answering column — the legacy branch shows Valve can keep old builds alive, but one branch for one game is the exception that proves the policy.

From here: the downgrade guide for the general manifest workflow, the servers hub for the 740 operations side, and the CLI reference for every flag these recipes used.