N64 Emulator for Android (2026 Guide): M64Plus FZ and RetroArch Setup, C-Button Mapping, Save Fixes, and Slowdown Tips

The short version: if you want to play Nintendo 64 games on Android, the quickest route is the standalone app M64Plus FZ Emulator. If you already run your other systems through RetroArch, the Mupen64Plus-Next core lets you keep everything in one place. Either way, the N64 problems people actually run into are not about BIOS files. They come down to two things: performance (slowdown and stutter) and saves that seem to vanish.

The N64 is a very different emulation target from 2D systems like the NES or the TurboGrafx-16. On top of its main CPU (a MIPS R4300i), an emulator has to recreate the console’s Reality Co-Processor, which does the geometry and graphics work, entirely in software. That is why some Android devices that handle PlayStation games with ease still struggle with certain N64 titles. On top of that, N64 cartridges used several different save methods, and if the emulator picks the wrong one, you get the classic “I definitely saved, but my progress is gone” problem.

This guide goes in order: choosing an app, why the N64 is demanding, setup for both routes, fixing slowdown, mapping the C-buttons, and managing saves and storage.

Everything here assumes you are playing games from an N64 and cartridges you own, dumped yourself. We do not cover where to get ROMs, and we never will.

The Short Answer: M64Plus FZ for a Standalone App, RetroArch with Mupen64Plus-Next to Keep Everything Together

Here is the overall picture first.

If you are unsure, go with M64Plus FZ. There are three reasons:

1. It is built specifically for the N64. Switching video plugins (such as GLideN64) and changing the resolution scale all happen in a straightforward settings screen inside the app.
2. It is free and self-contained. There are no separate cores or plugins to hunt down and install.
3. Its controller settings stand on their own. Your N64 button layout is not tangled up with settings for other systems, so you can build a mapping that suits the N64 controller.

RetroArch with Mupen64Plus-Next, on the other hand, makes the most sense if you already play NES, PlayStation, or other systems in RetroArch. You can reuse your controller setup and your approach to save folders, and that gets more convenient the more systems you add. The trade-off is that Mupen64Plus-Next has a long list of core options, so the first-time setup takes more effort than M64Plus FZ.

One general point: in our experience the N64 tends to ask more of a device than the PlayStation does, so do not assume that smooth PS1 performance means smooth N64 performance.

Why the N64 Is Hard to Emulate

Emulating the NES or TurboGrafx-16 is mostly a matter of reproducing the CPU one instruction at a time. The N64 is different. Alongside the MIPS R4300i CPU sits the RCP (Reality Co-Processor), a single co-processor that contains two processing units:

• RSP (Reality Signal Processor): a programmable processor that handles work such as geometry calculations and audio.
• RDP (Reality Display Processor): the unit that rasterizes, meaning it actually draws the pixels on screen.

The real hardware was designed around the CPU, RSP, and RDP all working at the same time, and an emulator has to imitate all of that in software.

The RDP side is usually the heaviest. N64 graphics leaned on techniques that were advanced for their day, such as perspective-correct texturing and the console’s distinctive texture filtering, and the more faithfully an emulator tries to reproduce them, the harder it works your phone’s GPU. That is why some devices find N64 games heavier than PlayStation games, even though N64 scenes often look simpler.

The other factor is microcode, which varies from game to game. N64 games could send their own programs to the RSP to customize how graphics were processed. Later titles such as Banjo-Kazooie, Perfect Dark, and Conker’s Bad Fur Day used custom microcode, and that is why performance can vary a lot between games on the same device. If one game runs perfectly and another stutters, your device is not broken; this is the reason.

Setting Up M64Plus FZ Emulator

Now for the hands-on part. Follow these steps in order.

1. Install the app

Search Google Play for “M64Plus FZ Emulator” (it used to be called Mupen64Plus FZ) and install it. It is a fork that continued development from the earlier Mupen64Plus AE. Several apps with similar names show up in search results, so confirm that the developer is listed as Francisco Zurita before you install. The app is free, and there is also a paid Pro version that adds extras such as netplay. App availability and naming here reflect what is on Google Play as of 2026.

2. Point it at your ROM folder

On first launch, allow storage access and select the folder where you keep your game dumps. Avoid non-ASCII characters and symbols in folder and file names. They are one of the most common reasons a library scan fails.

3. Understand the three ROM formats (.z64, .v64, .n64)

N64 ROM files come in three byte orders. The game data inside is the same; only the order of the bytes differs:

• .z64: big-endian, the N64’s native byte order.
• .v64: byte-swapped in 16-bit units, a format that dates back to the Doctor V64 backup device.
• .n64: little-endian.

Most emulators detect the format automatically by reading the first four bytes of the file, so this usually just works. Still, some dumping hardware saves in a format other than .z64, and in rare cases that can cause recognition problems. Right after dumping a cartridge, it is worth checking your dumper’s settings to see which format it wrote. If you have a choice, .z64 is the safest default.

4. Choose a video plugin

Pick the video plugin in the app’s video settings. GLideN64 is the right choice for most people. There is also Angrylion, a software renderer for the RDP that prioritizes accuracy, but it is very demanding. Think of it as a tool for checking how a particular game is supposed to look, not something to play with day to day.

5. Map your controller

The app starts with touch controls. If you are using a physical controller, assign the buttons in the controller section of the settings. The C-buttons are the tricky part, and we cover them in their own section below.

Setting Up RetroArch with Mupen64Plus-Next

This route is for people who want the N64 alongside their other systems in RetroArch.

1. Add the core

