Search this topic and you will find three completely different things all described as "playing Switch games on your iPhone". They are not interchangeable: the hardware floor, the setup time and the way they break are different in every case.
| Route | How it actually works | Hardware floor | Setup | Where it breaks |
|---|---|---|---|---|
| Emulator MeloNX and its lineage | Translates the game's instructions while it runs, which is why it depends on JIT (just-in-time compilation) | Any recent iPhone — but only where JIT can be enabled for your iOS version | An hour or two | Frame rates swing between games and builds; JIT availability changes with every iOS release; this corner of the ecosystem has been taken down before |
| Native rebuild nxnative, NX2Apple, d2r-mobile | The game's own code runs on the Apple chip. Only the operating-system services it calls are reimplemented, plus an offline shader translation | iPhone 15 Pro or newer for most titles; d2r-mobile runs from A14 | An evening — needs a Mac and a 30–60 minute first build | The memory ceiling, signature expiry, and per-game profile work |
| Streaming Remote Play, GeForce NOW, Steam Link | The game runs on your console or PC; the phone is only a screen and a controller | Any iPhone | Minutes | Needs a stable network and the other machine switched on |
This is the most useful thing to understand before you spend an evening on setup, and almost nobody explains it.
Switch games ship their textures in BC-compressed formats — a block-compression family designed for desktop and console GPUs. Apple's GPUs only gained a hardware path for those formats with the A17 Pro chip. On anything older, every texture in the game would have to be converted before the GPU could read it.
nxnative states this directly as the reason for its device floor: iPhone 15 Pro or newer, iOS 26 or later, and an M1 iPad or later. Its 62-game list was built inside that envelope — so "runs on iPhone" in that list means that iPhone.
d2r-mobile, the project this site started with, has a much lower floor: A14, the iPhone 12 generation. Its documentation does not explain the difference. Two plausible readings — it converts textures during the build, or Diablo II's assets happen to use a format Apple's GPUs already read — but treat that as our inference, not a project claim. What is certain is that the two projects made different trade-offs, and the cheaper one costs something somewhere.
| Blocker | What it means | What to do |
|---|---|---|
| No Mac | The build pipeline is macOS-only — it needs Xcode and Metal. NX2Apple wants an Apple-silicon Mac on macOS 13 or later. | Borrow one for an evening. Or use d2r-mobile's no-Mac route, which is the only one of the three that has one. |
| The memory ceiling | Without the increased-memory-limit entitlement, iOS gives a sideloaded app about 3.4 GB. Measured, not estimated: 3,375 MB on a 12 GB iPhone, where Tears of the Kingdom was killed at 3,342 MB opening the world map. | Sign with the Increased Memory Limit capability — AltStore, Sideloadly and LiveContainer can. Titles near or over the line: Hades II, Hyrule Warriors: Age of Calamity, Breath of the Wild, Cuphead. |
| Signature expiry | A free Apple ID signature lasts 7 days; after that the app stops launching until you re-sign. | Re-sign weekly, or use a paid developer account. |
Most failed attempts fail at step two, not step four. Plan for that.
prod.keys from your own console. None of these projects ship or link to any of it, and neither do we.log.txt. When something breaks, that file is the only thing that gets you an answer.| Your situation | Route | Why |
|---|---|---|
| iPhone 15 Pro or newer, plus access to a Mac | Native rebuild | Best result available: 60 fps, offline, no runtime translation, one evening of setup. |
| iPhone 15 Pro or newer, no Mac, and the game you want is Diablo II | Native rebuild, no-Mac route | d2r-mobile is the only project with a Windows/Linux packaging path — see the install guide. |
| iPhone 14 or older | Streaming | The texture-format wall is hardware, not software. No amount of setup gets around it. |
| A gaming PC or console already in the house | Streaming | Zero setup, no grey area, and the game runs at full quality on the host machine. |
| You want to try before committing an evening | Streaming first | Find out whether playing on a phone is even for you before you spend the evening on a build. |
All three native-execution projects — d2r-mobile, nxnative and NX2Apple — are MIT-licensed code that contains no game data. They work only with files from a copy you own, plus keys dumped from your own console. That is also why we will not host, link to, or explain how to obtain game files, keys, firmware or ready-made install packages; requests for those will not be answered.
Two honest caveats. Emulator projects have been taken down before, and the native-rebuild approach is newer and legally untested — needing your own copy makes it more defensible, not guaranteed. And this is not legal advice: whether you may use any of this depends on where you live and how you obtained your files.
Route characteristics, device floors, memory measurements and game counts from the nxnative project README and its unofficial guide (checked 2026-10-25), the NX2Apple README (checked 2026-10-26), and the d2r-mobile README and release notes. The BC-texture explanation is our reading of nxnative's stated requirement; the A14 comparison is our inference and is labelled as such. Nothing on this page was measured on our own hardware.