What Is Peanuts Native? Switch Games Running Natively on Android
Peanuts Native turns your own Switch dumps into Android apps, built on the phone. How it works and what it needs.

Peanuts Native turns a Switch game you already own into a standalone Android app, built on the phone, with no emulator in the middle. You point it at a game dump, tap Build, and it rewrites the game so it runs on your phone's own CPU. On a dual-screen handheld such as the AYN Thor, the bottom screen turns into a live map or party panel while the game runs up top.
That's a different trick from the emulators most people install. There's no virtual console to configure and no per-game profile to tune by hand. If you've been hunting for Switch games on Android that run without an emulator, this is the project people mean. The trade is hardware. This only works on a recent Snapdragon device with 12GB of RAM or more, and the first build of a large game can eat the better part of an hour.
This explainer covers what Peanuts Native actually does under the hood, what it asks of your phone, how to install it, and where the current 0.1.1 release still falls over.
What Peanuts Native does that an emulator doesn't
An emulator pretends to be a Switch. It loads the game's code, translates instructions as they execute, and hopes the timing holds.
Peanuts Native is a native translation layer, a fork of BananaNative by the developer behind Eden Duo. It reads your game dump before you play and rewrites the game's ARM64 code so it executes directly on the phone's CPU. Graphics calls get replayed over Vulkan, and the shaders are translated on the device before the first frame. The project's own description puts it plainly: a dump of a Switch 1 game you own becomes an Android app.
The practical difference shows up in overhead. An emulator has to model hardware that isn't there, so every frame pays a tax. A converted game skips that layer, which is why Metroid Dread and Super Mario Odyssey can hold 60fps on a handheld that would struggle to emulate them at 30.
It also means there's no compatibility list to babysit. A game either converts and runs, or it doesn't.
How a Switch game becomes an Android app on your phone
The build is the interesting part, and it happens entirely on the device.
- You add your keys file, your firmware dump, and a folder holding your game files.
- You open a game from the library and tap Build.
- The app imports the game, rewrites its code, translates its shaders, and installs the companion package for that title.
- When the build finishes, you tap the game and play.
On an AYN Thor, most games finish in five to 40 minutes, a range that runs wide because the work scales with the size of the game and the number of shaders it has to translate. A 2D title like Link's Awakening lands near the fast end, while a 3D game with a long shader list sits at the slow end of that range.
You can also build on a computer and push the result to the phone. That path is documented in the repo's BUILDER.md, and it's tested on macOS and Linux. Windows support is written but untested.
After an app update, rebuild every game you care about. The developer recommends it, and the steps are short: hold the game's cover, open Storage, tap Build, then Rebuild.
Why the bottom screen does the work
This is the feature that separates Peanuts Native from a plain conversion tool.
On a dual-screen handheld, the game plays on the top panel while the bottom panel renders a companion for that game. The companion shows a live map, your party, your items, or your quest log, read from the running game's memory and updated as you play. Touch works. So does haptic feedback, which means you can tap a map pin or a menu row without looking down.
Companions use the same package format as Eden Duo, so the existing Eden Duo companion library works here without conversion. You manage them under Settings, then Companions, where you can install, update, remove, or roll a companion back to an earlier release. Each download is checked against its published checksum before the app uses it.
Single-screen phones still run the converted games. They just lose the second panel, which is most of the appeal.
What you need before the first build
The requirements are strict, and they're the main reason people bounce off this project.
- A dual-screen Android handheld is the intended target. Peanuts Native is developed and tested on the AYN Thor. Other Snapdragon handhelds and flagship phones can work, but the companion is the point.
- Android 13 or later. Older versions aren't supported.
- 12GB of RAM or more. This is a hard floor, not a suggestion.
- A Snapdragon GPU with Vulkan 1.3 support. A Turnip Vulkan driver is recommended, and the app can download one for you.
- Free storage for the game and its build. Plan for the size of the game plus a few GB of scratch space.
- Your own prod.keys file, your own firmware dump, and your own game dump in NSP, XCI, or folder form, along with the matching game update.
That last point isn't optional, and it isn't a formality. Peanuts Native ships no game code, no firmware, and no keys. The project's README is explicit that it never downloads them and doesn't link to anyone who offers them.
Installing Peanuts Native on Android
There's no Play Store listing. The app comes from the project's own releases page, which is the only place you should get it.
- Open the Peanuts Native repository and go to Releases. Grab the APK from the latest 0.1.x release.
- Install the APK. Android will warn you about installing from an unknown source, so allow that for your browser or file manager first.
- Open the app and grant All files access when it asks. Without it, the app can't read your game folder.
- Add your prod.keys file on the first screen.
- Add your firmware, either as a folder or as a zip.
- Pick your game folder. If you want builds kept in one place, set a build folder under Settings, Library, Build folder. A microSD card works.
- Open a game and tap Build. Leave the phone awake and plugged in for the first one.
- When the build completes, tap the game to play. On a dual-screen device, the companion starts on the bottom panel.
If a game needs a specific update version, its page tells you which one it supports and asks before building anything else. Say no and nothing breaks.
The 12 games it runs at launch
The 0.1.1 release ships with these titles, and each one has a working companion on the Thor.
Game | Frame rate |
|---|---|
The Legend of Zelda: Link's Awakening | 60fps |
The Legend of Zelda: Echoes of Wisdom | 60fps |
Super Mario Odyssey | 60fps |
Metroid Dread | 60fps |
Mario Kart 8 Deluxe | 60fps |
Fire Emblem: Three Houses | 60fps |
Fire Emblem Engage | 60fps |
Castlevania: Belmont's Curse | 60fps |
Octopath Traveler 0 | 60fps |
Pokemon Brilliant Diamond | 60fps |
Animal Crossing: New Horizons | 30fps |
Persona 5 Royal | 60fps |
Two more titles have landed since the first release: Pokemon Sword and The Legend of Zelda: Breath of the Wild, both listed at 60fps with companions, with Breath of the Wild marked as little tested. Super Mario Bros. Wonder and Dragon Quest III HD-2D Remake appear in the table but haven't been tested on a device yet.
Where it breaks down
The honest version: this is a 0.1.x release, and it behaves like one.
Game updates are the biggest tripwire. Some games accept more than one update version. Others need the exact one listed on their page. Build with an unsupported update and the result may not start at all.
Resolution scaling goes from 0.5x to 2x, but not every visual effect follows the setting, so a game can look sharper while one layer stays soft.
Mods work, with a caveat. A mod that changes game code triggers a separate build with mods, and that build runs on its own. Until it's ready, the game starts without the mod.
And the companion isn't quite free. The project says the games above hold their frame rate with it running.
Is Peanuts Native legal?
The project answers this directly, and the answer holds up.
It runs a dump of a game you own, made from your own console, with keys from that console. It contains no Nintendo code, firmware, or keys. It doesn't download them and doesn't point you to places that do. The code is GPL-3.0-or-later, and the project states it isn't affiliated with Nintendo.
What you can't do is share the output. Built games and translated shaders are derived from your own files, so passing them around is off the table even inside the community.
FAQs
- Does Peanuts Native work on a normal single-screen phone?
- Yes. The game builds and runs, but you lose the companion panel on the bottom screen, which is the main reason to use this over a standard emulator.
- How long does the first build take?
- Five to 40 minutes on an AYN Thor, depending on the game. Large 3D titles sit at the slow end, and the phone should stay awake and plugged in.
- Do I need to own the games?
- Yes. You need your own dump, your own prod.keys, and your own firmware. The app ships none of that and won't fetch it for you.
- Will my existing game update work?
- Check the game's page in the app. Some titles accept several update versions, others need the exact one listed, and an unsupported update can produce a build that won't start.
- Can I move a build to another phone?
- No. Builds are derived from your own game files, and the project asks users not to share them.
The short version: Peanuts Native is worth a look if you already own a dual-screen Snapdragon handheld and a shelf of Switch games. On anything else, a normal emulator is still the easier path. Install it from the project's releases page, start with the smallest game you own, and let the first build finish before you judge the frame rate.