Terraria's old-version demand splits three ways. Nostalgia runs deepest here — this game is fifteen years old, its art and balance have been reworked repeatedly, and people genuinely want to stand in a 1.0 world where the sun, the armor and the merchant all look wrong in the right way. Mod ecosystems pin versions — entire generations of mods live on Terraria 1.3.5.3 and 1.4.3.6 and were never ported forward. And multiplayer matches versions strictly — a server stuck on an older patch, including most long-running tShock communities, only takes clients of the same version. The same mod-pinning pressure drives downgrades in its cozy-game cousin Stardew Valley, where SMAPI mods break on update just as Terraria's do. Terraria is a paid game: every route below needs an account that owns it.

01Worlds first — conversion is one-way

The only dangerous step is the one people skip Terraria upgrades saves silently: open a world or player in a newer version and the file is converted forward, permanently — there is no downgrade path for a save, and an older build pointed at a newer file will refuse it or crash. Before touching any old version, copy Documents\My Games\Terraria\ (the Worlds and Players folders are the treasure) and turn off Steam Cloud for Terraria, or cloud sync will happily shuttle converted files back onto the build that can't read them. Keep one save backup per era you play; veterans keep a folder structure like saves-1.3/, saves-1.4/.

02Modded? You may need zero manifests

If "old Terraria" actually means "old modded Terraria", stop before downloading anything by hand. tModLoader is its own free app on Steam (1281930) and ships its history as official beta branches: 1.3-legacy runs on Terraria 1.3.5.3, 1.4.3-legacy on 1.4.3.6, and the default branch tracks current. Steam's Properties → Betas dropdown switches between them — fully supported by the developers, no manifests, no tooling. And because these are plain public branches, DepotDownloader can fetch one into its own folder too, which is how you keep several eras installed side by side:

> .\DepotDownloader.exe -app 1281930 -branch 1.3-legacy -username you -dir .\tml-1.3

This is the happiest version of the whole story — the developers chose to keep the past on the shelf, so nobody has to dig for it. More games should do it; I wish I had to write fewer of these guides because of it. (Vanilla Terraria itself has no such branches; for that, read on.)

03The wrapper: TerrariaDepotDownloader

Terraria is one of the few games whose community built a dedicated GUI around DepotDownloader: TerrariaDepotDownloader (Windows, .NET, actively maintained). Its real value isn't the buttons — it's the catalog: a maintained ManifestVersions.cfg mapping version numbers from 1.0.x to current onto their manifest IDs, so "give me 1.2.4.1" is a dropdown choice instead of a SteamDB archaeology session. You feed it your own credentials (it's a wrapper, not a workaround — ownership rules apply exactly as everywhere), pick a version, and it can either download to a side folder or swap files directly into your Steam install via its "Use Steam Directory" mode. The usual wrapper caution applies: download it from the developer's GitHub or the official Terraria forums thread, nowhere else.

04The manual recipe

Doing it yourself is two IDs and a date. Windows Terraria lives in depot 105601; match your target version's release date against the manifest list on SteamDB (the Terraria wiki's version history gives you the dates):

> .\DepotDownloader.exe -app 105600 -depot 105601 -manifest <manifest-id> \
    -username you -remember-password -dir .\terraria-old

Terraria is a small game by modern standards — old builds are a few hundred megabytes, so collecting several eras costs nothing. macOS and Linux have their own depots under app 105600 on SteamDB; the workflow is identical.

05Installing and launching

Here's Terraria's quirk, and it's the opposite of PAYDAY 2's: the game carries its own ownership checks, and the experience of the wrapper's author is that old builds behave most reliably when they sit inside the Steam install directory rather than launched from a random folder — it's exactly why the wrapper grew its "Use Steam Directory" mode. So the dependable sequence:

Back up (or rename) your current steamapps\common\Terraria folder.
Copy the downloaded old build over it.
Steam → Properties → Updates → "Only update this game when I launch it", and launch through Steam as normal. For extra insurance against a surprise forced update, the read-only-appmanifest_105600.acf trick from the Skyrim guide works here identically.
Restoring the present is the same dance in reverse — or just undo the read-only flag and let Steam update. Your converted-forward saves were waiting in the backup you made in section 01, right?

For multiplayer, the strict version match cuts both ways: it's a hassle for joining strangers but trivial for friends — everyone runs the same downloaded build and the same era, and a matching TerrariaServer.exe ships inside every old build you download.

06Status in 2026

Terraria's manifest history sits under the same post-January-2025 weather as everyone else's: requests for old manifests may be granted or refused, and the answer shifts by account and over time — the request-code page decodes the refusal if you meet it. Two things soften it here. The tModLoader legacy branches are active branches, not historical manifests — they'll keep working regardless. And the wrapper's community keeps its version catalog current, which tells you what's worth grabbing while grabbing works. The conclusion writes itself by now, but Terraria's tiny installs make it painless, and if it were my shelf I'd just do it: a complete personal archive of every era you care about fits in a few gigabytes. Make it now, not the week after a manifest stops answering.