Lime3DS Setup Guide: Play Pokémon on Android [2026]

What Lime3DS actually is in 2026 (and why the name is confusing)

The lineage matters here because it explains what you are actually installing. Nintendo’s 2024 legal action against Tropic Haze, the team behind the Yuzu Switch emulator, ended with a **.4 million settlement** and the shutdown of Yuzu. Because the same core contributors also maintained Citra, the leading 3DS emulator at the time, Citra went dark in the same wave. Lime3DS rose out of that gap as a community-maintained Citra fork, picking up bug fixes and keeping Android builds alive for about a year.

In April 2025, Lime3DS itself stopped development. Its GitHub organization was archived with a single message pointing users to Azahar, a separate but closely related successor project. Azahar absorbed most of the remaining Lime3DS contributor base and kept building for Windows, Linux, macOS, and Android. The catch: nobody updated the Android package name when the rebrand happened, so the app you download from Google Play today, built and maintained by the Azahar team, still identifies itself internally as `io.github.lime3ds.android`. Third-party download aggregators like Softonic and Uptodown never updated their listing titles either, which is why “Lime3DS for Android” search results are really just Azahar with old branding attached.

Practically, this means you should install Azahar, not hunt down an actual “Lime3DS” app separately. Every instruction below applies to the current Azahar Android build, and we use both names interchangeably where it helps with search since that is genuinely how people look for this software. If you want the fuller history of how the 2024 shutdown reshaped 3DS emulation, our Azahar vs Citra vs Lime3DS breakdown covers the lineage in more depth than we have room for here.

The naming confusion is not unique to this one project. Emulation scenes tend to fracture into forks whenever the lead maintainer of a popular project burns out or, as happened repeatedly through 2024 and 2025, gets pushed offline by legal pressure. Citra split into Lime3DS and a handful of smaller, shorter-lived forks. Yuzu splintered into Suyu, Sudachi, Citron, and eventually Eden on the Switch side. What makes the Lime3DS-to-Azahar transition slightly less messy than most is that it consolidated back into a single, actively maintained project instead of scattering across five competing forks with inconsistent update schedules. That consolidation is part of why Azahar has become the default recommendation across most current 3DS emulation communities, even though the search traffic still flows toward the old name.

Why Android 3DS emulation is a different problem than desktop

Most existing Azahar and Lime3DS tutorials online were written for Windows or Linux, where you have a discrete GPU, effectively unlimited sustained power, and a keyboard for navigating settings menus. None of that carries over to a phone. Android emulation runs on a shared System-on-Chip where CPU, GPU, and memory controller all draw from the same power and thermal budget, and that budget shrinks the moment the phone gets warm in your hand. A Snapdragon 8-series chip that would crush 3DS emulation in a cool, well-ventilated desktop case can throttle down to a fraction of its peak clock speed after fifteen minutes of continuous 3D rendering in a phone body a few millimeters thick.

Storage access patterns differ too. Android’s scoped storage rules, introduced years ago and still tightened with each OS release, restrict how apps read and write files outside their own sandboxed directory. That is precisely why the 2126.1.2 changelog calling out “native file I/O” for the Vanilla build is a meaningful detail rather than a throwaway line. The Google Play build has to work within Android’s storage sandboxing more conservatively, which costs it real loading-time performance compared to a sideloaded build that can request broader storage access. None of this is visible from a desktop tutorial, and it is exactly the kind of detail that trips up someone who follows PC-focused instructions on a phone and cannot figure out why their experience does not match what they read.

Prerequisites: what your phone needs before you start

Azahar 2126.1.2 raised its Android floor from Android 9 to Android 10 in the September 2026 update, so older devices lose access to new builds and get stuck on the 2123.4.1 line. Check your Android version before doing anything else. Here is the full requirement breakdown, split between the documented minimum and what actually delivers a playable experience with Pokémon titles.

