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.
Prepare the source PC
On the source system, identify the actual Factorio save root: Windows: %APPDATA%Factoriosaves. The expected file/folder pattern is Save games are ZIP archives, normally named <save-name>.zip.. Close the game, let the active launcher finish writing and synchronizing, then make a complete offline copy rather than transferring a file that may still be open.
Preserve storefront and profile identity
Documented storefronts: 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. A transfer between two PCs is simplest when both systems use the same storefront/account/profile context. If the destination uses a different store or container, treat that as a migration problem rather than an ordinary restore.
Move the complete save boundary
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. Put the copied data on the destination only after confirming the destination save path. If the game creates a new empty save first, keep that new folder as another backup so you can compare structures and revert.
Handle cloud sync deliberately
Steam Cloud and GOG Galaxy cloud are documented. Decide whether the local transferred copy or cloud copy should be authoritative before launching the game. If possible, preserve both. After the transferred save loads correctly, make a fresh in-game save and let the launcher synchronize normally.
Check compatibility before blaming the transfer
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. If the destination does not see the transferred progress, 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. Verify game edition/version, store, profile IDs, redirected folders, and mod/DLC dependencies before editing the save itself.
Verification context: Reviewed against the current official Factorio Wiki application-directory documentation and PCGamingWiki save path.