What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Godlike.Host offers hosted Don't Starve Together servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
The safest Don’t Starve Together (DST) backup is a dated copy of the entire active profile or dedicated-server cluster, not a single save file. Stop the server so it completes its shutdown save, copy or ZIP the cluster with both Master and Caves data, store the archive away from the live server, and rehearse a restore on a spare location.
What a DST backup must contain
DST stores a world as a collection of cluster and shard files. The recovery unit is the complete profile or cluster directory. Copying only one apparent save file can omit world settings, player data, permissions, mods, or the second shard.
Free tools Windows power users keep installed
One-click scans. No signup required.
A local game installation normally keeps its profile under DoNotStarveTogether. A dedicated server uses the path selected by its launch options. Klei’s command-line layout is <persistent_storage_root>/<conf_dir>/<cluster>/: -persistent_storage_root is an absolute path, -conf_dir defaults to DoNotStarveTogether, and -cluster chooses the cluster directory. Those options override the platform’s usual location, so inspect the launch script, service unit, or scheduled task before copying anything.
| Platform or setup | Typical profile path | Important qualification |
|---|---|---|
| Windows local data | DocumentsKleiDoNotStarveTogether |
A dedicated server can use a different absolute persistent-storage root. |
| macOS local data | ~/Documents/Klei/DoNotStarveTogether |
Check the server’s launch options if it is not using the local client profile. |
| Linux local data | ~/.klei/DoNotStarveTogether |
Services and containers commonly point to a custom root. |
For Windows PC support, Klei’s official wording is: “For Don’t Starve Together on Windows PC, go to your DocumentsKlei directory and zip it up with all subdirectories.” For a dedicated server, use the same principle but identify the active root first and preserve the complete cluster beneath it.
#1 Best Overall
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Find the active server path before you copy
Do not assume that the first DoNotStarveTogether folder you find is live. A server started with -persistent_storage_root, -conf_dir, or -cluster can read and write somewhere else.
- Open the script, systemd service, Docker/hosting command, or shortcut that starts the server.
- Record the values of
-persistent_storage_root,-conf_dir, and-cluster. If-conf_diris omitted, useDoNotStarveTogether; if-clusteris omitted, identify the cluster selected by the startup configuration. - Build the resulting path in the form
<persistent_storage_root>/<conf_dir>/<cluster>/. - Confirm that the directory contains the cluster’s
cluster.iniand shard folders. Check modification times while the server is running to ensure this is the directory being updated. - If the server has more than one cluster, repeat the inventory for each one and back up each cluster separately.
This check prevents a technically successful backup of an old or unused profile.
Make the world consistent before taking the backup
Preferred method: shut down cleanly
Stop the server through its normal console or service procedure and wait until the process has exited. DST saves on shutdown, so an orderly stop captures the latest completed state and releases files that might otherwise be changing during the copy. Do not kill the process or reboot the host while it is writing.
When you cannot stop immediately
From the server console, issue c_save() to request a manual save, then stop player activity and copy only after the save has completed. This is a controlled-save fallback, not a substitute for an offline copy: files can still change while a live server is operating. For a scheduled backup, stop the service, archive the files, and start it again rather than relying on a long-running live copy.
Rank #2
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Record what you are backing up
- Note the cluster name and whether it has Master only or Master plus Caves.
- Write down the server version, launch options, and any non-default mod or shard configuration.
- Keep the date and time in the archive name, using a sortable format such as
dst-cluster-2026-10-14-2300.zip.
Understand the files inside a dedicated cluster
A dedicated cluster has shared files at its top level and separate files for each shard. The exact contents vary with enabled features, but the following items are the ones to preserve when present.
| Location or file | Purpose | Backup action |
|---|---|---|
cluster.ini |
Cluster-wide settings and identity configuration. | Copy it with the cluster root. |
cluster_token.txt |
Token identifying the server instance and required for operation. | Back it up, but treat it as a secret; never publish it in a screenshot, repository, ticket, or public download. |
adminlist.txt |
Administrators allowed to use server commands. | Preserve it to retain operator access. |
blocklist.txt |
Blocked users. | Copy it if present. |
whitelist.txt |
Allowed users when a whitelist is used. | Copy it if present. |
| Master shard directory | Surface-world data, shard settings, world-generation overrides, and shard-specific mods. | Copy the entire directory, including its save and configuration files. |
| Caves shard directory | Caves-world data and its shard-specific settings. | Copy the entire directory whenever the cluster uses caves. |
server.ini in each shard |
Per-shard server settings. | Keep the Master and Caves copies with their original directory names. |
worldgenoverride.lua and leveldataoverride.lua |
Optional world-generation and level-data overrides. | Include them when present; omitting one can change how a restored world loads. |
modoverrides.lua and mod download/configuration files |
Which mods are enabled and how they are configured. | Include the files and folders used by the cluster so the restored shards can reproduce the same setup. |
Master and Caves are separate shards, not interchangeable copies. If the cluster uses caves, both shard directories must remain together under the same cluster.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchBack up a local or dedicated server step by step
Windows
- Stop the DST server cleanly and wait for its process to exit.
- Open File Explorer and navigate to the active cluster’s parent. For the default local profile, start at
DocumentsKleiDoNotStarveTogether; for a dedicated service, follow its configured persistent-storage root. - Select the complete cluster directory, not just a shard or a file inside it.
- Right-click and choose the built-in compressed-folder option, or use an archive utility to create a ZIP. Keep all subdirectories and hidden files.
- Open the resulting archive and verify that it contains
cluster.ini, the token and permission files when present, and every enabled shard directory.
macOS
- Stop the server or perform the controlled-save procedure, then stop it before copying.
- For the default profile, open
~/Documents/Klei/DoNotStarveTogether. Use the path produced by the launch options for a dedicated service. - Copy the entire cluster directory to a staging folder, then create a ZIP from that folder so the directory hierarchy is retained.
- Inspect the archive before moving it to storage, especially for both Master and Caves directories.
Linux
- Stop the systemd service, container, screen/tmux session, or startup script that runs the server.
- For the default Linux profile, check
~/.klei/DoNotStarveTogether; use the configured absolute root when the service specifies one. - Create a ZIP or a recursive copy of the complete cluster. Preserve file names, directory structure, and permissions where your restore process depends on them.
- List the archive contents and confirm that shared files and every shard are present.
Command-line archive example
On a Unix-like host, after substituting the actual active path and cluster name, an archive can be created with:
cd /path/to/DoNotStarveTogether
zip -r /backup/dst-cluster-2026-10-14-2300.zip Cluster_1The command is an example of archiving a complete cluster directory. Do not use it until the server is stopped and the path has been confirmed. On Windows, use File Explorer’s compressed-folder command or an equivalent archive tool.
Rank #3
- Easily store and access 1TB to content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop. Reformatting may be required for Mac
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Store backups so a server failure does not destroy them
Save the dated ZIP outside the live server directory. A disk failure, mistaken deletion, bad update, or corrupted live folder can affect both the server and any archive stored beside it. An external hard drive for PC backup is a practical physical destination for these ZIP files; a second independent copy provides additional protection.
- Use names that include the cluster and timestamp, and keep several restore points rather than overwriting one archive.
- Maintain at least one copy on a different device from the server. Disconnect a removable drive after copying if it is not being used for another task.
- Restrict access to
cluster_token.txtand to any archive containing it. The token is operationally sensitive even though it is needed during recovery. - After creating an archive, open it or list its contents and check its size. A zero-byte, partial, or unexpectedly tiny ZIP is not a usable backup.
- Keep a short record of the launch options and the server’s Master/Caves layout beside the archive, without publishing the token itself.
Restore a DST dedicated server
Restore to a stopped destination. The destination can be the original host after a disk replacement, a new machine, or a spare test installation. The destination’s command-line options determine where the cluster must go.
- Install or prepare the dedicated-server files and stop all Master and Caves processes.
- Inspect the destination launch command. Decide whether to keep its existing
-persistent_storage_root,-conf_dir, and-clustervalues or change them to the intended location. The persistent root must be an absolute path. - Extract the archive so the complete cluster sits at
<persistent_storage_root>/<conf_dir>/<cluster>/. Avoid an extra nesting level such asCluster_1/Cluster_1/. - Confirm that the extracted cluster contains
cluster.ini,cluster_token.txtwhen required, permission lists, and the full Master and Caves shard directories. - Ensure the account that runs the server can read and write the restored files. Correct ownership or permissions if the service account cannot access them.
- Start the same Master and Caves shards that belonged to the cluster. Watch the console for path, token, mod, or permission errors.
- Connect as an administrator and verify the world name, season/day state, player data, inventories, structures, and shard travel. Test a normal save and a clean shutdown.
- Only after the test succeeds should you switch players to the restored instance or replace the production directory.
Copying a complete cluster into the destination is the reliable migration pattern because it carries shared settings together with each shard’s world and player state. If the destination uses a different root, remapping the launch options is sufficient; the internal cluster layout should remain intact.
Diagnose a restore that does not look right
The server starts a new world
Usually the process is reading a different path or cluster name. Stop it, print or inspect the effective launch options, and compare them with the archive’s extracted location. Check for the extra-nesting mistake and confirm that cluster.ini is directly inside the selected cluster directory.
Rank #4
- Easily store and access 4TB of content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Caves are missing
Verify that the archived cluster actually contained the Caves shard and that the restored startup launches both shards. Restoring only Master does not recreate the caves world.
Players, permissions, or server identity are wrong
Check that the complete cluster was extracted, including the player/world data, adminlist.txt, blocklist.txt, whitelist.txt, and cluster_token.txt when applicable. Do not substitute an empty cluster’s permission files for the archived ones without understanding the effect.
Mods or world settings changed
Compare each shard’s modoverrides.lua, optional worldgenoverride.lua and leveldataoverride.lua, and the mod download/configuration files with the archive. A missing override or mod file can make a restored shard load differently even when the world save itself is present.
The service cannot read the files
Check ownership and permissions after extraction. The account running the service needs access to the cluster, shard directories, and files it must update during saves.
Best Value
- [Upgraded Version] - This external hard drive features a mirrored logo stripe combined with a striped anti-slip design, and the rounded corners of the casing make it easier to grip. The stripes also have a heat dissipation function, ensuring stable and fast data transfer.
- 【Ultra-thin and quiet】 - The motherboard adopts JMicron 578 noise-free solution, giving you a quiet working environment. Lightweight and portable size designed to fit in your pocket for easy portability.
- 【Ultra-Fast Data Transfers】 - Pairing this external hard drive with JMicron 578 solution USB 3.0 and USB 2.0 interfaces enables blazing-fast data transfer. It boasts theoretical read speeds of up to 125MB/s and write speeds of up to 103MB/s.
- 【Plug and Play】 - With no software to install, just plug it in and the drive is ready to use.The hard disk chip is wrapped with an aluminum anti-interference layer to increase heat dissipation and protect data.
- 【What You Get】 - 1 x Portable Hard Drive, 1 x USB 3.0 Cable, 1 x User Manual, Gift-type shell packaging ,Three-year manufacturer's warranty and free technical support services.
The token was exposed
Treat a publicly posted token as compromised. Remove the exposed archive or screenshot, restrict access to replacement files, and follow the server platform’s token-replacement procedure before returning the instance to service. Never include the token in troubleshooting posts.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choose a backup method by its recovery properties
| Method | Completeness | Consistency | Portability | Recovery confidence |
|---|---|---|---|---|
| Offline ZIP of the complete cluster | Full cluster, shared files, and both shards when present. | Strongest when made after a clean shutdown. | Can be extracted under a different absolute root by changing launch options. | High only after opening and test-restoring an archive. |
| Live copy while the server is running | May include the full cluster, but files can be changing. | Lower; a save can be split across files. | Same path rules as an offline copy. | Uncertain until tested; use only when downtime cannot be arranged. |
Manual c_save() followed by copy |
Depends on whether the complete cluster is copied. | Better than an uncontrolled live copy, but weaker than stopping the server. | Same path rules as an offline copy. | Moderate; still rehearse a restore. |
| Single-file or single-shard copy | Incomplete; can omit permissions, mods, or the other shard. | Cannot represent the complete cluster reliably. | May start only if the destination already has matching files, but it is not a full recovery. | Low and unsuitable as the primary backup. |
The practical standard is a cleanly saved, complete, dated cluster stored separately, with at least one second copy and a restoration test. A backup is not proven until a spare host or copy can start the intended Master and Caves shards and show the expected world and player state.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Backup checklist
- Identify the effective absolute persistent-storage root and cluster name.
- Stop the server cleanly; use
c_save()only as a controlled fallback before stopping. - Archive the complete cluster/profile, not a lone save file.
- Include Master and Caves, all shared lists, token, overrides, and mod configuration files when present.
- Inspect the archive contents and protect the token.
- Store a dated archive outside the live directory and keep a second copy.
- Restore to a stopped destination using the destination’s launch path.
- Start both intended shards and verify world, players, mods, permissions, and a fresh save.
Frequently Asked Questions
Where are my DST server saves?
Use the path selected by the server’s -persistent_storage_root, -conf_dir, and -cluster options. Defaults are DocumentsKleiDoNotStarveTogether on Windows, ~/Documents/Klei/DoNotStarveTogether on macOS, and ~/.klei/DoNotStarveTogether on Linux.
Do I need to back up both Master and Caves?
Yes, when the cluster uses caves. They are separate shards and both must be restored under the same cluster directory.
Can I copy the files while the server is online?
A controlled c_save() followed by a quick copy is possible, but stopping the server after the save gives a more consistent offline archive.
What should I do if a restored server loads a new world?
Stop it and verify the effective launch path, cluster name, archive nesting, and presence of cluster.ini directly inside the selected cluster directory.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
