Where Your Breath of the Wild Progress Actually Lives
The save data for Zelda: Breath of the Wild on the Nintendo Switch is not stored in a single file you can simply copy and paste. It is scattered across multiple save slots in the system's NAND memory, encrypted and tied to the console's unique keys. That means a straightforward backup by dragging folders off the SD card will almost never give you a working restore. The data you need is locked inside memory regions that the game itself reads at runtime, and those regions sit at fixed offsets relative to the console's title ID. If you have lost a save file—maybe the NAND corrupted, maybe you accidentally formatted the user account, maybe the game crashed mid-save—you have to locate the raw encrypted block, decrypt it with the correct save key, and repackage it into a format the Switch will accept. The process is tedious, but the steps are repeatable if you know where to look.
Unlocking Botw Memory Location The Definitive Guide To Finding Your Lost Save Data
That string shows up in a few older forum threads and GitHub repos when people are digging into Switch memory editing tools. It is basically shorthand for the idea that there is a published table of memory offsets where BotW stores its save data, and that you can use that table to jump straight to the right region without scanning the entire dump. I rely on the same concept, though I usually supplement the old tables with a live search for the save header signature rather than blindly trusting a static address list. The core offsets haven't moved much across minor patches. The major shifts happen when Nintendo changes the save encryption scheme between major game versions. I have seen people spend hours trying to decrypt a dump from a 1.0.0 save with keys meant for 1.7.0, only to get garbled output every time. Subtract the version delta first, then apply the key.
How to Actually Find the Save Block
Step one is to get a raw NAND dump or a homebrew-app extract of the relevant save slot. If you are on custom firmware, a tool like MakeSave or SaveMFC can pull the encrypted save data for a specific title ID. If you already have a NAND backup, you can open it in a hex editor and search for the BotW save signature. The signature is not the same as the file header you would see in a decrypted backup; it is a pattern of bytes that appears at the start of each encrypted save block inside the NAND. I use a quick pattern search for the bytes that precede the known save metadata. In practice, that means searching for a short sequence like the ASCII string SWCH followed by a few null bytes, then backing up until you hit the block boundary. The exact offset varies by console model and firmware version, so do not assume the address you find in one tutorial will work on your system. Write down the absolute address from your dump, not the relative offset from some generic table. Once you have the raw encrypted block, you need the save key for that specific title. The save key lives in the console's title key database, which is normally inaccessible on a stock Switch. With CFW, you can extract it using a tool like prod.keys, but you must ensure the keys match the firmware version of the dump you are working with. Mismatched keys produce garbage output that looks like corruption, and you will waste time wondering whether the block is broken.
Get the Full Details
What the Guides Leave Out
The first thing I run into when someone sends me a recovered block is that the data is split. BotW stores the main quest progress in one region and the character inventory, armor, and weapon durability in another. They are separate save slots under the hood, even though they belong to the same playthrough. If you only decrypt the first block, you will restore a save that has no items and no completed shrines, which looks like a brand-new game. Another common trap is assuming the memory layout is identical across all Switch revisions. The OLED model and the original V1 unit sometimes have different padding in the NAND layout, which shifts the apparent offsets by a few dozen bytes. I learned that the hard way after I followed a guide to the letter and got a CRC mismatch on every attempt. The workaround was to compare the byte pattern around the signature with a known-good dump from a friend who had the same game version, then adjust the boundaries until the header checksum verified. You also need to check whether the save is flagged as cloud-enabled. If the game had automatic cloud sync turned on, Nintendo may have already stored a copy on their servers. In that case, deleting the local save and forcing a redownload from the cloud is faster than any manual memory surgery. I have done the cloud reset more times than I care to admit because it saves an hour of hex editing.
Decryption and Repackaging
After you have the correct encrypted block and the matching save key, you run it through a BotW save decryptor. Tools like BotW Save Editor or the newer open-source forks can handle this, but they expect the input to be in a specific binary format. If your dump includes padding or extra headers, trim it down to the pure save block first. I usually write a small Python script that strips anything before the signature and after the next known boundary marker, then feeds the result into the decryptor. The decryptor outputs a JSON-like structure with all the in-game values. At this point you can edit health, inventory, completed dungeons, or whatever you need to restore. After editing, you re-encrypt the block with the same key and feed it back into a homebrew save writer. The writer will patch the data into the correct NAND slot, but you must verify the checksum afterward. If the checksum fails, the game will refuse to load the save and may even mark the slot as corrupted. I always run a quick hex comparison between the re-encrypted block and a known-working backup to catch typos in the offset math.
When This Approach Fails Completely
This method requires either a NAND dump or direct memory access through custom firmware. On a stock Switch, you cannot read another application's save data without jailbreaking, period. Even with CFW, some saves are protected by the save encryption layer, which means you need the title key for that exact game version. If you do not have the key, you cannot decrypt the block, no matter how cleanly you locate it. There is also a bricking risk if you write corrupted data back into the wrong NAND region. I have seen people accidentally overwrite the save slot for a different title because they misidentified the boundary. The console will still boot, but the game will crash on launch and the save slot will appear empty. Recovery then requires a full NAND restore from backup, which is a much larger undertaking than fixing a single save file. If you do not have a recent NAND backup and your current save is already corrupted, manual memory extraction may be your only option, but you should weigh that against the possibility of causing further damage. In many cases, contacting Nintendo support for a cloud restore or a professional data recovery service is safer, even if it costs money and takes longer.
Practical Notes for Doing This Yourself
Keep a log of every offset you use and the firmware version of the dump. The moment you switch to a different game patch or a different console, those offsets become invalid. I use a simple spreadsheet with columns for title ID, firmware, NAND version, signature offset, block size, and save key file name. It cuts the process down from a two-hour guess to maybe twenty minutes once you have the pattern memorized. Always verify your decrypted save in a safe environment before writing it back. Run the save editor in offline mode, load the game in a sandboxed environment if you have one, and check that the in-game values match your expectations. If something looks off, do not proceed to the write step. A bad write can corrupt the entire save slot, and there is no undo button inside the NAND. Finally, do not treat any online table as absolute truth. The community updates these tables regularly, and the older guides are often outdated. Cross-reference with at least two recent sources, and when in doubt, search for the actual byte pattern in your own dump rather than trusting a remembered address. That habit alone has saved me more than once.
