Download
depot / guides / software-downgrade

Downgrading software on Steam

Steam isn't only games. Wallpaper Engine, Aseprite, RPG Maker, 3D modellers, utilities — a whole shelf of software sells through it, and software updates break workflows just like game patches break mods. The downgrade is mechanically the same as for a game; what's different is what you have to watch out for once you're back: your project files, your plugins, and the app's own update habits. I've rolled back a few of these myself when an update broke something I depended on, and the mechanics never surprised me — it was always the project files that needed the care.

~7 min read| updated june 2026| use case

01Why roll a tool back

The reasons are a creative or working person's, not a gamer's, but the shape is familiar:

  • An update broke your workflow. A new release changed a tool, removed a panel, altered a shortcut you have in muscle memory, or regressed performance on your machine.
  • A plugin or extension stopped working. Like a game's mods, an app's add-ons are often pinned to a version, and a major update can strand the ones you depend on until their authors catch up.
  • Project / file compatibility. You're collaborating with people on an older version, or a studio standardized on a specific release, and everyone needs to match.
  • A feature you relied on is gone. Software removes things too — a workflow built around it needs the version that still has it.

One genuine relief compared to games: software has no anti-cheat and no multiplayer-version-matching, so there's none of the VAC anxiety the game guides carry. This is purely about getting the version that works for you.

02It's the same downgrade

To Steam, an app is just an app — software has App IDs, depots and manifests exactly like games, so the workflow is the one on the universal downgrade guide:

  1. Find the app and the version you want on SteamDB — the App ID, the content depot, and the manifest dated to the release you're after (the find-your-IDs guide covers it).
  2. Download it with the account that owns the software:
> .\DepotDownloader.exe -app <appid> -depot <depotid> -manifest <manifestid> \ -username you -remember-password -dir .\app-old

Then install and pin it via after the download — and crucially, set the app to "only update on launch" so Steam doesn't drag you straight back to the version you just escaped. (Wallpaper Engine users: this page is about rolling Wallpaper Engine itself back; if you actually want to download workshop wallpapers with the tool, that's the workshop guide.)

03The project-file trap

Back up your work first Software's version of the save-compatibility problem is your documents and projects. Creative tools often upgrade a project file's format silently when you open it in a newer version — and an older version may then refuse to open it, or open it wrong. So before you switch versions, back up the projects you care about, and be cautious opening recent files in an older build. If you're downgrading specifically to collaborate on an older version, make sure your files are saved in (or exported to) a format that version understands, not just that the app matches. This is the one place a software downgrade can cost you real work, exactly as a game downgrade can cost a save.

04Plugins and the rest

If the tool has an add-on ecosystem (scripts, brushes, templates, extensions), match those to the version the same way you'd match mods to a game build: an extension compiled or written for the new API may not load on the old app, and vice versa. Keep the version's add-ons together with it. And if the app stores settings or a workspace layout in a user folder, note that an old build pointed at a newer config can behave oddly — keeping a backup of the config, or letting the old version regenerate its own, avoids a confusing afternoon. The discipline is the modded-game one in a creative-tool hat: app version, matched add-ons, compatible project files — one era. The one time I lost an afternoon to this, it was an old build reading a newer config folder, so now I always let the old version regenerate its own.

05Where software differs from games

A few honest software-specific notes:

  • You must own it. Same ownership wall as everywhere — the account you log in with needs to own the software, or the depot keys won't come (depot-key-denied).
  • Some apps self-update or phone home. A few programs have their own update mechanism independent of Steam, or check a license server on launch — for those, getting the old files via Steam's depots may not fully pin the version, and an online license check can override your local copy. Steam-native apps that update purely through Steam are the clean case.
  • Subscriptions and online services. If a tool's features depend on a subscription or a cloud backend, the old binary can't bring back a service that's been changed server-side — the same way an always-online game can't.

For the large majority — the creative tools and utilities that update through Steam like any app — a software downgrade is exactly a game downgrade: find the version, pull the depot, pin it, mind your project files. The shelf Steam built for old game versions is the same shelf for old software versions, and DepotDownloader reads both the same way. If it were my install, I'd back up the projects, pull the version, pin it to update-on-launch, and not think about it again until I actually wanted to move.

the mechanics, in fullHow to downgrade any Steam game →