Home/Blog/Nintendo

Nintendo 3DS

A 3DS emulator for Android, after Citra

Citra is gone, Azahar took its place, and the 3DS now runs on Android phones from an ordinary Google Play install. Which emulator to pick, which files work, which phones cope, and why Android has an edge here that the iPhone doesn't.

Updated 12 November 20267 min read

On iPhone or iPad? Read the iPhone version of this guide →

In short

The best-known 3DS emulator for Android, Citra, was discontinued in March 2024; Azahar, its open-source successor, is free on Google Play. Haptic Emulator also plays Nintendo 3DS games on Android, free from Google Play, running Azahar's core with its JIT recompiler on. It plays decrypted .3ds, .cci, .cxi and .3dsx files, needs no keys or system files, and wants a reasonably recent phone GPU.

Haptic Emulator's Nintendo 3DS layout: a kart race on the wide top screen, the course map on the touch screen below, and New 3DS controls with Circle Pad, ZL and ZR underneath
Haptic's 3DS skin: the wide top screen over the touchable lower one, New 3DS controls underneath.

A few years ago, if you asked which 3DS emulator for Android to get, the answer was one word: Citra. Then in March 2024 Citra disappeared, and anyone searching for it since has found a confusing mix of forks, old APKs on download sites and articles that stopped being true. The short version: the 3DS is very much playable on Android, from Google Play, and it runs better here than on an iPhone for a simple technical reason.

Here's what changed, what to use now, and what to expect.

What happened to Citra

Citra was the open-source 3DS emulator for years, on PC and on Android. It was made by the same team as Yuzu, the Switch emulator, and when that team settled Nintendo's lawsuit against Yuzu in March 2024, Citra was taken offline along with it. Its website and code repository went down with it.

Because the code was open source, it didn't vanish. Several forks carried on, and in October 2024 two of the main ones, Lime3DS and PabloMK7's Citra fork, announced they would merge into a single project: Azahar. Azahar's first release came in 2025, and it's now the maintained continuation of Citra, on Google Play.

Skip the old Citra APKs

Copies of the last Citra builds still circulate on APK download sites. They get no fixes, no updates for newer Android versions, and an APK from a random site is a classic way to end up with something on your phone you didn't want. Whatever you choose, install it from Google Play.

The best 3DS emulator for Android, honestly

We make Haptic, so weigh this accordingly. There are two good answers, and they suit different people.

AzaharHaptic Emulator
Where you get itGoogle Play (also GitHub)Google Play
PriceFree, open sourceFree to play, with ads; optional Pro
Systems3DS26, incl. 3DS, GameCube, PSP, DS
Game filesDecrypted onlyDecrypted .3ds, .cci, .cxi, .3dsx
CPU recompiler (JIT)YesYes, Azahar's
Settings to tuneManyA few: resolution 1× to 3×
Screen layoutSeveralStacked, as on the console
MultiplayerAdded in 2026Not for 3DS
LibraryGame listBox-art shelves, one per console

Details as of November 2026, from each project's own site and Google Play listing; they will drift, especially Azahar's, which updates often.

Azahar is the one to get if you like to tune: graphics options, layouts, and the kind of depth Citra users were used to. It's actively developed — its 2026 releases added multiplayer support, among other things — and the project itself recommends installing it from Google Play. Like Haptic, it plays decrypted games only; encrypted ones are refused.

Haptic is the one to get if you'd rather not tune anything. You import a game and press play. The 3DS gets its own skin with a New 3DS control layout, every press answers through the phone's vibration motor, and the game sits on a 3DS shelf with its cover art, next to your GBA, PSP and GameCube games. The trade is fewer options: one stacked layout, no 3DS cheats, no 3DS multiplayer.

Why 3DS on Android has a JIT

The 3DS's processor speaks a different dialect of ARM from your phone's. An emulator has two ways to deal with that. An interpreter reads each 3DS instruction and works out what it means, every single time. A JIT recompiler translates a block of the game's code into your phone's own instructions once, then simply runs the translation from then on. The second is far less work.

Apple doesn't let App Store apps use a JIT, which is why the iPhone version of Haptic runs the 3DS on an interpreter and has to work hard to keep up. Android has no such rule. On Android, Haptic runs Azahar's ARM64 recompiler, the approach Citra used on Android too. The processor side stops being the bottleneck, and the question becomes mostly about your phone's graphics chip.

Which phone you need

Haptic needs Android 9 or later on a 64-bit ARM phone, which is nearly every phone sold since about 2019. That's the minimum to install. For the 3DS, the useful question is the GPU.

