NX2Apple · unofficial guide
Install on iPhone / iPad
No App Store package and no macOS launcher on the phone. Build on the Mac targeting iPhone / iPad, then sideload with your own signing tool.
Not affiliated with Nintendo or the NX2Apple maintainers. We do not host installers, keys, firmware, or games — downloads go to GitHub Releases.
Install path
1 · Mac ready
Finish macOS install and setup so Xcode, keys, and dumps already work.
2 · Build for iPhone / iPad
In the launcher choose iPhone / iPad and Build. Watch stages; a stopped build can resume.
3 · Sideload
Follow the three on-screen install steps. We do not host IPA files.
4 · Play and entitlements
Open on device → Play. Huge titles may need Increased Memory Limit — read ENTITLEMENTS.md.
What the phone path actually is
People searching for an iPhone Switch app often expect a store install. NX2Apple does not distribute Nintendo games and does not offer a public App Store binary for piracy or grey-market stores. The supported story is bring-your-own dumps on a Mac, produce a device build, then sideload that build to hardware you control. Signing uses your Apple ID workflow; free provisioning windows expire and must be renewed. That renewal friction is normal for unsigned community apps and is not something this website can bypass. Controller support, touch layouts, and launch options are configured on device after install; see upstream playing docs linked from the project README when you need deep control mapping detail.
Memory limits and large games
Without Increased Memory Limit, iOS may give the app roughly a few gigabytes of headroom, which is not enough for the largest titles. The app requests the entitlement; whether it survives depends on the sideload tool. AltStore Classic, Impactor, and Xcode with a Personal Team are called out upstream as keeping it in common setups, while some other tools drop it. Read ENTITLEMENTS.md on GitHub for the current matrix instead of trusting screenshots that float around social media. Old romfs shard archives from early experiments may need a fresh romfs.img transfer through the launcher. External storage via the Files app can hold game data when internal free space is tight.
Device expectations
Upstream focuses on recent phones; older devices are largely untested on this fork’s release line. iOS version requirements move with the project — check the README for the version floor before you buy accessories or wipe a device for testing. Short stutters on first entry into a scene can be shader compilation; later visits should be smoother once caches exist. Personal backup and circumvention rules differ by country. You are responsible for knowing the law where you live. Never distribute dumps, keys, firmware, or the packages you build. If you enjoy a game, buy it from legitimate storefronts. This independent guide does not provide a ROM search, key database, or firmware mirror.
- Recent iPhone / iPad recommended
- Periodic re-sign with free or paid Apple ID
- romfs.img may live on Files-reachable storage
Step cards only — no device screenshots hosted here yet.
FAQ
- Can I install without a Mac?
- No. Building requires the macOS app and Xcode toolchain on Apple silicon.
- Where is the IPA download on this site?
- Nowhere. We do not mirror IPAs. Produce the build locally and sideload it.
- Why does the app stop working after a week?
- Free provisioning often expires. Re-sign with your usual sideload tool.
- Tears of the Kingdom crashes early on iPhone.
- Check memory entitlement survival for your sideload method and free space; see ENTITLEMENTS.md and GAMES.md.