Hosting a server in Unturned gives you control over rules, performance, and the player community, and this evergreen guide explains how to do it reliably on your machine or a remote host. Whether you want a small private session with friends or a public zone for the community, understanding server fundamentals makes your world run smoother with fewer interruptions and better uptime. This overview covers installation, configuration, port setup, and ongoing maintenance so you can launch and manage a stable Unturned server that matches your desired play style.
Unturned Server Hosting Essentials
Unturned server hosting relies on the same core concepts as many multiplayer games: a server process that holds the world state and synchronizes events to clients. You can host directly from your PC or use a dedicated machine or cloud provider for greater stability. Key concepts to grasp include the dedicated server build, command-line arguments, configuration files, and the balance between performance, player count, and simulation frequency. Understanding these basics reduces troubleshooting time and clarifies decisions about hardware, ports, and networking.
Server vs Client Roles
When you host, your machine becomes the server, authoritative for position, inventory, and zombie behavior, while clients send inputs and receive state updates. A dedicated Unturned server uses a headless build that does not require a full game client, reducing overhead and improving consistency. Knowing who is authoritative helps you avoid confusion about why clients see different zombie behavior or item spawns, and it guides decisions about port forwarding and firewall rules.
Install and Prepare the Server Files
To host an Unturned server, first acquire the server files from the official Unity build or through the Steam Console Client, depending on your platform and desired control level. For Windows, you typically download the server executable, place it in a dedicated folder, and ensure required runtime libraries are present. Organizing your configuration files, maps, and mods in predictable locations makes future updates and backups easier, especially when you manage multiple server instances.
Select Map and Difficulty Presets
- Choose a map that fits your intended player count and style, such as smaller maps for low-population sessions or larger maps for exploration-focused groups.
- Set difficulty presets that match your community’s expectations, including zombie health, damage, resource rates, and loot scaling.
- Test combinations locally before publishing to ensure performance and challenge levels align with your server goals.
Open Necessary Ports and Configure Networking
Proper networking is essential for external players to reach your server. Unturned typically uses one query port for server listings and one game port for actual player connections; most setups require port forwarding on your router and adjustments to any software firewall. NAT type, UPnP behavior, and whether you use IPv4 or IPv6 can affect connectivity, so documenting your settings simplifies future troubleshooting.
Firewall and Router Settings Quick Reference
| Port | Protocol | Purpose | Notes |
|---|---|---|---|
| 28015 | TCP/UDP | Game traffic | Adjust if occupied; forward both TCP and UDP |
| 28016 | TCP/UDP | Query/steamworks | Used for server listings; can be omitted for private servers |
Test Connectivity
Use online port checkers and in-game server browser tests to confirm your ports are correctly forwarded. If players report failed connections, verify that your external IP has not changed, that port forwarding rules are active, and that no conflicting applications are binding to the same ports.
Server Configuration and Whitelisting
Configuration files control player limits, passwords, auto-updates, and behavior settings such as loot tables and zombie spawn density. A basic server config balances fairness and challenge, while whitelisting gives you precise control over who can join. Combining whitelisting with a modest max player count keeps performance predictable and reduces chaotic lag during peak moments.
Key Config Options at a Glance
| Setting | Typical Value | Effect |
|---|---|---|
| Max Players | \n15–40 (varies by map) | \nHigher values increase RAM and CPU demand | \n
| Server Password | \nOptional | \nSimple access control; not encryption | \n
| Whitelist | \nSteam3 IDs or filenames | \nOnly listed players can join when whitelist enforcement is active | \n
| Auto Update | \nEnabled or Disabled | \nUpdates before restart reduce manual work but may affect mod compatibility | \n
Basic Whitelist Workflow
- Obtain each player’s Steam3 ID via a trusted lookup tool.
- Append IDs to the whitelist config file, one per line.
- Enable enforcement in server settings and restart the server.
- Notify whitelisted players to join with the correct credentials.
Performance Tuning and Crash Prevention
Performance issues often arise from insufficient RAM, heavy mods, or aggressive zombie settings. Monitor memory usage, limit background processes, and consider incremental changes so you can identify what improves stability. Regular backups of your world files protect against corruption, and scheduled restarts can clear minor memory leaks. If you rely on mods, test updates on a staging copy before applying them to your main server.
Stability Checklist
- Allocate sufficient RAM to the server process within your OS limits.
- Use a consistent tick rate and avoid frequent config churn.
- Schedule off-peak backups of the save world directory.
- Log major changes so you can roll back if an update causes issues.
- Watch server console for repeated errors that precede crashes.
Launch, Monitor, and Maintain
Once your server is configured and ports are open, start the server process using the recommended command-line arguments, then verify it appears in the in-game server browser. Use logging tools and query commands to watch for cheaters, high latency, or resource spikes. Consistent maintenance—backups, mod updates, and periodic restarts—keeps the experience stable and predictable over time.
Basic Launch and Monitor Routine
- Start the server from your chosen directory and confirm it binds to the correct ports.
- Check the console for initialization errors and confirm player count.
- Set up simple monitoring, such as log timestamps and automated backup scripts.
- Communicate rules and expected performance to your community to manage expectations.
Summary and Next Steps
Hosting an Unturned server successfully hinges on clear configuration, open ports, sensible performance limits, and regular maintenance. By following these evergreen steps, you create a reliable space where friends or the broader community can enjoy consistent gameplay without frequent disruptions. As you gain experience, you can refine settings, add monitoring dashboards, and scale to larger player counts while keeping the core fundamentals intact.
FAQ
Reader questions
Can I host Unturned for friends without port forwarding?
Yes, you can use peer-to-peer-like invites or third-party relay tools for local networks, but for public internet hosting, port forwarding or a proxy with proper UDP configuration is necessary for reliable connections.
Will mods break my server or cause crashes?
Mods can increase crash risk if they are outdated, incompatible, or poorly optimized. Test mods on a copy of your server, update them in a controlled order, and keep backups so you can revert changes quickly.
How often should I back up my world?
For active servers, schedule backups at least daily or after major events. More frequent snapshots are helpful during events or heavy mod changes so you can restore a stable state if something goes wrong.