Snes9x Cheats Not Working? Fix Game Genie and Pro Action Replay Codes (2026 Guide)

Short version: an SNES cheat code only fires when three things line up — the code format matches what the emulator expects, the ROM revision and region match what the code was written for, and the code is actually added and ticked in the cheat list. Miss any one of those and the code sits there looking perfectly correct while nothing happens in-game. No error, no warning, just a normal-looking game.

This guide works through those three failure points in order, using the Windows build of Snes9x as the reference, then covers Snes9x EX+ on Android and RetroArch, which each have their own specific trap. Everything here assumes you are playing a ROM you dumped from a cartridge you own — see the legal section further down.

30-second triage: match your symptom, then jump to the fix

What you are seeing	Most likely cause	Do this first
Absolutely nothing happens	Code was never added, or its checkbox is off	Confirm the code appears in the cheat list and its box is ticked
Code accepted, but no effect in-game	Format mismatch (Game Genie vs PAR), or wrong ROM	Check for hyphens, then check your ROM’s revision and region
Game freezes or corrupts the moment you enable it	Code is writing to the wrong address for your ROM	Disable everything, re-enable one code at a time
Cheats worked yesterday, list is empty today	ROM was renamed or moved, so the .cht no longer matches	Make the .cht filename match the ROM filename again
Only Game Genie codes fail; PAR codes work	ROM revision differs from the one the code targets	Look for a PAR version of the same cheat

Answers by situation

Your situation	The answer, up front
First time using cheats on SNES	Open the cheat editor, paste the code, add it, tick the box. That is the whole process.
You entered a code and nothing happened	It is format, ROM, or enablement. Nothing else is common.
Your code has hyphens in it	That is a Game Genie code. Paste it hyphens and all.
Your code is a plain run of hex digits	That is a Pro Action Replay (PAR) code, sometimes labelled “Action Replay” or just “cheat code”.
The code is two or more lines	Add each line as its own entry, then enable every one of them.
You are on Android with Snes9x EX+	Strip hyphens and spaces, enter one line at a time.
Cheats do nothing in RetroArch	You almost certainly skipped “Apply Changes”.
You are worried about your save file	Lean on savestates while cheats are active. Avoid in-game saves.
The game itself feels miserable to play	A real gamepad with turbo does more for a long RPG than most cheats do.

The three reasons Snes9x cheats fail

In practice, essentially every “my cheat does nothing” report falls into one of three buckets. Work them in this order, because the cheapest check is first.

1. Format mismatch — you are treating a Game Genie code as a PAR code, or the site you copied from mangled the spacing.
2. ROM mismatch — the code was written against a different revision or a different regional release than the ROM you loaded.
3. Enablement — the code exists in the dialog but was never committed to the list, or its checkbox is off.

Cause 1: the code format does not match

SNES cheat codes come in two families, and they do fundamentally different things.

Format	What it looks like	What it modifies	Practical note
Game Genie	Eight characters split by a hyphen, e.g. DD32-6DAD	Values read from the cartridge ROM	Paste it with the hyphen. Tied to a specific ROM build.
Pro Action Replay (PAR)	Eight hex digits, no hyphen, e.g. 7E0F3299	The console’s working RAM while the game runs	First six digits are the address, last two are the value written there.
Hand-written address:value	Six-digit address plus a two-digit value	Working RAM	Snes9x treats it as a PAR code. Recent builds also accept an “Address:byte” style with a colon.

A PAR code beginning with 7E is writing into the SNES’s main work RAM, which is why so many “infinite HP” and “max gold” codes start that way. If you are looking at a code that starts with 7E and has no hyphens, you are holding a PAR code, whatever the site called it.

In my own testing, the most common self-inflicted failure is pasting a code with the wrong separators — a code copied out of a forum post with a stray line break, or with the hyphen dropped by a text editor. Snes9x will usually take it without complaint and then quietly do nothing. Copy the code exactly as the source presents it.

