ROM Patching Guides
How to apply a ROM hack, fan translation or bug-fix patch, with notes for each console and fixes for the most common problems.
Patching in four steps
A patch file doesn't contain a game. It is a list of changes that turns one specific, unmodified ROM into a modified one. That is why you always need two files: your own clean ROM and the patch.
- ROM: choose your original, unmodified ROM file.
- PATCH: choose the patch file. If it came in a .zip, extract it first.
- APPLY: the patcher builds the modified game in your browser. Read any warning it shows.
- DOWNLOAD: save the new file and open it in your emulator or flash cart.
Your original ROM is never changed. The patched game is saved as a new file named after the ROM and the patch, for example Fire Emblem(Patch v1.1).gba.
Finding the right ROM version
Most patch problems come from using a different version of the game than the patch author used. Games often exist in several regions (USA, Europe, Japan) and revisions (such as "Rev 1"), and a patch made for one usually breaks the others.
- Read the patch's readme. Good patches name the exact version they need and often list a checksum (CRC32, MD5 or SHA-1).
- Compare checksums. When you load a ROM, this site shows its CRC32. If the readme lists a CRC32 and it matches, you have the right file.
- Trust the warning. BPS, UPS, xdelta, PPF, APS and RUP patches carry their own checksums. If the patcher says your ROM doesn't match, the result will very likely crash or glitch.
IPS patches have no checksum, so the patcher can't tell if you have the wrong ROM. With IPS, checking the readme is especially important.
NES / Famicom
NES ROMs (.nes) start with a 16-byte "iNES" header that tells emulators how the cartridge is wired. Nearly all NES patches are made for ROMs that include this header, so a normal .nes file is what you want. Most NES patches are IPS; newer ones are often BPS.
SNES / Super Famicom
Some SNES ROMs (.sfc or .smc) carry an extra 512-byte "copier header", left over from 1990s backup devices. Patches are made either with or without it, and using the wrong kind shifts every change by 512 bytes, which ruins the game.
- You can tell a ROM has a copier header if its size is a whole number of kilobytes plus 512 bytes (for example 1,049,088 bytes instead of 1,048,576).
- For BPS and UPS patches, this site detects a copier header and removes it automatically if the patch expects a headerless ROM.
- For IPS patches, check the readme. Most modern patches expect a headerless ROM, usually named
.sfc.
Game Boy, Game Boy Color & Game Boy Advance
These ROMs (.gb, .gbc, .gba) have no extra headers to worry about, so patching is usually simple. Many GBA hacks, including most Pokémon and Fire Emblem hacks, use UPS or BPS patches. These check that you have the right ROM.
Avoid "trimmed" GBA ROMs, where empty space at the end was cut off to save room. Patches expect the full-size original.
Nintendo 64
N64 ROMs come in three byte orders that contain the same game arranged differently:
| Extension | Byte order | First four bytes |
|---|---|---|
.z64 | Big-endian (native) | 80 37 12 40 |
.v64 | Byte-swapped | 37 80 40 12 |
.n64 | Little-endian | 40 12 37 80 |
Almost all N64 patches expect a .z64 ROM. If you have a .v64 or .n64 file, convert it to .z64 with an N64 byte-order converter before patching. The file extension isn't always accurate, so the first four bytes are the reliable test. APS patches made for the N64 also check the game's cartridge ID and checksum, and will warn you if they don't match.
Nintendo DS
DS translations and hacks are usually distributed as xdelta patches. Use a full, untrimmed .nds dump. Trimmed ROMs are smaller and won't match.
A few xdelta patches are created with an extra compression option that this site doesn't support. If you see that error, ask the patch author for a version made with xdelta3 -S none.
Sega Genesis / Mega Drive
Patches expect the plain binary format (.bin or .md). If your ROM is an .smd file, its data is stored in an interleaved layout. Convert it to .bin first or the patch will produce garbage.
PlayStation (PS1)
PlayStation games are disc images, usually a .cue file plus one or more .bin files. Patches (traditionally PPF, now often xdelta) apply to a .bin file, normally the first or only one, which holds the game data.
- Load the
.binas the ROM. Don't load the .cue, which is just a small text file. - Apply the patch and download the result.
- The patched file has a new name. Open the
.cuefile in a text editor and change theFILE "..."line to the new name, or rename the patched file to match the original.
Disc images can be hundreds of megabytes. Patching them works best on a computer; phones and tablets may run out of memory.
Applying several patches
Some projects ship a main patch plus optional add-ons. Apply them one at a time, in the order the readme gives:
- Patch the clean ROM with the first patch and download the result.
- Load that downloaded file as the ROM, load the next patch, and apply again.
Checksum warnings on later patches are normal if those patches were designed to go on top of an already-patched game. Follow the readme.
Troubleshooting
"ROM checksum doesn't match"
You have a different region, revision or dump of the game than the patch expects. Check the readme for the required version.
The game shows a black screen or crashes
Usually the wrong ROM version (see above), an SNES copier-header mismatch, or an N64 ROM in the wrong byte order. Also check that you're running the patched file, not the original.
"Unrecognized patch format"
The file isn't a supported patch. It may still be zipped, or it may be a format such as BDF that this site doesn't support yet.
"This ROM is already patched"
UPS and RUP patches work in both directions. If you load a ROM that already has the patch, you get the original back. That's handy for undoing a patch, but if it surprised you, you loaded the wrong file.
Old save files don't work
Hacks often change how saves are stored. Start a new game unless the patch author says saves are compatible.