Short answer: Barotrauma has no single, officially published dedicated-server specification. For a small vanilla server on a machine that is not running the game client, 2 GB of RAM available to the server is a sensible starting point. Larger crews, workshop-heavy mod sets, persistent campaigns, or a host that also plays the game need more headroom. CPU consistency, SSD space, operating-system overhead and network reliability matter as much as headline capacity.
Steam lists the complete game at a dual-core 2.4 GHz CPU, 4 GB RAM and 2 GB available storage minimum, with a quad-core 3.0 GHz CPU and 8 GB RAM recommended; those figures are not dedicated-server benchmarks (Steam store listing). A developer wrote on April 30, 2020 that the server uses a few hundred megabytes and that 1–2 GB should generally be enough, but that is dated guidance rather than a guarantee for current versions or modded campaigns (developer discussion).
How much RAM does a Barotrauma dedicated server need?
A small, unmodded server should start with at least 2 GB of RAM available to the server process, while keeping additional memory for the operating system and background services. There is no current official tier by player count. The best-known numeric guidance is Dynamoon’s April 30, 2020 statement that “The server tends to use a few hundred MB, so 1–2 GB should be more than enough.” Treat that as an observation from 2020, not a promise for version 1.13.4.0, large crews or heavily modded campaigns.
| Use case | Practical starting allocation | How to interpret it |
|---|---|---|
| Small vanilla group, dedicated host | 2 GB available to the server | Reasonable starting point when the machine runs little else; observe a complete play session before committing. |
| More players, active creatures or large submarines | More than the small-group baseline | Add headroom rather than treating 2 GB as a ceiling. The project does not publish a numeric benchmark for this tier. |
| Workshop-heavy or script-intensive campaign | More than the small-group baseline | Mods and persistent saves can increase working data and loading activity; size from measurements on your actual mod list. |
| Host also running the full game client | Reserve memory for both applications | The server estimate describes server usage, not the combined footprint of a game client, operating system and server. |
Check memory during a busy mission, a save, a crew change and a server restart. A host that is constantly swapping to disk can appear to work while producing stalls and slow joins. Leave enough unused RAM for the operating system, update tools, logging and any management panel; “available to the server” is not the same as total installed memory.
What CPU do I need for a Barotrauma dedicated server?
Choose a modern multi-core processor with strong sustained per-core performance. Simulation work, creature activity, submarine logic and many mod scripts can make one busy core more important than a large core count. Clock speed alone is not a guarantee, and no official dedicated-server CPU benchmark defines a required model.
| Reference | CPU figure | What it actually means |
|---|---|---|
| Steam minimum for the full game | Dual-core 2.4 GHz | Valve’s 2023 listing for running the game; it is not a dedicated-server measurement. |
| Steam recommended for the full game | Quad-core 3.0 GHz | A useful general reference for a modern host, but still not a promise about server capacity. |
| Practical dedicated hosting choice | Modern multi-core CPU with consistent per-core performance | Prefer predictable sustained performance over an old processor advertised with many slow cores. |
When comparing machines, ask whether the provider’s CPU is shared and whether its advertised frequency is a short boost rather than a sustained level. A lightly loaded physical or virtual core can feel better than a higher-numbered but oversubscribed option. If the host also runs the client, voice software or other services, those workloads compete with the simulation and require additional CPU margin.
How much storage does a Barotrauma server use?
The official hosting documentation does not publish a dedicated-server capacity target. Steam’s 2 GB available-storage figure applies to the complete game listing, not to every server installation, workshop item, save and log you may accumulate. Plan persistent storage for the installation plus growth, rather than allocating exactly the store listing number.
- Game files: the dedicated executable or SteamCMD installation and any dependencies.
- Workshop and mod content: downloaded packages can add substantially to the base install, especially when several campaigns use different collections.
- World and campaign saves: retain working space for new saves and backups instead of filling the volume.
- Logs and crash data: keep room for troubleshooting files and rotate or archive them deliberately.
- Updates and temporary files: patching may need free space while new files are downloaded and unpacked.
An SSD is a sensible choice for update speed, save access and recovery operations, but the project does not state that a particular drive type is mandatory. Capacity, persistent availability and reliable backups matter more than a benchmark label.
Can I run a Barotrauma server on a VPS or old PC?
Yes, either can work if it supports a documented Windows or Linux setup, provides persistent storage and allows the required UDP traffic. The deciding factors are available resources after the operating system, sustained CPU performance, network reachability, remote administration and uptime—not whether the machine is called a VPS or a home computer.
| Host type | Advantages | Checks before choosing |
|---|---|---|
| VPS | Datacenter uptime, remote access and predictable provisioning | Confirm game-server policies, CPU sharing, location and latency, firewall controls, backups and persistent SSD storage. |
| Old or spare PC | No recurring hosting bill and direct hardware control | Verify that it can run a supported OS, stay powered, accept inbound traffic and maintain adequate cooling, storage and broadband reliability. |
| Desktop also used for play | No second machine required | Budget RAM and CPU for the client and server together; updates, overlays and other applications can compete for resources. |
Test from a different internet connection, not only from the host itself. A local connection can succeed even when outside players are blocked by a router, firewall or provider-level restriction.
What software and operating-system support is documented?
The project’s official dedicated-server guide documents two routes: the built-in DedicatedServer.exe application and installation through SteamCMD. It covers Windows and Linux, with distribution-specific dependency notes.
Windows and the built-in server
On Windows, the built-in dedicated application is the straightforward route when the game files are already available. Keep the server data and configuration directories on persistent storage, and use the documented locations for permissions and files rather than placing them in a temporary directory.
Linux and SteamCMD
Linux hosting is supported, but package requirements vary by distribution. The guide notes that Ubuntu 22.04 may require an older OpenSSL library, while Ubuntu 24.04 appears to work out of the box. These statements can change as the game and distributions update, so verify the current guide and package requirements at deployment time.
The same page identifies its hosting data as last updated for version 0.18.15.0 while displaying game version 1.13.4.0. That mismatch is a warning to recheck instructions after game or distribution updates rather than assuming every command and dependency remains current.
Which network and firewall settings are required?
An internet-accessible server needs inbound UDP forwarding and matching firewall rules. The official guide’s default ports are:
- UDP 27015: game traffic.
- UDP 27016: Steam query traffic.
Forward those ports from the router to the host’s local address, permit them in the host firewall and ensure no second service is already using them. If you choose different ports, apply the same values consistently in the server configuration, router and firewall. Query visibility and player connections can fail independently, so test both from outside the local network.
How should I size a server before buying hardware?
Use a measured, staged approach instead of treating one specification as universal.
- Define the workload. Record the expected concurrent players, vanilla or modded status, campaign persistence, large-submarine use and whether the machine also runs a client.
- Select a conservative starting host. For a small vanilla group, make at least 2 GB available to the server and choose a modern multi-core CPU. Keep unused RAM and disk space for the operating system and data growth.
- Install through a documented path. Use
DedicatedServer.exeor SteamCMD on a supported Windows or Linux setup, following the current official guide. - Configure persistence. Confirm that
serversettings.xml, saves, workshop content and logs are stored on the intended persistent volume and included in backups. - Open and test the network. Forward UDP 27015 and 27016, apply firewall rules, then connect from an external network.
- Exercise a full session. Test loading, joining, a busy mission, saving, changing crews and restarting. Watch RAM, CPU saturation, disk space and latency while those events occur.
- Increase capacity from evidence. Add RAM when the host approaches its available limit or begins swapping; move to stronger per-core CPU capacity when simulation time or tick responsiveness degrades; expand storage when saves, mods, logs or updates consume the reserve.
What should I compare when choosing between hosts?
Compare the whole operating environment, not just advertised RAM or core count.
| Comparison axis | Why it matters | Questions to ask |
|---|---|---|
| Sustained per-core CPU performance | Busy simulation work can bottleneck one core. | Is the CPU shared, and is the listed frequency sustainable? |
| RAM available after the OS | Total installed memory overstates what the server can use. | How much remains free at idle and during a campaign save? |
| SSD capacity and I/O | Updates, saves, mods and logs need persistent space. | Is storage persistent, and are snapshots or backups available? |
| Latency and reliability | Players feel network delay even when CPU usage is low. | Where is the host located, and what uptime or traffic limits apply? |
| Administration | Servers need updates, restarts and recovery. | Can you reach the console remotely and restore a backup? |
| Total cost | A low monthly price can hide limits or backup charges. | Are bandwidth, storage growth, snapshots and support included? |
What are the common sizing and setup mistakes?
Treating Steam’s requirements as server requirements
The 4 GB minimum and 8 GB recommended figures are for the complete game listing. Use them as broad context, not as a measured dedicated-server threshold.
Allocating every gigabyte to the process
A server cannot use memory that the operating system, update process or management tools need. Leave operating headroom and watch actual peak usage during saves and restarts.
Ignoring mods and campaign growth
A configuration that works for a short vanilla session may not suit a long campaign with workshop content, active creatures and large submarines. Re-evaluate after adding a major mod collection or increasing the player roster.
Focusing on storage capacity but not persistence
A large temporary disk does not protect saves. Use persistent storage, keep backups and make sure logs and workshop files cannot silently fill the volume.
Opening one port and assuming the server is reachable
Game traffic and Steam query traffic use separate default UDP ports. Check forwarding and firewall rules for both, then test from outside the host’s network.
What is the practical recommendation?
For a small vanilla group, begin with a modern multi-core host that can spare 2 GB for the server, persistent SSD storage with room beyond the installation, and reliable access to UDP 27015 and 27016. Move up in RAM or CPU performance when measurements from a real campaign show pressure. Because the only named memory estimate is from 2020 and the official guide’s version notes are not fully current, document your own peak usage and recheck the hosting guide whenever the game or operating system changes.
Frequently Asked Questions
Does the 1–2 GB estimate include the operating system?
No explicit combined-machine figure is given. Read the developer’s statement as an estimate for the server workload itself, then reserve separate memory for the OS, updates, monitoring and any other services on the host.
Should I prioritize more CPU cores or a faster core?
For a lightly loaded server, consistent per-core performance is usually the safer first priority because simulation work can concentrate on a busy thread. Additional cores still help when the machine also runs the game client, management tools or several background tasks.
How can I estimate backup storage when no capacity target is published?
Measure the size of your saves, logs and workshop data after a representative campaign, then keep multiple generations of backups with room for updates. Recheck the total after adding a large mod collection or starting a new long-term campaign.
What should I verify before moving a home server to a VPS?
Confirm that the provider permits game servers, offers persistent storage, exposes the needed firewall controls and places the machine near your players. Test an external connection and check how snapshots, reboots and support are handled before migrating an active campaign.