This post contains affiliate links. If you buy through them, we may earn a commission at no extra cost to you. See our Affiliate Disclosure.
For a stock Switch, almost any brand-name microSD card works fine. For a homebrew Switch, the card works much harder: it holds your emuMMC (a full copy of the console’s system memory), the CFW itself, your homebrew, your game library — and every byte of it is read off the card, including the files SysDVR runs from. That makes capacity and honest speed ratings matter far more than usual, and it makes the market’s flood of counterfeit cards a real risk rather than a footnote.
Capacity first: the emuMMC tax
Before a single game is installed, a typical CFW setup reserves a large slice of the card for emuMMC. Hekate’s standard partitioning sets the emuMMC slot to “29 FULL” — roughly 29GB — on a regular Switch, and about double that on the OLED model, whose internal storage is twice as large. Budget for that first, then for games:
| Card size | Verdict for a CFW Switch |
|---|---|
| 128GB | The workable minimum. After emuMMC you have room for a modest library, and you will feel it. |
| 256GB | The sweet spot for most homebrew users — emuMMC, a healthy library, and headroom for clips and homebrew. |
| 512GB – 1TB | For large digital libraries, multiple setups (for example emuMMC plus Android), or people who hate deleting games. |
Speed ratings: what actually matters
- The bus ceiling. The Switch’s card slot is UHS-I. A faster UHS-II card simply falls back to UHS-I speeds in the console, so don’t pay for a bus the Switch cannot use.
- U3 / V30. These guarantee at least 30MB/s sustained writes. Installing games and writing an emuMMC are sustained-write workloads, so this is the rating that matters most after capacity.
- A1 / A2. Application Performance Class measures random small-file access. A2’s headline numbers rely on host features the Switch does not fully exploit, so treat A2 as a nice-to-have, not a reason to pay a big premium.
- Sequential read. Game loading leans on this most. Reputable brands publish it plainly; no-name cards publish fantasies.
Our pick: SanDisk’s Nintendo-licensed 256GB line
SanDisk’s microSD cards for Nintendo Switch are, in the manufacturer’s own words, designed, tested and approved for use with Nintendo Switch systems — the line is officially licensed, and the 256GB models publish read speeds up to 100MB/s and write speeds up to 90MB/s, comfortably past the U3 floor, backed by a lifetime limited warranty. That combination — guaranteed console compatibility, honest published speeds, and the capacity sweet spot — is why it is the card we point CFW users to: check the SanDisk 256GB card. If you move files on a PC constantly and want the fastest transfers there, SanDisk’s Extreme family is the step-up line; compare its current specs on SanDisk’s site before paying the difference.
The fake-card problem — and a five-minute check
Counterfeit microSD cards are the single biggest storage trap in this hobby. A fake reports a capacity it does not have; the console writes happily until the real (much smaller) storage fills, then files — including your emuMMC — corrupt silently. No statistic needed: the mechanism alone is reason enough to be careful.
- Buy from the brand’s own store or an authorized retailer — not the cheapest marketplace listing.
- Test every new card on a PC before trusting it: H2testw on Windows, or F3 on Mac and Linux, writes and verifies the full capacity.
- Migrate your CFW setup only after the card passes, and keep the old card as your backup until the new one has run for a while.
Signs your current card is the bottleneck
- Game installs and updates crawl, even though your internet connection is fast — installs write to the card, not the network.
- Load times in the same game are noticeably worse than on a friend’s console or in cartridge form.
- Homebrew or CFW crashes corrupt files often enough that reinstalling has become a routine.
- You are deleting games weekly to make room — a capacity problem that a faster small card will not solve.
Any one of these is a better reason to upgrade than a benchmark table. Size the replacement with the emuMMC math above, buy it from a seller you trust, test it before migrating, and the card quietly stops being part of your troubleshooting routine.
Two setup habits worth keeping
- Prefer FAT32. Homebrew guides generally recommend FAT32 over exFAT for CFW cards, because the Switch’s exFAT driver has a long-standing reputation for corrupting data when homebrew crashes mid-write.
- Back up before big updates. A full card image on your PC turns a failed firmware or CFW update from a disaster into an inconvenience.
Moving to a bigger card without starting over
Upgrading cards does not have to mean rebuilding your CFW setup from zero. If your emuMMC is file-based, the migration is mostly a careful copy of the old card’s contents to the new one. If it is partition-based, a plain file copy is not enough — the hidden partition has to be cloned with a dedicated tool, or recreated in hekate and restored from a NAND backup. The community-maintained NH Switch Guide keeps a current, step-by-step SD card transfer walkthrough that covers both cases; follow it rather than improvising, and do not format the old card until the new one has booted successfully at least once.
Next steps
- Setting up from scratch? Follow the SysDVR install guide once the card is ready.
- Full requirements for every platform are in SysDVR system requirements.