S2ARM / SHARED NATIVE GAME LIBRARY

S2Arm GitHub: Mac Download, iPhone Setup & Saves

S2Arm builds your own Switch games for Apple devices and keeps them in one game-library app. Use its Mac or Windows launcher to import files, prepare a build and install it; start here to choose the right platform and protect your saves.

S2Arm English game library with Install on iPhone and Export controls above the collection.
English launcher example published by S2Arm.

FORMAL RELEASE · 13 NOVEMBER 2026

Start with 0.3.4, especially after a failed 0.3.3 upgrade

A large game stopped opening

Update from 0.3.3 to 0.3.4, then open the affected game again. This release repairs that regression; start with the app update before reimporting or rebuilding the game.

Get the 0.3.4 release ↗

Your save shows older progress

If you moved from 0.2.4–0.2.9 to 0.3.0/0.3.1, update to 0.3.4 and follow the dated-backup recovery below. Updating fixes the cause; selecting the right backup recovers the lost progress.

Recover the pre-update save ↓

Already on 0.3.4 with working games? Keep your library and continue with the normal import or backup steps. Earlier 0.3.2/0.3.3 fixes are included; you do not need to install those versions in sequence.

Choose where you build and where you play

Launcher computer and player device are different choices
RouteWhat you getPrepare
Apple silicon Mac → MacA native Mac game library.The Mac launcher, your game files and its environment checks. Published player target: macOS 15+.
Mac → iPhone / iPadThe shared mobile app and each game’s resources.Full Xcode, the iOS platform, your Apple account and a trusted device. Published player target: iOS/iPadOS 18+.
Windows → iPhone / iPadA mobile build, with signing and installation through the bundled Impactor tool.The Windows launcher and its dependencies. Windows is the build computer, not a native Windows game player.

The player’s minimum OS is not an Xcode installation requirement. On Mac, use Settings to check Xcode and its SDK before an iPhone build. Android and HarmonyOS are listed as upcoming platforms in this release.

Choose S2Arm for a shared library

Several games live inside one application. Adding a game does not require a separate app identity for each title.

Download the launcher and finish its setup checks

  1. Get the matching release

    Open S2Arm v0.3.4 Releases ↗. On an Apple silicon Mac, choose S2Arm-mac-arm64.dmg; on Windows, choose S2Arm-windows-x64.zip. Release checksums are in SHA256SUMS.txt. The project also links its downloads from s2arm.com.

  2. Open the installed launcher

    On Mac, open the disk image and copy the application to Applications before launching it. Keep the installed app separate from your game-data folder. For a macOS warning, identify the exact message in the first-open guide and confirm the original release source.

  3. Complete the environment checklist

    Follow the welcome page’s primary action to prepare the computer. In 0.3.4, open Settings in the top-right toolbar for missing components. Older screenshots call this Environment. For an iPhone build on Mac, install full Xcode, open it to finish setup, add your Apple account and make the iOS platform available. Continue when the launcher says This Mac is ready.

Get from App Store action beside the missing Xcode requirement.

Install full Xcode first

Check again button at the bottom of S2Arm Settings.

Recheck after Xcode setup

0.3.4 · resolve setup through Settings

Open Settings in the top-right toolbar. This Mac is missing full Xcode, so the Metal compiler also waits for it. Install Xcode, open it once, then return to Check again.

Image source ↗
View the complete window S2Arm 0.3.4 English Settings showing missing Xcode and Metal Compiler, Get from App Store and Check again.Open full-size image ↗

Import the base, update and DLC together

One game’s input folderBase game · NSP or XCIMatching update · separate packageOptional purchased DLC · matching packages↓ Add games → review the selected title and version
Add games button in the current S2Arm welcome flow.

Choose your game files

Add your keys step in S2Arm.

Read whether this input needs keys

0.3.4 · add the game before resolving its keys

The current welcome page separates computer setup, Add your games and Add your keys. The keys note applies to NSP/XCI packages; extracted games skip that request. The top bar also shows the running 0.3.4 version.

Image source ↗
View the complete window Actual English S2Arm 0.3.4 welcome screen with Xcode setup, Add games and the NSP/XCI key requirement.Open full-size image ↗
  1. Prepare one complete game folder

    Put your legally obtained base game, chosen update and optional DLC in one folder. Keep the original files available. An update package alone does not supply the base game.

  2. Select Add games

    Choose the game files or their containing folder. The launcher also accepts extracted game folders. Review the selected game and version before building; similar filenames are not a reliable version check.

  3. Resolve the keys request for encrypted packages

    Add prod.keys from your own Switch when the launcher requests it for NSP/XCI extraction. Already extracted inputs can skip this request. If a package cannot be read, first check that the selected keys and base/update files belong to the game you imported.

S2Arm targets 64-bit AArch64 games. Its documented exclusions include 32-bit ARM games and games needing a 36-bit address space. Match an individual game’s import/build result rather than choosing solely by its title.

