Tomodachi Life: Living the Dream

Yes, a bad edit can corrupt your save and there's no in-game recovery, so the only way back is the backup you made before editing.

The editor does a few things to prevent corrupting your save:

• It never overwrites your original file, it creates a new one for you to download, so if something goes wrong the original is still safe.
• The editor will block some edits that are known to cause corruption, and warn you about risky ones.

Yes, always. Copy your Mii.sav, Player.sav, and Map.sav files somewhere safe before loading them here. A bad edit can corrupt your save with no in-game recovery, and the only way back is the backup you made.

No. The editor runs entirely in your browser, files are parsed and rewritten locally, and your save data isn't sent to any server.

The site is also open source, so you can read the code yourself on GitHub.

The game splits its data across three files, and the editor has a tab for each:

• Player.sav - your player data: your name, island name, money, play time, everything you unlocked...
• Mii.sav - per-Mii data for everyone living on your island: personalities, voices, relationships...
• Map.sav - the layout of your island: where each building is placed, what each tile on the ground is...

The three files are independent, you can edit one without touching the others, and you only need to upload the ones you actually want to change.

The structured tabs (Player, Mii, Map) cover the fields the editor knows how to render with proper labels and pickers. The Advanced section, found at the bottom of each tab, is a raw entry browser that lists every key found in the save, including ones that haven't been mapped to a friendly UI yet. Use it if you need to inspect or edit something the structured tabs don't expose.

Treat it as power-user territory. Some fields are cryptic, and editing them blindly is a good way to corrupt a save, back up first. Anything done here is at your own risk.

Save files reference content (clothes, food, treasures, room styles, and so on) by hash, not by readable name. The editor ships a hash list that translates as many of those hashes as possible back into names. When an entry shows up as a hex number or as "Unknown", it's a hash that isn't in the list yet. If you identify one, please open an issue or share it on Discord so it can be added for everyone.

• Stable (ltdsave.app) - the version you should probably use. This is the tested, polished version of the editor, where features are less likely to be broken and bugs are less likely to cause corruption. Useful for most people, especially if you're new to save editing.
• Beta (beta.ltdsave.app) - the experimental build, where new features land first. Expect more bugs and occasional broken behaviour. Useful if you want to try something that isn't on Stable yet, or if a fix you reported has just been merged.

You can switch between the two using the link next to the version badge in the header. Whichever you pick, always back up your saves first.

See the Adding a Localization section in the repo's README, it has the full set of steps.

Please open an issue on GitHub, the "Report an issue" link in the footer takes you straight to the new-issue form, or you can use this link. Helpful things to include:

• What you were trying to do.
• What happened instead.
• Whether you were on Stable or Beta, and the version number from the header.
• A screenshot if it's a UI issue.
• The save file itself if you're comfortable sharing it. Saves help reproduce a bug a lot faster than descriptions alone.

If you'd rather not file an issue, the Discord works too.

If something you want to edit isn't in the structured tabs, it's almost always one of two things:

• Nobody has mapped that field to the editor yet, the data is in the save, but no UI has been built for it.
• The field can't be edited safely on its own, it might be derived from other values, or part of a structure where changing one piece without the rest would corrupt the save.

Either way, the right move is to open an issue or ask on Discord describing what you're trying to change. New features get prioritised based on what people actually want.