Satisfactory Dedicated Server: Complete Setup & Optimization Guide

Satisfactory is unusual among dedicated-server-hosted titles in one important way: server load scales primarily with factory complexity, not player count. A 2-player server with a sprawling, heavily-optimized late-game factory spanning thousands of buildings and belts will need dramatically more CPU than an 8-player server still in its first few in-game hours. If you size hardware purely by headcount the way you would for Minecraft or ARK, you will be caught off guard three months into a save when the factory has grown into a genuine simulation burden.

This guide covers the official Dedicated Server Manager (Coffee Stain's own tool, distinct from community-run servers of earlier Satisfactory versions), realistic hardware sizing tied to factory complexity rather than just player count, mod installation via the Satisfactory Mod Manager, and the specific performance issues that show up as a save matures.

If you're used to sizing game servers by player count alone, unlearn that instinct here. The right question for a Satisfactory server isn't "how many people will play" but "how big and how automated will this factory realistically get in six months" — and answering that honestly up front avoids a mid-save hardware upgrade scramble once belts and splitters number in the thousands.

What Is a Satisfactory Dedicated Server?

It's the official standalone server software (SteamCMD app ID 1690800, also available on Epic Games Store) built and maintained directly by Coffee Stain Studios, distinguishing it from the earlier community workaround era before dedicated servers officially shipped. Key characteristics:

• Runs headless, independent of any player's own client, with saves persisting on server storage
• Managed through a browser-based Server Manager UI (a genuinely convenient built-in admin tool, unlike many survival titles that rely entirely on config files and RCON)
• Supports the same mod ecosystem as the client, installed via the Satisfactory Mod Manager (SMM) or the newer Ficsit App
• Scales its resource demands primarily with factory size/complexity and simulated production chains, not raw player count

System Requirements and Pricing

Sizing here should account for expected long-term factory growth, not just your launch-day player count.

The single-core clock speed of your CPU matters heavily here — like many Unreal Engine titles, a large chunk of Satisfactory's factory simulation logic doesn't parallelize perfectly across many cores, so a higher-clocked 6-core CPU often outperforms a lower-clocked 12-core CPU for this specific workload.

Reading Your Own Growth Curve Before You Provision

If you're starting a brand-new save, it's reasonable to begin on an early-game tier and plan an upgrade path rather than over-provisioning from day one — Satisfactory's Server Manager makes migrating a save to bigger hardware straightforward. If you're already mid-save and experiencing tick-time creep, size for where the factory is heading based on your community's ambitions (are you planning a full Space Elevator completion? A maxed-out late-game production chain?) rather than just its current state.

Step-by-Step Setup

1. Install via SteamCMD

steamcmd +force_install_dir ./satisfactory +login anonymous +app_update 1690800 validate +quit

1a. Epic Games Store Alternative

Satisfactory is also distributed on the Epic Games Store, and the dedicated server binary is available through Epic's tooling as well if your group primarily uses Epic rather than Steam accounts. The server software itself is functionally identical regardless of storefront — the choice mainly affects how you initially download and update it.

2. Launch and Access the Server Manager

Start the server binary, which exposes a web-based Server Manager interface (default port 8888 for HTTPS admin access). This is genuinely one of the better built-in admin experiences among dedicated-server-hosted titles — you can create/load saves, set server options, and manage basic administration entirely through a browser rather than editing raw config files for everyday tasks.

3. Configure Server Options via the Manager UI

Through the Server Manager, configure: server name, max player count, auto-pause when no players are connected (recommended — it saves CPU during off-hours the same way Zomboid's PauseEmpty does), auto-save interval, and admin password. These options used to require manual config file edits in earlier builds; the official server centralizes them in the UI now.

3a. Create Multiple Save Slots for Testing

The Server Manager supports multiple named saves on one running instance, which is genuinely useful for testing a risky factory redesign or a new mod on a duplicate save before committing changes to your community's main progress. Clone your main save through the UI, experiment freely on the copy, and only load the changes into the primary save once you're confident they work as intended.

4. Open Firewall Ports

Satisfactory dedicated servers use UDP 7777 (game traffic) by default and TCP/HTTPS 8888 for the Server Manager admin UI. With UFW: sudo ufw allow 7777/udp and, restricted to trusted IPs, sudo ufw allow from YOUR_IP to any port 8888 proto tcp — the Server Manager is an admin interface and shouldn't be exposed to the open internet.

5. Install Mods via Satisfactory Mod Manager / Ficsit App

Satisfactory's mod ecosystem runs through the Satisfactory Mod Manager (or its newer successor, the Ficsit App), which handles dependency resolution between mods automatically — a meaningful convenience compared to manually tracking mod load order like some other titles. Server-side mod installation mirrors the client install process; both server and connecting clients need matching mod versions.

5a. Common Mod Categories Worth Knowing

Popular categories include quality-of-life mods (extended build distance, additional blueprint options), logistics mods (expanded conveyor/pipe throughput options), and progression mods (alternate recipes, expanded late-game content). Since factory-focused mods can add their own per-tick simulation logic, test any mod's performance impact on a smaller test save before rolling it out to a large, mature factory where the added cost compounds across thousands of existing buildings.

6. Tune for Large Factories

As your save matures, watch server tick time in the Server Manager's diagnostics. If tick time climbs, common mitigations include reducing unnecessarily long conveyor belt chains (each belt segment carries simulation cost), consolidating overly fragmented production lines, and — if you're modding — avoiding mods known for adding expensive per-tick logic across large factories.

6a. Understanding Tick Time Diagnostics

The Server Manager exposes a rolling tick-time graph that's worth checking weekly on any actively-growing save. A healthy server holds a consistent tick time well within budget; a slowly climbing baseline (rather than occasional spikes) is the early warning sign of a factory outgrowing its current hardware, and it's far easier to plan an upgrade proactively than to react after players start reporting lag during automation-heavy play sessions.

7. Automate Save Backups

Even with the Server Manager's save/load UI, schedule an external backup of the save directory on a cron job, since UI-based saves alone don't protect against a corrupted save or accidental in-game deletion. Keep multiple rolling snapshots given how much time factories represent.

8. Plan a Migration Path for Hardware Upgrades

Because Satisfactory servers often need to scale up over a save's lifetime, know the migration process before you need it: stop the server, copy the save file (and any mod configuration) to the new box, install matching mod versions if applicable, and load the save through the new instance's Server Manager. Testing this process once on a small early save removes the uncertainty when you actually need to do it under time pressure with a mature factory.

Common Issues and Troubleshooting

Tick Time Climbing as the Factory Grows

This is expected behavior, not a bug — factory complexity directly drives CPU load. Check the Server Manager's performance stats to see whether it's conveyor/production logic or something else (like an expensive mod) driving the increase, and consider a CPU upgrade before the save gets large enough that it's painful to optimize retroactively.

Server Manager UI Not Accessible

Almost always a firewall issue on port 8888 (or whatever port you've configured) — confirm both the OS firewall and any cloud-level network firewall allow the connection, ideally restricted to your own IP.

Mod Version Mismatch Between Server and Client

The Ficsit App/SMM generally handles this well by flagging mismatches, but if you're manually managing mods, keep server and client mod manifests in sync manually to avoid connection refusals.

Save File Growing Very Large

Expected as factories scale — budget storage growth over the life of a long-running save, and don't assume your launch-week storage allocation is sufficient a year in.

Players Report Lag Only in Certain Factory Regions

This usually points to a localized production bottleneck (an overloaded splitter/merger network or an inefficient belt-heavy design) rather than a global server issue — the Server Manager's stats can sometimes help narrow down which systems are contributing most to tick time.

Server Manager UI Slow to Respond

This is typically unrelated to actual game-tick performance — the UI runs on a separate lightweight web service, so a slow interface points to a networking or browser-side issue rather than the factory simulation itself struggling.

New Mod Causes a Sudden Tick Time Jump

Isolate it by testing the mod alone on a smaller test save (per the save-slot workflow above) before assuming your factory has simply grown too large — some mods add meaningful per-tick overhead that's easy to misattribute to organic factory growth if you're not testing changes in isolation.

Troubleshooting Reference Table

Common Mistakes to Avoid

The most common mistake is sizing hardware purely for the current save state instead of the factory's realistic six-month trajectory — Satisfactory servers are one of the few in this genre where under-provisioning is a near-certainty if you only plan for day one. A second mistake is exposing the Server Manager's admin port to the open internet without an IP restriction, treating it like a normal game port rather than the administrative interface it actually is. A third is adding several mods simultaneously to an already-large factory without isolating each one's performance impact first, making it much harder to identify which mod (if any) caused a subsequent tick-time regression.

Buyer's Checklist

• Size hardware for where your factory will be in 3-6 months, not just where it starts — Satisfactory servers grow into their resource needs
• Prioritize single-core clock speed over raw core count when comparing CPU options
• Confirm the host allows access to the Server Manager's admin port with your own firewall restrictions
• Check for NVMe storage, since save file sizes and write frequency both grow substantially in late-game saves
• Ask whether the host supports mod installation via SMM/Ficsit App workflows without restrictive limitations
• Verify automated backup capability beyond just the in-game save system
• Ask whether migrating your save to a bigger plan later is a straightforward process the host supports

Frequently Asked Questions

Does Satisfactory server performance depend more on player count or factory size?

Factory size and complexity, by a wide margin. A small 2-player server with a massive automated factory needs considerably more CPU than an 8-player server still early in progression.

Can I manage the server entirely through a browser?

Yes — the official Server Manager exposes save management, basic settings, and diagnostics through a web UI, which is more convenient than the config-file-only approach many other survival titles require for day-to-day administration.

Do all connecting players need the same mods installed?

Yes, mod versions need to match between server and client — the Ficsit App/SMM tooling helps manage this, but mismatches will still block a client from connecting.

Should I upgrade CPU or add RAM first if my factory is lagging?

Check the Server Manager's tick time diagnostics first — Satisfactory's factory simulation is typically more CPU-bound than RAM-bound, so a CPU upgrade (or a higher-clocked plan) usually addresses tick lag more directly than adding RAM alone.

How often should I back up a Satisfactory save?

Daily for an actively-played server, using an external cron-based copy of the save directory in addition to in-game autosaves, since autosaves alone don't protect against corruption or accidental deletion.

Can I test a factory redesign without risking my main save?

Yes — use the Server Manager's multiple save-slot support to clone your current save, experiment on the copy, and only load the changes into your primary save once you're confident they work as intended.

Is the Epic Games Store version of the server any different from Steam's?

Functionally no — the dedicated server software itself is the same regardless of which storefront your group primarily uses; the main difference is just how you initially download and update the binary.

How do I know when it's time to upgrade my server's CPU?

Watch the Server Manager's tick-time graph for a steadily climbing baseline over several weeks rather than reacting to a single bad session — a consistent upward trend, not an occasional spike, is the real signal that your factory has outgrown current hardware.

Do mods significantly increase hosting costs?

It depends heavily on the specific mod — quality-of-life and cosmetic mods add negligible overhead, while mods that introduce new automated production systems can meaningfully add to per-tick cost at scale, so test any significant mod's impact before assuming your existing plan will absorb it.

Satisfactory is one of the few titles where planning for future growth matters as much as current player count — size your CPU for the factory you'll have in six months, not the one you have on day one. WebsNP's Linux dedicated server plans offer the high-clock dedicated cores large factories need, with VPS hosting a solid starting point for smaller early-game saves — contact us for help sizing a plan around your factory's growth trajectory. If your group also plays other Steam-distributed titles, our SteamCMD guide covers the shared install process, and our Enshrouded dedicated server guide is a good comparison for a different building-focused survival experience.