Cause 2: your ROM is a different revision or region

This is the cause people skip, and it is the one that produces the scary symptoms: enable the code and the game freezes, the music turns into noise, or sprites explode into garbage.

SNES cartridges were not immutable. Publishers shipped bug-fixed revisions of the same title — commonly labelled v1.0 and v1.1 in ROM databases — and the fix shifted code and data around inside the ROM. A Game Genie code is a hard-coded instruction to swap the byte at one specific location. Move that location and the code either does nothing or writes over something it should not have touched.

Region makes this worse. The North American, PAL and Japanese releases of the same game are different builds with different text, different memory layouts and sometimes different balance. A Game Genie code posted for the US release of a game is not expected to work on the European release, and neither is expected to work on the Japanese one.

Three things to check before you blame the emulator:

• Region — is your ROM the NTSC-U, PAL or Japanese release, and which one did the code list target?
• Revision — v1.0 versus v1.1 or later. Code lists that are worth using say which revision they assume.
• ROM identity — note the internal header info and checksum Snes9x shows you, so you can compare against what a code list specifies.

Because a Game Genie code targets a fixed ROM location and a PAR code targets a RAM address, revision changes tend to break Game Genie codes more visibly. That is a tendency, not a rule — RAM layouts also shift between builds, so PAR codes can miss too. If your Game Genie codes are the only ones failing, testing a PAR equivalent is a fast diagnostic.

Cause 3: the code is entered but not actually enabled

Snes9x has what amounts to a double lock, and both have to be released:

• Did you commit the code to the list? Typing a code into the entry field and closing the dialog discards it. There is a button — labelled Add in the builds I have used — that pushes it into the list. Use that.
• Is its checkbox ticked? A code sitting in the list with an empty box is inert.
• Is the .cht file still matched to the ROM? Snes9x stores cheats in a .cht file that it associates with the ROM by name. Rename or relocate the ROM and the association breaks, so the list comes up empty.

“It worked yesterday and today the list is blank” is nearly always the third one. Tidying up a ROM folder — renaming files to a consistent scheme, moving them into subfolders — silently orphans the cheat files.

Game Genie or PAR? Telling them apart, and why you cannot convert between them

Hyphen means Game Genie, no hyphen means PAR

That single rule resolves the great majority of cases. Game Genie codes for SNES are written as XXXX-XXXX using a restricted character set. PAR codes are eight hexadecimal digits with no separator. Sites that just say “cheat code” without naming the format are usually publishing PAR codes.

Converting one format to the other is not realistic

The two formats do not describe the same operation. Game Genie substitutes a value the console reads out of the cartridge; PAR writes a value into live RAM. There is no mechanical translation between them, and tools that claim to convert generally do not do what people expect. If you have one format and need the other, it is far faster to look for a second code list for the same game than to chase a converter.

Snes9x re-displaying your code as PAR is normal

Enter a Game Genie code and you may find the emulator shows it back to you as a Pro Action Replay code. This is expected behaviour, not corruption — Snes9x normalises what you entered into its internal representation. Do not re-enter the code trying to make it “stick” in the original format.

Entering cheats in Snes9x on Windows, step by step

First trap: the cheat editor is not the cheat search

The Cheat menu offers two things that sound similar to a newcomer:

• The one you want — the cheat editor, where you type or paste an existing code. In older builds this menu item is worded along the lines of “Game Genie, Pro Action Replay Codes”.
• The one you do not want yet — the cheat search or cheat finder, which scans memory while you play so you can discover new addresses yourself.

Exact menu wording has drifted between releases, and 1.63 added dedicated hotkeys for cheat edit and cheat search as separate functions, so your build may label these differently from a screenshot you found elsewhere. If the dialog you opened asks you to search for changing values, you are in the finder — back out and look for the editor.

The three-step flow that does not fail