Choose the target, then let the build finish

  1. Choose this Mac or iPhone / iPad

    Select the device on which you will play. Check the game title, selected update, output and available disk space. Then use the build action. The welcome flow calls it Build now.

  2. Read the active stage

    The launcher unpacks the game, prepares resources, analyzes graphics, compiles its shader library and builds/signs the application. Keep the computer plugged in and awake. Several games can queue and build in sequence.

  3. Use the completion screen

    Wait for the build/export result, then choose installation or reveal the files. If it stops, open Details and keep the first relevant error and active stage. Returning to Library while a job continues is different from cancelling it.

Completed Unpack and Prepare resources stages, active Analyze graphics, then Compile shader library and Build app and sign.

Follow the active stage

Disk space panel comparing the selected build’s estimated usage with available space.

Check space before starting

See what the build is doing

Follow the highlighted stage, from unpacking to shader compilation. Check the estimate against available disk space for the game you selected; use Details if a stage stops.

Image source ↗
View the complete window S2Arm export window showing graphics analysis, shader compilation and disk usage.Open full-size image ↗

Install the shared app and its game resources

English S2Arm Export complete window with separate App and Resources sizes and Install on iPhone and Show in Finder buttons.
Export complete with separate App and Resources sizes.

Wait for the completion result

Install on iPhone and Show in Finder buttons.

Install or reveal the output

Your export is ready. Install both parts.

The mobile completion example separates the application from its much larger resources. Install on iPhone uses the Apple account configured in Xcode on the Mac route.

Image source ↗ · Full-size image ↗

Keep the same signing route when updating

In Settings → How to put S2Arm on your iPhone, the current direct-install route signs and copies the game data over a cable. Under Signing identity, use the same Xcode account or developer-certificate route as your existing app.

Switching between those identities installs a separate app; its save container starts separately. Export a backup from the old app first and keep it installed until progress loads in the new one. The persistent Export and sign it yourself choice is disabled as “Coming in the next version” in 0.3.4; use the active route for this release.

Install to iPhone in one click, with signing and game-data transfer over a cable.

Use the active cable-install route

Xcode account is the selected signing identity.

Xcode-account route selected

My developer certificate is the other signing identity.

A separate certificate route

0.3.4 · installation and signing identity

Xcode account is selected here. My developer certificate is a different signing route. Keep the previous app and a save backup before changing this choice.

Image source ↗
View the complete window Actual English S2Arm 0.3.4 installation settings with one-click iPhone installation and Xcode-account versus developer-certificate identity.Open full-size image ↗
MAC

Open the completed Mac game

  1. Return to Library and select the built game.
  2. Use its play action after the Mac build completes.
  3. Confirm input, sound and save loading before changing display options.
IPHONE / IPAD

Sign, install and transfer

  1. Connect and unlock the device; complete its Trust and Developer Mode steps when requested.
  2. On Mac, use Install on iPhone and follow the selected Xcode account/team. On Windows, follow the bundled Impactor signing flow.
  3. Keep the device connected until application installation and game-resource transfer finish. Open S2Arm on the device and choose the game.

Installing only the application does not copy all game resources. The native route does not need an emulator JIT activation session; app signing, the game’s data and device memory still matter. For a different signing tool or app identity, back up first and follow the matching export flow available in that release. The NX2Apple guide covers its separate shared-IPA and standalone-IPA choices.

Use the library status to choose the next action

Imported

The title is in your collection. Choose a platform and build it.

Ready for iPhone

The mobile export is ready. Install it and finish transferring resources.

Installed

Open the intended game on its device; check controls and load progress.

Use the selected game’s controls and options rather than copying TOTK’s shortcuts into every game. For connection problems, complete Mac controller pairing before changing a game’s mappings.

Back up a game, then restore a checked copy

The Mac launcher has per-game save management. Use it with the game closed; save operations take the library lock so they do not compete with a running game or another library job.

Storage and three-dot actions for the selected game; choose the three-dot button for save management.

Open this game’s three-dot menu

Back up the selected game

The selected game’s three-dot menu leads to Saves. Keep that game closed while backing up or restoring.

Image source ↗
View the complete window English S2Arm selected game and its Install, Export and three-dot actions.Open full-size image ↗

Make an external backup

  1. Save in-game, quit and select the same game in the launcher.
  2. Open the selected game’s … menu, choose Saves and read the current file count/size.
  3. Choose Back Up To… and save the .s2asave archive outside the game library. Name it with the game version and date.
  4. Keep this copy unchanged while testing an update or another build.

Inspect before restoring

  1. Close the game and select the intended library entry.
  2. Choose Choose Backup… in Saves. It accepts S2Arm archives and supported community save folders/ZIPs.
  3. Check the preview’s game, version, creation time and file count before selecting Restore… and confirming the overwrite.
  4. Launch the game and load the expected slot. The restore operation keeps a before-restore.s2asave copy of previous progress.

The selected game’s save-folder action opens its SaveData/ handoff folder. Use the launcher’s backup/inspection flow for full-state recovery; copying a random cache folder is not a save backup. Supported community structures include JKSV, Checkpoint, yuzu and Ryujinx folders or ZIPs, subject to the preview checks.

