How to Fix Factorio Server Lag and Connection Problems

Fix Factorio multiplayer problems by identifying which of three things is failing: the simulation or host, the network path, or game-state synchronization. If every player slows down together, inspect the host CPU, memory, save and server settings. If players cannot join or are dropped, verify the exact game and mod versions, then check Factorio’s UDP port (34197 by default), forwarding and firewalls. If the game reports a desynchronization, do not treat it as ordinary lag: desyncs require investigating a bug, mod, scenario or hardware calculation.

Factorio uses deterministic lockstep. Each participant simulates the complete world and exchanges player inputs, so a weak host can hold everyone back while a reachability problem prevents a connection entirely. The sequence below isolates the cause before you change hardware or router settings.

Why is my Factorio server lagging?

First determine whether the slowdown affects everyone, only one player, or the connection attempt itself. Factorio’s symptoms overlap, but the fixes do not.

What you observe	Most likely track	Start here
All players’ actions feel delayed and the factory advances slowly for everyone	Simulation or host performance	Check the host’s CPU, RAM, save size, mods and server process; use a benchmark or headless test.
A player cannot join, is kicked during connection, or connects only intermittently	Network reachability	Match the game and mods, confirm UDP 34197 or your chosen port, then check forwarding and firewalls.
The client is removed with a desynchronization message	Desynchronization	Compare mods, scenarios, updates and logs; do not troubleshoot it as latency.

Factorio is deterministic lockstep: every participant runs the same simulation and the network carries player inputs rather than a complete stream of world objects. That design lets a small amount of network data represent a large factory, but it also means the simulation must remain consistent on every instance.

How do I fix Factorio connection failures?

Work through these checks in order. There is little value in changing router rules when the joining computer is running a different game build or mod set.

1. Match the game version exactly. The server and every client must use the same Factorio version. A seemingly minor build difference can prevent a join.
2. Match every mod exactly. All instances need the same enabled mods and compatible versions. Check the mod list and versions on the server and each player before testing the network.
3. Confirm the transport and port. Factorio uses UDP, not TCP. The default server port is 34197, although an administrator can choose another port in the configuration.
4. Make the selected UDP port reachable. Forward it from the router to the host’s local IP address and allow it through the operating-system firewall and antivirus. A router that randomizes outbound source ports may need additional configuration.
5. Use the simplest path available. On one local network, choose Play on LAN. For ordinary hosted games, Steam joining or the public server browser can avoid manual address entry. Use a direct IP:port connection when the host needs explicit address control.
6. Test from outside the host’s network. A server behind NAT needs a publicly reachable address and a forwarded port for direct Internet play. Testing only from inside the same LAN can hide an incorrect forwarding rule.

What must match before anyone changes the router?

Open the server and each client’s mod manager and compare the complete enabled list, not just the large content mods. Disable or update the outlier, restart the game and try again. If the server save depends on a mod, removing it may make that save unavailable; make a backup before changing a live setup.

Which Factorio port should I forward?

Forward UDP 34197 unless the server configuration specifies a different port. The forwarding rule must target the computer running the server, not another PC that happens to be on the same network. Permit the same UDP port in the host operating system’s firewall and in security software. Do not create a TCP-only rule: it does not carry Factorio’s server traffic.

If your router rewrites outbound source ports, follow its documentation for preserving or allowing the required UDP mapping. This behavior can make a rule look correct while remote players still fail to complete a connection.

Which connection method should I use?

Choose the path that removes the most unnecessary network complexity.

Situation	Recommended path	What it requires
Everyone is on the same home or office network	Play on LAN	Local discovery and firewall permission on the host; Internet port forwarding is not normally needed.
A friend is joining a normal hosted game through the game ecosystem	Steam joining or the public server browser	The host must still be reachable, but the service can simplify address discovery.
The host wants a known address and port	Direct IP:port	A public address, UDP forwarding and firewall allowance when the host is behind NAT.
A persistent world needs administration and repeatable operation	Dedicated headless server	A server process, save file, reachable UDP port, logs and a backup plan.

Managed third-party hosting is another supported deployment context. It can reduce NAT and maintenance work, while self-hosting retains control over the machine, port, files, logs and backups. Compare those operational differences rather than assuming a hosting move will increase the simulation speed of a large save.

How can I test a connection from the command line?

