# NMSSaveEditor: a Java save editor for No Man's Sky (WORLDS)

> NMSSaveEditor reads and writes No Man's Sky save files through a desktop UI, covering inventories, ships, frigates, settlements and raw JSON. It is built for players who want to undo a broken quest or skip the grind, and it requires a JRE 8 install and a manual backup habit.

**goatfungus/NMSSaveEditor** — No Man's Sky - Save Editor

- Repository: https://github.com/goatfungus/NMSSaveEditor
- Stars: 2,673 · Forks: 296
- Language: Unknown
- License: not declared
- Published: 2026-09-28 · Updated: 2026-09-28 · Language: en
- Canonical page: https://hysenlabs.com/projects/goatfungus-nmssaveeditor

## What NMSSaveEditor fixes, and who it is for

No Man's Sky has a history of progress-blocking bugs and systems that demand long resource loops. The README describes the author's own path: after finding an existing save editor that was limited and easy to corrupt a save with, he rewrote it in Java with a simpler interface and released it publicly. That origin explains the shape of the tool. It is a single-player save file editor, not a mod loader and not a memory trainer. It targets the WORLDS version of the game and supports Steam/GOG, PS4 through Save Wizard, and MS Game Pass on Xbox.

The audience is narrow but real. If a mission flag is stuck, if a settlement is in debt, if you want a specific multitool class without another twenty hours of searching, this tool edits the underlying data directly. The feature list is broad: currencies (Units, Nanites, Quicksilver), base stats for Exosuit, Multitools, Ships and Freighter, squadron wingmen, frigates, companions, settlements, milestones and reputation. It also handles inventory organisation across Exosuit, Multitools, Ships, Freighter, Vehicles and Base Storages, with drag and drop, right-click move menus, cloning with CTRL plus drag, repair and recharge, and inventory resizing.

## How the editor touches a save file

The working model is straightforward: the editor opens the save folder you point it at, reads the save, and presents the parsed contents as editable screens. Each screen maps to a slice of the save data. The Exosuit screen edits suit stats and inventory, the Ships screen edits ship type, class and seed, the Settlements screen edits population, happiness, production, upkeep and debt, and so on. There is also a raw JSON editor for advanced users, which is the honest admission that the UI cannot cover every field in a game that keeps changing.

Two mechanisms matter more than the field list. First, automatic backup and recovery of all saves. The README presents this as protection "in case you screw up something", which is the right framing for a tool that writes to the only copy of your progress. Second, backup and restore of Base and Freighter structures, described as usable across different systems or saves. That is a different capability from editing a value: it copies a structure out and back in, which is how players move a base between saves rather than rebuilding it.

The inventory model has a documented boundary. The README lists vanilla limits as Cargo 10x12, Technology 10x6 and Base Storage 10x5, then states in bold that you can go above this but the game might break. Treat that as the tool telling you where its own safety ends. It will let you write a value the game cannot load.

## Installing NMSSaveEditor and making a first edit

There are two installation routes, and the README is explicit about why the second exists. Option 1 is the self-extracting archive. Download the latest NMSSaveEditor.exe, run it, and extract the contents into an empty folder. The README warns that some antivirus products falsely flag that EXE, and points affected users to option 2. Option 2 is the manual zip: download NMSSaveEditor.zip, open it with 7-Zip or WinRar, and extract to an empty folder. The README says in capitals not to run the program from inside the zip file.

Both routes need Java Runtime Environment 8. On PS4 you also need Save Wizard. Once extracted, the README describes running the bat file, or the jar file if the .jar extension is associated with Java. After the main window opens, locate the folder that holds your saves and choose the most recent one. The README's own sequence is: locate the folder, choose the most recent save, then start tinkering.

A first edit should be small enough to verify. Open the Exosuit screen, change one currency value, and save. Then reopen the save in the editor and confirm the new value is there before touching anything structural. If something looks wrong, the automatic backup is the recovery path. For a structural change, the safer first exercise is exporting a multitool or ship rather than deleting one, because export and import are reversible in a way that deletion is not.

## Where the tool stops being the right choice

The clearest limitation is platform. The README lists Steam/GOG, PS4 via Save Wizard, and MS Game Pass. A search result asking for a good No Man's Sky save editor for Linux is not answered by this project: the README gives no Linux instructions, no package, and no platform-specific build. Java runs on Linux, but the README does not document that path, and this article will not pretend it does.

The second limitation is the inventory ceiling. The editor exposes resizing and slot enabling, and the README simultaneously warns that exceeding the vanilla limits can break the game. A tool that lets you do a thing and warns you not to is a tool with a sharp edge. The third is the raw JSON editor. It is labelled for advanced users only, which is accurate: a save file is structured data with relationships between records, and editing one field in isolation can leave the save internally inconsistent.