From RetroArch’s main menu, go to Load Core and then Download a Core, or use Online Updater and then Core Downloader; the exact menu names vary between RetroArch builds. Select Nintendo – Nintendo 64 (Mupen64Plus-Next). You will also see “ParaLLEl N64” in the list, but start with Mupen64Plus-Next. ParaLLEl is more accurate but asks even more of your device. Its ParaLLEl RDP renderer requires Vulkan and is really aimed at high-end hardware.

2. Open the core options

Load a game, open the Quick Menu, and go to Core Options. There are a lot of settings, but these three are the ones to look at first:

A quick word on HLE and LLE: HLE (high-level emulation) recreates what the RSP’s microcode is meant to accomplish, which is fast. LLE (low-level emulation) options reproduce the RSP more literally, which is more accurate but heavier. Keeping these three options in mind will make the slowdown section below much easier to follow.

3. Give N64 saves their own folder

RetroArch can keep saves for every system in one shared location, but for the N64 we recommend a separate save folder, because of the save-type issues covered later in this guide. When something goes wrong, having N64 saves isolated makes it far easier to figure out what happened.

Fixing Slowdown and Stuttering

“Every other system runs fine, but N64 is slow” is one of the most common complaints, and if you look at the symptom, the cause usually narrows down quickly. The table below covers N64-specific checks; general Android emulation tuning is a separate topic.

The order matters. First lower the internal resolution. If that is not enough, switch the RSP to HLE. Only then switch to a lighter plugin. Change one thing at a time; if you change everything at once, you will not know which setting actually fixed the problem.

Controller Setup: Solving the C-Button Problem

The N64 controller has four C-buttons (C-Up, C-Down, C-Left, C-Right) in addition to the analog stick and D-pad. Modern Xbox-style controllers have nothing that maps directly to those four buttons, and this is the biggest stumbling block for most people.

There are two main ways to handle it:

1. Map the C-buttons to the right analog stick. This is the default in many emulators: tilting the right stick up, down, left, or right registers as the matching C-button. It works well in most cases, though it can feel a little unnatural in games where you use the C-buttons for camera control and expect a stick to behave like a camera stick.
2. Map each C-button to a back button. If your controller has two to four rear paddles, you can put the C-buttons there and reach them without taking your thumbs off the sticks, which makes a noticeable difference in games that use them constantly.

Whichever approach you choose, save the mapping and it will load automatically next time. It is a one-time job.

Saves, Storage, and Your Setup

Once games are running, the last step is getting your environment in order.

Dump ROMs from your own console and cartridges

The rule is simple: dump games from an N64 and cartridges you own. We do not cover obtaining ROMs from anywhere else. Dumping is typically done with a dedicated cartridge-reading device that connects to a PC; we do not recommend any specific product here.

A note on the law (United States): N64 games are copyrighted software. Copying games you do not own, or sharing your own dumps with others, is copyright infringement. U.S. copyright law, including the Digital Millennium Copyright Act (DMCA), also restricts circumventing copy protection, and whether making a personal backup of a game you own is permitted is not clearly settled. The only approach this guide describes is dumping cartridges you personally own for your own use. This is general information, not legal advice; if you have questions about your specific situation, consult a qualified attorney. Laws differ outside the U.S., so check the rules where you live.

Choose your microSD card for speed

N64 ROMs are small compared with disc-based systems, but if you keep a whole library on the card, read speed makes a noticeable difference in how quickly things load. Look for the A2 and UHS speed ratings on the packaging, and pick a capacity that leaves room for the other systems you play.

Watch out for save-type mismatches

This is the N64’s biggest trap. Cartridges used several different save methods: SRAM, 4Kbit EEPROM, 16Kbit EEPROM, and FlashRAM, and some games saved to a Controller Pak memory card instead of (or as well as) the cartridge. Each game uses its own method.

Mupen64Plus-based emulators generally decide which save type to use from a built-in game database with per-ROM settings, not from the ROM header. That works for the vast majority of games, but it occasionally gets it wrong, and it is more likely to miss with modified ROMs or regional versions that are not in the database. The symptom is exactly the one people describe: saving appears to work, but when you come back, your progress is gone.

If this happens, check whether your app or core has an option to set the save type manually. If it does, switch it and choose the correct type. If you are not sure which is right, try the candidates one at a time and test each one properly: save, fully close the app, relaunch it, and see if the save loads. That is the only reliable confirmation.

Wrapping Up: Get Performance and Save Types Right, and the N64 Plays Well

A quick recap:

• M64Plus FZ Emulator (by Francisco Zurita) is the app to start with. If you want all your systems in one place, use RetroArch with Mupen64Plus-Next.
• The N64 is demanding because an emulator has to recreate the RCP and its two processing units, the RSP and RDP, in software. Differences between games come down to their microcode.
• When things are slow, lower the internal resolution, then set the RSP to HLE, then switch to a lighter plugin, one change at a time.
• Map the C-buttons to the right stick or to rear paddles. The mapping is saved, so you only do it once.
• If saves disappear, set the save type manually where your app or core allows it. The automatic detection is occasionally wrong.

There are more settings to think about than with PlayStation or TurboGrafx-16 emulation, but nearly every problem comes back to those two areas: performance and save types. Work through them in the order laid out here, and even an older device can run the well-known titles, like Super Mario 64 and The Legend of Zelda: Ocarina of Time, comfortably.

And one last reminder: ROMs and save data should come from your own console and your own cartridges. If your old N64 carts are sitting in a closet, this is a good way to bring them back out and play them on the couch or on your commute.