Your Switch games, running on your iPhone.
Not an emulator. No terminal. A macOS app does the whole build in a few clicks.
- A brand-new GUI — the Mac launcher is here: manage your game library the way you manage a Switch.
- Saves, freed — every Mac game's saves and logs live together in the game library folder.
- iPhone game data, freed — the game's
.imgdata finally loads straight from an external drive on iOS.
A macOS app takes your own game dumps and does the whole thing with a few clicks — unpack, rewrite the game's code for Apple silicon, translate its shaders to Metal, pack a slim IPA plus a sharded RomFS archive that a phone can actually install (even a 16 GB game), and then tells you the three steps to get it onto the device.
中文用户请看这里：简体中文 README
Formerly nxnative-romfs-archive — old links redirect here.
This is a community fork of nxnative — the NSO rewriter, the Horizon host, the NVN-on-Metal layer and the per-game profiles are upstream work, and this fork follows upstream automatically. What it adds:
- A GUI app for everyone. nxnative for Mac is a game library and a build tool in one window: pick a game's folder, choose This Mac or iPhone / iPad, and the build runs with live progress from the script's own counts. Finished Mac games appear in the library with their eShop key art, start with Play, and keep per-game launch options (the iPhone launcher's settings: frame rate, console mode, upscaling, …). Device dependencies are detected and installed with one click; English or Chinese, following the system. It also downloads the repository for you and updates itself — no git knowledge needed.
- A RomFS archive. Tears of the Kingdom's 304,243 files become 127 shards — the difference
between an iOS install that fails with
PackageExtractionFailedand one that works (details below). - ⏸️ Interrupted builds resume. Extraction, DLC, module rewrite and shader compilation are kept and reused: a failed or stopped build continues where it left off, and a rebuild after a tweak reuses everything unchanged (upstream's pipeline; the app drives it with its own build folder).