7 DAYS TO DIE · BACKUP AND TRANSFER · NOVEMBER 2026

How to Back Up and Move a 7 Days to Die Server Save

A 7 Days to Die world is two folders: the map and the save built on it. Where both live, why GameWorld and GameName decide whether a restore works, how to take a backup you can trust, and how to move a world to a new server without losing anyone’s progress.

Why one world is really two folders

7 Days to Die splits a world in two. The map, its terrain, towns and roads, is one thing. Everything players have done to it, every base, dug tunnel, looted building and character, is another. On a random world (RWG) the map lives in GeneratedWorlds and the changes live in Saves. A save without its map is useless, and that is the mistake behind most backups that will not restore.

The parts of a 7 Days to Die server world
All inside the user data folder unless noted
Saves/<world>/<GameName>/
Region/*.7rg, Player/, main.ttw, players.xml: everything players changed
Chosen by GameName
GeneratedWorlds/<world>/
The terrain, towns and roads of a random (RWG) map
Chosen by GameWorld
Saves/serveradmin.xml
Admins, bans and whitelist for the whole server
Shared by every save
In the server install folder
  • serverconfig.xml (or your renamed copy): GameWorld, GameName, seed, size, SandboxCode
  • Mods/: needed if the world was played with mods
Navezgane and the Pregen maps ship with the server, so for those worlds the save folder is enough.
The save records changes; the map supplies what they were made on. Back them up as a pair.

Two settings in serverconfig.xml tie the two halves together. GameWorld chooses the map: Navezgane, one of the shipped Pregen maps, or RWG to generate one from WorldGenSeed and WorldGenSize. GameName chooses the save inside that map, so one map can hold several saves side by side. The server only loads a save when both names match what is on disk. Change either, and it does not complain; it simply starts a new game.

Navezgane and the pregen maps ship with the server, so for those you only need the save. For a random world, keep the GeneratedWorlds folder too. Generating again from the same seed is not a safe substitute, because world generation changes between major versions, and a map rebuilt on a newer build may not match the save made on the old one.

Where the files are

WhatWhereWhy you want it
User data folder~/.local/share/7DaysToDie/ on Linux, %APPDATA%\7DaysToDie\ on Windows, or the path in UserDataFolderHolds everything below
The saveSaves/<world>/<GameName>/Bases, land claims, players, day count
The random mapGeneratedWorlds/<world>/The terrain your save was built on
Admins, bans, whitelistSaves/serveradmin.xmlYour moderators and ban list
Server settingsserverconfig.xml, or your renamed copy, in the server install folderWorld choice, SandboxCode, slots, ports
ModsMods/ in the server install folderNeeded if the world was played with mods

Inside the save folder you will see a Region folder of .7rg files, which hold the changed parts of the map, a Player folder with a set of files for each player, and state files such as main.ttw and players.xml. Copy the folder whole; picking out files is how backups end up half restored.

Older guides mention a SaveGameFolder setting. It was removed in V1.0, and saves now always follow UserDataFolder. If you set UserDataFolder later on, move the existing Saves and GeneratedWorlds folders to the new location at the same time, or the server will look in an empty folder and start a fresh world.

Back up a 7 Days to Die server

  1. Save first. Run saveworld in the server console, or use your panel’s save button, so everything held in memory is written to disk.
  2. Stop the server with shutdown or the panel’s stop button, and wait until it has fully exited.
  3. Copy the save folder, Saves/<world>/<GameName>/, and for a random world the matching GeneratedWorlds/<world>/. Copying the whole Saves and GeneratedWorlds folders is simpler and also picks up serveradmin.xml.
  4. Copy your serverconfig.xml so you know exactly which world, game name and Sandbox code the save belongs to.
  5. Label it with the date, game version and reason, such as 2026-11-20 V3 before mod update, and keep it away from the server.
  6. Start the server again.

Why stop instead of copying while it runs? The server keeps the world in memory and writes region and player files as it goes. A copy taken mid-write can mix old and new files, and nothing warns you until the restored world has a base with half its walls missing. A save followed by a clean stop is the only copy you can fully trust. Panel snapshots taken on a schedule are a good extra layer, as long as you know what they include and keep a downloaded copy now and then.

Take a backup before every update, every mod change and every wipe. Major versions are where saves most often misbehave: V3.0 moved many gameplay rules into a single SandboxCode, and our 7 Days to Die V3 server settings guide explains what that means for an existing world.

What to copy for each job

Which files each job needs
JobSaveMapAdminsConfigMods
Routine backupYesYesYesPartlyNo
Before a game updateYesYesYesYesYes
Moving to a new hostYesYesYesYesYes
Restoring one playerPartlyNoNoNoNo
Save = Saves/<world>/<GameName>/. Map = GeneratedWorlds/<world>/. Admins = serveradmin.xml. Config = serverconfig.xml. Mods = the Mods/ folder.
Yes = copy it. Partly = only part of it: one player’s files from Player/, or just the world, game name and Sandbox code values from the config.
GeneratedWorlds only matters for random (RWG) maps. Mods only if the world uses them.
The save folder and its map are in every full backup; the rest depends on the job.

The pattern is simple: the save and its map always travel together, and everything else depends on whether you are rebuilding the whole server or fixing one thing on it.

Restore a backup

  1. Stop the server.
  2. Rename the current save folder, for example MyGame to MyGame_broken, rather than deleting it.
  3. Copy your backed-up save folder into Saves/<world>/ and, for a random world, put the map folder back in GeneratedWorlds/ if it is missing.
  4. Check serverconfig.xml: GameWorld and GameName must point at the folders you just restored. For a random world, keep the same WorldGenSeed and WorldGenSize, so the server finds the existing map instead of generating a new one.
  5. Start the server and watch the log, then join and check a base you know well.

To restore a single player, for example after a lost character or a griefed inventory, stop the server and copy that player’s files from the backup’s Player folder over the current ones. Take every file belonging to that player, not just one. The rest of the world stays as it is.

Restored, but the server started a fresh world?
The server starts on day 1 after a restore or move
Does GameName in serverconfig.xml match the save folder’s name exactly?
No
Fix the nameSet GameName to the folder name, or rename the folder. Restart.
Yes
On a random map, is its folder back in GeneratedWorlds? (Navezgane and Pregen maps: yes)
Missing
Restore the mapCopy GeneratedWorlds/<world> from the backup and keep the same seed and size.
Yes
Does the save sit at Saves/<world>/<GameName>/, not one folder deeper?
No
Fix the layoutMove the folder up a level. Unzipping often adds an extra one.
Yes
Did UserDataFolder change, or is this a different install?
Yes
Wrong data folderPut Saves and GeneratedWorlds in the folder the server now uses.
No
Check the log for the paths it loaded, and that both servers run the same game version.
Your restored save is almost never lost; the server is just looking somewhere else.

Move a world to a new server or host

Moving a server is a backup on the old machine and a restore on the new one. Windows and Linux use the same save files, so a world can move between them as long as both run the same game version.

  1. On the old server, run saveworld, stop it, and download Saves, GeneratedWorlds and your serverconfig.xml. Include Mods if the world uses them.
  2. Install the same game version on the new server. Moving a save onto an older build is asking for trouble; moving to a newer one is a game update, so read the release notes first.
  3. Start the new server once if it needs to create its folders, then stop it.
  4. Upload the folders to the same places in the new server’s user data folder. On a rented server that is the folder the file manager shows holding Saves.
  5. Copy your GameWorld, GameName, WorldGenSeed, WorldGenSize and SandboxCode values into the new server’s config, start it and check the world.

A world you played in single player or hosted from the game works the same way: on Windows, copy the save from %APPDATA%\7DaysToDie\Saves\ and the map from %APPDATA%\7DaysToDie\GeneratedWorlds\, then set the server’s world and game name to match. Our guide to moving to a new host covers the rest of the switch.

Chunk resets and save size limits

Two settings can change a world without anyone touching it, and they are worth knowing before you blame a bad restore. MaxChunkAge resets areas nobody has visited for that many in-game days back to their original state, unless a land claim or bedroll protects them. SaveDataLimit caps a save’s size in megabytes, and when the limit is reached the server can reset saved chunks to free space. Both are off by default (-1). If you turn either on, a backup is the only way to get a reset area back.

Map size affects backups too. A WorldGenSize of 10240 covers almost three times the area of the default 6144, which means more terrain in GeneratedWorlds and more region files as players explore. Big worlds take longer to copy, so schedule backups for a quiet hour.

Want backups handled for you?

Many 7 Days to Die hosts run scheduled backups, give you SFTP access and let you restore from the panel. Compare UK hosts, and what each one includes, in our roundup.

Compare the best 7 Days to Die server hosts

7 Days to Die server backup FAQ

Where is the 7 Days to Die server save folder?

In Saves/<world>/<GameName>/ inside the user data folder, which is ~/.local/share/7DaysToDie/ on Linux and %APPDATA%\7DaysToDie\ on Windows unless UserDataFolder in serverconfig.xml points somewhere else.

Can I back up a 7 Days to Die server while it is running?

Only as a casual extra. Run saveworld first, but a copy of a running server can still catch files mid-write. For a backup you rely on, save, stop the server, then copy.

Do I need the GeneratedWorlds folder as well as the save?

For a random world, yes. The save only records what players changed; the map it was built on lives in GeneratedWorlds. Navezgane and the pregen maps ship with the game, so for those the save is enough.

Why does my server start a new world after a restore?

Because GameWorld or GameName no longer matches the folders on disk, the map folder is missing, or the save landed one folder too deep. Fix the names or the folder layout and restart; the restored save is still there.

Can I move a single-player world to a dedicated server?

Yes. Copy the save and, for a random world, the map from your own %APPDATA%\7DaysToDie folders to the server, run the same game version, and set GameWorld and GameName to match.

More 7 Days to Die server help

Compare hosts and get your settings and mods right.

7 Days to Die updates and host panels change. Where your server or your host’s panel works differently from what is described here, follow what you see on your server.

Similar Posts