You can render at 1×, 2× or 3× the original resolution. If a game struggles, dropping a step is the first thing to try. And since Haptic is free, the quickest way to know how a game runs on your phone is to try it.

Getting started: the one-minute part

  1. Install Haptic Emulator from Google Play. No APK, no "unknown sources" setting.
  2. Tap import and pick the game with Android's file picker. You can also share a file into Haptic from another app — Files, a browser download or your cloud drive app. Zip, 7z and RAR archives are unpacked for you.
  3. Let it file itself. The game lands on the 3DS shelf with its box art.
  4. Press play. The 3DS layout loads: Circle Pad, D-pad, A/B/X/Y, L and R, ZL and ZR, Select and Start.

The free version holds a handful of games in its library; Haptic Pro lifts the limit and adds unlimited save states, fast-forward and batch import.

"Decrypted" is the one word that matters

3DS cartridges are encrypted, and a straight copy stays encrypted. Haptic plays decrypted game files only and checks at import, so an encrypted file is refused with a message rather than failing later. .cia files are installers rather than games and are refused too. There's no keys file, firmware or system archive to add: the core ships open-source stand-ins for the system data games look for.

Two screens, and a real controller

The screens are stacked the way the console held them, the wide top screen over the smaller one, and the lower screen takes touch directly — menus, maps and move lists are a tap away. On a foldable or tablet the layout scales to the bigger display.

Controllers are where Android shines. PlayStation and Xbox controllers and other Bluetooth or USB gamepads all work, and on a controller the right stick acts as the New 3DS's C-stick. You can remap buttons, and if you'd rather keep vibration for in-game moments only, the in-game menu lets you switch the button, control and rumble feedback on or off separately.

What doesn't work

Your game files and saves stay on the phone and are never uploaded. Android's own Google backup doesn't include them, so use Haptic's export or backup if you want a copy somewhere else.

For the curious (optional)

The 3DS ran on an ARM11 processor, an older 32-bit design, with a PICA200 graphics chip, a 400×240 top screen and a 320×240 bottom one. Your phone's processor is a 64-bit ARM chip that can't run that old code directly, which is what the recompiler fixes. The graphics are a separate job: the PICA200's effects are rebuilt as shaders on your phone's GPU, compiled the first time they're needed and kept afterwards. That's why the GPU, not the CPU, decides how well 3DS games run on Android, and why that first-time stutter goes away.

Frequently asked questions

What happened to Citra on Android?
Citra was taken offline in March 2024. It was made by the same team as the Switch emulator Yuzu, and went down with it when Yuzu settled Nintendo's lawsuit. Its open-source code lived on in forks, and two of them, Lime3DS and PabloMK7's Citra fork, merged into Azahar, which is now the maintained continuation and is on Google Play. Old Citra builds get no updates.
What is the best 3DS emulator for Android?
For the most settings in an app made only for the 3DS, Azahar: it's free, open source and on Google Play. For the 3DS on the same shelf as 25 other systems, with console-style skins, vibration on every press and box art, Haptic Emulator, which runs Azahar's core. Both play decrypted game files only, and both are worth trying.
Does Haptic use JIT for 3DS on Android?
Yes. Android lets apps use a JIT recompiler, so Haptic runs Azahar's ARM64 recompiler, which translates the 3DS's processor code into the phone's own once and reuses it. The iPhone version isn't allowed to and runs an interpreter instead. On Android that makes the processor side much lighter work, and the phone's graphics chip becomes what matters most.
Which Android phones can run 3DS games?
Haptic needs Android 9 or later on a 64-bit ARM phone, which covers nearly every phone sold since about 2019. For 3DS, the graphics chip is what counts: games render on the GPU through Vulkan or OpenGL ES 3.2, so a recent mid-range or flagship phone runs them best, and older budget phones may struggle with the heaviest 3D games.
Which 3DS files work, and why was my file refused?
Decrypted .3ds, .cci and .cxi game files, .3dsx homebrew, and the compressed .zcci, .zcxi and .z3dsx. Encrypted dumps and .cia installer files are refused at import, with a message saying why. No AES keys, firmware or system files are needed.
Does Haptic Emulator come with 3DS games?
No. Haptic ships no games, no ROMs, no keys and no BIOS files, and provides no way to find them. It plays backups of games you already own.

The 3DS, and 25 more.

Haptic Emulator runs 26 retro systems on Android phones — free to play, and it ships no games: it plays the ones you already have.

Free on Google Play · Android 9 and later · 26 systems