Factorio final update: 2.1 stable and the support that continues

The current status: 2.1 is stable

Factorio’s developers announced 2.1 Stable in Friday Facts #449 on October 23, 2026. The official download page checked October 25 lists stable version 2.1.23. These are current first-party release statements, not an inference from an older roadmap.

Keep the two kinds of number separate: 2.1 identifies the major update line, while 2.1.23 identifies a specific release within it. A stable listing is not a promise that the patch number will remain unchanged after this article’s checked date.

The earlier May announcement discussed closed testing and a hoped-for experimental release. That historical testing plan does not describe the current stable state. Use the release page for today’s branch rather than assuming you still need to opt into experimental for 2.1.

What final means in Wube’s plan

In Friday Facts #440, Klonan describes 2.1 as the team’s envisaged last major Factorio update, followed by long-term support. The post explicitly includes bug fixes, platform compatibility and modding features in that continuing work.

That is a distinction between concluding active gameplay development and stopping every patch. It does not announce an immediate end to support, guarantee that no future plans can change, or turn a later compatibility fix into a contradiction.

The announced scope focuses on quality of life, smaller features, polish and modding improvements. It does not promise new planets, enemy types or research trees. Changes to existing enemy behaviour and balance are still compatible with that scope.

Changes worth checking in an existing factory

Mixed rocket delivery is documented as automatic batching of requested items, not a requirement to manually pack each launch. The logistics article explains prioritising small requests and handling incomplete payloads. Check your actual request settings before treating a partly filled rocket as a broken supply chain.

Quality remains enabled by default as a recommended dependency for Space Age, while the Recycler has its own module. Optional Quality does not mean the Recycler or the expansion’s progression disappears.

The fluid article also describes warnings when incompatible pipelines would mix and changes to high-throughput flow. An older blueprint that relied on a particular connection or output orientation deserves a check after upgrading. These are developer-described changes; Nisu has not benchmarked a factory or designed a replacement blueprint.

Area	Published 2.1 change	Why an existing design may need review
Space deliveries	Mixed-item rockets and platform-to-platform transfers	Old full-stack assumptions and delivery arrangements
Platform movement	Drag based on mass rather than width	A narrow platform is no longer the only route to speed
Platform damage	Asteroid damage based on remaining health	Existing defence expectations
Quality	Recycler split out; Quality can be disabled for Space Age	Mod configuration and progression assumptions
Asteroid reprocessing	Quality modules no longer allowed in those recipes	A quality-production loop built around reprocessing
Flipping and fluids	More flippable machines, drop-lane control and mixing prevention	Blueprint orientation and pipeline connections

Back up before loading a 2.0 save in 2.1

The stable announcement says 2.0 saves will load, but some changes can break existing factory designs. It specifically points to the circuit input/output split as an example. Being able to open a save does not prove that every circuit, platform or production chain still behaves as before.

Wube also warns that updated saves and blueprints cannot be downgraded to 2.0 and recommends backups. Keep copies of the saves and blueprints you want to preserve before upgrading, then check the systems affected by the published changes.

Review your actual mod set as well. The announcement says many popular mods were updated during the experimental period, while some may not be ready. That does not establish compatibility for every mod in an individual save.

This article does not load, convert or modify your files. It explains the developer’s migration cautions; no save conversion, modpack upgrade, multiplayer compatibility test or performance test was performed.

Use the release source that matches your question

For whether 2.1 is stable, use the October 23 stable announcement. For the exact available build, use the current official download page. For why the team calls it the last major update, use the May 29 scope and support statement. Those sources answer related but different questions.

This feature overview is not a complete patch-by-patch fix list. When checking whether a particular issue has been fixed, use the changelog linked from the current release page: the major-update roadmap alone does not identify the patch that contains a fix.

No release state for a separate console edition is inferred from the desktop download page. Match the branch, platform and mod requirements that your own client actually uses before deciding an update applies to your setup.

Quick help

Does final update mean no more bug fixes?

No. Wube’s stated plan is a final major update followed by long-term support, including fixes, platform compatibility and modding work.

Has Factorio 2.1 actually reached stable?

Yes. Friday Facts #449 announced stable on October 23, 2026; the download page checked October 25 lists 2.1.23.

Can I downgrade a converted save to 2.0?

The developer warns that saves and blueprints updated to 2.1 cannot be downgraded to 2.0. Keep backups before upgrading.

Is this another expansion with new planets?

The stated 2.1 scope does not add new planets or research trees. It concentrates on smaller features, quality of life, balance, polish and modding improvements.

Source and scope

Checked October 25, 2026 against Wube’s official stable announcement, original 2.1 plan, release page and feature posts. No game install, save migration, modpack, multiplayer or performance test was performed.