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?

It opens exact 32,768-byte raw Controller Pak images saved as .mpk, .pak, or .bin, plus exact 36,928-byte DexDrive .n64 backups. Cartridge save files such as .eep, .sra, and .fla are different formats.

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.

Where can I find free N64 games to try?

The FAQ's free-homebrew shelf links to a short list of creator-hosted ROM releases with clear licenses. They run in an emulator or on compatible flashcart hardware; the Pak Reader does not run games.

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

Drop in a Controller Pak backup and see what is actually on it. If the filesystem metadata is damaged, the reader only offers a repair when the good copy is clear.

Load a Pak and the reader walks you through the safe order: confirm what opened, check the filesystem, then save a copy before replacing it. Every note still shows its decoded name, game, publisher, and page footprint.

All 128 pages of the 32 KB filesystem, color-coded by owner. Use Inspect beside a note to connect the friendly save list to the exact page chain on the card.

Info

The collection shelf came first, but once I called this a Controller Pak project, I wanted it to actually understand one. The reader now opens the card's real 32 KB filesystem, follows each save through the allocation table, decodes the original N64 character set, and checks both copies of the important metadata. It will repair a bad backup only when the other copy is trustworthy; if the answer is murky, it stays read-only. Nothing is uploaded. I also kept the cartridge shelf, added a short directory of free homebrew you can genuinely download, and made the difference between those games and commercial-game source reconstructions explicit.

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
A simple loaded / checked / saved workflow, with unsaved-edit protection when switching files
Visual page map of all 128 pages, plus a built-in sample pak to explore
Verified free-homebrew shelf kept separate from commercial-game source reconstructions
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?: It opens exact 32,768-byte raw Controller Pak images saved as .mpk, .pak, or .bin, plus exact 36,928-byte DexDrive .n64 backups. Cartridge save files such as .eep, .sra, and .fla are different formats.
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.
Where can I find free N64 games to try?: The FAQ's free-homebrew shelf links to a short list of creator-hosted ROM releases with clear licenses. They run in an emulator or on compatible flashcart hardware; the Pak Reader does not run games.
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
A simple loaded / checked / saved workflow, with unsaved-edit protection when switching files
Visual page map of all 128 pages, plus a built-in sample pak to explore
Verified free-homebrew shelf kept separate from commercial-game source reconstructions
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?: It opens exact 32,768-byte raw Controller Pak images saved as .mpk, .pak, or .bin, plus exact 36,928-byte DexDrive .n64 backups. Cartridge save files such as .eep, .sra, and .fla are different formats.
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.
Where can I find free N64 games to try?: The FAQ's free-homebrew shelf links to a short list of creator-hosted ROM releases with clear licenses. They run in an emulator or on compatible flashcart hardware; the Pak Reader does not run games.
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.