The command-line reference documents a controlled client connection with --mp-connect ADDRESS. Replace ADDRESS with the server address, including the port when required by your setup. Use the same game and mod installation as the normal client so the test measures the real join path.

factorio --mp-connect ADDRESS

Add --verbose when you need more diagnostic output. For a server-side record that can be compared between successful and failed attempts, start the process with --console-log FILE and retain the resulting log file. Keep one log from a working connection and one from a failed connection; differences in the sequence are more useful than a single truncated message.

Run the test from a network that is genuinely outside the host’s LAN when checking Internet reachability. A successful local test proves that the server process is listening, but it does not prove that the public address, NAT rule or firewall is correct.

How do I fix Factorio simulation or server-side lag?

If everyone experiences the slowdown at the same time, investigate the host and the save before replacing network equipment. Deterministic lockstep requires the simulation to advance; when the server cannot process updates quickly enough, every connected player sees the factory fall behind.

Check the host against the published baseline

Wube Software’s official FAQ lists these baseline requirements (accessed in 2026): 4 GB of RAM, a dual-core 3 GHz-or-better processor, a 64-bit operating system and 3 GB of disk space. It recommends 8 GB of RAM and a quad-core 3 GHz-or-better processor. Those figures are baseline game requirements, not a promise that a very large, heavily modded factory will maintain a particular update rate.

Resource	Published minimum	Published recommendation	How to interpret it for a server
Memory	4 GB RAM	8 GB RAM	Leave headroom for the operating system, the server process, save operations and mods.
Processor	Dual-core, 3 GHz or better	Quad-core, 3 GHz or better	Clock speed and the save’s simulation workload matter; more cores alone do not guarantee faster simulation.
Operating system	64-bit	64-bit	A 64-bit system is required by the published baseline.
Disk space	3 GB	Not separately stated	Reserve additional space for saves, logs, backups and updates.

Separate network delay from update-rate delay

Ask players whether the factory itself is advancing slowly or whether only one player sees delayed input. A shared slowdown points to simulation capacity or the host process. A single affected player points first to that player’s local connection, route or machine. A join failure before the game starts is a reachability problem, not evidence that the factory is too large.

Use repeatable benchmark and startup options

Factorio exposes --benchmark and --benchmark-ticks for repeatable checks. Run the same save and tick count after each meaningful change so you compare like with like. The command-line reference also documents --start-server, --start-server-load-latest and --console-log. These options let an administrator load a known save and capture server output without relying on a player’s graphics session.

factorio --benchmark SAVE --benchmark-ticks TICKS
factorio --start-server SAVE --console-log FILE
factorio --start-server-load-latest --console-log FILE

Use the exact option syntax accepted by your installed Factorio build. Keep the save, tick count, enabled mods and hardware constant when comparing runs; otherwise a benchmark result cannot identify which change helped.

Should I use a dedicated headless Factorio server?

Use a headless server when you want the world to run independently of a player’s desktop, need repeatable startup and logs, or want to keep a persistent save available. It removes graphics initialization, but it does not remove the simulation workload of the save.

What the official headless package provides

Wube’s FAQ says Linux users can use a free, lightweight dedicated headless server package. The Linux package omits graphics and sound files and avoids libraries that a pure server may not have. The guide recommends running the process as a separate user. Firewall and port-forwarding details still depend on the Linux distribution and network environment.

How headless startup behaves

1. Start the server with --start-server and provide a save file, or use --start-server-load-latest to load the newest save.
2. Set the configured UDP port and make that port reachable through the firewall and, for Internet play, the router.
3. Run the process under a dedicated operating-system account and give it only the file permissions it needs.
4. Confirm the server log records startup, the save load and player connections before distributing the address.
5. Plan backups of the save directory. Factorio saves on exit and during normal autosaves, but an autosave is not a substitute for a separate backup.

In headless mode, graphics are not initialized and the server has no in-game character. The game pauses while no players are connected unless no-auto-pause is set. That pause is normal behavior, not a network failure. Set the option only when you intentionally want the factory to continue running while empty, and account for the extra simulation and save activity.

Is this lag or a Factorio desync?

A desynchronization means the server and a client no longer agree about the simulated game state. The official documentation explicitly states that networking, latency and performance problems do not cause desyncs, so a desync report needs a different investigation from ordinary lag.

