Cheat Sheets / Pokemon Red and Blue
Pokemon Red and Blue cheats
To cheat in Pokemon Red or Blue, use GameShark codes: on a GameShark plugged in with the cartridge, or in an emulator's cheat menu. A Game Boy GameShark code is eight characters, 01VVAAAA: 01, the value it writes, and the address with its low byte first, written again every frame. The codes below are built from the game's own memory map and each one was tested in the game.
GameShark code builder
Your code
- Your save
- Switched off
- Tested
- The format:
01VVAAAA, the address low byte first. How a code works. - Entering codes: a GameShark or an emulator's cheat menu. Where.
- Back up first: items, money, badges and the Pokedex go into your save. Before you save.
- Other lists' codes: 24 of them: 9 work, 10 work with a catch, 2 do not work, 3 not run. The verdicts.
Playing Yellow? Its values sit one byte lower, so most of these codes do something else there: use the Yellow page.
Every code the builder makes, tested
Each family below was built from the game's own memory map (the address is a label in the game's code, never a number copied from a list), switched on in the game in an emulator, used the way a player would, then switched off to see what stays. The codes shown use the builder's starting values.
Any item in your bag Tested
Slot 1 of your bag holds RARE CANDY x99.
It stays when you switch the code off.
Pick a slot that already has an item in it. A slot past your last item writes over the bag's end marker, and the bag then lists a junk item after it, even with the code off (tested).
Tested in Red and Blue. What the run read:
- bag slot 1 in RAM
- RARE CANDY on the bag screen
- quantity 99 on the bag screen
- code off: RARE CANDY x99 stays in the bag
- the end marker after the last item is overwritten while the code is on
- code off: the end marker is still gone

Money Tested
Your money reads 999999. The game stores it as 3 bytes, two digits each.
It stays when you switch the code off.
Tested in Red and Blue. What the run read:
- money in RAM
- 999999 on the Trainer Card
- badges byte in RAM
- code off: money and badges stay

Any wild Pokemon Tested
Every wild Pokemon you meet in grass, caves or water is MEW at level 50.
Wild Pokemon are normal again at the next battle.
In battle its picture can come out scrambled: the game draws the picture from the part of the cartridge that the Pokemon it replaced keeps its pictures in. It is still MEW: catch it and you have a real MEW (tested with MEW, caught with a Master Ball). Switch the codes off before a trainer battle: the game builds a trainer's Pokemon from the same bytes (from the code; trainer battles were not tested).
Tested in Red and Blue. What the run read:
- battle text names MEW
- wEnemyMonSpecies is MEW
- wEnemyMonLevel is 50
- level 50 on the battle screen
- caught
- code off: MEW is in the party
- its level is 50

Walk through walls Tested
You walk through trees, walls and counters.
Switching the code off does NOT stop it: the byte stays at 1 (tested). From the game's code, it is cleared at the end of a ledge jump or a walk the game moves you on, and it is not in your save, so turning the Game Boy off clears it too.
Walking off the edge of a map where no route joins it takes you into places the game never drew.
Tested in Red and Blue. What the run read:
- code off: a step left into the trees is blocked
- code on: a step left lands on the tree tile
- and the next step is past the trees

No wild battles Tested
No wild Pokemon from walking in grass, caves or water (tested in tall grass). Trainers still see you, and fishing still hooks Pokemon: the rods start their battles another way (from the code).
Wild battles come back at once.
Tested in Red. What the run read:
- no wild battle in 200 steps of tall grass
- control (no code): wild battles happen in the same grass
Badges Tested
The badges you tick are yours: the Trainer Card shows them and the game checks this byte for them.
They stay when you switch the code off.
Tested in Red and Blue. What the run read:
- money in RAM
- 999999 on the Trainer Card
- badges byte in RAM
- code off: money and badges stay

Pokedex complete Tested
All 151 Pokemon seen and owned. 38 codes: one for each byte of the two flag lists.
The flags stay when you switch the codes off, so you can enter them a few at a time if your GameShark holds fewer codes.
Tested in Red and Blue. What the run read:
- SEEN 151 and OWN 151 on the Pokedex screen
- code off: every owned flag stays (151 bits set)

