TEARS OF THE KINGDOM / APPLE SILICON
Play Tears of the Kingdom on your Mac
Build a native app with MacNativeGames using your own game files. Check the essentials, then follow the task you need.
Choose your next step ↓
- YOUR MAC
- Apple siliconmacOS 26 or later
- YOUR BASE GAME
- Version 1.0.0XCI or NSP + prod.keys
- FREE SPACE
- 25 GB / 40 GBFresh base build / with update
16 GB memory recommended. Full requirements ↓ · Watch the Mac walkthrough ↗
Go straight to your task
- Build the appYour paths, quoted command and output folders.
- Change controller layoutGenerate and check controls.txt; download and undo.
- Find an errorLocate the failure stage and follow a recovery check.
- Picture & settingsKeys 1–4, native 2K vs MetalFX, ultrawide, and how to reset.
- Saves & modsSave folder, update backups, restoring, RomFS mods.
- iPhone & iPadTested devices, the unsigned IPA and its limits.
- Performance recordsCompare recorded frame rates and build times by chip and game version.
Check your starting point
- Apple silicon Mac with macOS 26 or later. The project recommends 16 GB memory.
- Your uncompressed base game 1.0.0 XCI or NSP, plus your prod.keys.
- For NSP input: firmware or extracted shared fonts, unless a valid work-folder font cache already exists.
- About 25 GB free for a fresh base build; 40 GB with an update.
Keep the base and update separate
| Target version | Base | Separate update |
|---|---|---|
| 1.0.0 | XCI or NSP 1.0.0 | None |
| 1.1.2 / 1.2.1 / 1.4.3 | XCI or NSP 1.0.0 | The chosen update’s NSP or NSZ |
The script identifies update versions from executable hashes, not the filename. A compressed base, combined package or cartridge image used as an update is a different input.
FROM FILES TO PLAY
See what you’ll prepare, build and open
01 / YOU SUPPLY
Optional: a separate update
02 / YOU BUILD
- 1Code
- 2Data & fonts
- 3Shaders
- 4Mac app
Runs locally on your Mac
03 / YOU OPEN
Tears of the Kingdom.appFind the output folder.
Open the app in Finder.
NSP input also needs a font source, unless valid fonts are already cached. Keep an update separate from the base.
Already building? Read the four Terminal stages to see what happens before the finished app opens.
What this route changes
- Native build
- The game’s ARM64 code runs on Apple silicon. The host supplies Switch services and translates graphics for Metal. Native execution still involves adaptation and translation work.
- Your inputs
- You build locally using your game files and keys. The repository has no ready-made game app in its Releases.
- Other routes
- A console emulator and a Windows compatibility layer accept different software and have different requirements. The word native alone does not establish a speed advantage.
When it starts running
- Open the app from Finder. Keeping it in its final location helps reuse shader caches.
- The first use of new shader variants can briefly stall. Repeating the scene can reuse compiled variants.
- Keys 1–4 select picture modes in supported builds. A larger output canvas alone does not prove a higher internal rendering resolution.
- The project does not provide online features or amiibo support.
Use the first error from the build or game log. For the source and supported games, see the project reference.
The first start checks the game data inside the app (about 17.1 GB in this recording). Leave the window open until the game appears.
View the recorded verification message ↗