Validate before rewriting.
Future editing tools should understand what a value means and verify the resulting file before a player trusts it.
About EditorSaves
About EditorSaves
Learn about EditorSaves, the project building a universal game save editor by studying real save files, engine formats, parser needs, and difficult edge cases.
The mission
Build the tool around real-world save data, not assumptions.
Game saves are not one format. They can be JSON, SQLite, XML, engine-specific binary data, compressed payloads, or a mixture of several layers. Two games using the same engine can still structure progress differently.
EditorSaves therefore starts with collection. Real samples can reveal version differences, field layouts, compression patterns, and edge cases that documentation alone does not capture.
- Make save-file workflows accessible from a browser.
- Learn from real formats before promising universal editing.
- Keep validation, backups, and transparency central to future editing.
- Design for players, hobbyists, and technical users alike.
A careful approach
Save files can represent hours of progress.
That makes reliability a product feature, not a later refinement.
Keep originals protected.
Backups and clear recovery paths help prevent a single mistake from turning into lost progress.
Explain what happens.
Users should understand what the site accepts, what it stores, what it changes, and what it does not yet support.