Finally, the release and maintenance picture. The repository is not archived, and the last push was on 2026-06-05. There are no retrieved releases, so version tracking happens through VERSION.txt and CHANGELOG.md rather than a release feed. The README states an intention to keep maintaining the tool as long as there is interest in the game, and links a Patreon page for contributions. That is a stated intention from the author, not a published support commitment.

## NMSSaveEditor compared with a web-based editor

The natural alternative is a browser-based save editor, the kind that parses an uploaded save in a page. The difference in approach is where the data lives. NMSSaveEditor is a local Java application: you point it at your save folder, it reads and writes files on your machine, and it keeps its own automatic backups there. A web editor requires you to upload the save to someone else's server, which changes the trust question entirely. For a file that represents hundreds of hours of play, keeping it local is a defensible default.

The trade-off runs the other way too. A local Java application means installing Java Runtime Environment 8 and dealing with an EXE that antivirus products may falsely flag, as the README itself notes. A web editor has no install step. NMSSaveEditor also carries version coupling: the README is written for WORLDS, and previous releases are archived in the repository under names like Atlas Rises (1.3), Next/Visions (1.5), Beyond (2.0), Adrift (4.5) and a Legacy UI branch. That archive is useful if you are on an older game version, and it is also evidence that the tool has to be re-pointed at the save format each time the game moves.

## Licence, maintenance and the cost of upgrading

The repository metadata does not state a licence, and there is no LICENSE file in the top-level entries. The README says the tool will always be released publicly for free and links a Patreon page for contributions. Free to download and open source with a named licence are different things, and anyone planning to redistribute the binary, bundle it, or build on the code should treat the absence of a licence file as an open question to resolve with the author rather than an implied permission. This is a factual gap, not legal advice.

Upgrade cost is mostly game-version cost. The README is titled for WORLDS, and the repository keeps prior-version READMEs under separate branches, which tells you the editor is versioned against the game rather than against a stable save format. When the game updates, the editor may need a matching update before it can read new saves. The practical consequence: keep the previous NMSSaveEditor build you were using until you have confirmed the current one opens your save correctly. The automatic backup covers a bad edit; it does not cover a version mismatch, because a save written by a newer game build may not be readable by an older editor at all.

## Conclusion

Adopt NMSSaveEditor if you play No Man's Sky on Steam, GOG, PS4 with Save Wizard, or Xbox Game Pass and you want to repair a stuck save or skip a grind loop. Do not adopt it if you cannot install Java Runtime Environment 8, if you expect a supported Linux build, or if you are unwilling to keep your own copy of the save folder. Before your first edit, confirm which save folder the game writes to, keep the automatic backups the tool makes, and stay at or below the vanilla inventory limits the README lists (Cargo 10x12, Technology 10x6, Base Storage 10x5), because the README warns that going above them can break the game.

## FAQ

### Can you get banned for save editing in No Man's Sky with NMSSaveEditor?

The README does not discuss bans or anti-cheat. It describes the tool as a save file editor supporting Steam/GOG, PS4 via Save Wizard, and MS Game Pass, and frames it around fixing bugs and skipping grind. It makes no claim about online consequences, so this article cannot either.

### Is there a good No Man's Sky save editor for Linux?

The README does not document a Linux build or Linux instructions. It lists Steam/GOG, PS4 via Save Wizard, and MS Game Pass as supported platforms, and requires Java Runtime Environment 8, but the documented launch steps are a bat file or the jar file on Windows.

### Is the NMS save editor safe?

The README states that some antivirus solutions falsely flag the self-extracting NMSSaveEditor.exe as a virus, and offers a manual zip download as an alternative. It also states that the editor makes automatic backups of all saves for recovery. It does not make a security claim beyond that.

### how to use nmssaveeditor

Extract the archive to an empty folder, run the bat file or the jar file, then locate the folder holding your saves and choose the most recent one. From there you edit screens such as Exosuit, Multitools, Ships, Freighter, Frigates, Companions, Settlements, Milestones and Account, or the raw JSON for advanced use.

### how to install nms save editor

Option 1 is to download NMSSaveEditor.exe, run it, and extract the contents to an empty folder. Option 2 is to download NMSSaveEditor.zip, open it with 7-Zip or WinRar, and extract to an empty folder, without running the program from inside the zip. Both need Java Runtime Environment 8, and PS4 needs Save Wizard.

### what is nms save editor

It is a Java desktop application that reads and writes No Man's Sky save files. The README describes editing currencies, base stats for Exosuit, Multitools, Ships and Freighter, squadron wingmen, frigates, companions, settlements, milestones and reputation, plus inventory management and a raw JSON editor.

## Sources

- [goatfungus/NMSSaveEditor on GitHub](https://github.com/goatfungus/NMSSaveEditor)
- [Issues](https://github.com/goatfungus/NMSSaveEditor/issues)
- [README](https://github.com/goatfungus/NMSSaveEditor/blob/master/README.md)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/goatfungus-nmssaveeditor