– Android version: Android 10.0, 64-bit
– Chipset: Snapdragon 835-class or better
– RAM: 2 GB
– GPU API: OpenGL ES 3.2 or Vulkan 1.1
– Storage free: ~150 MB for the app
– Emulator version: Azahar 2126.1.2 (Sept 20, 2026)

You also need three things Azahar cannot legally provide for you: a real Nintendo 3DS console you own, the Pokémon game cartridges or eShop purchases you own, and a way to move dumped files from that console to your Android device. There is no shortcut around this part. Downloading keys or ROM dumps from a third-party site is a copyright and, in some jurisdictions, a circumvention-law issue, and it is also how people end up installing malware disguised as a “keys pack.” Dump your own hardware.

Step 1: Confirm your device meets the baseline

Open Settings, then About Phone, and check your Android version and chipset. If you are running Android 9, Azahar will still install from Play Store archives, but you will be capped at version 2123.4.1 indefinitely since 2126.1.2 and everything after it requires Android 10. If your chipset predates the Snapdragon 835 generation (roughly 2017 and earlier flagships, or most budget phones from any year), expect Pokémon Sun and Moon to run below full speed even at the lowest settings. There is no way to reliably promise exact frame rates for a given phone since performance depends on GPU driver maturity, thermal headroom, and background load as much as raw chipset class, so treat any site quoting a locked “30 FPS” figure for a specific phone model with skepticism unless they show their testing conditions.

Step 2: Install Azahar from the correct source

Two Android variants exist. The **Google Play build** (package `io.github.lime3ds.android`) is the one most people should use since it auto-updates and comes from a listing you can verify directly on the Play Store. The **Vanilla build**, distributed as a sideloaded APK through the project’s GitHub releases or the Obtainium app, adds native file I/O that the 2126.1.2 changelog specifically calls out as meaningfully faster for game loading than the Google Play build. If you care about shaving seconds off boot times and do not mind manually installing update APKs, Vanilla is worth the extra step. If you want it to just stay current without thinking about it, use Play Store.

– Play Store route: search “Azahar Emulator” or open the direct listing at play.google.com/store/apps/details?id=io.github.lime3ds.android and tap Install.
– Vanilla APK route: install Obtainium from its GitHub releases page, add the app source `https://github.com/azahar-emu/azahar`, and let it track and install new APK releases directly.
– Avoid any APK offered through a ROM site, a Discord invite link, or a “modded” build promising extra speed. There is no verified legitimate reason a 3DS emulator needs a modified APK, and this is the most common malware vector in the emulation space.

After installation, confirm you actually got version 2126.1.2 rather than a stale cached build, since some regional Play Store mirrors and third-party stores lag behind the official release by days or weeks:

“`
# Check the installed Azahar version and package details
adb shell dumpsys package io.github.lime3ds.android | grep -E “versionName|versionCode”

# Expected output on a current install:
# versionName=2126.1.2-googleplay
# versionCode=21261200
“`

Step 3: Dump your system files from your own 3DS

Azahar needs four files pulled from a real, powered-on 3DS console before it can decrypt and run commercial game files: `boot9.bin`, `boot11.bin`, an AES key file, and `seeddb.bin`. The standard, well-documented way to get these is with GodMode9, a homebrew file manager that runs directly on 3DS hardware. Checkpoint is a separate tool built for save-file management, not full system-file dumping, so do not substitute it for this step. If you have never installed homebrew on your 3DS before, follow GodMode9’s own current documentation for your exact console model and firmware version, since the entry method (browser exploit, Homebrew Launcher, etc.) shifts depending on your system software.

Once GodMode9 is running, use its built-in dump options (usually under a menu labeled something like “Dump boot9.bin/boot11.bin” and a separate NAND or key dump function) to write the four files to your SD card. This has to happen on hardware you own. There is no legitimate way to obtain someone else’s dumped keys, and using shared keys downloaded from a forum or Discord server violates both the emulator project’s guidelines and, depending on your country, actual law.

