How to Back Up and Transfer a Terraria World

What a Terraria world actually is

Think of a Terraria world as a file set, not as a server state. The core save is a .wld file. Vanilla also keeps a neighbouring .bak file, which is simply the previous save. A tModLoader world adds a .twld file for modded world data, so a modded world is not complete unless the .wld and .twld travel together.

Just as important is what is not inside the world. Player characters are local .plr files on each player’s machine, not part of a normal server world. TShock accounts, groups, regions and server-side characters are stored in TShock’s own data, and your enabled mod list is separate again. If you only move the world file, the map moves; those other systems do not.

A final detail that catches people out: Journey is a world and character rule, not a transfer bug. Journey characters can only enter Journey worlds, and Journey worlds can only be entered by Journey characters.

Where to find your world

The location depends on how the world was created and where the server runs. Hosted panels usually expose a Worlds folder inside the server files, but the exact panel layout varies, which is why it helps to understand game server control panels in general rather than relying on one screenshot.

Cloud worlds are the common “I cannot find my save” case. If a world has its Cloud toggle enabled, it is not in the normal Documents folder, so the file manager on your PC will look empty. Switch the Cloud toggle off for that world first, then Terraria will give you a normal local world file that you can upload. If new worlds keep behaving like cloud saves, the CloudSavingDefault setting exists; its default is false.

On Linux, capitals matter. MyWorld.wld and myworld.wld are different names, so a path that looks close enough on Windows can still fail on a VPS.

The golden rule: save first, stop before you upload

This is the part that explains most “my world reset” stories. The Terraria server does not constantly read and write the world file with every block change. It keeps the active world in memory and writes that state to disk on save. Auto-save happens from time to time, including at dawn in game, the server saves when the last player leaves since 1.4.5.0, and it saves on shutdown only if you use exit.

That means two things. First, a file copied from a running server is only the last saved version on disk, not necessarily the live state in memory. Second, if you upload a replacement world while the server is still running, the next save or clean exit can write the old in-memory world back to disk and wipe out your upload. Doing it properly costs you a minute of downtime. In return, the file on disk and the world your players were standing in are finally the same thing.

save
exit

Use exit-nosave only if you intentionally want to stop without writing current changes. Do not close the console window with the X button, kill the process, or assume hibernation counts as stopped. When no players are online the server hibernates and time does not pass, but the process still exists and still owns that world session.

You can tell a clean save-and-stop worked by checking that the world file’s modified time advances before you copy it, and by confirming the server process is fully down before you upload anything back.

How to back up a Terraria server world

A sensible backup plan stacks quick local rollbacks with copies stored somewhere else. That way you cover simple mistakes, corruption and a machine or host problem separately. For a broader view of game server backups in general, the same principle applies here: short-term convenience and long-term safety are not the same job.

Manual off-server copy

1. Run save in the console. This forces the in-memory world to disk so your copy contains the latest state rather than the last scheduled save.
2. Shut the server down with exit. That clean stop prevents the process from writing older in-memory data back over the files while you copy.
3. Copy the world files out of the Worlds folder to another machine or storage location: .wld, .bak, and .twld if it is a tModLoader world. This costs bandwidth and storage space, but it protects you if the server disk or host itself is the problem.
4. If the server uses TShock or mods, copy the matching TShock data and mod list separately. The world file alone cannot restore regions, accounts, SSC or the enabled mod set.

Built-in Terraria backups

Every save keeps the previous version as the neighbouring .bak file, which is the fastest recovery if the latest save is bad. Terraria also supports rolling world backups through WorldRollbacksToKeep in config.json or serverconfig.txt. The default is 2. At 2 or higher, rolling backups are enabled; by default that means one additional backup on top of the previous save, and the maximum is 9. The trade-off is simple: more rollback points cost more disk space.

TShock backups

TShock adds its own timed backups, written to the tshock/backups folder. Our TShock setup guide covers the rest of the config; what matters here is how long those backups stick around. These are the defaults in the Settings block of tshock/config.json:

