SCIM Save Editor: the Complete 2026 Satisfactory Guide
Last updated: May 24, 2026. Verified against Satisfactory 1.2.2.2 (May 19, 2026).
SCIM (Satisfactory Calculator Interactive Map) is the most powerful save-editing tool available for Satisfactory dedicated servers and single-player worlds. It is a browser-based interactive map maintained by the satisfactory-calculator.com community, runs entirely client-side (your save never leaves your machine), and lets you do things the in-game console cannot: teleport stuck players, mass-delete bugged buildings, unlock all alternate recipes, spawn items, import community blueprints (Megaprints), and inspect every entity on your map.
This page is the definitive 2026 walkthrough for using SCIM on a dedicated server. It covers the save path on a Supercraft Satisfactory plan, every common editing task, the 1.2 patch compatibility story, what to do when SCIM cannot fix your save, and the safest workflow for editing a multiplayer world without breaking it for everyone else.
The Three Things You Use SCIM For
- Fix stuck players. Player fell through the world, logged out inside a deleted vehicle, or got jammed into terrain. SCIM teleports them to the HUB or any coordinate you choose.
- Clean up bugged structures. Mass-delete ghost foundations, orphaned poles, or invisible hitboxes left after a mod uninstall. The lasso tool selects an area; one click and they are gone.
- Inspect and edit production. See live throughput per machine, find bottlenecks, unlock alternate recipes you missed, or spawn items into your inventory when an MK6 belt eats your starter equipment.
Step-by-Step: Edit a Dedicated Server Save
Step 1: Stop the server
Open the panel and click Stop. The dedicated server holds the .sav file open while running; editing a save under a running server is the most common cause of "my edits did not apply" tickets. Wait until the status flips to Stopped before continuing.
Step 2: Download your save from the panel
Open the File Manager and navigate to the Saves partition. On a Supercraft Satisfactory server the on-disk path is:
/home/u<port>/stf/data/SatisfactoryDedicatedServer/Saved/SaveGames/server/You will see a list of .sav files. The naming convention is:
<WorldName>.sav- the latest manual save<WorldName>_autosave_0.savthrough_autosave_4.sav- rotating autosaves<WorldName>_CALCULATOR.sav- a save you previously exported from SCIM
Download the most recent one. If you are recovering from a problem, download an older autosave that you remember being in a good state.
If you are running a self-hosted Linux server outside Supercraft, the default save path is ~/.config/Epic/FactoryGame/Saved/SaveGames/server/.
Step 3: Open SCIM and drag your save in
In a modern browser (Chrome or Firefox have the best results; large saves above 200 MB can stutter in Safari) open the SCIM interactive map. There is no upload step in the API sense; the page parses the file locally in your browser using WebAssembly. Drag your .sav onto the map. Parsing takes 5-30 seconds for normal saves and up to 2 minutes for very large worlds (1 GB+).
If the parser errors out, the most likely causes are: (1) the save is from a newer game patch than SCIM has parsed yet - reload the page in 24 hours; (2) the save is corrupted and the parser refuses to continue - see the corruption section below; (3) you tried to open a backup .bak file instead of a .sav - only .sav files work.
Step 4: Make your edits
See the per-task table below. Each operation is one to three clicks once you know where to look.
Step 5: Export the modified save
Click Save in SCIM's top bar. A modified .sav file downloads with the suffix _CALCULATOR.sav. You can rename it on download if you want a cleaner filename - just keep the .sav extension.
Step 6: Upload back to the server and start
Upload the modified .sav to the same Saves partition. In the Config tab of the panel, set the active save to the new filename (or rename your file to match the original's name). Click Start. The server loads your edited world and players can rejoin.
Keep the original .sav locally for at least 24 hours after the edit lands. If something went wrong, the rollback is a 30-second upload back to the previous file.
Per-Task Reference
| Task | SCIM operation | Notes |
|---|---|---|
| Teleport a stuck player to HUB | Find the player icon on the map, right-click, "Teleport to HUB" | Works on both dead and live players |
| Move player to specific coordinates | Right-click the player icon, "Edit", set new X/Y/Z values | Z is height; if a player is stuck underground try Z+1000 |
| Revive a Doggo (Lizard Doggo) | Right-click the Doggo icon, "Update Health", set to 100 | Also works on Cyber Wagon and other tamed creatures |
| Mass-delete bugged structures | Pick the lasso (polygon) tool, draw around the area, click "Delete selected" | Verify selection count before clicking; undo is limited |
| Delete a specific building type | Buildings panel โ filter by type โ select all โ Delete | Useful for removing every ghost power pole or every conveyor in a section |
| Unlock all alternate recipes | Research tab โ Alternates โ "Unlock All" | Cheaty; usually used to recover from "I accidentally rolled the wrong alt" |
| Unlock all milestones | Research tab โ Milestones โ "Unlock All" | Skips entire progression; reserve for creative runs |
| Spawn an item into your inventory | Right-click your player icon โ Inventory โ Add Item โ pick from dropdown | Use sparingly on multiplayer servers; visible in event log |
| Spawn a power slug | Player Inventory โ Add Item โ Power Slug (any colour) | Faster than hunting for the last 20 you missed in the world |
| Find a Death Crate | Filter map markers โ "Death Crates" โ click to see contents โ teleport to your position | Recovers stuff you lost when you died in an unreachable location |
| Import a Megaprint (community blueprint) | Megaprints tab โ browse โ select โ "Import to save" | Imported blueprint lands at world origin; teleport it after import |
| Add a hard-drive (research scan) | Items panel โ Hard Drives โ add to inventory | Lets you re-roll an alt-recipe research |
| Inspect production statistics | Statistics tab โ pick item โ see per-machine throughput | Identifies the bottleneck machine in 30 seconds |
The 1.2 Patch Story: What Changed and What Still Works
Satisfactory 1.2 has been rolling out through 2026. The patch timeline:
- 1.2.0.0 - March 17, 2026 (Experimental branch)
- 1.2.1.0 - early April 2026
- 1.2.2.0 - April 28, 2026
- 1.2.2.2 - May 19, 2026 (current as of this article)
The 1.2 line introduced fluid tanker trucks, train signalling refinements, and a series of save-format tweaks. SCIM has tracked every release within a few hours. If you are on the Experimental branch and a brand-new patch dropped this morning, SCIM may still be on the previous version for the first 1-2 hours; reload the page and retry.
1.2 also introduced new edge cases for save corruption around trains (signalling state) and the tanker truck routing graph. These are typically NOT fixable in SCIM because they involve cross-entity relationships the editor does not surface; restoring from a pre-corruption backup is the only safe path.
When Your Save Will Not Open in SCIM
Three categories of failure:
1. Parser error: "Invalid save header"
You uploaded the wrong file. Common mistakes: a .bak file instead of .sav, a .sav.gz from your panel's archive download, or a file that downloaded incomplete (network glitch). Re-download the original .sav and try again.
2. Parser error: "Unsupported version"
Your save is from a patch newer than SCIM has parsed yet. This happens within hours of any Coffee Stain patch. Wait 24 hours and try again; reload the page (Ctrl+Shift+R) to clear cached parser code.
3. Parser hangs or produces a corrupt map
Your save itself is corrupt. Try these in order:
- Try a slightly earlier autosave from the same world. Coffee Stain keeps 5 autosaves; one of them is usually clean.
- If you have a Supercraft daily-backup tier, restore yesterday's snapshot. The panel makes this one click.
- Try Goz3rr's
SatisfactorySaveEditor(the open-source desktop alternative). It has a different parser and sometimes opens what SCIM rejects. - If nothing works, the save is unrecoverable. Restore a 7-day-old backup and forge ahead.
Safe Editing Workflow for Multiplayer Servers
Edits on a single-player save affect you. Edits on a multiplayer server affect everyone. A few rules that have come out of community experience:
- Stop the server. Always. Do not edit a running save. The server overwrites your changes on its next autosave.
- Announce the maintenance window. A Discord ping before you stop the server prevents "the server is down, my factory" panic.
- Back up before editing. Both the panel's automatic backup and a manual local copy of the original .sav.
- Limit the scope of one session. Make one to three coherent changes per edit cycle. Five unrelated edits at once means five times the chance of one introducing a corruption.
- Test by joining alone before announcing "we are back". Two-minute spot check catches the obvious breaks before everyone tries to connect.
- Communicate creative edits. If you spawn power slugs into your inventory, say so. Players notice when one admin advances three tiers overnight and the trust drops fast.
SCIM Versus Goz3rr's SatisfactorySaveEditor
Two community tools dominate save editing. They are different shapes:
| Aspect | SCIM (browser) | Goz3rr SatisfactorySaveEditor (desktop) |
|---|---|---|
| Platform | Browser, any OS | Windows-only .NET application |
| Install | None; load satisfactory-calculator.com | Download from GitHub releases |
| Map view | Full interactive map with everything plotted | Tree-based entity browser, no map |
| Mass operations | Lasso, area, filter selection | Manual entity-by-entity |
| Megaprint import | One-click from a curated library | Not supported |
| Update cadence | Hours after each Coffee Stain patch | Days to weeks; community-maintained |
| Best for | 99% of users, 99% of tasks | Saves SCIM cannot parse; raw entity inspection |
For practical purposes: try SCIM first. If it cannot open your file, try Goz3rr's editor. If neither works, restore from backup.
Common Questions
Does SCIM upload my save to a server?
No. SCIM runs entirely in your browser using WebAssembly. The .sav never leaves your machine. The "upload" terminology is just the browser file-picker dialog; nothing transits the network.
Is editing my own save against the EULA?
No. Coffee Stain has been explicit that editing your own single-player or self-hosted server saves is allowed. Editing official Coffee Stain Hub saves or distributing modified saves of someone else's world is a different matter.
Will SCIM break achievements?
On single-player saves: yes, depending on what you edit. Unlocking milestones or alternate recipes disables the corresponding achievements for that save. On dedicated servers: achievements are per-client, and editing the server save does not directly disable them, but anything you give yourself through SCIM still counts as cheating from Steam's perspective for the achievements still locked.
Does SCIM support mods?
Yes. SCIM tracks 93+ Satisfactory mods (as of May 2026) and parses their custom building, item, and recipe entries. Some very new or very small mods may not have a SCIM definition yet; those entities show as generic "unknown" placeholders.
I deleted something I needed. Can I undo?
SCIM has limited undo within the current session, but once you export and overwrite your save, the deletion is permanent. The recovery path is the .sav backup you took before editing. This is why "back up before editing" is rule 1.
The modified save loads but my factory looks different than I expected.
Compare the modified file's timestamp with the autosave timestamps in the same folder. If a server autosave fired between your stop and your upload, the new file may have been replaced. Re-edit from the actual most-recent autosave, or set the active save explicitly in the Config tab.
Related Satisfactory Server Guides
- Restore from a backup (when SCIM cannot save your save)
- Configure automatic backups
- Memory leak optimization (large factories that grow until they corrupt)
- Performance optimization (factory-load tuning)
- Late-game Linux server optimization
- Patch 1.2.2 update notes
- Train locomotive crash on 1.2.2 (SCIM-related workaround)
- Dedicated server optimization
Need a Satisfactory host where SCIM-based maintenance is one click and backups roll out hourly? see our Satisfactory server hosting plans. Daily auto-backups, panel-managed save downloads, and one-click rollback are included on every tier.