Most Hytale server owners don't think about backups until the moment they need one — a crashed update, a griefer with admin access, or a botched mod install that corrupts the world file. By then it's too late. A single corrupted universe folder with no backup can end a server's community overnight, and most "back up your world" advice floating around doesn't even say where that folder actually lives. Here's exactly where Hytale stores your world data, how to back it up without making things worse, how to restore it cleanly, and how to migrate a server to a new host without losing progress.
Where Hytale Actually Stores Your World Data
Before you can back anything up, you need to know what you're actually copying:
- Singleplayer worlds live in %appdata%\Hytale\UserData\Saves\ on Windows — this is the folder to grab if you're backing up a solo world or preparing to move it to a server.
- Server worlds live inside a universe folder in your server's root directory, with individual worlds stored under universe/worlds/. That single universe folder holds everything — world data, player data, and map chunks — not just the terrain.
- Per-world settings sit in a config.json file inside each world's own folder, separate from the chunk data itself.
The distinction that trips people up: backing up only the specific world folder and skipping the rest of universe means you lose player data on restore — inventories, positions, and progress — even though the terrain comes back fine. Always back up the whole universe folder, not just the world inside it.
How to Back Up a Hytale Server Correctly
The process itself is simple, but the order of operations matters more than it looks:
- Stop the server first. Never copy or download world files while the server is running — chunks are actively being written, and pulling a copy mid-write is one of the most common causes of a corrupted world that only shows up after you've already deleted the "old" version.
- Copy the entire universe folder, not just the world you care about, to preserve player data alongside the terrain.
- Store it somewhere that isn't the same disk as your server. A backup that lives on the same drive as the thing it's backing up doesn't protect you from a drive failure — copy it to external storage or a cloud bucket, not just a second folder on the same machine.
- Restart the server once the copy has finished.
If you're on managed hosting, most providers now run scheduled automatic backups in the background — but "automatic" isn't the same as "reliable." Confirm your specific plan includes backups you can restore yourself on demand, not a policy that requires opening a support ticket and waiting. Our hosting guide covers exactly what to check for in a provider's backup policy before you commit to one.
Restoring From a Backup
Restoring reverses the backup process, with one detail that matters more than people expect:
- Stop the server before touching anything, same as with backing up.
- Replace the universe folder exactly — the restored folder needs to be named universe, all lowercase, in the server's root directory. A mismatched name is a common reason a restore silently fails to load.
- Match your mods to when the backup was taken. If the backup includes a world that was running with specific mods installed, those same mods need to be present on the server before it starts back up — restoring a world without them is a frequent cause of crashes or players finding their modded items missing entirely. Our mod installation guide covers the server-side setup if you need to reinstall anything to match.
- Test before reopening to players. Boot the restored server privately first and confirm the world loads, spawns correctly, and nothing looks off before you tell your community it's back.
Migrating to a New Host Without Losing Progress
Moving to a new host is really a backup and restore across two different machines, with a few extra steps that matter at scale:
- Take a full backup first — universe folder, mods, and any permission or config files your setup depends on. Treat this exactly like a disaster backup, because if the transfer goes wrong, it's the only copy you'll have left.
- Compress it into a single zip before transferring. A universe folder can contain thousands of individual chunk files, and uploading them one at a time over FTP is slow and dramatically increases the chance of a corrupted file breaking the whole transfer.
- Use SFTP for anything over roughly 100 MB, not your host's web-based file manager. Browser uploads aren't built for large, sustained transfers and are far more likely to time out or drop partway through on a multi-gigabyte world.
- Boot the new server privately first. Confirm the world loads correctly, settings match your old config, and any mods your community relies on are installed and working before you point anyone at the new address.
- Update your server's IP everywhere players will look — your Discord, your website, and your Hytale Top Servers listing, so the live status pinger tracks your new host instead of reporting the old one as offline.
Only after all of that checks out should you actually shut down the old host and send your community to the new one. A migration that goes straight from transfer to public announcement, with no testing step in between, is how a routine host switch turns into a multi-day outage.
Moving a Singleplayer World to a Multiplayer Server
The same universe folder logic applies if you're promoting a singleplayer world you've already built into a real server for friends. Copy the world data out of %appdata%\Hytale\UserData\Saves\ on your PC and place it into the new server's universe directory in place of the default generated world. If you were running any mods in singleplayer, install the matching server-side versions before you boot it, for the same reason a restore needs matching mods — a mismatch is the most common cause of a "successful" migration that immediately crashes on launch.
Common Mistakes That Cause Data Loss
- Copying files while the server is still running. This is the single most common cause of a "backup" that turns out to be corrupted when you actually need it.
- Never testing a restore. A backup you've never restored from is a theory, not a safety net — do a practice restore on a spare instance occasionally so you're not learning the process for the first time during an actual emergency.
- Backing up to the same drive as the server. It protects you from world corruption, but not from the hardware failure that takes the drive down entirely.
- Forgetting mods when restoring or migrating. A world file alone isn't the whole picture if mods were part of what made that world work.
- No offsite copy at all. Whatever your host's automatic backup schedule looks like, keep at least one copy somewhere you control — a cloud drive or your own machine — independent of that host entirely.
The Bottom Line
Hytale stores everything that matters — world, players, and progress — inside one universe folder, and protecting it comes down to a short list of habits: always stop the server before touching files, back up the whole folder rather than just the world inside it, keep a copy off the host itself, and actually test a restore before you need one for real. Migration is the same discipline applied across two machines, with compression and SFTP replacing a simple copy-paste. Get the fundamentals in this guide right once, and a bad update or a host outage becomes an inconvenience instead of the end of your community.
Still setting up your hosting environment from scratch? our complete server setup guide covers backups alongside every other launch step. Already running a server and want more players to actually find it once it's stable? list it on Hytale Top Servers for free, or browse the current listings to see how established communities present theirs.