Satisfactory Server Lag Fix (Stutter, Rubber Banding, Freezes)

Satisfactory server lag almost always comes from one of four things: the server's CPU cannot keep up with the size of the factory, the autosave freezes the game every few minutes, the server is short on RAM, or the network settings do not suit your connection. Check when the lag happens. A freeze every few minutes is the autosave. Constant rubber banding that grows with your factory is CPU or RAM. Lag only for one player is usually their connection.

Quick diagnosis

What you see	Most likely cause	First fix
Everyone freezes for a second or two every few minutes	Autosave on a big save	Raise the autosave interval
Rubber banding that got worse as the factory grew	CPU single core speed	Fewer active machines and vehicles near players, faster CPU
Lag builds over hours, then the server crashes	Out of memory	More RAM, regular restarts
Slow to load in, then smooth	Network Quality, connection	Try a higher Network Quality
One player lags, everyone else is fine	That player's ping or Wi-Fi	Wired connection, check distance to the server
Low FPS on your PC, but other players are smooth	Your graphics, not the server	Lower graphics settings

The last row matters more than it sounds. Satisfactory late game is heavy on your own PC too. If your FPS counter drops while other players are fine, the server is not the problem.

Why Satisfactory servers lag as the factory grows

The server simulates the whole factory while anyone is online: every machine, belt item, train, truck and drone. Most of that work runs on one CPU core, so single core speed matters far more than core count. The official wiki asks for a CPU with a single thread rating of about 2000 or better.

What costs the most:

Belts packed with items. Thousands of moving items are thousands of things to track.
Vehicles. Trucks, tractors and drones on long routes are expensive. Trains are cheaper per item moved.
Players spread out. Each player keeps the area around them loaded in detail. Four players in four corners of the map load four areas.
Mods. Mods that add machines, logistics or world changes add work for the server.

You cannot make a megabase free, but you can stop it from being worse than it needs to be.

Fix autosave stutter

When the server autosaves, it pauses to write the save. On a fresh world you will not notice. On a large factory the pause becomes a freeze every time.

Open Server Manager in the game, select your server and sign in with the admin password.
Under the server settings, raise Autosave Interval. The default is 5 minutes. On a big save, 10 to 15 minutes means far fewer freezes, at the cost of losing a little more if the server crashes.
Keep Auto-Save on Player Disconnect on, so a save still happens whenever someone leaves.

We would not go above 15 minutes. A crash that costs half an hour of building hurts more than a short freeze.

Make sure the server has enough RAM

Satisfactory memory use grows with the save. The official wiki gives 8 GB as the minimum and 16 GB for four or more players. Signs you are short:

Lag that gets worse the longer the server runs.
The server restarting or crashing after a few hours online.
Long hitches when players fly to a part of the map nobody has visited this session.

Rough sizing from our own plans:

Factory	RAM
New or mid game save, up to 4 players	8 GB
Late game factory, 4 to 8 players	12 GB
Megabase, heavy mods or 8 players and up	16 GB

A daily restart helps too. The server manager's Server Restart Interval is really a time of day: set it to an hour when nobody plays, and the server restarts itself then.

Reduce what the server simulates

These cost you nothing and help on any machine:

Replace truck and drone routes with trains where you can.
Shorten long belts. Belts carrying parts across the whole map are some of the most expensive things in the game. Build closer to the resources and move goods by train.
Clean up. Dismantle old test builds and abandoned factories that are still running.
Test mods one at a time. If lag started after adding mods, remove the newest one and compare.

Network settings

Network Quality

Server Manager has a Network Quality setting. Per the official wiki, raising it can improve load times and network performance for players, at the cost of server framerate. On a strong server with a few players, try a higher setting. If the server is already struggling with the factory, a lower setting gives that CPU time back.

Timeouts

If players get kicked with timeouts while the server freezes, for example during a big autosave, the connection timeout is shorter than the freeze. The timeouts are in Engine.ini:

[/Script/OnlineSubsystemUtils.IpNetDriver]
InitialConnectTimeout=30.0
ConnectionTimeout=20.0

Raising them stops the kicks but not the freeze. Fix the autosave first.

Advanced: network tick rate

The official wiki documents tick rate settings in Engine.ini (NetServerMaxTickRate and related keys). A higher tick rate sends updates more often, which can look smoother but costs CPU and bandwidth, and can make lag worse on a busy server. Only try it after everything above, change one value at a time, and always edit with the server stopped: Satisfactory writes its ini files when it shuts down and will overwrite changes made while it runs.

When the problem is one player

If only one person lags:

Ask them to use a wired connection instead of Wi-Fi.
Check where the server is. A server far from the group means high ping for everyone, but the farthest player feels it most.
Make sure they are on the same game version and branch as the server. A mismatch usually stops the connection outright, but see Satisfactory server can't connect if they cannot get in at all.

For lag on any game, why is my game server lagging covers the general causes.

Fixing lag on a GamezServers Satisfactory server

On a GamezServers Satisfactory server:

Upgrade the plan from 8 to 12 or 16 GB any time, prorated, keeping the same save. It applies on the next restart.
Autosaves to keep is in Settings. Fewer rotating autosaves means less disk, not less lag, so leave it at 3 unless you need more history.
Timeouts are written into Engine.ini by the panel on every start, so edits to those two lines are undone. If you need longer ones, email support@gamezservers.com. The rest of Engine.ini is yours to edit in the Files tab under FactoryGame/Saved/Config/LinuxServer/. Stop the server before you edit.
Backup before trying risky changes. You keep 3.
Console shows the server log, so you can see autosaves happen and match them to the freezes.

Autosave interval and Network Quality are set in Server Manager in the game, the same as anywhere else. More setup help is in the Satisfactory hosting quick start.

FAQ

Does a Satisfactory server need a fast CPU or more cores?

A fast CPU. The factory simulation leans on one core, so single core speed matters most. Extra cores help a little with other work but will not fix a slow simulation.

Why does my Satisfactory server freeze every 5 minutes?

That is the autosave, which runs every 5 minutes by default. On a large save each one causes a short freeze. Raise the Autosave Interval in Server Manager.

Does Auto Pause cause lag?

No. Auto Pause stops the simulation when nobody is online. When the first player joins it resumes, and you may see a short hitch while the area loads.

Will more players make the server lag?

Yes, especially when they spread out across the map, because each one keeps their area loaded. That is why more players need more RAM.

Do mods make Satisfactory servers lag?

They can. Mods that add machines, logistics or world changes add simulation work. Remove the newest mod first when lag appears after an update to your mod list.