Steam Workshop mods and file based mods are not the same thing

A game with a Steam Workshop and a game with a mods folder look similar from the outside and behave differently in almost every way that matters.

The Workshop version

You press subscribe on a web page or in an in game browser. Steam downloads the item into a folder it manages and the game reads it from there. You never handle a file, there is no version to choose, and updates arrive whether you wanted them or not.

That last part is the important one. Workshop items update silently, and the item you tested on Tuesday can be a different item by Friday, with no way to ask for the old one. When a Workshop heavy setup breaks for no reason you can see, this is usually why.

It also means there is no download link. There is nothing to point at, because the transfer happens inside Steam between your client and Valve. This site links to the item's page for exactly that reason, rather than showing a button that could not work.

The file version

You download a file. You put it somewhere. It stays exactly as it is until you change it.

More work, and in exchange you get the two things the Workshop cannot give you: a specific version, and a copy that nobody can update out from under you. If a build works, you keep it, and you can hand the same file to a friend and know they are running what you are.

Why a game often has both

The Workshop is very good at content the game already knows how to load. Maps, skins, vehicles, scenarios: things the game reads as data.

It is much weaker at code, because code needs a loader, and a loader needs to run before the game does, which is not something a subscription system can arrange. So plenty of games end up with maps and cosmetics on the Workshop and every code mod on a separate site, which is why searching one place finds half the ecosystem.

Both halves are indexed here, side by side, with where each one actually lives.

The practical differences

Sharing a setup with friends is easy on the Workshop and manual with files. Reproducing a setup later is the reverse: files are exact, Workshop items are whatever they are today.

Multiplayer usually cares. Many games check that everyone has the same Workshop items, which is convenient, and many others check file hashes, which is unforgiving.

And when you want to stop, unsubscribing deletes the files. If your save built something out of a Workshop item, that thing is gone on the next load, and the game's reaction to that is its own business.