What can cause a desync?

• A Factorio bug.
• A bug in a mod or scenario.
• A hardware miscalculation that produces a different result on one instance.

A desync report contains player and server save-state material plus a log, but the report itself does not automatically identify the cause. Treat it as evidence to compare, not as a diagnosis.

How should I investigate a mod or scenario?

1. Record the Factorio version, enabled mods, scenario and the action that preceded the desync.
2. Back up the affected save before changing its content.
3. On a test copy, remove mods added most recently or roll back recent mod updates.
4. Repeat the same action to see whether the desync disappears.
5. Re-add the suspected mod or update one at a time to reproduce the problem and narrow the trigger.

Do not “fix” a desync by lowering graphics quality, replacing a network cable or forwarding another port. Those changes address other tracks and cannot make two divergent simulations agree.

What are the trade-offs between hosting approaches?

The right choice depends on who controls the network and how much administration the group wants to perform.

Approach	Connection and NAT	Performance control	Operations	Best fit
LAN-hosted game	Simple local path; usually no Internet forwarding	Uses the host computer’s CPU, memory and save	Manual starts and local backups	Players in one home or office
Internet game from a personal PC	Requires a public address, UDP forwarding and firewall rules unless another supported path handles reachability	Full control of hardware and mods	Owner handles updates, logs, backups and uptime	Small groups comfortable with networking
Self-hosted headless server	Same UDP and NAT requirements, with a persistent process	Dedicated CPU and memory headroom; no graphics session	Scriptable startup, logs, saves and separate user account	Persistent worlds and technical administrators
Managed third-party server	Provider generally handles much of the public reachability	Depends on the selected service and allocated resources	Less control, but simpler maintenance and often easier backups	Groups that prefer convenience over machine-level control

When comparing options, check the connection path, who controls UDP forwarding, NAT complexity, CPU and memory headroom for the save, mod synchronization, log access, automatic backups, geographic distance to players and whether the game pauses when empty.

How many players can a Factorio server support?

Wube’s official FAQ says multiplayer supports up to 500 players in one game. The Factorio wiki lists a hard player limit of 65,535 while noting that the practical limit is much lower. Neither figure guarantees that a particular save, mod set, host or network can deliver a good experience at that scale; simulation workload and connection quality remain limiting factors.

What should I check when a fix does not work?

Use this short escalation path instead of changing several variables at once:

• Cannot see or join the server: verify the exact version and mods, then confirm that the server is running and listening on the configured UDP port.
• LAN works but Internet play fails: check the public address, router forwarding target, operating-system firewall and any source-port randomization behavior.
• Only one player is affected: test that player’s route and local firewall, and compare with another network before changing the host.
• Everyone slows down together: use a controlled save or benchmark, inspect CPU and memory headroom, and test whether a large or recently changed mod set is responsible.
• A desync appears: preserve the report and logs, then test recent mod or scenario changes on a copy of the save.
• The server stops progressing when empty: check whether automatic pausing is enabled; headless servers pause with no connected players unless no-auto-pause is set.

Change one variable per test and write down the result. A known-good save, a known-good client and a recorded server log give you a baseline for every later comparison.

Frequently Asked Questions

Can I host Factorio for friends without opening a router port?

Yes, when everyone is on the same LAN, use Play on LAN. Steam joining, the public server browser or managed hosting can also simplify reachability, but a direct Internet connection to a server behind NAT generally needs a publicly reachable address and forwarded UDP port.

Does a headless server automatically make a large factory run faster?

No. Headless mode removes graphics initialization and lets the server run independently, but the same save simulation still has to be processed. Faster hardware, fewer costly mods or a smaller workload may be needed when update-rate performance is the limit.

Why does my server stop while nobody is playing?

A headless Factorio server pauses when no players are connected by default. This is expected; set the no-auto-pause option only if you deliberately want the factory to continue running while empty.

What player count should I plan for in a real game?

The official FAQ states support for up to 500 players, while the wiki lists a hard limit of 65,535 and says the practical limit is much lower. Your save, mods, host hardware and network distance determine a usable capacity well before a hard limit.

Can better Internet latency repair a desynchronization?

No. Factorio’s documentation separates desyncs from networking, latency and performance problems. A desync requires examining the game version, mods, scenario, possible bugs and the associated save-state and log material.