A safer Freelancer savegame editor for singleplayer pilots, mod users, and savegame testing.
| Build | Best for | Download |
|---|---|---|
| Windows x64 | Most Windows PCs | FLAtlas-Savegame-Editor-v0.9.1-windows-x64.zip |
| Windows ARM64 | ARM-based Windows devices | FLAtlas-Savegame-Editor-v0.9.1-windows-arm64.zip |
| Release page | Changelog, checksums, older builds | GitHub Releases |
| ModDB mirror | Freelancer community download page | FL Atlas Savegame Editor on ModDB |
Download the ZIP, extract it to a folder, and start the editor from the extracted folder.
FLAtlas Savegame Editor is a standalone editor for Microsoft Freelancer singleplayer .fl save files. It helps with repair work, progression edits, loadout testing, mod savegame checks, and safe inspection of raw savegame data.
The editor reads game data from your selected Freelancer or mod installation, so systems, bases, factions, ships, equipment, commodities, jump gates, and jump holes can match the install you are actually playing.
- Edit credits, rank, description, current system, current base, player faction, and Trent appearance.
- Inspect and adjust ship setup, core components, equipment entries, hardpoints, weapons, shields, thrusters, cargo, and commodities.
- Work with reputation, discovered objects, visited systems, locked gates, and Freelancer universe data.
- Resolve labels from vanilla Freelancer, Freelancer HD Edition, and modded installations.
- Validate savegames and keep unresolved or unknown rows visible instead of silently discarding them.
- Creates backups before writing savegame changes.
- Preserves encrypted
FLS1savegames when saving. - Keeps unknown savegame rows round-trippable where possible.
- Blocks risky edits while Freelancer is running.
- Warns about compatibility issues before saving.
Keeping a personal backup of important savegames is still recommended, especially before large experimental edits.
This GitHub repository is the public download and information page for FLAtlas Savegame Editor. Release assets are published through GitHub Releases. Development happens privately; this public repository intentionally does not contain the full source tree.
Bug reports, feature requests, and release questions can be submitted through GitHub Issues.