1. Type a description. Optional as far as the emulator is concerned, essential for you. Six codes named nothing are unmanageable an hour later. “Max gold”, “Infinite HP”, “Walk through walls”.
2. Paste the code into the code field. Match the source’s punctuation exactly — keep the hyphen for Game Genie, keep the digits unbroken for PAR.
3. Press Add, then tick the checkbox. Confirm with your eyes that the row appeared in the list and that its box is checked. Closing the dialog with OK without pressing Add is the single most common way to lose a code.

Advanced: editing the .cht file in a text editor

Entering twenty codes through the dialog is tedious. Editing the cheat file directly is much faster — but back it up before you touch it.

1. Load the game in Snes9x and add one cheat through the normal dialog, so the emulator generates the file for you.
2. Close Snes9x. Open the generated file, named after your ROM with a .cht extension, in a plain text editor.
3. Duplicate the block that is already there and edit the copies, incrementing the entry number each time.

The file is a simple list of numbered entries, each carrying a description, a code, and an enabled flag. The exact key names and the way the enabled flag is written vary between Snes9x branches and versions — some builds write a boolean, others a numeric value, and forks such as the Wii and 3DS ports differ again. Rather than copying a format from a guide, match the format of the lines Snes9x already wrote in your own file. That is the only version-proof approach.

Two operational notes. Multi-part codes can often be stored joined into a single entry rather than split across several, so look at how your build wrote an existing multi-part cheat before you invent a layout. And because the file is bound to the ROM by filename, any renaming project needs to rename the .cht alongside it.

Snes9x EX+ on Android

The Android build presents a different interface, and the input rules are stricter.

1. With the game running, open the in-game menu and choose the cheats section.
2. Select the option to add a Game Genie or Action Replay code.
3. Enter the code with no hyphens and no spaces. This is the part people get wrong.
4. Give it a short description so you can identify it later.
5. Confirm the entry, then enable it in the list.

The Android build takes one code per entry. A cheat published as three lines becomes three separate entries, all of which must be enabled. The same is true on desktop, but Android enforces it more obviously.

Menu labels differ across versions of the app, so treat the above as the shape of the process rather than exact button names. And if a code enters cleanly but does nothing, the diagnosis is identical to the desktop case: suspect the ROM revision first.

When cheats fail in other emulators

The three root causes carry over, but each front-end adds its own wrinkle.

Emulator	What catches people out	Where to look first
RetroArch (Snes9x core)	Adding or toggling a cheat does not activate it by itself	Select Apply Changes in the cheat menu after editing the list
RetroArch (other cores)	Cores differ in which code formats they accept	Try the Game Genie form first for SNES titles
RetroArch (cheat files)	Cheat files are matched to content by name	Check that the cheat file name lines up with the loaded ROM
Mesen2	Separate UI conventions from Snes9x	Register the code in the cheat list, then enable it there
bsnes and accuracy-focused forks	Stricter about ROM integrity and code handling	Verify the ROM matches the revision the code assumes
PCSX2, Saturn and other systems	Code systems are platform-specific	Confirm the code was written for that console at all

RetroArch also exposes options to auto-apply cheats on load and to apply after each toggle. Turning those on removes the most common RetroArch complaint entirely.

The regional wrinkle Western players hit

Two region-related problems catch North American, UK and Australian players specifically.

PAL versus NTSC builds. If you own a PAL cartridge and dumped it, your ROM is a European build. Code lists on English-language sites frequently assume the North American release. Same game, different binary, so a Game Genie code aimed at the US build has no reason to land correctly. When a list does not state which region it targets, treat that as a red flag.

Games that never got an SNES release in the West. Some of the most cheat-searched RPGs were Japan-only on the hardware. Final Fantasy V was the one mainline entry on the SNES that never shipped outside Japan; its first official English console release came on PlayStation, in the Final Fantasy Anthology compilation published in North America in 1999. Dragon Quest VI likewise stayed in Japan on the Super Famicom, and reached English speakers only through the Nintendo DS remake, released in North America in 2011 as Dragon Quest VI: Realms of Revelation.