Expect this step to take longer than the rest of the setup combined if you have never touched 3DS homebrew before. Getting GodMode9 onto the console in the first place typically means running a browser-based or game-save exploit specific to your firmware version, since Nintendo never intended the console to run unsigned code. Once GodMode9 boots, though, the actual dump operations are quick, usually under a minute each, since you are reading a few hundred kilobytes of boot firmware rather than an entire game cartridge. Write the resulting files somewhere you will not accidentally delete them. Losing a working set of dumped keys means starting the entire homebrew entry process over again from a factory-fresh system state, which is the most common reason people give up on 3DS emulation midway through setup.

Step 4: Move key files to your Android device

Pull the SD card from your 3DS, connect it to a computer, and copy the four dumped files over to your phone through a cable, cloud sync folder you control, or a direct SD-to-phone transfer if your device has a card reader. Azahar expects these in a specific folder structure inside its app data directory. If you are comfortable with ADB, this is the fastest and most reliable way to confirm the files landed in the right place:

“`
# Connect phone via USB with debugging enabled, then:
adb push boot9.bin /sdcard/Android/data/io.github.lime3ds.android/files/sysdata/
adb push boot11.bin /sdcard/Android/data/io.github.lime3ds.android/files/sysdata/
adb push aes_keys.txt /sdcard/Android/data/io.github.lime3ds.android/files/sysdata/
adb push seeddb.bin /sdcard/Android/data/io.github.lime3ds.android/files/sysdata/

# Confirm all four files transferred correctly
adb shell ls -la /sdcard/Android/data/io.github.lime3ds.android/files/sysdata/
“`

A correct transfer produces output like this, confirming file sizes match what GodMode9 wrote on the 3DS side:

“`
-rw-rw—- 1 u0_a234 media_rw 65536 2026-09-27 14:02 boot9.bin
-rw-rw—- 1 u0_a234 media_rw 65536 2026-09-27 14:02 boot11.bin
-rw-rw—- 1 u0_a234 media_rw 2320 2026-09-27 14:02 aes_keys.txt
-rw-rw—- 1 u0_a234 media_rw 139264 2026-09-27 14:03 seeddb.bin
“`

If you would rather skip ADB entirely, most Android file managers can reach the same app-private folder as long as you enable “show hidden files” and navigate manually, though this varies by Android version and manufacturer skin.

Step 5: Point Azahar at your key files

Open Azahar, go to Settings, then System, and look for a key/file import option. Recent 2126-series builds detect files sitting in the expected sysdata folder automatically and show a green checkmark or similar confirmation next to each required file. If it shows a file as missing even after your ADB push completed cleanly, double check the exact folder path, since a misplaced trailing slash or wrong subfolder name is the single most common setup failure at this stage.

Step 6: Dump your Pokémon game files

With keys in place, dump the actual games. If you own physical Pokémon cartridges, GodMode9 can create a decrypted `.3ds` or `.cia` file from the cart while it is inserted in your console. If you bought Pokémon titles digitally through the eShop, you can create a legally sound personal backup using the same homebrew tools, since you already own a license to the software. Move the resulting game files to your phone the same way you moved the keys, ideally into a dedicated folder like `/sdcard/3DSGames/` to keep your library organized as it grows.

Do not download Pokémon `.3ds` or `.cia` files from ROM sites even if you own the physical cartridge. Owning a cartridge does not make someone else’s uploaded dump a legal substitute for your own personal backup in most jurisdictions, and pirated dumps are also a common source of tampered, malware-laced files.

Step 7: Load your first game and verify it boots

Back in Azahar, tap the folder icon or “Add Game Directory,” point it at your `3DSGames` folder, and the app should scan and populate a library grid with box art pulled from the game’s embedded metadata. Tap a title to launch it. A clean first boot shows the Nintendo 3DS system logo animation followed by the game’s own splash screen within a few seconds on a Snapdragon 8-series phone, closer to 10-15 seconds on something in the Snapdragon 835-to-660 range. If the app crashes immediately on launch instead, that is almost always a missing or corrupted key file rather than a problem with the game dump itself.

