So you've been playing Conan Exiles solo, you've stacked up a sandstone fortress somewhere in the Exiled Lands, tamed a few thralls, and now you want to invite friends in. Good news – you can move your singleplayer save across to a dedicated server. It's a handful of steps and a bit of care around file paths, and that's about it.
The save filename changed under the Enhanced (UE5) update on May 5 2026, so this guide covers both the current Enhanced format and the older Legacy (UE4) format. Most of what's below is identical either way – the only real difference is which file you're picking up.
Where Conan Exiles keeps its saves
Conan Exiles is a bit odd here. Instead of dropping saves into AppData like most games, it writes them into its own install folder. For a standard Steam install that's:
C:\Program Files (x86)\Steam\steamapps\common\Conan Exiles\ConanSandbox\Saved\
Quickest route: in Steam, right-click Conan Exiles → Manage → Browse local files. Steam opens you straight into the install root, then it's ConanSandbox\Saved\.
Inside that folder you're after one file. Which name it has depends on which version of Conan you're running:
- Conan Exiles Enhanced (UE5, May 2026 onwards) – the file is
game_0.db. On the very first boot of Enhanced, the game copies the oldGame.dbtogame_0.dbifgame_0.dbdoesn't already exist, then keeps writing togame_0.dbfrom then on. Inflexion's own migration guide calls this out specifically – any backup script or upload tool that was looking atGame.dbneeds updating to point atgame_0.db. - Conan Exiles Legacy (UE4, pre-Enhanced) – the file is still
game.db. If you're staying on the Legacy beta branch, nothing on this page changes for you.
That one file is your world – character, buildings, thralls, chests, placed torches, the lot. It's a single SQLite database, and on a current Enhanced install it's the only thing you need to copy.
A note on Isle of Siptah: under Legacy, Siptah was a separate map with its own DLC_Siptah.db save file. Under Enhanced, Funcom merged Siptah into the Exiled Lands map – there's no longer a separate Siptah save type, and a singleplayer Enhanced save lives in game_0.db whether you're playing in the Exiled Lands region, the Siptah region, or both. If you've still got a DLC_Siptah.db lying around from your Legacy days, hold onto it as a backup but don't expect to upload it to an Enhanced server – the schema isn't compatible, and Enhanced servers won't read it.
One catch worth flagging. If you first launched Conan Exiles without admin rights on Windows, UAC may have quietly redirected your save into the VirtualStore:
%LOCALAPPDATA%\VirtualStore\Program Files (x86)\Steam\steamapps\common\Conan Exiles\ConanSandbox\Saved\
If your save isn't where you expect it, paste that path into the File Explorer address bar and have a look – plenty of players' saves end up there without them realising.
Before you touch anything
Two things, both matter.
Stop the server first. Log into control.low.ms, find your Conan Exiles service, hit STOP. Uploading over a running server is a straight route to a corrupted save – the database is an open SQLite file that the server writes to constantly, and overwriting it mid-write leaves you with something half-rewritten that won't load. Stop it, give it a good ten or fifteen seconds to actually come down, then start the transfer.
Back up what's already on the server. Even if the server's brand new and there's nothing worth keeping, get into the habit now. In the panel sidebar, click Cloud Backup and take one. Takes seconds. If your imported save turns out to be broken, or isn't the version you thought it was, Cloud Restore puts you right back.
Match the version before you upload
The schema between Enhanced and Legacy isn't cross-compatible. An Enhanced server won't read a Legacy game.db, and a Legacy server won't read an Enhanced game_0.db. So before you start moving files:
- Enhanced client → Enhanced server. Upload
game_0.dbto the server. Standard case for any new save made on or after May 5 2026. - Legacy client → Legacy server. Upload
game.dbto the server. This is the path for anyone who's chosen to stay on the UE4 build by opting into the "Conan Exiles Legacy" Steam beta branch on both client and server. - Legacy client → Enhanced server, or vice versa. Don't try to mix. The cleanest path is to bring both client and server up to the same version first – usually that's "let Steam update both to Enhanced" – and then do the upload. If you've got a Legacy save you really want preserved on an Enhanced server, open a ticket and we'll see what we can do, but the schema differences make this a one-way migration in practice.
Uploading via File Manager
The panel's File Manager is fine for this job:
- Log into control.low.ms and pick your Conan Exiles server
- Click File Manager in the sidebar
- Open
ConanSandbox/Saved/ - Delete the existing
game_0.db(orgame.dbon a Legacy server). If you'd rather have a quick local rollback, rename it to.bakinstead of deleting - Upload your save file from
ConanSandbox\Saved\on your PC into the same folder on the server –game_0.dbfor Enhanced,game.dbfor Legacy
File Manager handles a single file upload cleanly, and that's really all you're doing here – one file across. Where it starts to feel slow is on long-lived servers where the database has grown, or if you're on a flaky connection. At that point SFTP is the better call.
Uploading via SFTP
SFTP is on port 8822. You'll need a client – WinSCP and FileZilla both work fine. Your connection details live in Service Settings in the panel.
- Protocol: SFTP
- Host: the address shown in Service Settings
- Port: 8822
- Username / Password: your panel credentials for this service
Connect, navigate to ConanSandbox/Saved/ on the server side, drag the matching .db across from your local machine. SFTP gives you a proper progress bar and recovers better on bigger transfers, which is what you want if the database has any real size on it.
Starting back up
Kick the server off from the panel. First boot with an imported save takes longer than normal – Conan has to open the database, validate it, rebuild its in-memory state and bring the world back. If it's a big save, give it a couple of minutes and don't panic.
Pop open Web Console and watch the logs. Once the scrolling settles down and the server goes quiet, grab your connection details and join in. Character, base, thralls – all where you left them.
A quick note for anyone still on Legacy: under UE4, Conan dedicated servers picked which map to load via the ServerDefaultMap= line in Engine.ini (or via a launch-arg override in Commandline Manager). On Enhanced this is no longer a thing – there's only one map, the engine loads it, the Siptah region is reachable from inside it for any player who owns the DLC. So if you're upgrading a Legacy server to Enhanced, the old ServerDefaultMap= line is harmless to leave in place but doesn't do anything anymore.
A few useful things to know
The .db file being a plain SQLite file has one nice upside: you can open a copy on your own machine with something like DB Browser for SQLite and poke around. Tables for buildings, characters, thralls, inventories – it's all sitting there. A couple of community projects wrap a friendlier UI around the same data: Conan Server Toolbox and the conanexilessql script collection are both worth a look if you want to reset a stuck player, clean up an abandoned base by hand, or just see how the game is put together. Always work on a copy – there's no undo button on a hand-edited SQLite file.
A heads-up for anyone digging in for the first time on an Enhanced save: the schema changed in places between UE4 and UE5. Older community SQL scripts that still reference UE4 table or column names may not work cleanly on a game_0.db from an Enhanced server. Test on a copy.
Version drift is another one to watch. If your local game has updated and the server hasn't (or vice versa) the schema the server expects can be out of step with what's in your save, and you'll see the world refuse to load or come up partial. Keep both on the same build – use Steam Update in the panel to bring the server onto the version your client is on before you import.
If any of this goes wrong, that's what your backup is there for. Cloud Restore, pick the backup you took at the start, and you're back where you were. For anything on tuning settings once your world is up and live, have a read of the Conan Exiles server settings guide.