Latest Versions

Choosing Your Set Up

Guide Information

This information will explain how things work after you hack your Switch. It will help you choose the best route to take so you don’t get banned, and ensure you are still able to use your Switch normally (without the hack for online services) if that’s something you will still want to do.

Background

Before you hack your Switch and dive into using custom firmware (CFW) there are some things you need to consider. You need to determine the right route to take to suit your needs, and set everything up so you don’t receive a ban or do something that cannot be reversed later.

What you intend to do with CFW will give you an indication of the best way to go, but first lets explain some of the basics to help you decide which set up will be the right fit for you.

First, let us look at the how the Switch comes out of the box before you hack it:

Out Of The Box Switch

System NAND or sysNAND for short, is referring to the contents stored on the system internal memory inside your Switch. sysMMC is another term used for sysNAND.

When you use a Switch before setting up CFW, everything you do is done on sysMMC using stock/original firmware (OFW).

Switch Internal Memory

The Switch comes with 32GB of internal storage, a portion of which is reserved for use by the system. What is leftover is used to store game save data and can be used to install content to, but you probably won’t get by with such a small amount of onboard storage.

MicroSD Card

You can utilise additional storage by using a microSD card up to 2TB in capacity.

You can use a microSD card to save screenshots and software data, including downloaded software, software updates, and DLC.

You will then have 2 different locations to store your content:

  1. The internal storage.

  2. The microSD card, in the Nintendo folder.

Game save data is stored in the console’s system memory. This does not change whether downloadable software or software from a game card is being played. Game save data cannot be saved or copied to a microSD card.

Switch With Atmosphere CFW

Atmosphere is a custom firmware for the Nintendo Switch. It consists of multiple components, each of which replaces/modifies a different component of the system. It reimplements some of the Nintendo Switch’s Operating system modules, whilst adding a few patches or options that wouldn’t normally be available. It is able to mimic the existing operating system, or a system module’s functionality and allow greater freedoms to do things with the Switch that would be impossible to achieve without it.

In short Atmosphere CFW, is basically like having a second firmware. It opens the Switch up to being able to use homebrew apps, custom themes, emulators, game mods and a myriad of other cool things.

You can learn more about Atmosphere CFW by clicking the link below.

After setting up Atmosphere CFW you are able to boot the Switch with, or without Atmosphere CFW and still use the Switch as if it had just come out of the box. To achieve this you must set everything up correctly, taking the necessary precautions.

So now you have 2 different ways to boot and use your Switch:

  1. Stock/OFW (No CFW)

  2. Atmosphere CFW on sysMMC

Switch Internal Memory

Atmosphere CFW can be used on sysMMC (internal memory).

MicroSD Card

Atmosphere CFW can be used on emuMMC (microSD card).

Atmosphere CFW on sysMMC

Switch Internal Memory

Atmosphere CFW used on sysMMC (internal memory) means you are using a modified version of the stock operating system on the Switch itself.

Everything you do in Atmosphere CFW on sysMMC effects the stock operating system as well. For example, if you install a game in Atmosphere CFW on sysMMC and boot your Switch into stock firmware (without CFW), the game will be visible there as well. It shares the same locations for save data and any installed content with the stock firmware because it is running in the same location, on the sysMMC.

MicroSD Card

The microSD card will be used to store the folders and files required for running Atmosphere CFW and any additional homebrew applications to function. All of the content installed in stock firmware to the Nintendo folder on the microSD card will be accessible if Atmosphere is used on sysMMC.

Due to the link between stock/OFW and Atmosphere CFW on sysMMC, you have to be careful you don’t do something ban worthy whilst using Atmosphere CFW on sysMMC. If you do, you are wavering the ability to boot into a clean untouched sysMMC to use stock/OFW. You are essentially self banning yourself due to not being able to connect to Nintendo. This means no more official online play and no more eShop, not even for future game updates.

Some people often don’t appreciate the risks when using Atmosphere CFW on sysMMC. Once they realise they’ve done something that will get them banned, they restore a NAND backup, or a try full system wipe, but in a lot of cases the damage is done and they’ve already been banned, unless they had ban protection active.

If you still intend on using any of Nintendo’s online services you should probably play safe and avoid using Atmosphere on sysMMC until you fully understand what you are doing.

Whilst it is possible to use Atmosphere CFW on sysMMC without getting banned for some things, it isn’t advisable unless you know what you are doing. People often use Atmosphere CFW on sysMMC to play games with mods online, use themes or run homebrew apps from the hbmenu. In order to do this they make sure they have nothing that will get them banned installed to the sysMMC and only use legitimate purchases that they own. People also use Atmosphere CFW on sysMMC if they don’t intend on using stock/OFW again, Nintendo online services, if the Switch is already banned, or if they don’t have the space on your microSD to create an emuMMC. Using Atmosphere on sysMMC can also be more convenient than using OFW and having to inject a payload to get back into CFW. 

Atmosphere CFW on sysMMC can also be used to dump games and saves from stock/OFW, which can then be installed to the emuMMC if you have an emuMMC set up.

Atmosphere CFW on emuMMC

Switch Internal Memory

Using Atmosphere CFW on emuMMC does not use, modify, or have any effect on the sysMMC.

MicroSD Card

Emulated NAND or emuNAND for short, is referring to an emulated copy of the Switch sysMMC (internal memory storage) that’s stored entirely on a microSD card. emuMMC is another term used for emuNAND.

The microSD card will be used to store the folders and files required for Atmosphere CFW and any additional homebrew applications to function.

In addition to this it will also store an emulated copy of the Switch sysMMC (usually on a partition). All of the content installed in stock/OFW to the Nintendo folder on the microSD card will not be accessible if Atmosphere is used on emuMMC. emuMMC does not use the Nintendo folder on the root of your microSD card, instead it creates its own Nintendo folder inside the emuMMC folder that is created on the root of your microSD card when you create an emuMMC. Save data is not stored on the device if you use emuMMC, it is saved to the emuMMC on the microSD card. Any save data created in stock/OFW is not accessible in emuMMC. Although, creating emuMMC will carry over a copy of the saves from your sysMMC at the time of creating it.

emuMMC takes up 29.16GB of your microSD card capacity because it is emulating the Switch internal memory and storing a copy of it on there. Once built, emuMMC and sysMMC are totally separate from each other, meaning they will need to be maintained independently of each other. Games installed on one will not be accessible to the other. They also require updating separately, firmware updates applied on the sysMMC will not update the firmware on emuMMC and vice versa. emuMMC can only be booted with Atmosphere CFW. When using Atmosphere CFW on emuMMC you won’t be able to access Nintendo’s services any longer because they are deliberately blocked to minimise the risk of receiving a ban for doing something you shouldn’t have. If you connect to Nintendo without ban protection after you have done something wrong – you will be banned!!!. You can connect to the internet using emuMMC but you must have ban protection and blocks in place to stop your Switch communicating with Nintendo.

So now you have 3 different ways to boot, and use your Switch:

  1. Stock/OFW (No CFW)

  2. Atmosphere CFW on sysMMC

  3. Atmosphere CFW on emuMMC

MicroSD Card With emuMMC

MicroSD Card With emuMMC

The red section at the top illustrates the 29.16GB emulated copy of the Switch sysMMC (internal memory) on the microSD partition/file, this is the emuMMC.

The purple section in the middle illustrates the Nintendo folder that is used for content in stock/OFW and in Atmosphere CFW on sysMMC. (Remember you can still use stock/OFW so you still use this for content installed there).

The dark blue section at the bottom illustrates the files and folders required to run Atmosphere CFW and the emuMMC folder where digital/dumped games are installed to in emuMMC.

Summary

If you are a beginner using Atmosphere CFW on emuMMC is recommended, because this prevents your Switch internal memory being used so the sysMMC stays clean which means you can still use it without Atmosphere CFW, then boot separately into Atmosphere CFW on emuMMC (with protection) and enjoy the best of both worlds.
It is also easier to rectify any potential bricks using emuMMC, because at worst the microSD card can be reformatted and a new emuMMC can be built to start over as many times as you like. Fixing your Switch if you use Atmosphere CFW on sysMMC is often more involved and requires someone with in-depth knowledge.
In both cases a full NAND backup is something you should always have in case something bad happens.