The practical consequence: for these titles, any SNES-era code you find is written against the Japanese cartridge. English-language cheat lists for them are sometimes written against fan-translated ROM builds instead, which are yet another distinct binary with yet another memory layout. If you are cheating in a game that never had a Western SNES release, expect the ROM-matching problem to be the dominant one.

Protect your save file before you start cheating

Cheating is a legitimate way to enjoy a 40-hour RPG on an adult schedule. It is also a genuine risk to your save data, because you are writing values the game’s own logic never expected to see.

Prefer savestates over in-game saves while cheats are active

The battery save inside the ROM is the game’s authoritative record. If you overwrite it while the game is in an inconsistent state, turning the cheat off afterwards does not undo the damage — the corrupted state is now the save. A savestate, by contrast, is a snapshot of the entire machine that you can return to at will.

So: while cheats are on, avoid inns, churches, and save points. Use savestates instead.

How a flag desync ruins a playthrough

A concrete failure pattern worth understanding. Suppose you enable an “all items” cheat in an RPG:

1. The cheat marks a plot-critical item as already in your inventory.
2. You reach the scene where an NPC is scripted to hand you that item, and the game’s give-item routine cannot complete in a sane way.
3. The event flag never advances. Dialogue loops or the scene simply does not fire, and the story cannot continue.

The cheat is not “wrong” in any mechanical sense — it did what it said. The game just has no branch for that state. If your only save is a battery save written after that point, the run is over. If you had a savestate from before the scene, you reload it, disable the cheat, and continue.

A three-step rule that prevents almost all of this

1. Before enabling any cheat, make a savestate of the known-good game.
2. While cheats are on, rotate savestates across multiple slots rather than overwriting one. A corrupted state you saved over is no help.
3. Before making an in-game save, turn the cheats off and verify the game behaves normally for a few minutes.

Savestate hotkeys vary with your build and your key bindings, so check the input configuration screen rather than trusting a default from a guide.

Legality in the United States: what to know before you dump

This is general information, not legal advice. Copyright law here is genuinely unsettled in places, and how it applies to your situation depends on facts this article cannot know. If the stakes matter to you, consult a qualified attorney.

The community norm, and the position this site takes, is simple: dump games you legally own, and keep those dumps to yourself.

A few points worth understanding rather than repeating from memes:

• 17 U.S.C. §117 permits the owner of a copy of a computer program to make certain copies, including for archival purposes. Whether and how neatly that provision covers dumping a console game cartridge has been argued for years and is not something anyone should describe as settled. It is a real statutory provision, not a blanket permission slip.
• DMCA §1201 prohibits circumventing technological measures that control access to a copyrighted work. SNES-era cartridges predate modern DRM, but §1201 is very much live for later systems, and it is the reason “just rip it” advice that works for a 1993 cartridge does not transfer to a modern console.
• The Copyright Office’s triennial rulemaking grants time-limited exemptions to §1201 for specific activities, including preservation work by qualifying libraries, archives and museums. These exemptions are narrow and conditional. They are not a general public licence to download games.
• Owning the cartridge does not legalise downloading someone else’s dump. The widely repeated “you can download it if you own it” and “24-hour rule” ideas have no basis in US law. Downloading a copy you did not make is a separate act from owning the physical item.
• Cheat codes themselves are a different question from ROMs. Applying codes to your own copy, on your own machine, for your own play, is a private act. Distributing a modified ROM built from those changes is not, and this article does not cover it.

For that reason, you will not find ROM sources named here, and you will not find anything about acquiring pre-patched or hacked ROMs. Everything above assumes a dump you made from hardware you own.

Hardware that makes some cheats unnecessary

Worth saying plainly: a lot of people reach for cheat codes because the grind is tedious, not because the game is too hard. A decent controller with a turbo function solves the tedium directly, without touching memory addresses.

