Satisfactory save analyzer: compatibility & limitations
Local, read-only analysis with explicit limits.
Open the Factory Command Centre →
Supported files
The browser importer accepts one Satisfactory .sav or .sbp at a time. A blueprint can include its matching .sbpcfg. Single-player, multiplayer and dedicated-server world saves use the same file format; this is not a live server connection.
Verified save-format versions are 41, 42, 46, 51, 52, 53 and 58. Builds newer than the reviewed 1.2.4.1 build 513885 are rejected until reviewed. Other versions are rejected, including unverified future formats. Current production mathematics is restricted to format 58 (Satisfactory 1.2) base-game saves. Legacy and modded worlds provide locations and saved settings without applying current base-game rates.
What is analysed
- Recognised actor buildings, position, yaw, recipe, clock, amplification and saved producing flags.
- Configured recipe inputs/outputs and average production power using the existing SatisGrid engine.
- Saved conveyor, pipeline and power-wire connections where both endpoints resolve.
- Suggested nearby facilities, building inventories where recognised, and blueprint header material costs.
- Missing recognised input connections, a production output exceeding its directly connected belt, unbranched supply-route capacity checks, and capacity comparisons for fully resolved power circuits.
- Two compatible snapshots, compared by object reference for added/removed buildings and changed configuration or position.
What remains unknown
Installed capacity is not achieved production. A save is a snapshot, not telemetry. Resource purity and extraction capacity are unknown unless both resource and purity are recoverable from that save. We do not assume the default map when nodes may have been randomised.
Fluid head lift, backflow, sloshing, valve/pump behaviour, mixed-item splitter routing, loops, scheduled freight, drone throughput and complete power-switch topology are not simulated. A zero-issue report does not certify a balanced factory. Lightweight foundations and walls are counted separately from map actor buildings. Unknown binary properties remain in the original file and are not rewritten.
Safe handling of files
Parsing and analysis run in an isolated Web Worker. The decompressor checks chunk lengths and expanded memory budgets before allocation; strings and collection counts are bounded. Cancel terminates the worker. Parser errors are translated into safe messages instead of exposing raw player information.
Device memory hints determine a conservative expanded-file budget. On browsers without a hint, desktop uses a 128 MB expanded budget and small-screen devices use 32 MB. A file may be rejected even when another device can open it. This protects the surrounding planner, but cannot guarantee every browser will have enough free memory.
Nothing is uploaded or stored automatically. Optional browser-local notes include only facility names and acknowledged issue references. Exported JSON reports contain the world name, statistics, machine settings, connection references, issue evidence and building coordinates; review them before sharing. Closing a world or the tab discards its analysis. Account factory saves are separate.
Expansion planning
The expansion tool calls the existing SatisGrid production calculator. It compares your recognised configured output with a fresh additional production line. It does not assume surplus ingredients are available, change existing saves or claim to optimise all existing machinery. Review recipe choices, supplies and limits in the main planner.
Save and blueprint editing
No binary editing or modified-file export is enabled. Every released edit will need original-file protection, reference validation, round-trip checks, and successful load tests in the supported game version. Those in-game tests have not been performed for this release. Keep backups outside the site.
Parser and licensing
satisfactory-file-parser 4.1.2 is MIT licensed. Its browser-compatible TypeScript implementation supports world saves and blueprints. SatisGrid applies bounded decompression and reader guards to the pinned package. Pako 2.1.0 provides zlib decompression; licence notices are bundled.
The C# SatisfactorySaveNet project would require a different browser runtime. SMLVE’s desktop editor is not used; a commercial-reuse licence was not established during this audit. No code from either was copied.
Game data and artwork retain the attribution shown elsewhere in SatisGrid. The imported-world map uses an original coordinate-grid renderer, without third-party terrain assets.
Verification
Read the automated fixture and performance results. These local-development timings are indicative, not promises for every device. The original byte buffers are checked for mutation. Corrupt, truncated, oversized and unverified-version inputs are rejected. Synthetic diagnostics fixtures are used only in tests, never as user report data.
Enormous megabases, arbitrary mods and dedicated-server-specific gameplay scenarios still need broader real-world testing. No in-game edited-save tests have been performed because no editing operation is released.
Open the factory planner →