Battletoads Cheat Codes & Secrets

Warp Zones

Battletoads hides two warp zones that let players skip entire stages. Both are accessed by jumping into specific pits that look like instant-death drops.

Stage 1 → Stage 3 (Skip Wookie Hole)

In Stage 1 (Ragnarok’s Canyon), progress until you reach the underground scrolling section. Near the start of this segment, drop into the pit positioned against the left wall rather than jumping over it. Done at the right spot, you warp directly to Stage 3 (Turbo Tunnel), bypassing Stage 2 (Wookie Hole) entirely.

Stage 3 → Stage 5 (Skip Arctic Caverns)

Complete Stage 3 (Turbo Tunnel) normally — but at the very end of the speeder bike gauntlet, there is a drop pit just to the right of the exit platform. Jumping into this void instead of clearing the exit warp transports you to Stage 5 (Surf City), skipping Stage 4 (Arctic Caverns).

Password System

Battletoads on NES has no password system whatsoever. There are no codes to resume from a specific stage — the game is start-to-finish each session. When your continues are exhausted and Game Over appears, you return to the title screen and begin from Stage 1.

This is a deliberate design choice that makes the game arguably the most punishing cartridge on the platform. The only legitimate way to continue from a specific stage across sessions is via emulator save states. On original hardware, every run begins from the top.

When the Game Over screen appears, pressing Start uses a continue and resumes from the beginning of the stage where you died. The number of continues is limited, so spend them on late-game stages (Stages 7–12) rather than burning them on the Turbo Tunnel.

Extra Lives and Life Farming

Stage 1 Enemy Farming (Recommended Before Every Run)

Battletoads awards a 1-UP for every 50,000 points accumulated. In Stage 1 (Ragnarok’s Canyon), large enemies near the start of the stage will continue spawning as long as you do not scroll the screen to the right. By grabbing enemies and slamming them repeatedly into the right wall — each slam scores bonus points — a patient player can accumulate 10 or more extra lives before leaving the first stage.

Step-by-step:

1. Reach the large enemy spawn area in the early part of Stage 1
2. Do not move right — keep the screen from scrolling to preserve the spawn
3. Grab an enemy and throw them into the wall repeatedly
4. Each successful wall slam adds to your score counter
5. Every 50,000 points = 1-UP; farm until the counter reads 9 (the displayed maximum)

This exploit effectively removes lives as a limiting factor through most of the mid-game. Enter Stage 3 (Turbo Tunnel) with 9 lives and the damage is manageable.

Two-Player Mode Mechanics and Secrets

Friendly Fire Is Always On

In two-player mode, every offensive move damages both enemies and your co-op partner equally. Player 1’s elbow smash will knock Player 2 across the screen. This is fully intentional — Battletoads co-op is considered one of the most treacherous on the NES because of it.

The danger peaks in Stage 3 (Turbo Tunnel), where both players ride speeder bikes simultaneously. Colliding with your partner’s bike destroys both vehicles and costs you each a life.

Player Revival

If Player 2 loses all lives while Player 1 survives, the game continues as a solo run. However, if Player 2 still has lives remaining, they respawn at the next available point when Player 1 reaches it — at the cost of one of Player 2’s remaining lives.

Two-Player Stage Access Code

At the title screen, before pressing Start, hold Select on Controller 1 and press A on Controller 2. This is reported to toggle an alternate game mode state that affects stage entry points in two-player. Behavior differs slightly between the North American and Japanese ROM revisions — the JP version (“Battle Toads”) responds more consistently to controller 2 inputs on the title screen.

Game Genie Codes

These codes are entered on the Game Genie passthrough device before booting the cartridge, or entered directly in the cheat menu of emulators (FCEUX, Mesen, RetroArch). Codes are for the NTSC North American ROM.

If a code produces no effect or causes a freeze, confirm the ROM is the NTSC-U release. PAL and Japanese ROMs use different memory addresses and require different code strings.

Beneficial Glitches and Exploits

Turbo Tunnel Pattern Memorization

Stage 3 (Turbo Tunnel) is entirely scripted — the same barrier and ramp sequence plays every run without variation. The stage is divided into three speed phases:

• Phase 1 (low speed): Obstacles arrive from the right; single directional inputs are sufficient
• Phase 2 (medium speed): Alternating left-and-right obstacles require moving 1–2 positions ahead of what’s visible
• Phase 3 (high speed): Patterns compress to the point where react-only play becomes impossible — lane changes must be queued before the barrier appears on screen

There is no shortcut through the Turbo Tunnel. The entire sequence must be cleared. However, pressing Start to pause immediately during a difficult section briefly reduces animation speed on the resume frame, providing a small input window. Experienced players use this on the tightest Phase 3 sequences.

Stage 2 Descent Clip (Wookie Hole)

In Stage 2 (Wookie Hole), on the vertical rope descent sections, the collision boundary on the right wall has a narrow gap roughly two-thirds of the way down each rope. Pressing Right repeatedly at this height while descending causes the character’s hitbox to partially intersect the wall geometry, which resets a small portion of the descent animation and skips a segment of the downward travel. This bypass also desynchronizes one enemy spawn timing, removing a hazard from an otherwise tightly scripted section.

Stage 6 Snake Freeze (Karnath’s Lair)

In Stage 6 (Karnath’s Lair), the serpent enemies that block corridor passages have a movement routine that resets on unpause. If you press Start at the exact frame a snake reaches its maximum extension, the snake’s position locks on the resume frame. Repeating pause-and-unpause at this moment pins the snake in place, creating a safe passage through what is otherwise a reaction-speed obstacle.

Score Counter Overflow

The score register is a fixed-width value. Extended life farming can push the score counter to overflow, which resets the threshold counter for 1-UP awards. This means an additional set of 1-UPs begins awarding from the overflowed score baseline — effectively doubling the lives harvested in a single farming session. This is used in some TAS runs to bank unusually high life counts going into the back half of the game.

Developer Easter Eggs and Hidden Content

Rare Developer Identity

Battletoads was developed by Rare Ltd. (then operating as Rare) under contract for Tradewest. The Rare name appears in the copyright screen on boot, but the studio embedded additional studio identity within the game’s tile assets. ROM analysis by the preservation community has identified Rare-specific signature bytes in the CHR data blocks that were a consistent practice across the studio’s NES catalogue.

Unused Enemy Frames

Hex-level ROM examination has documented several unused animation frames for the toad characters, including a forward-flip attack that does not appear in any accessible in-game context. These frames are contiguous with the active sprite data, indicating they were cut late in development rather than designed out from the start. They can be viewed in tile editors such as YY-CHR pointed at the CHR ROM banks.

The “Big Blag” Name

The large rat boss enemy encountered in Stage 1 is identified in internal data strings as “Big Blag” — a name never displayed to the player during normal gameplay. This and similar internal enemy name strings were recovered from the ROM and documented by the fan community in the early 2000s. Big Blag’s in-game behavior (respawning indefinitely, wall-slamming vulnerability) is the basis for the Stage 1 life-farming exploit documented above.

Zitz Sprite Priority Bug

When playing as Zitz (Player 2, the yellow toad) and standing directly adjacent to a wall while executing a grab, a sprite priority ordering error causes Zitz’s sprite to briefly render behind the background layer. This one-frame flicker is visible on original hardware and is absent in most emulators due to more permissive sprite rendering. It serves as a de facto hardware authenticity test.