What is an N64 Controller Pak?

The Controller Pak is the Nintendo 64's memory card. It plugs into the bottom of the controller and stores game saves on a 32 KB filesystem of 128 pages. It is often called a memory pak or memory card.

What save files does this reader open?

Raw .mpk Controller Pak dumps and DexDrive .n64 backup files, up to the full 32 KB card image.

Does my save file get uploaded anywhere?

No. The reader runs entirely in your browser using typed arrays, so the file never leaves your device.

Can it fix a corrupted Controller Pak save?

It can safely restore redundant ID or allocation-table metadata when one checksum-valid copy is authoritative. If both copies are invalid or disagree, it stays read-only rather than guessing. It does not repair corruption inside a game's save payload.

How do I get a .mpk file from my real Controller Pak?

Export the 32 KB card image with a Controller Pak dumper such as a DexDrive, a flashcart save tool, or a compatible adapter, then drop the file here.

How are the game values estimated?

Each value is a rough collector range for a loose cartridge and a complete-in-box copy, rounded from recent public sales on eBay and PriceCharting and refreshed periodically. The eBay and PriceCharting links show the live numbers.

N64 Controller Pak Reader

Inspect N64 Controller Pak saves locally, recover redundant filesystem metadata when a trusted copy exists, and keep ambiguous cards safely read-only.

Drop in a real Controller Pak save and every note decodes: names in the console's own character set, resolved game titles, the publisher, and the page footprint of each save.

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.

Info

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, and validates redundant filesystem metadata. Repair is deliberately conservative: a checksum-valid copy can restore its damaged twin, while ambiguous cards remain read-only. Everything runs client-side with typed arrays, so saves never leave the browser. The collection shelf also surfaces rough low-high market estimates for marquee titles, loose and complete-in-box, with one-tap links to find a copy on eBay or see full price history on PriceCharting.

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
Recovery-safe metadata repair that refuses to guess when redundant copies are ambiguous
Visual page map of all 128 pages, plus a built-in sample pak to explore
Collection shelf with 296 classic titles, tracked in LocalStorage
Low-high value estimates (loose and CIB) for ~25 marquee titles, with coverage and vintage shown

Frequently Asked Questions

What is an N64 Controller Pak?: The Controller Pak is the Nintendo 64's memory card. It plugs into the bottom of the controller and stores game saves on a 32 KB filesystem of 128 pages. It is often called a memory pak or memory card.
What save files does this reader open?: Raw .mpk Controller Pak dumps and DexDrive .n64 backup files, up to the full 32 KB card image.
Does my save file get uploaded anywhere?: No. The reader runs entirely in your browser using typed arrays, so the file never leaves your device.
Can it fix a corrupted Controller Pak save?: It can safely restore redundant ID or allocation-table metadata when one checksum-valid copy is authoritative. If both copies are invalid or disagree, it stays read-only rather than guessing. It does not repair corruption inside a game's save payload.
How do I get a .mpk file from my real Controller Pak?: Export the 32 KB card image with a Controller Pak dumper such as a DexDrive, a flashcart save tool, or a compatible adapter, then drop the file here.
How are the game values estimated?: Each value is a rough collector range for a loose cartridge and a complete-in-box copy, rounded from recent public sales on eBay and PriceCharting and refreshed periodically. The eBay and PriceCharting links show the live numbers.

About this project

Binary ParsingSave ForensicsCollection ManagerAngular Signals

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
Recovery-safe metadata repair that refuses to guess when redundant copies are ambiguous
Visual page map of all 128 pages, plus a built-in sample pak to explore
Collection shelf with 296 classic titles, tracked in LocalStorage
Low-high value estimates (loose and CIB) for ~25 marquee titles, with coverage and vintage shown

Frequently Asked Questions

What is an N64 Controller Pak?: The Controller Pak is the Nintendo 64's memory card. It plugs into the bottom of the controller and stores game saves on a 32 KB filesystem of 128 pages. It is often called a memory pak or memory card.
What save files does this reader open?: Raw .mpk Controller Pak dumps and DexDrive .n64 backup files, up to the full 32 KB card image.
Does my save file get uploaded anywhere?: No. The reader runs entirely in your browser using typed arrays, so the file never leaves your device.
Can it fix a corrupted Controller Pak save?: It can safely restore redundant ID or allocation-table metadata when one checksum-valid copy is authoritative. If both copies are invalid or disagree, it stays read-only rather than guessing. It does not repair corruption inside a game's save payload.
How do I get a .mpk file from my real Controller Pak?: Export the 32 KB card image with a Controller Pak dumper such as a DexDrive, a flashcart save tool, or a compatible adapter, then drop the file here.
How are the game values estimated?: Each value is a rough collector range for a loose cartridge and a complete-in-box copy, rounded from recent public sales on eBay and PriceCharting and refreshed periodically. The eBay and PriceCharting links show the live numbers.