Save-management interface ↗ · Stopped-game backup, inspection and restore ↗

Recover progress after the 0.3.0 / 0.3.1 save rollback

This recovery is for the older-save import problem fixed in 0.3.2. It mainly affected iPhone users upgrading from 0.2.4–0.2.9. Close the game and copy its current data somewhere safe before replacing anything.

  1. Find the last backup before the update

    Open Files → On My iPhone → S2Arm → padrec. Each name_date_time.saveN folder holds a complete backup from an in-game save. Use its date and matching screenshot to choose the last correct progress from before the upgrade.

  2. Copy both parts of that backup

    Open the chosen folder and copy its account folder and user file. Keep the original dated backup intact. Do not choose an older slot just because its folder appears first.

  3. Replace the matching game's save handoff

    Go to S2Arm → games → this game's title ID → SaveData. Move the existing save folder somewhere else. Put the copied account folder and user file here, then rename account to save.

  4. Open the game and check the expected slot

    Use the updated S2Arm app, open this game and load the progress shown in the backup's screenshot. Keep the previous save and dated backup until you have confirmed the correct location and progress.

Inside the selected game's SaveData folderaccount/ from the backup → rename to save/user from the same backup → keep as userMove the previous save aside first. Keep both backup items together.

For normal backups and restoration, use the Mac launcher's save-management flow. If you are using the other launcher, follow NX2Apple's own update and save locations instead.

Update the launcher, game and app identity separately

ChangeBefore you change itAfterwards
Launcher releaseFinish active jobs and keep an external save backup.Open the existing library with the new launcher and check its entries.
Game version or built runtimeRecord the working title/version and back up that game.Build the intended version, install its app/resources and load the expected save.
Xcode account ↔ developer certificateExport saves from the existing mobile app and record its signing route.Changing identity installs a separate app. Restore the matching backup there before removing the old installation.
Beta → io.s2arm.* releaseExport saves while the beta app is still available.The OS treats the new identifier as another app. Complete installation, then migrate the matching saves; keep the old app until progress loads.

Do not delete a working mobile app to renew its signature. Keep the same app identity and signing account for an in-place replacement. The release’s io.s2arm.* identifier change is a migration, so beta saves do not carry over automatically. Keep the old installation and backup until the new app opens the correct progress.

Find the failed stage, then fix that part

A large game will not open after 0.3.3
  1. Install the formal 0.3.4 update, then open that game again. The official fix restores affected large-game launches.
  2. Keep the existing game and save data while trying this repair; reimporting the whole library is not the first step.
Writing game.img fails in a protected Windows folder
  1. Use 0.3.4, which includes the protected-folder export fix from 0.3.3. Retry the export with the same source game.
  2. If Windows still reports access denied, use a folder your account can write to and retain the first detailed error. Do not remove game originals to make space.
An imported game or the library fails on Windows
  1. Use 0.3.4 before rebuilding the library. Earlier 0.2.7/0.2.8 fixed import and non-Western-encoding failures; 0.3.2 fixed additional folder-permission and cover-write failures.
  2. Reopen the existing library and retry the import. Keep the original game inputs and save backup.
Keys requested or encrypted package cannot be read
  1. NSP/XCI packages need your own matching keys. Already extracted games can skip that request.
  2. Check the base/update selection and exact first error. Renaming an update to a base-game filename does not change its contents.
Build stops during graphics or shader work
  1. Read the first error in Details and keep the active stage.
  2. Check Settings, the selected SDK and free disk space. Keep the successful build cache; do not erase the whole library as a first fix.
App is installed but game data is missing
  1. Finish transferring the selected game’s resources as well as the shared app. Current releases show the transfer failure reason and offer retry or another transfer route.
  2. If the app says resources use an old format, re-export that game with the current launcher and transfer the new resources. Keep saves separate from game images.
The last transfer appears stuck at 99%
  1. Use the current release: 0.3.2 corrected an installation wait that continued after the transfer finished.
  2. Read the current transfer status and error before retrying. Keep the device unlocked and connected; a completed app install and a completed resource transfer are separate results.
Progress went backwards after 0.2.x → 0.3.0/0.3.1
  1. Update to 0.3.4, close the game and use the padrec recovery steps above. The fix for the underlying import problem first shipped in 0.3.2.
  2. Keep the old save, matching user file and dated backup until the recovered slot loads. A beta app-identifier migration is a different case; use Update and migrate for that route.

When reporting a problem, include the launcher release, build computer/OS, destination device/OS, game/update version, failed stage and first error. Keep game packages, keys and account credentials out of public reports.

13 November 2026 · Release v0.3.4 · Source b923ac5 · Published interface examples accompany the relevant steps.

Source version and related setup guides

The welcome, Xcode-check and signing controls were captured from the official English 0.3.4 Mac app on 13 November 2026. The library, build-progress and completion images are published project examples, unchanged in the tagged 0.3.4 documentation. Their game, duration and resource sizes belong to those examples. The folder map explains the release’s documented save recovery. Project code is Apache-2.0; game names and assets belong to their owners.