Steam's download_depot command

01What download_depot was

Steam ships a hidden developer console, and one of its commands, download_depot, told the Steam client to fetch a specific depot — optionally at a specific manifest, i.e. a specific version. For a long time it was the no-extra-software way to downgrade: type one line into the console, point it at an old manifest, and Steam pulled those files. It's the method nearly every older "how to downgrade" guide and YouTube tutorial still shows, which is exactly why so many people arrive at it, try it, and find it broken.

02How you used it

For reference (and because "how do I open the Steam console" is its own search), the method was:

1. Open the console — paste steam://open/console into your browser's address bar (or add -console to Steam's launch options to get a Console tab).
2. Run the command, with the IDs from SteamDB: download_depot <appid> <depotid> <manifestid> — for example download_depot 440 441 7799601114471810121.
3. Wait — there's no progress bar; the console just prints "Depot download complete" when it finishes, and the files land under Steam\steamapps\content\app_<appid>\depot_<depotid>\, which you then move into the game.

Even at its best it was clunky — no progress display, no resume, and it dumped files into a shared content folder you had to clear between downloads. But it worked, and it needed no third-party tool. That's the part that's gone.

03Why it stopped working

The breakage isn't a bug you can fix — it's a deliberate change to how Steam authorizes old downloads. In 2021 Valve introduced manifest request codes: to download a specific (especially older) manifest, the request now has to carry a short-lived code that Steam issues per account, per manifest. The built-in download_depot console command was never updated to navigate that flow for arbitrary old manifests, so today it typically does one of two disappointing things:

• Refuses — "Manifest not available" or an Access-Denied error when you ask for an old manifest, because no request code is obtained for it.
• Ignores your manifest — quietly downloads the current build of the depot instead of the old one you specified, which is useless for downgrading.

This is widely confirmed by the community: the console trick "no longer works and can only be used to download the current version," as one downgrade tutorial bluntly puts it. It's not your console, your syntax, or your account — it's the request-code system, the same gate explained on the request-code page and tracked on the status page.

04Migrating to DepotDownloader

Here's the good news, and why you likely ended up on this site: DepotDownloader does navigate the request-code flow, using the account you log in with, so it still downloads specific old versions where the console can't. The migration is almost mechanical — the same three IDs, rearranged into flags:

What you gain in the move: it logs in with your account (so it can request the codes the console can't), it shows real progress and resumes interrupted downloads, and -dir puts each version in its own folder instead of a shared content directory you have to clean out. Same IDs, a tool built for the job. New to it? Install it in two minutes, then follow the universal downgrade guide; the find-your-IDs page covers the SteamDB lookup the console needed too. And if the old build downloads cleanly but the game still boots the latest, that's the downgraded game launches the wrong version snag, not a download failure.

05The honest fine print

DepotDownloader isn't a magic bypass — it plays by the same rules, just properly. Two honest limits carry over:

• You still need to own the game. The console required your logged-in Steam client to own it; DepotDownloader requires the account you sign in with to own it. Neither downloads games you don't have a license for — and tools that claim to are a different, riskier thing entirely.
• Valve can still gate a specific old manifest. Since January 2025 some old manifests return "no manifest request code" even through DepotDownloader — that's the publisher/Valve restriction, not the tool failing. The request-code troubleshooting decodes when that's happening and what your options are.

So: the download_depot console method is effectively retired for downgrading, the migration is a one-line rewrite, and the result is a better-behaved download that still respects ownership and Valve's gating. If you only ever needed the current version, the Steam client was always the faster path; for a specific old build you own, DepotDownloader is now the way. Running a dedicated server and hit the same wall from the SteamCMD side? It's the same story — why SteamCMD can't pin an old version covers rolling a server back by manifest.