NX2AppleNX2Apple

NX2Apple · unofficial guide

NX2Apple vs nxnative

Pick the GUI if you want clicks and a library. Pick upstream CLI if you already build from a terminal. Keys and dumps stay yours either way.

Not affiliated with Nintendo or the NX2Apple maintainers. We do not host installers, keys, firmware, or games — downloads go to GitHub Releases.

Roles in one paragraph each

nxnative (seedds/nxnative) is the engine: rewriter, Horizon host layer, NVN on Metal, per-game profiles, and command-line build scripts. NX2Apple (LNPANDY/NX2Apple) is a community project that follows nxnative, carries a patch queue, and adds a macOS launcher with setup wizard, progress UI, and a Play library. Both require your dumps and prod.keys; neither ships Nintendo content. This website documents the GUI path first because that is what most non-developers install from Releases.

When to choose which

Choose NX2Apple for guided setup, dependency checks, stoppable builds with visible stages, and day-to-day Play. Choose nxnative docs and CLI when bringing up a new title, debugging engine patches, or automating builds in scripts. App chrome bugs belong on NX2Apple issues; deep engine defects often belong upstream, sometimes after you confirm they reproduce outside the launcher. You can read both READMEs; you should not mix random binaries from unrelated forks without understanding signing and profile differences. Community branches that target older iOS versions may exist outside this fork — evaluate them separately and still bring your own keys.

  • nxnative — engine and CLI
  • NX2Apple — macOS launcher on top
  • Same BYO dumps and keys model

Shared responsibilities

Regardless of GUI or CLI, you must keep Xcode sane, match update versions to profiles, and avoid sharing keys. Release discipline still matters: pinned upstream commits and patch queues can invalidate assumptions from last month’s blog posts. This comparison page is not an official endorsement chart from either repository’s authors. 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.

This site is not official. We do not host installers, prod.keys, firmware, or game dumps. Downloads go to GitHub Releases. Bring your own legally obtained dumps and keys.

FAQ

Is NX2Apple the same repo as nxnative?
No. NX2Apple follows nxnative and adds launcher experience plus patches.
Can I use both?
Advanced users might, but pick one daily driver to avoid mixed toolchains and confused logs.
Where do I get support?
Launcher issues → NX2Apple GitHub. Engine-deep issues may need upstream context.
Does either distribute ROMs?
No. Both expect files you already own.