Skip to content
Game save workbench
Local-first tools No installation Support status shown
DEVICE-LOCAL Favorites and recent pages stay in this browser.

Backups & Safety

How to Back Up Factorio Saves

A game-specific Factorio backup and restore workflow based on the researched save boundary, launcher/cloud behavior, compatibility notes, and recovery risks for the PC release.

Editorial state
Reviewed
Reading time
3 min
Difficulty
Beginner
Last reviewed

Before you start

Close the game before copying or replacing saves. Keep one untouched backup outside the live save directory. Identify the storefront/launcher and active player/profile before changing files.

Key takeaways

What this guide establishes.

  • Use the documented save directory for the PC storefront/profile you actually play.
  • Back up the complete save boundary before restore, migration, repair, or editing.
  • Treat cloud synchronization as a separate copy that can overwrite a manual restore.
  • If progress is missing, verify storefront, account/profile, path redirection, and cloud state before assuming corruption.

Factorio is straightforward to archive because each world save is itself a ZIP file, but the surrounding mod environment still matters. A user can copy one .zip and preserve the map bytes, yet later discover that required mods or versions are missing. SaveEditor recommends backing up the saves directory together with mod/version notes and checking whether the installation is standard or portable before assuming %APPDATA% is authoritative. The page deliberately separates ZIP structural validity from the game-level compatibility of the serialized factory.

Choose the correct backup boundary

For Factorio, the researched PC save location is Windows: %APPDATA%Factoriosaves. The known save file or folder pattern is Save games are ZIP archives, normally named <save-name>.zip.. Copy the entire saves directory and, for important modded factories, also preserve the mods folder and mod-list/version context. Keep the original .zip extension and avoid unpack/repack cycles unless required by a known workflow. Copying the complete documented save boundary is safer than selecting one visually obvious file, because companion metadata, indexes, backups, or multiple slots can be required together.

Make an offline copy before changing anything

Close the game first, wait for the active launcher to finish writing, then copy the save data to a separate folder that the game and sync client do not watch. Label the copy with the game, storefront, profile, and date. Documented launcher context: Steam, GOG, standalone. The default Windows root is AppData/Roaming, but ZIP/portable installations can use a local game data directory according to Factorio configuration.

Account for cloud saves

Steam Cloud and GOG Galaxy cloud are documented. Before restoring an older backup, decide which copy should win. If the game or launcher starts while an older manual copy is in place, synchronization can replace it before you confirm that it works. Keep the untouched backup outside the live save path until the restored progress has been opened and saved normally.

Restore without changing format assumptions

Factorio’s standard user-data directory keeps saves as zip files. The archive contains the serialized map/state needed by the game, and the application directory can be relocated in portable/custom setups. Compatibility note: A save can load differently or fail when required mods/versions are absent. The fact that the file is a valid ZIP archive does not guarantee semantic compatibility with another Factorio environment. Restore into the matching storefront/profile context whenever possible. Do not rename a save extension, move a folder into a different container type, or assume a console/mobile copy is equivalent unless a tested migration path specifically says so.

Recovery fallback

If a save is missing, verify whether the installation uses the standard user-data directory or a portable/custom write-data path. If loading fails, compare Factorio and mod versions. If the restored copy fails, put the untouched original back first. Then compare location, account/profile, cloud state, and the full directory structure before trying a different backup. The objective is reversible recovery, not repeated destructive experiments on the only copy.

Verification context: Reviewed against the current official Factorio Wiki application-directory documentation and PCGamingWiki save path.

Troubleshooting

If the expected result does not match.

Game-specific note: If a save is missing, verify whether the installation uses the standard user-data directory or a portable/custom write-data path. If loading fails, compare Factorio and mod versions.

Verification and sources

How this guide was checked.

Phase 27 generated this Guide from the reviewed Phase 23/24 Game Hub evidence for Factorio. The backup boundary, cloud context, and restore risks were cross-checked against the same public references recorded on the Game Hub. No unsupported game-specific editor, checksum, encryption, or cross-platform conversion capability is implied.

  1. www.pcgamingwiki.com
  2. wiki.factorio.com