Skip to content
Game panel

Upload your existing Project Zomboid world

Project ZomboidIntermediateBuild 41 · Build 42

Move a world you started with Host or at another dedicated host to OXY. You will check the world, characters and mods separately before inviting players back.

What you'll do
  1. Collect the world and matching settings
  2. Check the exact game build
  3. Back up and upload to OXY
  4. Join and check world, characters and mods
  1. Co-op world started with Host: stop hosting and close the game. On the host PC, open %UserProfile%/Zomboid/Saves/Multiplayer/ and copy the folder for that world. From %UserProfile%/Zomboid/Server/, copy its matching <name>.ini, <name>_SandboxVars.lua and <name>_spawnregions.lua if present. Include %UserProfile%/Zomboid/db/ in your untouched source export; it can contain server account records.

    Another dedicated host: stop that server and download the same save folder and matching config files through its file manager or SFTP. Keep its db folder in the untouched export too, if available. Ask that host for a complete export if you cannot access these files. Keep the source folder layout; a client-side cache from someone who merely joined the server is not a full server export.

    Keep a separate note of the exact build, profile name, WorkshopItems= and Mods= lists. Keep non-Workshop mods as a separate copy. A Workshop collection or ID list may omit required dependencies. Keep the untouched source copy on your PC.

  2. In the game panel, stop the server and create and download a backup. Confirm it completed before replacing files. The OXY save and config name is Pterodactyl by default; if you changed Save/Config Name, use its current value instead. In Files, check the active .cache/Server/<ServerName>.ini and .cache/Saves/Multiplayer/<ServerName>/. Keep the existing OXY world and config in the backup. Rename the current <ServerName>/ folder to <ServerName>-before-upload/ and add a .before-upload suffix to its matching config files, so the new files cannot mix with the old ones.

  3. On your PC, prepare a staging folder with .cache/Saves/Multiplayer/<ServerName>/ and .cache/Server/. Put copies of the save and matching config files there, then zip the .cache folder. Keep the source db folder out of this upload: the published Host transfer advice covers another Host PC, and it does not establish which account records an OXY dedicated server needs. If you need old accounts or characters to carry over, ask support whether the source database is needed before uploading it. Do not attach the database to a ticket or overwrite the OXY database yourself. Upload the archive with SFTP, then use Unarchive in Files. Place the world at .cache/Saves/Multiplayer/<ServerName>/ and the matching <ServerName>.ini, <ServerName>_SandboxVars.lua and optional <ServerName>_spawnregions.lua in .cache/Server/. Rename the incoming save folder and matching config files to the active OXY name, or set Save/Config Name to the source profile name. Check that files are directly inside the named save folder, not another nested folder. If the names or data root differ from what you see, stop and ask support to identify the active profile before starting.

  4. Compare WorkshopItems= and Mods= in the uploaded .ini with your source note. Follow the mod installation guide for the required Workshop items and dependencies. If PZ Mods is available on your server, run Sync Mods/Map for the active profile; otherwise use the guide’s manual route. Handle non-Workshop mods according to their authors’ dedicated-server instructions; ask support if the installation route is unclear. Start the server only after the build, profile and mods match. Check the console for save or mod errors.

  5. Join the OXY server with the exact account username used on the old server, including capitalization and special characters. Check world and bases, character, inventory and skills, and mod features separately. Using the same Steam account alone does not identify the old character. If a character is missing, verify the exact username and source profile before creating a replacement; an already dead character will not be restored by changing a login. Do not edit databases to try to repair it yourself.

My world is here, but my character is missing

Section titled “My world is here, but my character is missing”

The save folder contains world and character data, but a matching world does not guarantee every character will load. Check the exact Account username used before migration, not just the Steam account. If the name matches and progress is still missing, contact support with the source and destination profile names, exact builds, the username and relevant console lines. Never send account, panel or server passwords in a ticket. OXY can help with a one-time migration or a problem afterward; character recovery is not guaranteed.

  • Wrong or empty world: stop the server and compare the active profile name with the uploaded folder and .ini before changing more files.
  • Mods fail to load: check the first relevant console error and each mod’s build, dependencies and dedicated-server instructions; see install mods.
  • Need to roll back: stop the server and follow Restore your world to check the recovery point and matching files before replacing anything; restoring can discard progress made after the backup.

Host your own Project Zomboid server

Play together on your own server

View servers