Infinite HP in battle Tested
Your Pokemon's HP in battle is set back to 100 every frame.
HP goes down normally again.
Use your Pokemon's max HP. A bigger number shows over the max and stays after the battle (tested with 255 over a max of 31).
Tested in Red and Blue. What the run read:
- HP stays at the max every turn
- battle PP of move 2 stays 30
- party PP of move 2 stays 30 (the second code)
Infinite PP Tested
Move 1 keeps 35 PP, in battle and in your first Pokemon's own copy.
PP goes down normally again.
The game takes a PP from two places each turn: the battle's copy and your Pokemon's own. A code on the battle copy alone (as most lists print it) lets your Pokemon's own PP run down (tested).
Tested in Red and Blue. What the run read:
- HP stays at the max every turn
- battle PP of move 2 stays 30
- party PP of move 2 stays 30 (the second code)
Game Corner coins Tested
Your coins read 9999. Stored as 2 bytes, two digits each.
They stay when you switch the code off.
Tested in Red and Blue. What the run read:
- coins in RAM
- code off: the coins stay
Codes from other lists, tested
The codes most Pokemon Red and Blue code lists print, each switched on in the game and checked the same way. The address of every code was looked up in the game's own symbol files, so the verdict says what the code really writes to.
| Code | Lists call it | Verdict | What the game does |
|---|---|---|---|
01FF56D3 | All badges | Works | Writes $FF to wObtainedBadges, all eight bits. The same code the builder makes. |
010138CD | Walk through walls | Works, with a catch | Writes 1 to wSimulatedJoypadStatesIndex: the collision check skips walls while the game thinks it is moving you itself. It keeps working after you switch it off, until a ledge jump or a scripted walk clears the byte. |
010139CD | Walk through walls | Does not work | One address off: $CD39 is wUnusedSimulatedJoypadStatesMask, a byte the game writes and never reads. Walls stay walls. |
01033CD1 | No random battles | Works | Writes 3 to wNumberOfNoRandomBattleStepsLeft, the game's own count of steps with no wild battle after a battle. While it is not 0 the game skips the wild check. 200 steps in grass, no battle. |
0115D8CF | Wild Pokemon is Mew (01??D8CF: any Pokemon) | Works, with a catch | Writes wEnemyMonSpecies2, which the battle builds the wild Pokemon from a frame after the grass picks one. You meet and can catch Mew, but its picture comes out scrambled (see the builder's note). |
0132F3CF | Wild Pokemon level 50 (01??F3CF) | Works, with a catch | Writes wEnemyMonLevel after the battle has worked out the stats, so it shows L50 with level 3 stats (15 max HP in our test). Catch it and the game works the stats out again: a real level 50. The builder's level code writes wCurEnemyLevel instead, before the stats. |
019947D3019948D3019949D3 | Max money | Works | 999999 in the game's two-digits-a-byte money. The Trainer Card shows it; it stays. |
01281ED301631FD3 | Rare Candy x99 in the first slot (01??1ED3, 01631FD3) | Works | Item and quantity of bag slot 1. Use a slot that already holds an item. |
01011ED3 | 99 Master Balls | Works, with a catch | Only the item byte: slot 1 turns into MASTER BALL and keeps the old quantity (x5 in our test). Add 01631FD3 for 99. |
01017CCF | Master Ball for sale in the Poke Mart | Not tested | Not tested: our test save broke at the mart's door in both emulators, so no run reached the clerk. From the code: $CF7C is wItemList+1, the first item of the list a clerk shows, and the game prices MASTER BALL at 0 (data/items/prices.asm). |
01287CCF | Rare Candy for sale in the Poke Mart | Not tested | Not tested, for the same reason. From the code: the same first slot of the clerk's list; RARE CANDY costs 4800 there. |
01FF16D0 | Infinite HP | Works, with a catch | Writes $FF to the low byte of wBattleMonHP: HP 255, over your max (31 in our test), and the party keeps 255 after the battle until you heal. Type your max HP in the builder instead. |
01282DD0 | Infinite PP, move 1 | Works, with a catch | Sets the battle's PP of move 1 to 40 (Tackle's max is 35). Your Pokemon's own PP still drops: 35 to 32 after three Tackles. The builder adds the second code. |
0100E7CF | Wild Pokemon faints at once | Works | Writes 0 to the low byte of wEnemyMonHP. The battle ends before the first menu and you still get the experience. |
0170E9CF | Wild Pokemon can't attack and is burned | Works | Writes $70 to wEnemyMonStatus: the burn, freeze and paralysis bits. Frozen, it never moves; the burn still takes its HP each turn. The screen shows BRN. |
01FFD6CF | Never miss | Works, with a catch | Writes $FF to wPlayerMoveAccuracy, the highest the game has. Red and Blue still miss 1 time in 256 at that number (pret's note on the accuracy check), and it does nothing for critical hits. |
0199A4D50199A5D5 | 9999 Game Corner coins | Works | 9999 in wPlayerCoins, two digits a byte. It stays. |
01FF0AD3 ...all 39 codes01FF0AD301FF0BD301FF0CD301FF0DD301FF0ED301FF0FD301FF10D301FF11D301FF12D301FF13D301FF14D301FF15D301FF16D301FF17D301FF18D301FF19D301FF1AD301FF1BD301FFF6D201FFF7D201FFF8D201FFF9D201FFFAD201FFFBD201FFFCD201FFFDD201FFFED201FFFFD201FF00D301FF01D301FF02D301FF03D301FF04D301FF05D301FF06D301FF07D301FF08D301FF09D301FF0AD3 | Seen every Pokemon (a list of 39 codes) | Works, with a catch | The list stops one byte short and starts one too early: the Pokedex shows SEEN 144 and OWN 152 (a flag past MEW), and its first code writes $FF over the last byte of your sixth Pokemon's nickname. The builder's Pokedex codes give 151 and 151. |
017136D7 | Jump on top of anything | Works, with a catch | Writes $71 to wMovementFlags, which includes the ledge-jump bit: the collision check skips walls and the wild check skips you, as during a jump. You walk through trees. |
014501C2 | Ghost mode, walk through walls | Does not work | $C201 is an unnamed byte in the player's sprite data. Trees still block you. |
010100D7 | Bicycle speed everywhere | Works | Writes 1 to wWalkBikeSurfState: you are on the bicycle, a step in 8 frames instead of 16. |
010157D0 | Catch a trainer's Pokemon | Not tested | Not tested (no trainer battle in our runs). From the code: it holds wIsInBattle at 1, the value for a wild battle. |
016447DA | Infinite Safari Balls | Works, with a catch | 100 in wNumSafariBalls, still 100 after a throw. The menu prints two digits, so it reads BALL x 0 (tested). 016347DA, 99 balls, reads right. |
01F00ED7 | Infinite Safari Zone time | Works | Holds the low byte of wSafariSteps at $F0: 30 steps later the counter still read 496. |
How a GameShark code works
A Game Boy GameShark code is eight characters, TTVVLLHH. TT is the code type: 01 writes one byte; 9b first switches the Game Boy Color's work RAM to bank b; 8b first switches the cartridge's save RAM bank. VV is the byte it writes. LLHH is the address with its low byte first, so 010138CD writes 01 to address CD38.
The GameShark plugs in between the Game Boy and the cartridge and writes every code's byte again once a frame, about 60 times a second, from the game's VBlank interrupt. It only writes memory; it never changes the cartridge. So a code works when the game reads that byte for the thing you want, and it keeps working only while the game would not change it back. That is why some codes stay when you switch them off (your money really is 999999 now) and others stop at once (wild Pokemon are normal again).
How we tested: the game runs in an emulator with no change to its code, and before every frame our model of the GameShark writes the code's byte, the way the device does. For the codes whose timing could matter, a second emulator whose own GameShark writes at the exact moment the real device does gave the same result.
How to enter the codes
On a real GameShark
The GameShark sits between the Game Boy and the cartridge, and you enter codes on it before the game starts; it holds 10 to 25 codes at once. We did not test a real device.
In RetroArch
- Load the game and open the Quick Menu, then Cheats.
- Choose Add New Code to Top (or to Bottom), open the new line and pick Code.
- Type the code, set Enabled to on, go back one level and choose Apply Changes.
In Delta (iPhone and iPad)
- Start the game and open the pause menu, then Cheat Codes.
- Tap + and choose GameShark as the cheat device.
- Give it a name and type the code.
Other emulators have a cheat menu too; pick GameShark as the code type. These steps come from each emulator's own help pages. Codes with more than one line are entered as one cheat with one code per line, or as separate cheats that are all on.
Before you save
Items, money, coins, badges and Pokedex flags go into your save the next time you save the game, and switching the code off does not take them back. Wild Pokemon, walking through walls and no wild battles are never saved. If you want to be able to go back, copy your save file first (an emulator's save file, or a second save on a real cartridge is not possible: there is one). Caught Pokemon from a code are normal Pokemon and stay in your save.
Codes for glitch Pokemon and glitch items are left out of this page on purpose: they can damage a save in ways the game cannot repair.
Questions people ask
How do you cheat in Pokemon Red?
With GameShark codes: on a GameShark plugged in with the cartridge, or in an emulator's cheat menu. A code such as 01281ED3 puts a Rare Candy in the first slot of your bag; the builder on this page makes codes for items, money, wild Pokemon, walking through walls, no wild battles, badges and the Pokedex.
What is the GameShark code for Rare Candy in Pokemon Red?
01281ED3 makes the first item in your bag a Rare Candy and 01631FD3 makes it 99 of them. Use them together, with at least one item already in your bag. They work in Blue too.
What is the walk through walls code for Pokemon Red?
010138CD. It works in Red, Blue and Yellow, and it keeps working after you switch it off until you jump a ledge or the game moves you on a scripted walk. 010139CD, which some lists print, does nothing.
What is the Mew GameShark code for Pokemon Red?
0115D8CF makes every wild Pokemon a Mew. Walk in tall grass and you meet one; catch it and it is a real Mew. Its picture in battle comes out scrambled, because the game draws it from the part of the cartridge that the replaced Pokemon's picture lives in.
Do Pokemon Red codes work in Blue and Yellow?
Red codes work in Blue: every address on this page is the same in both (checked label by label in the symbol files, and tested in both games). Most do not work in Yellow, which keeps its values one byte lower.
Will GameShark codes ruin my save?
Codes for items, money, badges and the Pokedex change your save as soon as you save the game, and switching the code off does not undo them. Wild Pokemon, walking through walls and no wild battles are not saved. Back up your save before you try a code that writes into it.
How do you get 99 Master Balls in Pokemon Red?
01011ED3 and 01631FD3 together: the first makes slot 1 of your bag a Master Ball, the second makes it 99. On its own, 01011ED3 keeps whatever number the slot had.
Is there a GameShark code for shiny Pokemon in Red?
No. Shiny Pokemon came with Gold and Silver; Red, Blue and Yellow have no shiny check at all.
How this was checked
Tested in the game's own code in an emulator, English Red and Blue 1.0, on . Not on a real GameShark or cartridge. Every address comes from the symbol files of the pret disassemblies built to match these exact cartridges, and every name in the builder (items and Pokemon) from the same source code. Each code family and each list code was switched on in the game, used, and read back from the game's own memory and screen. Pokemon is made by Game Freak and published by Nintendo; GameShark is a trademark of its owner. GardenFlouer is a fan site and is not connected to either.
Read next
- Pokemon Yellow GameShark codes: the same builder and checks for that game.
- Pokemon Gold and Silver GameShark codes: the same builder and checks for that game.
- Pokemon Crystal GameShark codes: the same builder and checks for that game.
- The Glitchhouse: Gen 1 glitches, each one tested in the game's own code.
- Cheat Sheets: codes and secrets for more games, each one checked.