Starbound does not have an official dedicated-server hardware specification. The 2 GB RAM, 3 GB storage and processor figures on the Steam listing describe the game client, not a persistent server. A dedicated host also needs memory for the operating system, world saves, logs, updates and backups, plus enough CPU and network headroom for the way your players actually explore, fight, build and travel.
The dependable way to size a server is to measure the exact Starbound version, world, mod set and player workload. Use the published client figures as a floor for installing the software, then observe peak memory, per-core CPU use, save-time delays, traffic and storage growth before committing to a player limit.
What are Starbound’s official system requirements?
Chucklefish’s Steam listing publishes client requirements for Windows, Linux and macOS. It does not separate a dedicated-server profile, so these numbers should not be presented as a promise that a server will support a particular number of players.
| Platform | Minimum processor | Minimum RAM | Minimum storage | Recommended processor | Recommended RAM | Recommended storage |
|---|---|---|---|---|---|---|
| Windows or Linux | Core 2 Duo | 2 GB | 3 GB | Core i3 | 4 GB | 4 GB |
| macOS | 64-bit Intel CPU | 2 GB | 3 GB | Not stated separately | 4 GB | 4 GB |
The listing is associated with Starbound’s 2016 release; it does not state a separate year in which the requirements were published. The storage and memory figures are for the client installation. A server’s world data, logs, temporary files, update packages and independent backups can make its disk footprint larger over time.
Is 2 GB of RAM enough for a Starbound dedicated server?
Two gigabytes is a client minimum, not a reliable dedicated-server allocation. A server may start with that amount, but the operating system and background services leave less memory for simulation and saves, and a persistent world needs room for short-lived peaks.
What memory pressure looks like
- Paging or swap activity increases while players are online.
- The server’s resident memory keeps growing instead of settling after startup.
- Saves take longer, joins pause, or interactions become delayed during busy scenes.
- Other services on the machine compete for memory and cause inconsistent performance.
There is no authoritative current RAM-per-player formula. Player count alone is not enough: exploration, combat, construction, travel, world generation, mods and save operations can all change the working set. Treat 4 GB as the Steam listing’s recommended client figure, not as a server recommendation.
How much CPU does a Starbound server need?
The published Core 2 Duo and Core i3 figures are client requirements, and no official CPU-per-player specification exists for a dedicated server. A modern processor with strong single-core performance can be more useful than simply adding memory when simulation work becomes concentrated on one core.
Signs that the processor is the bottleneck
- One logical core stays near saturation while total CPU usage appears moderate.
- Actions, chat, joins or movement are delayed during combat, travel or other simulation-heavy activity.
- Adding memory does not change the delay because the process cannot complete its update work quickly enough.
Use top or htop on Linux and Task Manager on Windows to observe the server process. Record per-core utilization, not only the machine-wide average, and compare it with the moments when players report delayed interactions.
How should I size RAM and CPU for my player group?
Because Starbound has no tested universal capacity table, size the machine from measurements rather than a guessed “RAM per player” rule. The following procedure gives you a repeatable baseline.
- Start with the real installation. Use the server version, operating system, world and mod list that players will actually use. Include any client-required content.
- Capture an idle baseline. After the dedicated process settles, record memory, per-core CPU use, disk activity and network traffic. A graph over time is more informative than one reading.
- Add players gradually. Bring in the expected group in stages instead of connecting everyone at once. Note the process memory and CPU at each stage.
- Exercise representative workloads. Test exploration, combat, construction and travel. Include busy scenes, simultaneous movement, joins and saves rather than only an empty starting area.
- Record peaks and symptoms. Mark the highest memory and per-core CPU readings, save duration, interaction or tick delay, and upload/download peaks.
- Reserve headroom. Keep capacity for the operating system, updates, backups and short-lived spikes. Set the reserve from your measurements and tolerance for lag, not from an invented percentage.
- Repeat after changes. Re-run the test when you change the server version, world, mods, operating system or configured player limit.
This process answers “how many players can my server support?” for your particular workload. It does not turn the result into a guarantee for a different world, mod collection or hosting environment.
How much storage should a Starbound server have?
Reserve more than the 3 GB minimum or 4 GB recommended client figures. A persistent server stores universe and character data, logs, updates and working files, and a safe backup plan requires space outside the live installation.
What to include in the storage budget
- Live server files: the executable, configuration and installed content.
- Universe and player data: visited worlds and ongoing progress can grow as the group explores.
- Logs and crash information: useful for troubleshooting but capable of accumulating unnoticed.
- Update and temporary space: leave room for downloads and replacement files during maintenance.
- Independent backups: keep copies on a different storage location from the live world so a disk failure or mistaken deletion does not remove both.
No universal server-disk number has been established. Monitor actual growth, set an alert before the volume fills, and decide how many backup generations your recovery policy requires. Chucklefish’s support guidance warns that resetting the universe removes visited worlds, so make a backup before any reset operation.
How much bandwidth does a Starbound server need?
There is no official bandwidth-per-player figure. Measure upload and download during normal play and worst-case activity, then leave room for other traffic on the connection. A host that looks fine at idle can saturate its upstream when several players join, move through active areas or trigger saves at the same time.
Network measurements that matter
- Peak upload and download while the expected number of players is connected.
- Short spikes during joins, busy scenes and simultaneous movement.
- Whether other household or server traffic competes with the game process.
- Connection delay reported by players when the host’s CPU and memory are otherwise healthy.
Record the peaks during the same workload used for CPU and RAM testing. If upload is saturated, reducing memory or changing the processor will not solve the network queue; you need more upstream capacity or less competing traffic.
What port does a Starbound server use?
The documented default is port 21025. Community guides reported by iTechGuides in 2026 disagree about whether the rule should be TCP only or TCP and UDP, so inspect the configuration shipped with your installed version before opening a firewall or router rule.
- Check the server configuration for the current listening port and protocol.
- Allow that protocol and port in the host operating system’s firewall.
- If the host is behind a router, forward the same rule to the machine’s private IP address.
- Reserve the host’s private address so the forwarding target does not change after a reboot.
- Test from another device on the local network, then from an external connection.
- If local access works but outside players cannot connect, investigate double NAT or carrier-grade NAT with the internet provider.
Do not assume that a successful local test proves internet reachability. External testing checks the router, firewall, public address and provider-level NAT as well as the game process.
Does maxPlayers tell me how powerful the server must be?
No. The multiplayer guide cited by iTechGuides lists a default maxPlayers value of 8, but that is a session limit, not a benchmark showing that eight players will run smoothly on a particular machine.
Use the setting as a configuration choice after measuring the workload. If your test shows delayed saves or saturated CPU with fewer players, lower the limit or move to stronger hardware; raising the value does not create capacity.
Should I host Starbound myself or use a managed service?
The right option depends on whether you value control or convenience. Compare persistence while the usual host is away, router and firewall administration, maintenance, mod and file control, backups, measured player capacity, network quality and total cost.
| Hosting approach | Best fit | Advantages | Responsibilities and limits |
|---|---|---|---|
| Player-hosted session | Occasional small-group play when the host is normally present | Simple setup and no separate persistent machine | The world is unavailable when the host’s game closes; capacity depends on the host PC and connection |
| Self-managed dedicated machine | Persistent play with direct control of files and mods | Full control over configuration, worlds, monitoring and backups | You maintain a 64-bit system, firewall, router, updates, storage and recovery plan |
| Managed hosting | Persistence without maintaining home hardware or exposing a home router | Provider handles the machine and network environment | Verify Starbound version, mod support, backups, player limits, uptime and renewal cost directly; no provider is established as universally best |
For a managed service, ask how backups are created and restored, whether you can download world files, which mod versions are supported, and what happens when the subscription or renewal term ends. For self-hosting, budget administrative time as well as hardware and internet costs.
How do mods change Starbound server requirements?
Mods can alter simulation work, memory use, save behavior and connection requirements. A server that is stable in an unmodified test may behave differently with the exact collection your players install.
A reliable mod-testing sequence
- Back up the universe and player data before changing the mod set.
- Reproduce the problem with all mods enabled and note when it occurs.
- Disable all mods and test again to determine whether the base server is stable.
- Enable one suspected mod and test the same workload.
- Add the remaining mods in small groups, using the exact versions that clients will connect with.
- Keep the working list and configuration with the backup so you can restore a known-good state.
Chucklefish’s support FAQ specifically recommends disabling all mods to identify a factor, then enabling one test mod that may be causing the error. Mod isolation is also useful for capacity testing because it shows whether a memory or CPU peak belongs to the base server or an added feature.
What should I monitor after the server goes live?
Keep a time-based record instead of relying on occasional snapshots. The useful signals are the server process’s memory, per-core CPU utilization, save-time latency, upload and download peaks, disk growth and player-visible delays.
- Review graphs after busy sessions and scheduled saves.
- Investigate sustained paging, steadily growing resident memory or a disk volume approaching full capacity.
- Correlate reports of delayed interactions with CPU, memory and network timestamps.
- Keep update files and backups from consuming the same free space needed by the live world.
- Repeat the capacity test after any version, world, mod, operating-system or player-limit change.
What is a practical pre-launch checklist?
Before inviting the full group, verify each item below on the machine and network you will actually use.
- Use a 64-bit operating system for a self-managed dedicated setup.
- Install the intended Starbound version and exact mod list.
- Measure idle and loaded memory, per-core CPU, network peaks and storage growth.
- Test exploration, combat, construction, travel, joins and saves with the expected players.
- Leave measured reserve for the operating system, maintenance and spikes.
- Confirm the configured port, firewall rule, router forwarding and stable private IP.
- Test both local and external connections, including a double-NAT or carrier-grade-NAT check when needed.
- Automate or schedule backups outside the live storage location and verify that a backup can be restored.
- Set the player limit to the number your workload test supports, not simply the default of 8.
Frequently Asked Questions
Can a Starbound dedicated server run on a 32-bit operating system?
A self-managed setup should use a 64-bit system, as required by the practical hosting guidance for maintaining the server. The client listing’s platform rows do not establish a separate 32-bit dedicated-server exception.
What happens if I reset the Starbound universe?
Resetting removes the worlds that players have visited. Make a backup first so you can restore the previous universe if the reset was unintended or causes data loss.
Why can one CPU core be overloaded while total CPU usage looks low?
A simulation task may concentrate on one core, so an average across all cores can hide the bottleneck. Check per-core graphs and compare the busiest core with the moment players report delayed actions.
How can I determine whether a mod caused a server error?
Reproduce the issue with every mod disabled, then enable one suspected mod and repeat the same test. Continue adding mods individually or in small groups, while keeping a backup of the universe and the last known-good configuration.