N64 Memory Pak

A browser-based parser for the N64 Controller Pak filesystem. Drop in a real .mpk file and it walks the inode chains, decodes note names in the console's own character set, and repairs most corruption in one click.

N64 Memory Pak preview
Drop in a real Controller Pak save and every note decodes: names in the console's own character set, resolved game titles, and links to each game's community decompilation project.
Drop in a real Controller Pak save and every note decodes: names in the console's own character set, resolved game titles, and links to each game's community decompilation project.
All 128 pages of the 32 KB filesystem, color-coded by owner. Fragmented save chains show up exactly the way they sit on the card.
All 128 pages of the 32 KB filesystem, color-coded by owner. Fragmented save chains show up exactly the way they sit on the card.

About this project

Binary ParsingSave ForensicsCollection ManagerAngular Signals
The collection shelf came first. Then I wanted the project to earn its name, so I wrote a parser for the Controller Pak's actual on-card filesystem: 32 KB, 128 pages, 16 note slots, checksummed ID blocks. It walks the allocation table, decodes note names using the console's own character set, flags corruption, and can usually repair it. Everything runs client-side with typed arrays, so saves never leave the browser.
  • Reads real .mpk and DexDrive .n64 save files in the browser
  • Walks the pak filesystem: inode chains, note table, and ID block checksums
  • Decodes note names with the N64's own font code, katakana included
  • One-click repair for corrupted checksums and desynced backups
  • Visual page map of all 128 pages, plus a built-in sample pak to explore
  • Collection shelf with 296 classic titles, tracked in LocalStorage
N64 Memory Pak screenshot 1