Skip to content
NX Native

How to check whether nxnative supports your Switch game

nxnative does not run every Switch game. It needs a profile for each game, and the project only lists games that were brought up and tested. Here is how to check yours before you spend an hour on a build.

Updated 1 November 2026. 5 min read.

How to check whether nxnative supports your Switch game

Start with the title ID

Every game has a 16-character title ID. It is usually written in square brackets in the file name. The project's own example shows a base game and its update:

Super Mario Bros. Wonder [010015100B514000][v0].nsp
Super Mario Bros. Wonder [010015100B514800][v327680].nsp

The update has its own ID, so search with the ID of the base game, the one with [v0]. The build script reads the title ID from the package itself and uses the one in the file name only as a fallback.

Search the games page

Open the games page and type the game's name or its title ID in the search box. You can also filter by engine or show only games with a 60 fps result. If your game is not in the list, jump to the section on unlisted games below.

Read what the page tells you

FieldWhat it means
Tested buildThe game version the project's notes were made with, such as an update number.
Nintendo SDKThe version of the Switch system library the game was built with.
EngineWhat the game is made with, such as Unity or Unreal Engine.
Graphics APIHow the game draws. Most use NVN, the Switch's own graphics API, which nxnative rebuilds on Metal.
Badge, such as "60 fps with 1.2.0"The game runs at 60 fps (30 on the Switch) with that update.

Other short notes appear on the project's list too, for example "played by touch", "controller only", "offline" or "no Mii heads". They tell you how the game is played or what does not work yet.

Support is tied to game versions

A profile is written for specific versions of a game. The script checks every code module's build ID against the profile, so use the version the page names as the tested build, with its update. If you have only the base game or a different update, read the notes first, because what was tested may not match what you have. The script's -p option can pack an older version, and the folder still needs both NSPs.

A listed game is not a perfect game

The project lists games "tested on Mac or iPhone", and each notes page says which platforms were tested, how far the work got and what is still open. A game may be tested only on the Mac, or play through its first chapters and stop there. Before you build, read the sections called "Found on this game" and "Open". Listing a game here does not mean this site has verified it.

Games that are not listed

Other games are not supported yet. The script then writes a survey to <title ID>_survey/survey.md, makes a provisional profile by guessing the game's settings and still tries to pack an IPA. That IPA may not start. If you try anyway, expect to do the bring-up yourself, and report what you learn on the official issue tracker.

A short checklist

  1. Find the base game's title ID in the file name.
  2. Find the game on the games page.
  3. Compare the tested build with the update you have.
  4. Check that your device meets the requirements.
  5. Read "Found on this game" and "Open" on the notes page.
  6. Then follow the build guide.

Facts on this page were checked against the official nxnative commit bfc70881 (31 Oct 2026). The project changes often, so the official repository always wins.

This is an unofficial guide based on the project's public documentation. Use only games you own. For the latest details, check the official repository.