How to Homebrew a Nintendo Switch: Complete 2026 Guide

Homebrewing a Nintendo Switch allows you to run unofficial software such as homebrew applications, emulators, save-management tools, utilities, custom themes, and community-developed games.

However, the method you use depends heavily on your Switch model. Some early V1 Nintendo Switch consoles can run custom firmware through the RCM exploit without permanent hardware modification, while patched V1, V2, Switch Lite, and OLED systems generally require compatible modchip hardware before Atmosphère can be launched.

Quick Answer: To homebrew a compatible Nintendo Switch, first determine whether the console is an unpatched V1 or a patched/modchipped model. For an unpatched V1, prepare a microSD card with Atmosphère and Hekate, enter RCM using an RCM jig, inject the Hekate payload, create a NAND backup and preferably an emuMMC, then boot Atmosphère and launch the Homebrew Menu. Patched, V2, Lite, and OLED consoles normally require a modchip before this software setup can be used.

The NH Switch Guide lists Atmosphère 1.11.2 and Hekate 6.5.3 as supporting Switch firmware through 22.5.0. Nintendo firmware 23.0.0 is not yet supported by that stable combination, so users planning to use CFW should verify compatibility before updating.

Table of Contents

What Does Homebrewing a Nintendo Switch Mean?

Nintendo Switch homebrew refers to unofficial software created by developers and hobbyists that runs outside Nintendo’s standard software environment.

Homebrew can include:

Emulators
Original homebrew games
Save-management utilities
File managers
System-monitoring tools
Custom themes
Controller utilities
Media applications
Development and debugging tools

The NH Switch Guide defines homebrew as unofficial software written for closed systems such as the Switch and notes that almost all Switch homebrew requires custom firmware (CFW).

The most widely used Nintendo Switch CFW is Atmosphère switch. It runs alongside Nintendo’s Horizon OS and provides the environment needed for homebrew applications.

Can Your Nintendo Switch Be Homebrewed?

Before downloading anything, determine which Nintendo Switch model you own.

This determines which homebrew method is available.

Unpatched V1 Nintendo Switch

Early HAC-001 Switch consoles contain a hardware-level vulnerability commonly known as fusee-gelee.

These consoles can normally launch custom firmware through RCM mode without installing a modchip.

The exploit is tied to the Tegra X1 bootROM, meaning Nintendo cannot remove it through a normal firmware update on affected units.

Patched V1 Nintendo Switch

Nintendo later revised the original Switch hardware and patched the RCM exploit.

A patched V1 cannot normally use the same fusee-gelee method.

For modern firmware, these systems generally require a compatible modchip to launch CFW.

Nintendo Switch V2

The improved-battery HAC-001(-01), commonly called the V2 Switch, uses revised Mariko hardware.

It is not vulnerable to the original unpatched V1 RCM exploit and normally requires modchip hardware for homebrew.

Nintendo Switch Lite

Switch Lite systems also use Mariko hardware and require a compatible modchip before Atmosphère can be launched.

Nintendo Switch OLED

Nintendo Switch OLED models are also outside the original unpatched V1 RCM path and normally use a modchip-based CFW setup.

How to Check if Your Switch Is Patched

For an original V1 Nintendo Switch, check the console’s serial number.

You can find it under:

System Settings → System → Serial Information

or near the USB-C port on the bottom of the console.

The NH Switch Guide maintains serial ranges for:

Unpatched consoles
Potentially patched consoles
Patched consoles

For example, some early XAW1, XAW4, XAW7, XAJ1, XAJ4, and XAJ7 serial ranges are known to contain unpatched units.

If your console falls into a potentially patched range, the serial alone cannot guarantee exploitability.

What You Need to Homebrew a Switch

For an unpatched V1 Switch, the normal setup requires:

Compatible unpatched Nintendo Switch
microSD card
Computer
USB-C data cable
RCM jig
Hekate
Atmosphère
Homebrew Menu
Payload injector

A larger microSD card is recommended if you plan to create an emuMMC.

The NH Switch Guide recommends at least 128 GB when following its emuMMC path, although smaller cards can be used when emuMMC is not required.

For a patched console, you first need an already installed compatible modchip before following the CFW software preparation steps.

Step 1: Prepare the Nintendo Switch microSD Card

Start with a reliable microSD card.

