01The jobs I actually use it for
Stripped of marketing, here's the honest shortlist of what I reach for DepotDownloader to do, with the command shape for each. Every one of these is something the Steam client either can't do or makes painful:
| The job | The command shape | Why not just the client |
|---|---|---|
| Pin an old build I own | -app 218620 -depot 218621 -manifest <id> -username you | The client only ever installs the latest; this fetches one exact past version by manifest. |
| Clean server, no account | -app 258550 | Anonymous, no Steam client, fully scriptable on a headless box. |
| One file from a 60 GB depot | -app 730 -depot 731 -filelist want.txt | The client is all-or-nothing; this pulls just the config or asset you need. |
| A build for another OS | -app 380870 -os linux | Download the Linux server depot from a Windows machine, or vice versa. |
| A Workshop item headless | -app 730 -pubfile <id> | By ID, with no client running anywhere — what a build server actually needs. |
If you only ever do the first one, that's normal — rolling a game back to a specific patch is the reason most people find this tool, and it has its own step-by-step guide.
02What I don't use it for
Being honest about the limits is the fastest way to save you a wasted evening — these are the things people hope it does and it doesn't:
- Games I don't own. Depot keys are license-checked; it downloads what your account is entitled to and nothing more. That's deliberate, not a missing feature — the honest answer is here.
- Getting the current version fast. For today's build, the Steam client's multi-CDN install is genuinely faster and smarter about it. I only reach for DepotDownloader when I need a version the client won't give me.
- Keeping a refunded or revoked game. Once the license is gone, so is access — there's no offline copy trick here.
- Any kind of "bypass". It plays strictly by Steam's rules. Tools that claim to unlock what you don't own are a different, riskier thing entirely, covered honestly on the forks page.
Every flag above is documented in full, verified against the source, in the CLI reference.