Factorio 2.1 Experimental on Your Server — Opt-In, Mods, and the No-Downgrade Rule
Last verified: June 12, 2026. Per FFF-440: experimental targeted for the end of June 2026, stable by end of summer. 2.1 is Factorio's final major update.
Two facts from Wube's published 2.1 plan frame every server decision this summer. First, 2.1 hits the experimental branch around the end of June 2026, with stable following by the end of summer. Second — the bigger one — 2.1 is the last major update: after it ships, Wube moves to maintenance, compatibility, and modding support while the studio turns to new projects. Whatever state 2.1 stabilizes into is the Factorio your server lives on for years. Here is what is actually in it, how the experimental branch works for a multiplayer server, and the order of operations that avoids the classic experimental-week disasters.
What 2.1 is (and deliberately is not)
Wube has scoped 2.1 as quality of life, small features, polish, and modding improvements — explicitly ruling out new planets, enemies, research trees, and resource chains. The meaty announced area is space logistics (Friday Facts #441):
- Rocket silos will request exactly the number of items a platform actually needs for construction, ending the over-shipping dance.
- Platforms will prioritize foundation and cargo bays before other construction materials.
- Platforms can request items from all planets by default, with an optional filter to pin a request to one planet.
For multiplayer Space Age saves, that last one quietly removes an entire genre of "why is the platform starving" support questions. Community wishlists (visible planets from platforms, interplanetary circuit connections) are circulating, but treat anything not in an FFF as speculation — the full announced picture lives in our Factorio 2026 roadmap, updated as FFFs land.
How experimental works for a server
- It is opt-in on both ends. Experimental builds publish alongside stable: a Steam beta branch for clients, and experimental-tagged headless packages from factorio.com for servers. Nothing moves until you move it.
- Version match is absolute. Clients and server must run the same version. Moving a community server to 2.1 experimental means asking every player to flip their branch — which is why most multiplayer servers should not be first-week adopters unless the group explicitly wants to be.
- Experimental iterates fast. During an experimental cycle, point releases can land multiple times a week. Headless servers either chase them (auto-update + announced restarts) or pin one build and update deliberately. Pin; chasing is for test servers.
The no-downgrade rule
The single most expensive mistake of every experimental cycle: saves do not load backwards. A map touched by 2.1 will not open under 2.0. The binary downgrades fine; your two-hundred-hour map does not. So:
- Copy the save file itself before switching — a real file copy you control, not only a panel snapshot you have never restored.
- Keep the 2.0 backup until the group commits. If 2.1 experimental goes badly (a mod you depend on lags, a bug bites your base), the rollback is: restore binary, restore save, lose the sessions played on 2.1. Decide in advance whether that trade is acceptable, and tell your players.
Mods: audit before you flip
2.1 concentrates changes in space-platform logic and the modding API — exactly where mods break. The pattern from every previous cycle: major mods update within days, mid-size mods within weeks, abandoned mods never. Practical sequence: export your mod list, check each mod's portal page for 2.1 releases after experimental lands (the portal serves per-version builds — your server on 2.1 pulls 2.1 releases, which will be young), and classify each as critical / nice-to-have / droppable. A server whose permissions or protection mod is "droppable" has a different definition of droppable after the first griefing. Our mod installation guide covers the per-version mechanics.
The decision matrix
- Fresh group starting this summer: start on 2.1 experimental. You inherit no save risk, you get the QoL from day one, and you will be on stable before your base is big enough to fear bugs. Dial in your map-exchange settings with the Factorio map generator before world creation — resource richness and biter settings are the two you cannot change later without commands.
- Active long-running save, vanilla: wait for two or three experimental point releases, then move with a verified backup. The space-logistics improvements are worth it; the first-week bugs are not.
- Active save, heavily modded: wait for stable, or for your critical mods to publish 2.1 builds — whichever comes first. The end-of-summer stable target makes this a weeks-not-months wait.
- Archival megabase: no rush, ever. 2.1 is the final destination; it will still be there when every mod has caught up. The update mechanics are in how to update your server.
Want the version flip to be a dropdown instead of a package swap? Host a Factorio server with Supercraft — pin 2.0, test 2.1 experimental, and move when your group is ready.
Looking for managed Factorio server hosting? Supercraft runs Factorio dedicated servers with daily backups, instant setup, and 5 region options. Plans from $5.99/mo.