"BackupInterval": 10,
"BackupKeepFor": 240,
"AutoSave": true,
"SaveWorldOnCrash": true,
"SaveWorldOnLastPlayerExit": true,

With those defaults, TShock backups only reach back about 4 hours: a backup every 10 minutes, each one deleted after 240 minutes. That is brilliant for undoing griefing you spotted the same evening and useless for damage nobody noticed until the weekend. If you want TShock to cover longer gaps, raise BackupKeepFor (2880 is two days) and keep an eye on disk space.

A routine that covers most failures

• Take a manual off-server copy before game updates.
• Take one before big irreversible world-state moments such as moving into Hardmode.
• Take one before adding or changing mods.
• Keep a regular off-server copy on top of the built-in and TShock layers.

The easy way to judge whether your routine is good enough is to ask two questions: “How far back can I roll?” and “Can I still restore if this machine disappears?” If either answer is weak, add another layer.

Move a single-player or Host & Play world onto a server

Once you know where the files live, uploading a personal world is straightforward. If you are still working through the basics of setting up a Terraria dedicated server, sort the base server first, then move the world across.

Self-hosted dedicated server

1. If the world is a Steam Cloud world, switch its Cloud toggle off first so you get a normal local world file to copy.
2. Stop the dedicated server cleanly with save then exit. This matters even on a brand-new server, because a running instance can still generate or save its own world files.
3. Copy the world into the server’s world folder. For vanilla, bring .wld and preferably .bak; for tModLoader, bring .wld, .bak and .twld.
4. Point the server at that world in serverconfig.txt. The server loads the file named there; if the name or path is wrong and autocreate is set, it can generate a fresh world instead.
5. Start the server and check that the expected world name and builds are present before inviting players back in.

worldpath=/path/to/Worlds
world=/path/to/Worlds/MyWorld.wld

The autocreate trap is the big one. autocreate=1|2|3 tells the server to make a new small, medium or large world if the named file is not found. So a typo, wrong folder or wrong capital letter can look like a mysterious reset when it is really the server doing exactly what that setting asked. If you launch through TShock, remember that -world expects an absolute path.

Hosted panel

1. Stop the server in the panel first. Do not upload into a running world slot.
2. Upload the world files into the server’s Worlds folder.
3. Set the panel’s world name or save name field to the exact file name expected there.
4. Start the server and check that it loads the right map, not a newly generated one.

The reason panels need both the file upload and the world-name setting is that storage and startup are separate pieces. Uploading only places the file on disk; the startup setting tells the server which file to mount on launch.

Download a server world to play it locally, or move it to a new host

Pull a server world back to your PC

1. On the server, run save and then stop with exit. Otherwise your download may only contain the last disk save rather than the latest live state.
2. Download the world files: always the .wld, ideally the .bak, and the .twld as well if the server is modded.
3. Place the files into your local Worlds folder. If it is a tModLoader world, use the tModLoader Worlds folder instead of the vanilla one.
4. Launch the matching game client. The world appears in single player because Terraria simply scans the Worlds folder for valid world files.

If you are keeping the download as a safety copy rather than as an active local world, keep an extra copy outside the live Worlds folder too. That avoids accidental overwrites during later testing.

What to bring when moving to a new host or machine

Version matching matters as much as file copying. Do not start the new server until its game version matches the save’s version. For tModLoader, keep the same enabled mods and the same tModLoader version as well. If a newer server updates the world, older clients, including mobile players on a different version, can be locked out.

tModLoader and mobile specifics

tModLoader worlds

A modded world is a pair, not a single file. The .wld contains the base world, while the .twld holds extra modded data. If you copy only the .wld, the server can still start, but modded content may vanish, fail to load, or behave as if the world lost part of its state.

Bring the same tModLoader version and the same enabled mods. The active mod list is stored in enabled.json, and if you are changing or adding content, this is a good point to review the practical side of installing mods on a Terraria server. The world file is not a mod pack; it expects the same environment that created it.

