Quick Answer: S2Arm lets you run Switch games you own on iPhone, iPad and Mac. It rewrites the game's ARM64 code at build time so the processor runs it directly, and it sends graphics straight to Metal. You bring your own games and keys, and the launcher handles the build for you.
Most guides about Switch games on iPhone start with an emulator comparison. This one starts with a number. The project's own evidence page reports a 34-minute cold build for a 17.5 GB open-world game on a 16 GB MacBook Air (M3). That number tells you more about what it's like to use this than any frame-rate chart. S2Arm is an open-source project under Apache-2.0, and it takes a different route from the emulators you may have seen.
How a native port differs from emulation
Most emulators translate the console's CPU instructions on the fly, every frame. That translation layer is where much of the heat and battery drain comes from. S2Arm skips it. According to the S2Arm README, the game's own ARM64 code is rewritten at build time and then runs directly on the processor in your device.
Graphics take a similar shortcut. Calls are translated straight to Metal, Apple's graphics API, and system services come from a native host built on the Ryujinx compatibility layer. When the translation happens once at build time instead of constantly at runtime, the cause-and-effect is simple: less work per frame, so less heat.
The project reports a Switch 2 game running at a full 60 fps on an iPhone 17 Pro Max while the phone is cool. Once sustained load heats the device, it drops to 37–43 fps, at roughly 0.15 J per frame. Those are the developers' measurements, not independent benchmarks, so treat them as a strong signal rather than a guarantee.
Here's where most people get it wrong. They assume a native port is automatically faster than an emulator. It isn't a blanket win. What it changes is the cost profile: you pay up front during the build, and you get a more efficient run afterward.
The build step is your real bottleneck
Almost everyone asks about frame rate first. The bigger practical issue is the build. Shader count and game size drive how long you wait, and the project's numbers make that clear:
| Game (type) | Game files | Shaders | Build time (cold, 16 GB M3 MacBook Air) |
|---|---|---|---|
| 23.5 GB action RPG | 23.5 GB | 1,222 | 6.4 min |
| 12.0 GB life-sim game | 12.0 GB | 9,315 | 8.6 min |
| 17.5 GB open-world game | 17.5 GB | 26,999 | 34 min |
Notice that the 17.5 GB open-world game isn't the largest file in the table. The 23.5 GB action RPG built in under 7 minutes because it has far fewer shaders. Shader count predicts build time better than file size does.
This is the counter-intuitive part. Most advice treats the game file as the cost. For S2Arm, the cost is the translation work, and that work scales with how many shaders the game uses. Plan for the long build on shader-heavy titles, and keep the launcher open. It shows elapsed time, remaining time and disk use for each stage, and it can queue several games to build one after another.
That said, the build succeeded on the first try for 95% of the 211 games the project surveyed. The failures are real, so budget time for a second attempt, and read the stage that failed before you retry.
Setting up: three steps and one caveat
The launcher's welcome page reduces setup to three steps: prepare this computer, add your keys, add your games. In practice, the sequence looks like this:
- Install Xcode if you're building for iPhone from a Mac. It's free from the Mac App Store and needs your Apple ID. The launcher walks you through the sign-in.
- Import your keys and games together. Put the base game, updates and DLC in one folder and import that folder as a unit. Importing them separately is the most common reason for a failed build, since the game then can't find its update files.
- Choose iPhone / iPad or this Mac, then click Build. Then sign and install with your own Apple ID. Windows users get the same result through the bundled Impactor signing tool and apple-codesign.
Here's the caveat most readers miss. S2Arm uses the new app identifier io.s2arm.*, which iOS treats as a brand-new app. Saves from the beta builds won't carry over automatically. Back up your saves before you update.
Mac, iPhone or Windows: which launcher do you need?
The platform you start from changes what you can do:
- Mac launcher: builds locally and plays games directly on the Mac. It also supports
s2armctldiagnostic export. - Windows launcher: builds and installs games onto iPhone or iPad. It can't yet export diagnostic bundles.
- iPhone or iPad: the app is where you pick a game. Every title lives in one app and takes a single App slot on your developer account, so adding games doesn't consume extra signing slots.
The trade-off is simple. If you want to play on a Mac, you never leave one machine. If you want the phone, you need a build machine plus signing. Choose based on where you'll play, not on which launcher looks nicer.
Let an AI handle the tedious parts
Both launchers expose a control tool, s2armctl. An AI assistant can import games, start builds, install them, and read errors while you watch each step in the launcher window. The commands look like this:
/Applications/S2Arm.app/Contents/Resources/s2armctl start
/Applications/S2Arm.app/Contents/Resources/s2armctl next
The next command tells the assistant what to do, who should do it, and why. Anything that needs you, such as system permission prompts, Apple ID sign-in or tapping Trust on your phone, stops the AI and asks you to act.
Be careful here. Giving an AI assistant command-line access to your machine is a real trust decision. Read the operator skill file linked in the README before you grant it, and watch the launcher window rather than letting it run unattended.
Limits, risks and the legal line
Some boundaries matter more than the marketing:
- 64-bit only. S2Arm runs AArch64 games. Apple silicon can't execute 32-bit ARM code, so 32-bit titles are out of scope.
- No 36-bit address space games. Titles that need one aren't supported.
- No bundled content. The project ships no games and no keys. You need to obtain your own game files legally.
- Not affiliated with Nintendo. Game titles and trademarks belong to their owners.
The most common misconception is that "one app for the whole library" means every game will work. It doesn't. The app only consolidates installs. Each game still goes through its own build, and each build can fail.
Frequently Asked Questions
What is S2Arm?
S2Arm is an open-source project under Apache-2.0 that rebuilds your own Switch games as native ARM64 for iPhone, iPad and Mac. It rewrites the game code at build time and sends graphics to Metal. It ships no games or keys, so you supply your own legally obtained files.
How do I run Switch games on iPhone?
Download the launcher, import your keys and game files in one folder, choose iPhone as the target and click Build. Then sign and install with your own Apple ID and open S2Arm to pick a game. The Mac launcher needs Xcode for iPhone builds.
Why does the Switch game build take so long?
The build translates the game's code and shaders ahead of time, so the cost scales with shader count more than file size. A 17.5 GB open-world game with 26,999 shaders took 34 minutes cold, while a 23.5 GB RPG with 1,222 shaders took 6.4 minutes.
Does S2Arm work with 32-bit Switch games?
No. S2Arm targets 64-bit AArch64 code, and Apple silicon can't execute 32-bit ARM instructions. Games that need a 36-bit address space are also outside the project's support.
Run it, then tell someone else
The most useful takeaway: budget for the build, not just the play session. Pick one game you already own, check its shader count if you can find it, and start a single build on a machine with plenty of free disk space. Note the total time and the stage that took longest. Then pass this to someone wrestling with slow Switch games on iPhone, because their first build will go faster once they know where the time goes.