Disclaimer: This guide has not been meaningfully updated since 2020 and may be out of date. Use at your own risk. A (more) updated version can be found on Eip’s website.
Bans are scary and Nintendo hasn’t been shy about banning hacked Switch consoles. However, educated hackers know that bans are avoidable and they know how to avoid them. The Q&A below should answer any questions you may have on how bans work and how to avoid getting your console banned.
If you have any further questions after reading this page, you can ask them on the Nintendo Homebrew Discord server.
Put simply, a ban is when Nintendo decides not to let a specific console or Nintendo account use its online services. Most bans associated with hacking are console bans, meaning that the specific console that Nintendo has banned will be unable to use Nintendo’s online services, including the eshop, game updates, and online play. Nintendo reserves the right to withhold these services per their user agreement.
The following actions will cause an immediate ban of your Nintendo Switch:
- Piracy of any sort
- Homebrew NSPs (installed to the home menu)
- Changing user icon through Homebrew
- Sketchy eShop behavior
The following actions will not result in an immediate ban, but will still result in a ban:
- Modding online games
- Cheating in online games
- Clearing error logs after they’ve been uploaded to Nintendo (this may extend to using both emuMMC and sysMMC online, due to mismatched logs)
The following actions have not resulted in a ban (so far):
- Atmosphere itself
- Homebrew (via title takeover)
- Custom themes
- Custom sysmodules
- Mods/cheating in offline games
- Overclocking with sys-clk
(Thanks to Val on the ReSwitched Discord server for this list)
Nintendo filled the Switch with telemetry systems. Telemetry systems basically monitor what the user does on the console, including what games they install, what games they play, and a bunch of other data too. The Nintendo Switch stores this data constantly, even while offline, and will send these data logs to Nintendo as soon as it connects to the internet and Nintendo’s servers. This means that if a bannable action is performed on the Switch (even while offline) and the console connects to the internet at any point afterward, even briefly, Nintendo will receive the telemetry log and ban the console.
There are essentially two ways to prevent getting banned. The first is to avoid performing any of the actions that Nintendo bans for on your Switch. The second is to keep your console permanently offline so that even if you take a bannable action, Nintendo will never be sent the telemetry log and will never find out about it.
NAND is simply a type of data storage that is used in a variety of electronic devices. eMMC is the type of NAND that is used in the Switch as its internal data storage. All of the Switch’s data is stored on its eMMC, which is an internal component of the Switch. This internal storage is sometimes referred to as the system NAND/eMMC or sysNAND/sysMMC. An emuNAND or emuMMC (emulated NAND or emulated eMMC) is a copy of the SysNAND stored on the SD card.
Since the telemetry logs are stored in the Switch’s NAND, an emuNAND is useful because it allows you to have two copies of the Switch’s internal storage. Your sysNAND can be used for online play and eshop purchases while your emuNAND can be used for CFW and hacking and be kept permanently offline. This lets you have the best of both worlds! If you followed the recommended CFW setup on Nintendo Homebrew’s guide, you should already have an emuNAND set up.
An emuNAND is a tool to help prevent bans, it is not a silver bullet. You have to keep your emuNAND permanently offline or it won’t help you very much. It is also important to note that even though the internal storage of your sysNAND and emuNAND are separate, they are still copies of the same system with the same unique identifiers. If Nintendo bans your emuNAND then your sysNAND gets banned too and vice versa.
If you still want to use your internet connection on your always-offline console (or emuNAND), there is a way to do so. You just need to make sure that even though your console may be connected to the internet, it won’t be able to connect to Nintendo’s servers and therefore won’t be able to send the telemetry logs.
The recommended way to do this is 90DNS, which are custom DNS servers that allow connection to the internet, but block Nintendo’s servers. You can find instructions on setting up 90DNS here.
Incognito is not recommended for a variety of reasons. It functions by blanking your console’s PRODINFO, which is console-unique data that your console requires to boot. If Incognito goes wrong, it can result in damage to your console, even an unrecoverable brick. Additionally, Incognito is less reliable than 90DNS as it depends on Nintendo rejecting telemetry logs from consoles with blanked PRODINFO and while that is currently true, Nintendo may change this in the future.
As of Atmosphere 0.12.0, a virtual PRODINFO blanking feature was included, which is safer than Incognito, but still not a viable replacement for 90DNS.
(Thanks to noirscape on the Nintendo Homebrew Discord server for the explanation of why Incognito is bad)
You can’t. Sorry.
Restore a “clean” NAND backup of the system from before you performed the bannable action. You can find instructions for doing that here.
Using the Switch’s stock “factory format” feature does not erase telemetry logs and will not protect you from a ban.
You messed up. Make sure to make a NAND backup for the future.
There is a method for manually resetting the NAND’s data, but it is not as reliable as restoring a NAND backup and should not be your preferred option.
Nothing in life is guaranteed. The information here is based on quite a lot of experience, but Nintendo can always decide to change what actions they consider bannable or add new ways of gathering telemetry. Part of hacking your console means accepting a little risk and taking responsibility for your decisions.