Homebrew Menu for Nintendo Switch

The homebrew launcher used to find and run Switch NRO applications from your SD card.

Homebrew Menu for Nintendo Switch

Launch homebrew from your microSD

The homebrew launcher used to find and run Switch NRO applications from your SD card.

Ready Switch NRO

hbmenu.nro

Preserved build: 3.6.1 · 2.34 MiB

Copy the console NRO to the path shown below. This is a ready build; no compilation is required.

Download NRO
Checksums, contents & source

2,455,539 bytes

SHA-256: 6cf6d130515723ebe0041c2479420caf9726895087439ff7b2e528c2ed39c100

The Switch NRO signature and section bounds were checked.

Original package

Version, requirements & SD path

PlatformNintendo Switch
Preserved build3.6.1
Install pathsdmc:/hbmenu.nro

An existing supported homebrew/CFW environment. Installing hbmenu alone does not enable homebrew on an unmodified console.

These links preserve the verified version above. Check the linked release and your actual CFW/system version before installation.

Install & use Homebrew Menu

  1. Install at the SD rootCopy hbmenu.nro directly to sd:/hbmenu.nro. Keep the previous launcher before replacing it.
  2. Add your applicationsPut ready Switch NROs in /switch/ or their documented subfolders, together with their companion data.
  3. Open through your existing CFWUse the entry point documented by your installed homebrew setup. For applications needing full memory, hold R while starting an installed game until hbmenu opens.
  4. Choose an applicationBrowse the list and launch an app. Copying hbmenu alone does not enable homebrew on a stock console. Follow each app’s launch-mode requirements.

Keep the complete file layout

sd:/hbmenu.nro
sd:/switch/ [applications and their data]

If something does not work

For an empty list, check /switch/ and the actual .nro filenames. An app may need full application mode even when hbmenu itself works in Album/applet mode.

Project, images & file verification

Homebrew Menu project icon from its Homebrew App Store listing. The original image bytes are retained with their source URL and checksum. Ready console files have matching local backup copies, with version, size and SHA-256 recorded. Original containers and older versions are preserved. No downloaded application was executed and physical-console operation was not tested.