FAT32 is commonly preferred for Switch CFW setups because it avoids the file-corruption concerns associated with exFAT in some homebrew environments.

Your homebrew SD card will eventually contain folders similar to:

SD:/
├── atmosphere/
├── bootloader/
├── switch/
└── hbmenu.nro

The major components are:

/atmosphere/ – Atmosphère CFW files
/bootloader/ – Hekate configuration and Nyx files
/switch/ – Homebrew applications
hbmenu.nro – Homebrew Menu

Atmosphère itself bundles the Homebrew Loader and Homebrew Menu components required for normal homebrew operation. Atmosphère 1.11.2 currently bundles hbloader 2.4.5 and hbmenu 3.6.1.

Step 2: Download Atmosphere and Hekate

Download Atmosphère from the official Atmosphere-NX repository.

Atmosphère is the custom firmware environment responsible for enabling most Nintendo Switch homebrew.

Then download Hekate.

Hekate acts as a Nintendo Switch bootloader and provides tools for:

Launching Atmosphère
Creating NAND backups
Managing emuMMC
SD card access
Payload management
Boot configuration
Hardware information

Avoid old YouTube tutorial packages or unknown all-in-one archives. The NH Switch Guide specifically warns that video guides and preconfigured packages can quickly become outdated or contain incorrect files.

Step 3: Copy Atmosphere and Hekate to the SD Card

Extract the Atmosphère package.

Copy its contents to the root of the microSD card.

Next, extract Hekate and copy:

bootloader/

to the SD root.

Your microSD card should now resemble:

SD:/
├── atmosphere/
├── bootloader/
├── switch/
└── hbmenu.nro

The exact configuration can vary depending on whether you plan to use emuMMC or sysCFW.

Step 4: Enter RCM Mode on an Unpatched Switch

An unpatched V1 Nintendo Switch uses Recovery Mode, commonly called RCM, to launch the initial Hekate payload.

RCM is a low-level Tegra recovery environment. The fusee-gelee vulnerability allows compatible early Switch consoles to execute an unsigned payload from this state.

To enter RCM:

Completely power off the Nintendo Switch.
Remove the right Joy-Con.
Insert an RCM jig into the right Joy-Con rail.
Hold Volume Up.
Briefly press Power.
Release the buttons.

If the console successfully enters RCM, the screen remains black.

A black screen is normal because RCM itself does not display a user interface.

The NH Switch Guide recommends using a proper RCM jig rather than improvised household objects.

Step 5: Inject the Hekate Payload

Once the Switch is in RCM, connect it to your computer with a USB-C data cable.

Inject the Hekate payload:

hekate_ctcaer_x.x.x.bin

using a compatible payload injector.

You can also use a dedicated RCM Loader instead of a computer.

After successful payload injection, the Nintendo Switch should display the Hekate/Nyx interface.

If the Switch remains black after payload injection, check:

USB cable supports data
Switch is actually in RCM
Correct Hekate payload selected
Payload injector recognizes the Switch
microSD card is inserted correctly

Step 6: Create a NAND Backup Before Installing Homebrew

Before making deeper changes, create a NAND backup.

This is one of the most important parts of a safe Switch homebrew setup.

A NAND backup contains a copy of the console’s internal storage and can help recover the system if important data becomes damaged.

The NH Switch Guide explicitly treats a NAND backup as an essential step and recommends storing the backup somewhere safe outside the Switch microSD card.

In Hekate, use the NAND backup tools to back up the required internal storage partitions.

Afterward, copy the backup to:

Your PC
External drive
Another reliable backup location

Do not keep your only NAND backup on the same SD card used by the console.

Step 7: Create an emuMMC

For many users, an emuMMC is the preferred way to run Atmosphère.

emuMMC creates an emulated copy of the Nintendo Switch internal system storage on the microSD card.

This means you can have two separate environments:

sysMMC → Normal internal Nintendo system
emuMMC → Separate CFW/homebrew environment

Hekate provides tools for creating and managing emuMMC.

The NH Switch Guide offers both emuMMC and sysCFW paths, with emuMMC requiring more microSD storage.

An emuMMC is useful for separating your CFW environment from your normal system environment, but it does not guarantee protection from Nintendo account or console enforcement.

Step 8: Boot Atmosphere Custom Firmware

Once Atmosphère, Hekate, and your selected environment are configured, return to Hekate.

Choose:

Launch

