This document explains what “redump SNES” means, why it matters, legal and ethical considerations, tools and workflows, best practices for archival-quality dumps, verification, metadata, preservation, and community resources. It’s written for preservationists, retro collectors, and technically minded users who want to create accurate, verifiable Super Nintendo (SNES/Super Famicom) disc/cartridge images for long-term archival and research.
The process of creating a Redump-verified SNES ROM is painstaking:
Hardware Acquisition – A dumper like the Sanni Cart Reader (open-source) or INL-retro-prog is used. These devices read the cartridge’s ROM chip directly via the cartridge slot. redump snes
Initial Dump – The dumper reads the entire ROM address space (e.g., 4 Mbit for Super Mario World, 48 Mbit for Tales of Phantasia). It does this multiple times to ensure consistency.
Hashing – The dumped file is run through SHA-1 and CRC32 algorithms to create a unique digital fingerprint. Redump SNES — A Practical Treatise This document
Verification – The dumper submits their hash to Redump’s internal database. If the hash matches a previously verified dump (from a different physical cartridge), the ROM is confirmed good. If not, at least two more independent dumps from separate cartridges are required.
Release – Once verified, the ROM is listed in Redump’s datfile (an XML file containing names, hashes, and sizes) but Redump does not host ROMs — they only distribute datfiles. Hardware Acquisition – A dumper like the Sanni
Because Redump does not distribute ROMs, you have two legal options:
To contribute to the database, the following data packet is required:
.sfc file (zipped).