Unturned Dedicated Server: How to Change the Map Step by Step

How Unturned dedicated server map settings work

An Unturned dedicated server reads its startup settings from a folder named after the server. When you launch the server with a name such as MyServer, the game creates a directory at Servers/MyServer inside the installation folder. Inside it you will find a Server folder holding Commands.dat, plus configuration files and the saved world data.

Commands.dat is a plain text file. Each line is a command the server runs as it starts, such as the server name, the maximum number of players, the port, the game mode and the map. The map line looks like Map PEI or Map Washington. Change that line, restart, and the server loads the new map.

World progress is saved per map, so changing the map does not erase your old world. If you later switch back, the previous save is usually still there unless you delete it.

Step by step: change the map on your Unturned dedicated server

These steps work the same on Windows and Linux. On a Windows server you can do them through Remote Desktop and File Explorer; on Linux you use SSH and a text editor such as nano.

• Stop the server cleanly. Type save and then shutdown in the server console, or stop the service, so the current world is written to disk.
• Back up the server folder. Copy Servers/YourServerName somewhere safe before you edit anything.
• Open Commands.dat. It lives in Servers/YourServerName/Server/Commands.dat.
• Edit the Map line. Replace the old name with the new one exactly as the game spells it, for example Map Russia or Map Yukon. If there is no Map line, add one.
• Save the file as plain text. Make sure your editor does not add a different extension or rich formatting.
• Start the server again. Watch the console as it loads. It should name the new map while loading the level.
• Join and check. Connect from the game and confirm you spawn on the new map.

Loading a curated or Workshop map

Official maps that ship with the game load with just the Map line. Curated and community maps from the Steam Workshop need one more step, because the server must download them first.

In the same server folder you will find WorkshopDownloadConfig.json. It contains a list called File_IDs. Add the numeric Workshop ID of the map, which you can copy from the end of the map's Workshop page address. Then set the Map line in Commands.dat to the map's internal name, which is usually shown on the Workshop page or in the map's description.

When the server starts it downloads the Workshop item, then loads the map. The first start after adding a map takes longer because of that download. Players who join will be prompted to download the same content automatically.

• Use the Workshop file ID, not the creator's profile ID.
• Keep the JSON valid: IDs are separated by commas, with no trailing comma after the last one.
• Spell the map name exactly, including spaces and capitals, as some names contain more than one word.
• If the map relies on extra mods, add their IDs to File_IDs as well.

Resetting or keeping your world

Because saves are stored per map, you can rotate between maps without losing progress. Saved data sits under the server folder in a Level directory, with a subfolder for each map you have played.

If you want a fresh start on the same map, stop the server, move that map's folder out of the Level directory and start again. The server generates a new world. Moving rather than deleting means you can restore the old world if the group changes its mind.

Player inventories and skills are also saved per server and map. Tell your players before a switch so nobody is surprised to find an empty backpack.

Common problems when changing the map

Most failed map changes come down to a handful of causes.

• The server still loads the old map: you probably edited Commands.dat in a different server folder. Check the name you pass at launch matches the folder you edited.
• Map not found: the name is misspelled, or the Workshop item has not downloaded. Check the console output for the download step.
• Players cannot join after the switch: they may need to download the Workshop content. Ask them to restart the game and try again.
• Server crashes while loading: large custom maps use more memory than the base maps. Check memory usage and logs, and consider more RAM.
• Changes revert: a hosting panel or startup script may overwrite Commands.dat on boot. Edit the setting in that panel or script instead.

Rotating maps for a community server

Some communities like to rotate maps every few weeks to keep things fresh. Because each map keeps its own save, rotation is simple: announce the date, save and stop the server, change the Map line and start again. Players return to their previous progress when the rotation comes back round.

If you want rotation to happen without logging in, write a small script that swaps in a prepared copy of Commands.dat and restarts the service. On Linux a cron job can run it at a quiet hour; on Windows the Task Scheduler does the same job. Keep a separate Commands.dat file for each map, named clearly, so the script only copies files and never edits text.

Whatever approach you choose, test the switch once on a weekday before relying on it, and keep the backup step in the script so a bad map file never costs you a world.

Why map size matters for server resources

Bigger maps hold more objects, more zombies and more structures built by players. Over time a long running world on a large map uses noticeably more memory than a fresh world on a small one. Workshop maps also vary widely in how carefully they were optimised.

On shared hosting, a heavy map can cause stutter when other workloads on the same host get busy. A server with dedicated CPU resources keeps tick rate steadier, which players notice as smoother movement and fewer rubber band moments. If you plan to run a large curated map with a full player list, it is worth giving the server reserved cores and generous memory from the start.

Running Unturned on your own server

Unturned server files are installed with SteamCMD, Valve's command line tool for dedicated servers. On Linux you install SteamCMD, log in anonymously, download the Unturned dedicated server app, then launch it with the server name you want. On Windows the process is the same, and you can manage files through a normal desktop over Remote Desktop.

Whichever operating system you choose, open the game port in the server firewall, run the server under a process manager or as a service so it restarts after a reboot, and schedule regular backups of the Servers folder. Our guide on game server hosting covers firewalls, backups and choosing a location, and the Windows or Linux guide helps you decide which system suits you.

Choosing a server for your Unturned world

For a small group on an official map, a modest server is fine. For a public server, large Workshop maps or many plugins, choose dedicated CPU resources so the game is not competing with neighbours. You can buy a dedicated server with reserved cores, or compare with Linux VPS plans for lighter worlds.

Every rdp-buy.com server includes full root or administrator access, so you can install SteamCMD and edit Commands.dat freely, plus a dedicated IPv4 address your players can save. Pick from 33 server locations close to your players, choose monthly, half-yearly or yearly billing, and get help from 24/7 support. Servers are ready in minutes, so your new map can be live tonight.

Frequently asked questions