Adding cheat codes to Nintendo 64 games running on RetroArch requires loading the correct core cheat file (.cht format) and activating them directly inside the quick menu. While the official documentation outlines basic menu navigation, players often hit roadblocks regarding file formatting, core compatibility issues with Mupen64Plus-Next, and matching specific ROM region hashes (such as USA vs. Japan).
This guide walks you through setting up, formatting, and executing cheat codes for N64 titles on RetroArch without breaking your emulator save states or crashing the core.
Choosing the Right N64 Core
Before you touch a single cheat file, your choice of emulator core dictates how cheat codes process. The older Project64 core lacks stability on modern hardware and modern RetroArch builds, whereas Mupen64Plus-Next handles modern cheat files reliably.
- Mupen64Plus-Next (GLES3 / Vulkan): Best overall compatibility, supports high-res texture packs, and reads standard RetroArch
.chttext files natively. - ParaLLEl N64: Ideal for low-level graphics emulation, but its cheat parser can be finicky with older game shark formats.
Verify your core by opening RetroArch, going to Main Menu > Online Updater > Core Updater, and downloading the latest version of Mupen64Plus-Next.
Where to Find and Format N64 Cheat Files
RetroArch uses standard .cht files structured in plain text. You don't need proprietary software, but your text encoding matters.
- Head over to the official libretro GitHub Cheats repository to pull community-verified cheat packs for Nintendo 64.
- Ensure you download the specific file corresponding to your ROM region. Applying a USA (U) GameShark code to a European (E) ROM will instantly freeze or crash the emulator.
- Open the
.chtfile in any standard text editor (like Notepad or TextEdit) and verify the syntax looks like this:
cheats = 1
cheat0_desc = "Infinite Health"
cheat0_code = "810A2B40 03E7"
cheat0_enable = false
Save the file using UTF-8 encoding without a BOM (Byte Order Mark) so the Linux and Windows parsers read line breaks correctly.
Placing Files in the Correct Directory
RetroArch looks in specific folders depending on your operating system. If your cheat files aren't showing up in the user interface, they're sitting in the wrong directory.
- Windows:
%APPDATA%\retroarch\cheats - macOS:
~/Library/Application Support/retroarch/cheats - Linux:
~/.config/retroarch/cheats
Inside the cheats folder, drop your .cht file. Crucially, the cheat filename must match your ROM filename down to the exact character, minus the extension.
- ROM:
Super Mario 64 (USA).z64 - Cheat File:
Super Mario 64 (USA).cht
If you use compressed .zip or .7z archives for your N64 ROMs, name the cheat file to match the compressed archive title, not the internal ROM filename.
Step-by-Step: Activating Cheats in-Game
With your files in place, fire up RetroArch, load your N64 game, and follow these steps to turn the modifications on:
- Open the RetroArch Quick Menu (default hotkey is
F1on keyboards, or the Guide button / Select+X combo on controllers). - Scroll down and select Cheats.
- Choose Load Cheat File (Replace) and navigate to your
cheatsfolder to select your game's.chtfile. - Once loaded, the menu updates to display a list of every individual cheat contained in that file. Scroll through and toggle your desired cheats from
falsetotrue. - Scroll back to the top of the Cheats menu and select Apply Changes.
If you want these cheats to launch automatically every time you start this specific ROM, toggle Auto-Apply Cheats to On before exiting the menu.
Troubleshooting Common N64 Cheat Failures
Even when files match, N64 emulation is notoriously complex. Here is how to fix common errors:
- Codes Aren't Showing Up: Double-check your directory paths in RetroArch by going to Settings > Directory. Ensure the "Cheats" path points directly to your target folder.
- Game Freezes on Activation: GameShark and Action Replay codes for N64 often require master codes or specific security bypasses. If a game crashes immediately, the cheat pack you downloaded is likely meant for a different ROM revision (e.g., version 1.0 vs. version 1.1). Check your ROM's internal serial number and find a matching cheat set.
- Lag and Audio Crackling: Running too many memory-patching cheats simultaneously strains the CPU scheduler on mobile devices or lower-end handhelds. Turn off unused cheats to stabilize the frame rate.
Frequently Asked Questions
Can I add cheats on mobile versions of RetroArch (Android or iOS)?
Yes. The folder structure is identical, but you'll need a file manager app on your phone to drop the .cht file into the internal RetroArch/cheats directory.
Why do some GameShark codes cause graphic glitches?
N64 cheats frequently alter memory registers assigned to rendering pipelines and polygon buffers. If a cheat modifies values outside the game's intended player data, it spills over into graphical memory, causing texture tearing or polygon explosions.
Can I edit existing cheat codes directly inside RetroArch?
Yes. Go to Quick Menu > Cheats, select an individual cheat, and you can edit its hex code or description right on your screen, then save the changes back to your profile.