How to Back Up and Restore a Conan Exiles Server Save
Protect your Conan Exiles world before updates, mod changes and wipes, restore a broken save cleanly, and move a single-player world onto your server, without the game_0.db, journal-file and stray game.db traps that undo a restore.
Bases, thralls, clans, inventories and characters live in a single SQLite file. On Enhanced that live file is game_0.db, not the older game.db.
While the server is live, recent writes sit in SQLite journal files beside the main database. Copying only the main file during that window can give you an incomplete restore point.
Your database does not contain server rules, passwords, region settings or mod load order. Back up the config folder and modlist.txt with every world copy.
Rolling copies are useful for a quick undo, but they live on the same disk as the live save. They do not protect you from a wiped machine, reinstall or host-side loss.
What a Conan Exiles backup actually is
A proper Conan Exiles server backup is not just one file copied at random. The world itself is one SQLite database, but the server also relies on separate config files and, if you use mods, a separate mod list that defines load order. If you restore only the world database, players may get the map back but lose the settings, passwords or mod state that made that world usable.
Use this file map as the baseline for what to copy and what to restore in each situation. Every path starts in the ConanSandbox folder of the server install.
| Path | What it holds | Back up? | Restore when |
|---|---|---|---|
Saved/game_0.db | The live Enhanced world: characters, clans, bases, thralls, chests and placed items. | Yes | Always for Enhanced restores and migrations. |
Saved/game_0.db-walSaved/game_0.db-shm | SQLite journal files used while the server is running. | No | Set aside or delete on restore so old journal data is not applied to the restored world. |
Saved/game_0_backup_N.db | The game’s rolling copies of the Enhanced world. 1 is newest. | Optional extra | When you need a quick rollback from a recent bad change. |
Saved/game.db | Legacy live world, or an old world left behind after migration. | Yes if you still run Legacy or want a Legacy fallback copy | For Legacy restores, or to avoid the first-start copy trap on Enhanced. |
Saved/dlc_siptah.db | Legacy Isle of Siptah world. | Yes for Legacy Siptah only | Only on Legacy Siptah restores. |
Saved/Config/WindowsServerSaved/Config/LinuxServer | ServerSettings.ini, Engine.ini, Game.ini: passwords, rules, region settings and other server behaviour. | Yes | Restore alongside the world if settings changed or reverted. |
Mods/modlist.txt | Mod IDs and load order. | Yes if modded | Restore whenever the world depends on mods, especially after a rollback. |
| File or folder | Back up | Put back on restore | Move aside on restore or wipe |
|---|---|---|---|
Saved/game_0.db | Yes | Yes | Yes |
Saved/game_0.db-wal and -shm | No | No | Yes |
Saved/game_0_backup_N.db | Partly | Partly | No |
Saved/game.db (old or Legacy) | Partly | No | Yes |
Saved/Config/ | Yes | Partly | No |
Mods/modlist.txt | Yes | Partly | No |
On Enhanced, update any old backup scripts or habits that still target game.db. That rename is the reason some admins think they have backups, then restore the wrong file and end up with an empty or older world.
Why you must stop the server first
Conan Exiles stores the world in SQLite. While the server is running, new writes do not always go straight into the main database file. They first land in game_0.db-wal, with game_0.db-shm helping SQLite coordinate access. Later, those changes are folded back into game_0.db.
That matters because a file copy taken mid-run can be logically older than the live world even if the timestamp looks current. The missing pieces tend to be the newest transactions: the last building placements, inventory moves, character progress or thrall changes. This is not a bandwidth problem; it is a consistency problem inside the storage layer.
Stopping the server forces a clean close of the database so recent writes are merged back into the main file. The cost is a short interruption for players, but the benefit is a backup that matches a real point in time. If you are editing config at the same time, stop for that too: changes made to the INI files while the server runs often do not stick.
How to back up safely
Whichever route you use, the rule is the same: stop the server, copy the right files, and store at least one copy away from the machine or panel that runs the server. If the only copy sits on the same disk, you have convenience, not resilience. For the bigger picture, see how game server backups work.
Host panel backup
- Schedule a quiet moment and stop the server.
- Use the panel’s backup or archive function to create a copy of the server files.
- Confirm the backup includes the world, config and mods area, not just one folder.
- Download a copy off the panel if that option exists, or ask support if your provider keeps separate offsite copies.
- Label the backup by date, branch or build, map and mod set.
This route is easiest for rented servers, especially if you do not have direct file access. The trade-off is control. On some panels, including GPORTAL’s (the host that also runs the console servers), backups are never taken automatically, and the server stops and restarts while one is made. Some hosts keep separate offsite copies for months that support can restore on request, others keep everything on the same storage, so ask before you rely on it.
Manual copy via file manager or SFTP
- Stop the server from the panel.
- Open
ConanSandbox/Saved/and copygame_0.dbfor Enhanced, or the Legacy file that matches your branch. - Copy the matching config folder under
Saved/Config. - Copy
ConanSandbox/Mods/modlist.txtif the world uses mods. - Save those items together in one labelled backup folder on your PC or another storage location.
This gives you clean file-level control and makes selective restore simpler. The cost is your own time and attention: if you forget modlist.txt or restore the wrong config folder, the world may load but objects tied to mods or server rules can break. If you need a refresher on mod order and dependencies, see installing mods on a Conan Exiles server.
Self-hosted Windows or Linux
- Stop the server cleanly.
- Copy the same world, config and mod files from the server folder to a separate backup location.
- Keep one copy off the machine, not just on another folder of the same drive.
- On Linux, check file names stay lower case exactly as expected.
- Restart the server and confirm it loads normally.
Self-hosting gives you the most freedom, but also the most room for silent mistakes. The main resources involved here are disk and operator discipline, not server CPU or RAM. If you are building or rebuilding a machine for this, setting up a Conan Exiles dedicated server covers the layout around the save folders.
Take a fresh backup before every game update or branch change, before adding or removing mods, before any wipe or region change, and before uploading a different world onto the server. That same habit matters when updating a Conan Exiles server and fixing version mismatch, because save and build mismatches are easier to unwind when you have a known-good copy from just before the change.
The game’s own rolling copies: useful, but not enough
Conan Exiles keeps its own rolling world copies in the same Saved folder. On Enhanced they are named game_0_backup_1.db, game_0_backup_2.db and so on. Number 1 is the newest, and higher numbers go further back.
These are created when the server starts and periodically while it runs. By default that has long been about every five minutes. Each one is a full database copy, not a tiny delta, so the resource cost is plain disk space and more file churn. On a large world, that can add up quickly, and a full disk is one of the easiest ways to turn “backup safety” into “save failure”.
Made at start and about every five minutes
Manual on some panels
Taken with the server stopped
- ConanSandbox/Saved/game_0.db
- The ConanSandbox/Saved/Config folder
- ConanSandbox/Mods/modlist.txt
- The date and game build in the folder name
The reason they are not a real backup is simple: they live on the same disk as the live save. If the machine is lost, the server is wiped, a reinstall goes wrong or a host-side problem takes the whole storage with it, those rolling copies disappear too. Use them as a quick undo layer, not as the only plan.
You can tell they are helping if a very recent mistake is reversible without touching your off-machine archive. You can tell they are becoming a problem if disk usage keeps climbing or saves begin to fail.
Choose a backup route that matches the risk
If your group has a casual disposable world, the game’s rolling copies plus an occasional manual export may be enough. If you are protecting months of building, named thralls and a settled mod stack, you want a routine that survives bad updates, host wipes and human error.
| Your situation | Best backup route | Why this is the safer choice |
|---|---|---|
| Small private server, no mods, few changes | Manual stopped copy of world and config, kept off the server | Low admin overhead, but still protects against the panel or machine failing. |
| Modded world with frequent building and admin changes | Panel backup plus separate file-level copies of game_0.db, config and modlist.txt | Lets you restore both the world state and the exact mod order that world expects. |
| Before updates, branch switches or map changes | A labelled backup taken immediately before the change | Gives you a clear rollback point tied to one build and one ruleset. |
| Moving to another machine or provider | File-level backup stored locally before transfer | Reduces the risk of discovering a broken upload after the original has already been overwritten. Pair it with moving your server to a new host if you are changing provider. |
The right panel tools and file access save a lot of grief when a world needs restoring quickly. If you are comparing options for better backup handling, off-machine copies or easier file access, use our host comparison before you move.
Compare the best Conan Exiles server hostsHow to restore without making it worse
Restore is the point where most avoidable damage happens. The usual causes are swapping files while the server is still running, leaving old journal files in place, or restoring a good game_0.db only for an old game.db to be copied back in on next start because the live file was missing.
- Stop the server completely. Do not replace world files on a live server.
- Set the current broken state aside. Copy out the current
game_0.dband anygame_0.db-walorgame_0.db-shmfiles so you can return to them if needed. - Clear leftover journal files. Remove or set aside
-waland-shmbefore bringing the restored world in. This stops old pending writes being applied to the restored database. - Place the backup back as
game_0.db. If you are using a rolling copy, copygame_0_backup_N.dbtogame_0.dbrather than renaming the original backup away. - Restore config and
modlist.txtif those changed. This is what brings back passwords, rules, region settings and the correct mod order. - Check for a stray
game.db. On Enhanced, ifgame_0.dbis missing on first start, the server copiesgame.dbinto place. That can silently resurrect an older world. - On Linux, confirm the file name is all lower case.
game_0.dbmust be exactly lower case or the server will ignore it. - Start the server and watch the log. If it stops immediately, treat that as a load failure until proven otherwise.
- Join and check the world before inviting players back. Verify spawn area, a major base, thralls, clan ownership and a few modded items.
If the server shuts down straight after the restore, check the persistence load setting in ServerSettings.ini. It may be refusing a damaged or mismatched world instead of crashing randomly.
IsLoadErrorsFatal=True
When that is enabled, a broken database or branch mismatch will usually stop the server cleanly at startup. That is useful because it points you towards the world file, mod mismatch or branch/build mismatch rather than sending you off to chase CPU or network issues.
Moving a single-player world onto the server
You can upload a local world to a dedicated server, but treat it like a restore, not a casual drag-and-drop. The world file on a Steam client sits under the game’s local ConanSandbox\Saved\ folder. On Enhanced the file is game_0.db; on Legacy it is game.db. If you cannot find it there on Windows, check the VirtualStore location as well, because UAC can redirect it.
The safe method is straightforward: stop the server, back up the current server world, set aside any -wal and -shm files, upload the local world into ConanSandbox/Saved/ and make sure it is named exactly game_0.db for Enhanced. Client and server must be on the same branch and build before you do this. The first boot can take longer than usual while the database loads, so give it a moment before assuming it has failed.
Legacy to Enhanced is one-way. Once a save has been loaded in Enhanced, it cannot go back to Legacy. If you are bringing an old Exiled Lands world forward, keep the original game.db somewhere safe as your fallback copy. Be aware of the first-start copy rule too: if an Enhanced server has no game_0.db, it will copy game.db into place on startup.
Legacy Isle of Siptah bases cannot come across into Enhanced because the island’s coordinates changed. If your move also involves map or region changes, review the Isle of Siptah and region settings before you start.
Wipe vs restore: do the one you actually mean
A wipe is not the same as a restore. For a clean wipe on Enhanced, stop the server and move game_0.db out of the folder. Then move any old game.db out as well. If you leave that older file behind, the next start can copy it back into game_0.db and your “wipe” turns into an accidental rollback.
Restore is the opposite: you keep a chosen old world and deliberately put it back. The trade-off is that every player loses progress made after that restore point. That is why dates, build labels and mod labels matter. You need to know exactly what you are putting back, not just that it is “a backup from some time last week”.
Do not edit configs during either job while the server is live. The usual symptom is settings that seem to save, then quietly return to their old values after the next restart.
Common restore problems and the first fix to try
| Symptom | Likely cause | First fix |
|---|---|---|
| Everyone is back at day one after an update | Old scripts or habits still backed up game.db, or the wrong file is live on Enhanced | Check which branch you run, confirm the live world file is game_0.db, and restore from a backup that actually contains that file |
| You restored the world but the old world came back | The swap happened while the server was running, or leftover -wal/-shm re-applied newer data | Stop the server, set aside the current files, clear -wal and -shm, then restore again |
| The server shuts down at start after restore | Damaged or mismatched database, branch mismatch, or load errors blocked by IsLoadErrorsFatal | Check the log, confirm client/server branch and build, then try an earlier backup |
| A restored world on Linux is ignored | The file name uses capitals | Rename it exactly to lower-case game_0.db |
| Buildings or items are missing after restore | The mod list differs, mods are absent, or load order changed | Restore the matching modlist.txt and make the mod set match the world you restored |
| Settings are back to defaults after restore | The config folder was not restored, or INI files were edited while the server was running | Stop the server and restore the correct Saved/Config folder |
| Disk is full or saves start failing | Rolling backup copies have piled up on the same disk | Free space, archive what you need elsewhere, and review how many local copies you keep |
A short backup routine that keeps risk low
The simplest reliable routine is to take one clearly labelled stopped copy before every risky change, plus occasional off-machine archives for disaster recovery. Keep the world, config and mod list together so you can restore a complete state rather than trying to reconstruct it later.
| When | What to copy | Where to keep it |
|---|---|---|
| Before every update or branch change | game_0.db, Saved/Config, modlist.txt | Off the server, in a folder labelled with date and build |
| Before adding, removing or reordering mods | The same set, with extra care for modlist.txt | Off the server, grouped by mod set |
| Before wipes, map or region changes, or imported worlds | The current live world and config | Off the server and easy to reach for rollback |
| At regular milestones you care about | A full stopped copy of world, config and mod list | A separate machine or storage location, not just the same disk |
Conan Exiles server FAQ
Where is the Conan Exiles server save file?
On the server, the world lives in ConanSandbox/Saved/. Enhanced uses game_0.db as the live world file, while Legacy uses game.db, and Legacy Isle of Siptah uses dlc_siptah.db.
Is game.db or game_0.db the right file to back up?
For Enhanced servers, back up game_0.db. Older guides and old scripts may still point at game.db, which is a common cause of restoring the wrong world after an update or migration.
Can I restore a Conan Exiles backup while the server is running?
No. While the server is live, SQLite may still be holding recent writes in -wal and -shm journal files. Stop the server first, then restore and clear those journal files so stale pending writes do not get applied to the restored database.
How do I upload my single-player world to a Conan Exiles server?
Stop the server, back up the current world, then upload the single-player save into ConanSandbox/Saved/ using the correct live file name for that branch, usually game_0.db on Enhanced. Make sure client and server are on the same branch and build before you start the server again.
Does Conan Exiles make automatic backups?
It makes rolling local copies of the world in the same Saved folder, and number 1 is the newest. They are useful for a quick rollback, but they are not a substitute for a proper Conan Exiles server backup kept off the server.
More Conan Exiles server guides
Our Conan Exiles host comparison and the server guides that go with this backup walkthrough.
Game updates, branches and host panels change over time. If your provider’s current panel flow differs from this guide, follow the provider’s latest steps but keep the same safety rules: stop first, copy the right files, clear journal files on restore, and keep at least one backup off the server.