What turbo and macros actually save you

• Holding the confirm button through random battles in a long RPG
• Sustained fire in shoot-’em-ups without wrecking your hand
• Advancing dialogue boxes in text-heavy games
• Mapping fast-forward and savestate functions to spare buttons, so you never touch the keyboard mid-game

A wired USB gamepad with a turbo toggle is the cheapest fix here and is widely available.

A note on very cheap SNES-style pads

The lowest-priced SNES-shaped USB pads are a gamble. The recurring complaints are a mushy or misregistering d-pad, which is fatal for anything requiring diagonals, and stiff face buttons that make turbo pointless. If you are buying primarily to play SNES games, the d-pad is the component that matters most, and it is the one budget pads compromise first.

Recreating the original feel

8BitDo’s SNES-styled controllers are the usual recommendation for people who want the period-correct layout with modern internals — wireless, rechargeable, and configurable. They are sold globally through Amazon.com, AliExpress and 8BitDo’s own store, so no importing is required for most readers. Wireless latency depends on your receiver, your USB port and local radio congestion, so treat “no perceptible lag” as environment-dependent rather than guaranteed.

What actually matters when choosing:

• D-pad feel — the closer to the original pivot action, the more reliable your diagonal inputs
• Extra buttons — shoulder buttons or a back paddle give you somewhere to bind fast-forward and savestates
• Connection — wired if you are latency-sensitive, wireless if convenience wins

If you have cartridges but no dumps, a cartridge dumper is the piece of hardware that gets you legitimately started. These are sold as generic devices on Amazon.com and AliExpress; some Japan-only all-in-one units are also popular but require importing and are not necessary.

FAQ

My code is two or more lines. Can I paste them all at once?

No. Add each line as its own entry, then enable every one. A multi-line code where one line is unticked usually produces partial, confusing behaviour rather than an obvious failure. This applies to both desktop and Android. Note that some builds do store multi-part codes joined in a single .cht entry — that is the file format’s business, not something to replicate by hand in the entry dialog.

Codes work for every game except one. Why?

ROM revision, nine times out of ten. That title probably shipped in more than one revision, or you have a different regional build from the one the code list assumed. Find a list that states which revision it targets.

The game freezes when I turn cheats on

Usually too many codes enabled at once. Untick everything, then enable one at a time until the freeze returns — that identifies the offender. Stat-modifying codes and event or flag codes conflict particularly readily, since both can be writing to overlapping regions.

All I can find is something labelled “cheat code” with no format given

Enter it as-is. Eight hex digits with no hyphen will be handled as a PAR code. If it has a hyphen, it is Game Genie. The label the site used does not change what the code is.

How do I delete a cheat I added?

Untick it to disable, or delete the row to remove it. To wipe everything for one game, delete the .cht file that shares the ROM’s name — the list returns to empty next launch.

Which version of Snes9x should I run?

The current stable release from the official project. As of September 2026 that is 1.63, which among other things accepts an “Address:byte” form for cheat input and adds multiselect in the cheat edit dialog. Older builds work, but their cheat UI is laid out differently enough that guides and screenshots will not match what you see.

Does using cheats break achievements or netplay?

Anything that verifies game state — achievement systems, netplay sessions — treats memory modification as disqualifying by design. Assume cheats and those features are mutually exclusive.

Summary

When a cheat code does nothing in Snes9x, check these in order:

1. Format — hyphen means Game Genie, plain hex means Pro Action Replay. Paste exactly as published.
2. ROM — region and revision must match what the code was written for. This is the cause people skip and the one that produces freezes.
3. Enablement — added to the list, checkbox ticked, and for RetroArch, changes applied.

Then protect yourself: savestate before you enable anything, rotate slots, and keep cheats off when you write an in-game save. And keep the whole exercise where it belongs — your own dumps, your own machine, your own playthrough.