Satisfactory Server Requirements: CPU, RAM, Disk & Network
Satisfactory server requirements cover x86-64, memory, disk and open ports. See the published guidance, current Linux depot size and what remains unknown.
You will need
- A PC copy of Satisfactory on Steam or Epic for each player
Satisfactory server requirements are lighter than the requirements for playing the game: the dedicated server needs a 64-bit x86-64 machine, community guidance starts at 8 GB RAM, and the current Linux game depot is about 2.78 GB installed. That depot is only the game files, not a complete disk budget. These requirements are for PC players using Steam or Epic; those versions can join the same dedicated server, while console players cannot. Here is what to check before you leave a machine running for your factory.
Choose an x86-64 CPU with a fast core#
The server build targets 64-bit x86-64 processors from Intel or AMD. There is no native 32-bit or ARM server build, so an old 32-bit system or a Raspberry Pi is not a supported starting point. The dedicated-server requirements reference describes its CPU figures as community recommendations, not guaranteed minimums.
The same reference recommends roughly a recent Intel Core i5-3570 or AMD Ryzen 5 3600 class processor or better. It also says the server favors high single-thread performance even though it uses multiple cores. Treat that as a way to screen a candidate PC, not a promise that a named CPU will run every late-game factory smoothly. A save with many machines, vehicles and production lines can behave differently from a new world.
If the server will share a computer with the game client, both workloads compete for processor time. A machine that meets the server guidance on paper may feel different when you also play on it, run other services, or use power-saving settings. Check CPU use and server tick behavior with your own save before deciding that the processor is the only bottleneck. This guide does not include a controlled CPU benchmark.
Plan memory around the save, not a player formula#
The community guidance starts at 8 GB of RAM and suggests 16 GB for a large save or more than four players. Those two figures are useful planning markers, not hard limits, a player-slot rule or an allocation formula. The source does not define exactly what counts as a large factory, and a player count alone cannot describe the world’s simulation load.
For a small group starting a new world, 8 GB is the published baseline to evaluate. If the save has grown substantially or more than four players are expected, plan around the 16 GB recommendation and leave memory for the operating system and any other processes. Do not assume that adding one friend always requires a fixed number of gigabytes. The server’s actual use is more useful than a generic player chart.
If memory is your main question, our guide explains how much RAM a rented server needs. It covers plan sizing and the difference between official guidance and host estimates; this page stays focused on a machine you supply yourself. Whichever machine you choose, watch its memory use during normal play and autosaves as your factory expands.
Budget disk space beyond the server download#
The Linux server depot is about 2.78 GB installed according to the SteamCMD app manifest checked on 12 October 2026. The manifest reports approximately 1.50 GB to download and 2.78 GB installed, using decimal units. That is the game depot alone. It is not a claim that a Linux computer with 2.78 GB free can host a server.
Leave room for the operating system, temporary files while updates are applied, and your world saves. Backups need additional space too, especially if you keep several copies or store them on the same machine. Save size depends on the world and its history; no universal save allocation or current total disk minimum was verified for this guide. A growing save can require more room than the initial server download.
The wiki’s Linux estimate includes a typical operating system and an older approximate game-file size, so it measures a different bundle from the current depot manifest. Do not add those two figures together or present the older estimate as a current exact requirement. The SteamCMD app manifest reports the current depot size; it can change when the game updates.
Open the current game and messaging ports#
The dedicated server needs three protocol-and-port rules by default. Allow each one in the host firewall. If the server sits behind a home router, forward the same rules to the server’s local IP address as well.
| Port | Protocol | Purpose |
|---|---|---|
7777 |
UDP | Game traffic |
7777 |
TCP | Server traffic and the HTTPS management API |
8888 |
TCP | Reliable messaging |
These are separate rules even though two use port 7777: TCP and UDP are different network protocols. Opening only UDP does not cover the TCP connection. Ports 15000 and 15777 appear in older guides but are obsolete for the current dedicated-server setup. Check the current port and firewall reference before changing a custom configuration, because a game update can change defaults.
On a home router, a forwarding rule must point to the server’s current local address. If that address changes, the rule can point to another device and friends may lose access. The dedicated-server installation path and the rest of the connection steps are in the complete self-hosting path. This requirements page does not replace that setup walkthrough.
Check connection quality without guessing a bandwidth number#
Players need a stable route to the server, and the firewall rules must be reachable from outside your local network. The reference material recommends broadband but does not publish a trustworthy upload Mbps requirement per player, a maximum player count based on bandwidth, or a latency target. No defensible per-player throughput benchmark was found for this article.
That means a number such as “X Mbps for each friend” would be false precision. Your upload capacity, other household traffic, router behavior and the server’s workload all affect the experience. Test the actual connection with the players who will join, then check for packet loss or a saturated uplink if they report interruptions. A successful port check can show that a service is reachable; it does not prove that the game session will remain stable under load.
If you cannot forward ports through your router, ask the network administrator or use a supported VPN arrangement that every player can access. Do not expose the server’s admin credentials to make the network test easier. The game’s management interface uses HTTPS on TCP 7777 by default, so treat that access as administrative access rather than an ordinary public game port.
Separate server hardware from gaming-PC graphics requirements#
The dedicated server runs the simulation and session; players’ PCs render the factory. The dedicated-server requirements page does not publish a separate graphics-card model or GPU memory requirement. A GPU listed on a client requirements page is for playing the game locally and should not be copied into a server checklist as a server requirement.
For a headless machine, check the operating system, x86-64 CPU, memory, storage and network access described above. If that same computer will also run Satisfactory’s 3D client, use the game client’s current requirements for the playing workload and account for its additional memory and graphics use. The combined setup has different needs from a headless server; no tested shared-machine performance claim is made here.
Likewise, the server’s OS and CPU guidance does not guarantee a certain factory size, frame rate or tick rate. There is no verified minimum save size, universal “players per core” ratio, or number of buildings that a particular processor can sustain. Start from the documented guidance, monitor the world you actually run and adjust based on its behavior.
Decide whether to run your own always-on machine#
Self-hosting makes sense if you already have a suitable x86-64 computer, can keep it on when the group wants to play, and are comfortable managing its firewall, updates and saves. You control the machine and avoid renting a separate server, but you are also responsible for network access and keeping enough disk space for the world and recovery copies.
If you prefer not to leave a PC running or manage router rules, managed hosting is another option for a compatible group. Game Hosting’s Satisfactory service is for PC players on Steam and Epic; console players cannot connect to that dedicated server. Its current plans list 8, 12 or 16 GB memory and a Ryzen 9 9900X with four threads. Those are published plan specifications, not a benchmark or a promise that every factory will perform the same way. See the Satisfactory server options after confirming that your players use the compatible PC versions.
For self-hosting, use the full setup walkthrough after your hardware clears this checklist. For a rented plan, compare its included memory and CPU details against the world you expect to run, then check real usage as your factory grows.
Quick answers
What are the minimum requirements for a Satisfactory dedicated server?
The community-maintained server guide recommends a 64-bit x86-64 CPU and 8 GB RAM, with 16 GB suggested for large saves or more than four players. These are planning recommendations, not a guarantee for every factory.
How much disk space does a Satisfactory server need?
The Linux game depot was about 2.78 GB installed on 12 October 2026. Add space for the operating system, update staging, saves and backups; no fixed total machine minimum was verified.
Does a Satisfactory dedicated server need a graphics card?
The dedicated-server requirements reference does not publish a separate GPU requirement. Client graphics recommendations describe the game you play, not a verified server GPU specification.
What ports does a Satisfactory server use?
The current defaults are 7777 UDP, 7777 TCP and 8888 TCP. Allow each protocol through the server firewall and, for a home server, forward it through the router.