tModLoader also uses separate folders from vanilla. On first launch it offers to copy vanilla players and worlds, and those vanilla saves are not modified. If that automatic copy does not work, manually copy the Worlds and Players folders from the vanilla Terraria Documents path into the tModLoader folder.

Mobile and Android

On Android, the Worlds folder is Android/data/com.and.games505.TerrariaPaid/Worlds, and the usual way to reach it is by connecting the phone to a PC with USB. The same rule applies as on desktop: copy only after a clean save, and keep versions matched between device, server and world.

If mobile players suddenly cannot join after a transfer, the cause is often version drift rather than a broken save. A world touched by a newer server may no longer suit an older client. Keep game, server and world on the same version before you let players back in.

Restore a world after corruption, griefing or a reset

Restore from the built-in .bak

1. Stop the server cleanly.
2. Move the broken .wld aside instead of deleting it.
3. Copy MyWorld.wld.bak and rename that copy to MyWorld.wld.
4. For tModLoader, restore the matching modded backup as well so the .wld and .twld stay in step.
5. Start the server and check the expected rollback point.

Moving the bad file aside is safer than deleting it because you keep one more recovery option. If the .bak turns out to be too old, or the fault was somewhere else, you can still inspect or recover from the original file later.

Restore from rolling backups, TShock backups or an off-server copy

If the simple .bak is not far enough back, use the newest known-good rolling backup, then TShock backup, then your off-server archive. Newer restores give you less lost progress but a higher chance of carrying the same damage forward; older restores lose more recent changes but are often safer if corruption or griefing went unnoticed for a while.

Since 1.0.4, Terraria can prompt you to load a world backup if the current world is corrupt. Treat that as a useful hint, not as your only plan. Before accepting any restore path, keep copies of the current broken files so you do not close off another recovery route.

If the world only seems to have reset, check the startup setting before restoring anything. A wrong file name or path can make the server load or generate a different world, which looks like data loss even though your original save is still sitting on disk.

Troubleshooting a world that is gone, wrong or older than expected

Work through this as a file problem first: wrong file set, wrong path, wrong version, or wrong timing. That approach is quicker than treating every bad load as corruption.

Self-hosted or rented: who handles backups?

The answer is usually “you, at least partly”. A host can make stop/start and file access easier, but your world still matters most when you have your own clean copy off the server. If you are comparing options, start with our Terraria server hosting comparison and judge them by file access, clean stop controls, version management and how easy it is to pull your own backups.

Terraria world backup FAQ

Where are Terraria server worlds saved?

On Windows they are in %USERPROFILE%\Documents\My Games\Terraria\Worlds, on Linux in ~/.local/share/Terraria/Worlds, and on macOS in ~/Library/Application Support/Terraria/Worlds. Hosted servers usually expose a server-side Worlds folder through their panel. If the world uses Steam Cloud, it will not appear in the normal Documents folder until you switch cloud saving off for that world.

How do I upload my single-player Terraria world to a server?

First make sure you have a normal local world file, not a cloud-only one. Then stop the server, upload the .wld file and any matching .bak or .twld files into the server’s Worlds folder, set the server’s world name or path to that file, and start it. The stop-first step matters because a running server can overwrite your upload on its next save.

Why did my Terraria server create a new world instead of loading mine?

The usual cause is a wrong file name, wrong path, or a capitals mismatch on Linux. If autocreate is enabled, the server makes a fresh world when it cannot find the file it was told to load. Check the startup setting first before assuming the original world is gone.

How do I restore a Terraria world from a .bak file?

Stop the server, move the broken .wld file aside, then copy the .wld.bak file and rename that copy back to .wld. For tModLoader, restore the matching modded backup as well so the world data stays aligned. Start the server only after the restored files are in place.

Do I need to move my character when I move a Terraria world?

Not for a normal server world transfer. Characters are separate local .plr files on each player’s machine, so moving the world does not move anyone’s character. The exception is TShock server-side characters, which live in TShock’s database and need the TShock data moved with the server.

More Terraria server help

The host comparison and the Terraria guides that sit alongside this one.