and select your Atmosphère configuration.

Depending on the setup, you may see an entry similar to:

Atmosphere emuMMC

or:

Atmosphere sysMMC

Atmosphère will start and load the Nintendo Switch HOME Menu.

To verify Atmosphère is active, open:

System Settings → System

The firmware line should include:

AMS

which represents Atmosphère.

For example:

22.5.0 | AMS 1.11.2 | E

E usually represents emuMMC, while S represents sysMMC/sysCFW in Atmosphère’s version string.

Step 9: Open the Homebrew Menu

Once Atmosphère is running, you can launch the Homebrew Menu.

The easiest method is normally through the Album icon.

However, opening Homebrew Menu through Album uses Applet Mode, which provides less memory to homebrew applications.

The NH Switch Guide recommends using title takeover for applications requiring full system resources.

Open Homebrew Menu Through Album

While running Atmosphère:

Open Album from the HOME Menu.
Homebrew Menu should load.
Your installed .nro applications will appear.

Open Homebrew Menu With Full Memory

For applications requiring more resources:

Hold the configured title-override button, commonly R.
Launch a normal game or application.
Continue holding the button until Homebrew Menu appears.

This launches Homebrew Menu using the application’s resources rather than the limited Album applet environment.

Step 10: Install Homebrew Applications

Most Nintendo Switch homebrew applications use the:

.nro

file format.

These applications normally go inside:

SD:/switch/

For example:

SD:/
└── switch/
    ├── app1/
    │   └── app1.nro
    └── app2/
        └── app2.nro

After copying the application to /switch/, reopen Homebrew Menu.

The app should appear automatically.

Use trusted developer repositories and official release pages whenever possible.

How to Homebrew a Patched, V2, Lite, or OLED Switch

Patched consoles cannot normally use the original unpatched V1 fusee-gelee exploit.

This includes most:

Patched V1 consoles
Nintendo Switch V2
Nintendo Switch Lite
Nintendo Switch OLED

These systems generally require a compatible hardware modchip before Hekate and Atmosphère can be launched.

Modchip installation involves motherboard-level microsoldering.

The NH Switch Guide warns that this requires significant soldering experience and that poor installation can permanently damage the console.

Once a compatible modchip is already installed, the software-side process typically involves preparing the SD card with Hekate and Atmosphère and booting the Hekate payload through the modchip.

Should You Use emuMMC or sysCFW?

Both approaches run Atmosphère, but they serve different purposes.

emuMMC

emuMMC stores an emulated system environment on the microSD card.

Advantages include:

Separates CFW environment from sysMMC
Easier to maintain a dedicated homebrew setup
Allows different firmware versions between environments
Useful for testing modifications

It requires additional microSD storage.

sysCFW

sysCFW runs Atmosphère directly on the console’s internal system environment.

It requires less storage and is simpler, but system modifications happen directly against the internal firmware environment.

For users who want a clearly separated homebrew environment, emuMMC is generally the more structured option.

Can You Homebrew a Switch on the Latest Firmware?

Firmware compatibility depends on Atmosphère and Hekate.

The physical RCM exploit on an unpatched V1 console is hardware-based, so a normal Nintendo firmware update does not patch the underlying fusee-gelee vulnerability.

However, Atmosphère and Hekate still need software support for each newer Horizon OS release.

As of September 19, 2026, the NH Switch Guide lists:

Atmosphère 1.11.2 → supports through 22.5.0
Hekate 6.5.3 → supports through 22.5.0
Nintendo firmware 23.0.0 → not yet supported

If your goal is to use homebrew, do not install a newly released Nintendo firmware until compatible Atmosphère and Hekate versions are available.

Is Homebrewing a Nintendo Switch Safe?

Homebrew itself does not automatically damage a Nintendo Switch, but modifying system software always introduces additional risk.

Common problems include:

Incorrect SD card files
Corrupted microSD card
Unsupported firmware
Outdated Atmosphère
Outdated Hekate
Broken sysmodules
Custom theme crashes
Improper NAND modifications
Failed modchip installation

The most important safety measures are:

Verify your Switch model first.
Follow current documentation.
Use official Atmosphère and Hekate releases.
Create a NAND backup.
Back up the SD card.
Verify firmware compatibility before updating.
Avoid random CFW packs.
Avoid modifying internal partitions unless you understand the change.

Does Homebrewing a Switch Get You Banned?

