7D2D Server User Guide

Follow these trusted workflows to back up, upload, and update your 7 Days To Die server without losing progress. Every section comes from our in-house success team and mirrors the latest Supercraft control panel.

Protect Saves Upload Worlds Update Safely

Start with the task you actually need

Pick the fastest path first, then drop into the full step-by-step workflow or support answer only if you need more detail.

Download a backup

Grab a fresh world ZIP before updates, imports, or mod changes so you always have a safe rollback point.

Open backup workflow

Upload a save in browser

Use the web uploader when you already have the correct ZIP structure and want the quickest import path.

Open uploader workflow

Upload a save with FTP

Choose FTP for larger worlds, manual GameWorld changes, or migrations that need more control.

Open FTP workflow

Update safely

Follow the stable update path, confirm the install in the console, and only restart once the job completes.

Open update workflow

Restore after rollback

Use the backup guidance when your world rolls back, corrupts, or you need to identify the right archive to keep.

Open restore answer

Import worlds or mods via FTP

Use the FTP path for bigger imports, manual mod folders, or file layouts that do not fit the browser uploader.

Open FTP import answer

1. Download a Manual Backup

  1. Select Manage Server on the portal and wait until every control initializes.
  2. Open Files & Mods, expand your active world, and choose Download. Larger saves may need up to 10 minutes; keep the tab open.
  3. Optional: inspect user_data/saves via the dropdown to confirm the save slot you intend to protect.
  4. When the progress bar completes the portal displays Ready to download and starts transferring automatically (use the button only if the browser canceled the file).
  5. Find the zipped world such as World Number 12.zip in your downloads folder and move or extract it into %APPDATA%/SevenDaysToDie before restoring.
  6. Always complete a manual backup before large game updates from The Fun Pimps so you can roll back safely.

2. Upload a Save with FTP (FileZilla Example)

  1. From Details in the server dashboard copy the FTP host, username, password, and port (use Show password as needed).
  2. In FileZilla enter the credentials exactly, then click Quickconnect.
  3. On the remote pane browse to SDTD/activeworld/userdata.
  4. Create GeneratedWorlds if missing and delete the default Navezgane folder to prevent conflicts.
  5. On the local pane open C:\Users\<you>\AppData\Roaming\7 Days To Die.
  6. Under saves drag the save folder into userdata/saves remotely; monitor the transfer queue until it completes.
  7. Copy new game options, sd cs profiles, and server admin files from the local directory and overwrite the remote versions.
  8. Switch to userdata/generatedworlds remotely and upload the matching generated world folder. Large worlds can take longer.
  9. Return to Manage → Files & Mods and verify both generatedworlds and saves display the uploaded data.
  10. Edit activeworld/serverconfig, update GameWorld so it exactly matches the uploaded world name, save, and restart the server. Confirm the console log references the correct world/version.

Need a quick refresher or port details? Bookmark the dedicated FTP access page for connection steps and troubleshooting links.

3. Upload a Save with the Web Uploader

  1. Prepare files locally under C:\Users\<you>\AppData\Roaming\7 Days To Die by creating an Upload folder with userdata and savegame inside.
  2. Within userdata create GeneratedWorlds and Saves.
  3. Copy the generated world you need into Upload/userdata/GeneratedWorlds.
  4. Copy the matching save folder plus new game options, sdc s profiles, and server admin into Upload/userdata/Saves.
  5. Move the entire Upload folder somewhere easy (Desktop) and compress it to a ZIP archive.
  6. In Manage Server → Files & Mods scroll to Upload a Save World, choose the ZIP, and upload. Wait until the portal lists the new save.
  7. Press Activate → Activate and Restart. The service unpacks files, replaces server data, and restarts automatically.
  8. After the restart expand world.zip → userdata from the dropdown to confirm your files before letting others connect.

4. Update an Unmodded Server Version

  1. Verify the current version on the banner or Manage Server page and cross-check the console for real-time info.
  2. Click the yellow Check for Steam upgrades button; the status moves through “Reconfiguration scheduled” and “Server is off”.
  3. Once the service stops, read the Console Log and wait for successfully installed before starting the server.
  4. Watch the boot log for the updated version string, especially for crossplay servers where console parity matters.
  5. If players see “incompatible version,” rerun the upgrade only after downloading a fresh manual backup.
  6. After the portal reports Online, confirm the main banner reflects the new version before inviting players.

Additional Best Practices

  • Store dated backup ZIPs somewhere safe so you can roll back after failed uploads or corruption.
  • Never close the browser tab while downloads, uploads, or restarts run; you could miss prompts even though the backend continues.
  • After importing new saves always inspect the console for red errors and verify the loaded save name before players join.
  • When unsure, download a fresh backup before every major change - upload, FTP overwrite, or version update.

Bookmark this guide and return to any section whenever you repeat a task. Need extra help? Contact the Supercraft support team.

What to read next

Continue the admin journey without leaving the site.

Control panel overview Console commands Upload maps/mods via FTP Monitor with CSMM Help & FAQ