Running your own Satisfactory factory means treating the server like another production line: undersize it and everything chokes. Whether you’re hosting a two-person co-op base or a sprawling late-game megafactory, getting the RAM, CPU, and port configuration right is what separates a smooth 60-tick world from a stuttering, unjoinable mess. This guide breaks down the official dedicated server requirements, clears up the port confusion that lingers from older versions, and helps you pick a hosting plan sized to your actual player count.
The official hardware requirements
According to the official Satisfactory wiki, the dedicated server has a fairly modest baseline but scales hard with save size and player count. The published figures are:
- Minimum RAM: 8GB
- Recommended RAM: 16GB for larger saves or hosting more than 4 players
- CPU: The server uses multiple cores but heavily favors high single-core performance. The wiki notes that anything with a single-thread rating of 2000 or higher should work.
- Architecture: x86-64 only (no 32-bit, no ARM).
- Storage: SSD strongly preferred — save autosaves can stall a busy world on slow disks.
The single biggest misconception is that Satisfactory is a “more cores = better” game. It isn’t. The simulation runs on a tick that benefits far more from raw clock speed and per-core throughput than from extra threads. A high-clock CPU with a strong single-thread rating will outperform a many-core chip with weaker per-core speed. When choosing a host, prioritize providers running modern high-frequency CPUs over those advertising raw core counts.
12GB vs 16GB RAM: which do you actually need?
The official minimum is 8GB, but in practice that’s only comfortable for a small base and a couple of players early in a save. RAM usage in Satisfactory grows with the number of placed buildings, belts, and active machines — not just player count. A heavily built world in the late game can consume far more than a fresh save.
That’s why hosts commonly offer plans in 12GB and 16GB tiers. A 12GB plan is a sensible middle ground for a small group on a maturing save, leaving headroom over the 8GB floor. The official recommendation jumps to 16GB once you’re hosting more than 4 players or carrying a large save file, so if you’re planning a long-running world or a bigger crew, size up front rather than fighting out-of-memory crashes later. Note these exact thresholds are version-dependent and tied to your build size — a giant save can outgrow any tier.
Ports: what changed, and what you forward today
This is where a lot of outdated guides will lead you astray. Older versions of Satisfactory used port 15777 (query) and port 15000 (beacon). As of Patch 1.0, those ports are no longer used. Do not forward them on current servers — they do nothing.
The current setup is simpler. The server uses port 7777 on both TCP and UDP, plus a separate reliable-messaging port. Here’s the official breakdown:
| Port | Protocol | Purpose | Status |
|---|---|---|---|
| 7777 | UDP | Game traffic, Lightweight Query API | Current — required |
| 7777 | TCP | Server traffic, HTTPS API | Current — required |
| 8888 | TCP | Game traffic, reliable messaging | Current — required |
| 15777 | UDP | Legacy query port | Removed in Patch 1.0 |
| 15000 | UDP | Legacy beacon port | Removed in Patch 1.0 |
Two important configuration notes from the wiki: port 7777 does not support redirection — the internal and external port numbers must match. The reliable-messaging port (default 8888) can be remapped using the -ExternalReliablePort launch parameter, which matters if you run multiple servers on one machine and need to avoid a collision.
Port forwarding and firewall setup
If you self-host on home hardware, the server has to be reachable from the internet. That means two layers have to cooperate:
- Router port forwarding: Forward 7777 (TCP and UDP) and 8888 (TCP) to your server machine’s local IP.
- Local firewall: Allow the server process to listen on those same ports — Windows Firewall or your Linux firewall will block them by default.
This is the most common reason a server won’t show up or friends can’t connect — see our server not showing up / can’t join fixes for a full diagnostic walkthrough. The advantage of managed hosting is that this entire step disappears: ports are opened and routed for you, with no router config or static-IP headaches. Our Satisfactory server configuration docs walk through the panel settings step by step.
Sizing a hosting plan by player count
Satisfactory defaults to a small player cap, but you can raise it (see our guide on changing max players). Use this as a rough starting point, remembering that save/build size pushes requirements up faster than raw player count:
- 1–4 players, early/mid save: 8–12GB RAM, a high-clock CPU. Comfortable for most co-op groups.
- 4+ players or a large late-game save: 16GB RAM, per the official recommendation. This is where you want the headroom.
- Heavily modded or megafactory saves: 16GB+ and the fastest single-thread CPU you can get — mods and dense factories are the real RAM and tick eaters.
If you’d rather skip the hardware math and port forwarding entirely, spinning up a managed Satisfactory server gets you correctly-sized RAM, high-frequency CPUs, and pre-configured networking out of the box. Once it’s running, you may also want our save file backup guide to keep that megafactory safe.
Frequently asked questions
Is 8GB of RAM enough for a Satisfactory server?
8GB is the official minimum and works for a small base with a few players early in a save. Because RAM usage scales with the number of buildings and belts, larger or late-game worlds will outgrow it. The wiki recommends 16GB for bigger saves or hosting more than 4 players, with 12GB as a reasonable middle tier.
Do I still need to forward ports 15777 and 15000?
No. As of Patch 1.0 those ports are no longer used. Current servers need port 7777 (both TCP and UDP) and port 8888 (TCP) for reliable messaging. Forwarding the old query and beacon ports has no effect.
Does Satisfactory need a lot of CPU cores?
Not especially. The server uses multiple cores but heavily favors high single-core performance — the wiki suggests a single-thread rating of 2000 or higher. A fast, high-clock CPU beats a many-core chip with weaker per-core speed.
Ready to play?
Run your own Satisfactory server with XGamingServer
Spin up an always-on Satisfactory server your friends can join in minutes — no port-forwarding, no tech headaches.