Homebrew and custom firmware change the normal software environment of the Nintendo Switch.

Nintendo can restrict online services or consoles when it detects activity that violates its terms or platform protections.

There is no configuration that can guarantee a modified Switch will never receive online enforcement.

If maintaining normal Nintendo online functionality matters to you, understand the risks before modifying the console and avoid assuming that emuMMC, DNS settings, or other tools make a modified environment undetectable.

Common Problems When Homebrewing a Switch

Switch Does Not Enter RCM

If the Nintendo logo appears, the console did not enter RCM.

Check:

RCM jig placement
Volume Up is being held
Console was fully powered off
Console model is compatible with the exploit

Payload Injector Does Not Detect the Switch

Try:

Another USB-C cable
Another USB port
Correct payload-injector driver
Re-entering RCM

An RCM Switch usually identifies itself as an NVIDIA APX device over USB.

Hekate Does Not Launch

Verify:

Correct Hekate .bin payload
microSD card inserted
Hekate bootloader folder exists
SD card filesystem is readable

Atmosphere Does Not Boot

Check:

Atmosphère version
Hekate version
Nintendo firmware compatibility
SD card files
Custom sysmodules
Custom themes

Atmosphère 1.11.2 officially supports Horizon OS through 22.5.0.

Homebrew Menu Does Not Open

Verify that:

hbmenu.nro

exists on the SD card root.

Also confirm Atmosphère successfully loaded.

If Album mode works but a particular app crashes, try using title takeover to provide the application with additional memory.

Frequently Asked Questions

How Do You Homebrew a Nintendo Switch?

First determine whether your Switch is an unpatched V1 or requires a modchip. For an unpatched V1, prepare an SD card with Atmosphère and Hekate, enter RCM, inject Hekate, create a NAND backup and emuMMC, then boot Atmosphère and launch Homebrew Menu.

Can Every Nintendo Switch Be Homebrewed?

Homebrew is possible across Switch hardware families, but the method differs.

Unpatched V1 consoles can use the RCM exploit. Patched V1, V2, Lite, and OLED systems generally require compatible modchip hardware.

Do You Need a Modchip to Homebrew a Switch?

Not for an unpatched V1 Switch.

Patched models and Mariko-based systems such as V2 and Switch Lite normally require a modchip.

What Is Atmosphere on Nintendo Switch?

Atmosphère is an open-source Nintendo Switch custom firmware used to provide the environment required for most homebrew software.

What Is Hekate Used For?

Hekate is a Nintendo Switch bootloader commonly used to launch Atmosphère, manage emuMMC, make NAND backups, inspect hardware, access SD storage, and manage payloads.

Do I Need an RCM Jig?

For an unpatched V1 Switch using the standard RCM method, an RCM jig is the recommended way to trigger Recovery Mode through the right Joy-Con rail.

Does Homebrew Work on Switch OLED?

Yes, but OLED models do not use the standard unpatched V1 RCM exploit. They generally require a compatible hardware modchip before Atmosphère can be launched.

What SD Card Size Is Recommended for Switch Homebrew?

The required size depends on your setup. The NH Switch Guide recommends at least 128 GB for its emuMMC path.

Can I Still Play Normal Games After Installing Homebrew?

Atmosphère continues to run Nintendo’s Horizon operating system, so normal software can still function. Compatibility and online-service risks depend on how the modified environment is configured and used.

Should I Make a NAND Backup?

Yes. A NAND backup is one of the most important recovery measures before making deeper changes to a Switch. The NH Switch Guide explicitly classifies this backup as essential.

Conclusion: How to Homebrew a Switch

Learning how to homebrew a Switch starts with identifying the hardware model.

An unpatched V1 Nintendo Switch can use the RCM exploit to launch Hekate and Atmosphère without a permanent hardware modification. Patched V1, V2, Lite, and OLED consoles generally require a compatible modchip before the CFW software setup can begin.

For an unpatched Switch, the main process is to prepare the microSD card with Atmosphère and Hekate, enter RCM, inject Hekate, create a NAND backup, configure emuMMC, boot Atmosphère, and launch Homebrew Menu.

Keep Atmosphère, Hekate, and Nintendo firmware compatibility in mind throughout the process. Use current project releases and maintain backups before modifying the system so your Nintendo Switch homebrew environment remains easier to maintain and recover.

Latest post: