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.
Identify the exact save you intend to edit
The researched Factorio PC save location is Windows: %APPDATA%Factoriosaves. Known file/folder pattern: Save games are ZIP archives, normally named <save-name>.zip.. Storefront 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. Do not edit a similarly named file from a different profile, edition, or cloud cache.
Make an untouched backup first
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. Keep that copy outside the live save directory and do not overwrite it with later experiments. Cloud context: Steam Cloud and GOG Galaxy cloud are documented. If a launcher can synchronize the save, prevent it from silently replacing either the original or edited copy while testing.
Understand the format boundary
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. File-extension context: .zip 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. These facts help identify the save but do not automatically reveal every field, checksum, encryption rule, or version-specific structure inside it.
Use only a Tool whose claim matches the file
Generic viewers and diff tools can inspect bytes without claiming game-specific semantics. A game-specific editor should be used only when its Tool page explicitly lists Factorio, a matching supported version/container, and a Verified operational runtime. A planned URL or Game Hub is not evidence that an editor exists.
Test the edited copy safely
Write to a new output file when the Tool supports it, keep the original backup, restore the edited copy into the correct profile/storefront location, and launch the game only after the file operation finishes. If the game rejects it, 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. Return to the untouched backup before trying another change.
Verification context: Reviewed against the current official Factorio Wiki application-directory documentation and PCGamingWiki save path.