Step 8: Choose your renderer, Vulkan or OpenGL

Azahar supports both OpenGL ES 3.2 and Vulkan 1.1 on Android. The 2126.1.2 update specifically fixed a Vulkan regression that produced incorrect textures and a crash tied to malformed geometry shaders in earlier 2126-series builds, so Vulkan is now the more sensible default on a phone with a mature driver, meaning most 2022-or-newer Snapdragon and recent Dimensity chips. Go to Settings, then Graphics, and switch the renderer to Vulkan. If you see visual corruption, sudden crashes to the home screen, or noticeably worse frame pacing than OpenGL gave you, switch back. Test a full gameplay session rather than judging from the first minute, since some rendering issues only appear after shader caches build up during actual play.

Step 9: Set up touch controls and the virtual gamepad

Pokémon games lean on the 3DS lower touchscreen constantly, for menus, the Poké Transfer app, and battle UI shortcuts, so getting the on-screen layout right matters more here than in most emulated games. Open the in-game overlay menu (usually a small gear or controller icon at the edge of the screen) and find “Toggle Controls.” The September 2026 update fixed bottom-edge flickering and misaligned click boxes in this exact menu, so if you tried Azahar earlier in 2026 and found the control editor buggy, it is worth revisiting now.

– Drag the Circle Pad, D-pad, and face buttons to comfortable thumb positions, then lock the layout once you are happy with it.
– Lower the opacity of on-screen buttons to 40-50% so they do not obscure the lower touch screen during menu navigation.
– Keep the lower screen fully touch-responsive at all times. Pokémon’s menu system and several minigames depend on it.
– For long play sessions, pair a Bluetooth controller through Android’s standard Bluetooth settings. Azahar recognizes standard HID controllers automatically once paired, and it removes thumb fatigue from holding a phone with on-screen buttons for hours.

Step 10: Tune resolution and New 3DS mode

Pokémon Ultra Sun, Ultra Moon, and the enhanced New Nintendo 3DS features in several titles run noticeably better with New 3DS emulation mode enabled, since it unlocks the extra CPU cores the New 3DS hardware physically had. Under Settings, then System, enable “Is New 3DS” if you plan to play New 3DS-enhanced titles. For internal resolution, start at native (1x) before increasing the scaling slider. Bumping resolution scaling makes text and 3D models sharper but adds real GPU load, and Pokémon’s overworld rendering in the Sun and Moon era is demanding enough on lower-end chipsets that 1x is often the difference between a stable 30 fps and constant stutter.

Step 11: Configure save states and back up your saves

Azahar supports standard save states alongside the game’s native in-game save system. Use save states for quick checkpoints before a risky battle or trade, but do not treat them as a replacement for the game’s real save file, since save state compatibility can break across emulator updates in ways native saves do not. For deeper save management, including fixing corrupted Pokémon data or transferring a roster between game versions, our PKHeX save editor guide covers the tool most people reach for next. Back up your save folder (found under the app’s data directory, in a subfolder matching each game’s title ID) to cloud storage or a computer periodically. This is the single most overlooked step by people who lose 40 hours of a Pokédex run to a phone factory reset or app data wipe.

If you would rather not remember to do this manually, a simple scheduled pull to a computer on the same network covers most people’s needs:

“`
# Pull the full save directory to a dated backup folder on your computer
mkdir -p ~/azahar-backups/$(date +%Y-%m-%d)
adb pull /sdcard/Android/data/io.github.lime3ds.android/files/saves/
~/azahar-backups/$(date +%Y-%m-%d)/

echo “Backup complete: ~/azahar-backups/$(date +%Y-%m-%d)/”
“`

Step 12: Test local play and trading features honestly

Whether two phones running Azahar can trade Pokémon with each other over local wireless is not something with a clean, documented answer as of the September 2026 builds. Support for this kind