If you play Snes9x on Android or keep your library on a retro handheld, the microSD card is the component everything else depends on: it holds your games, your .srm battery saves and, on many handhelds, the firmware itself. It is also the most counterfeited product in the whole setup. This guide covers what class of card to buy for a retro library, how fake-capacity cards work and why they quietly destroy saves, the warning signs before you buy, and the verify-on-arrival routine that takes a few minutes and settles the question for good. The card we point readers to as a starting point is a genuine SanDisk A2-class microSDXC bought from a reputable seller — the seller matters as much as the brand, which is rather the point of this page.
What class of card a retro library needs
SNES games are tiny by modern standards, and raw capacity is rarely the issue — even a large, carefully kept library is small next to today’s card sizes, so buy for trustworthiness, not for the biggest number on the packet. What does matter is the card’s speed class for random access: cards rated A2 (Application Performance Class 2) are designed for running apps and lots of small reads, which is exactly a handheld or Android workload of launching emulators, loading ROM lists and writing save files. An A1 card also works; a no-name card with no class marking at all is the thing to avoid. Format the card the way your device expects (most handheld firmwares and Android devices are happiest with exFAT for larger cards, FAT32 for smaller or older devices) and let the device do the formatting where it offers to.
How fake-capacity cards work — and why saves die first
A fake-capacity card is a small card whose controller has been reprogrammed to report a much larger size. It accepts writes cheerfully — until the real storage runs out, at which point new data either silently overwrites old data or vanishes, while the file system still believes everything is fine. On a retro handheld or phone, the casualties appear in the worst possible order: the card fills gradually as you add games, so the corruption begins right around the time you have built a library and a set of saves worth keeping. A battery save written months into a playthrough can land on phantom space and be gone at the next boot, with no error ever shown. This is why “the card was suspiciously cheap and huge” is not a bargain signal in this hobby; it is the failure mode itself. It is also why the card bundled free with a budget handheld deserves replacing with a known-genuine one, as noted in our retro handheld comparison.
Warning signs before you buy
- Price far below every other seller for the same marked capacity — the classic tell.
- Marketplace listings from sellers with no history, or packaging that looks almost-but-not-quite like the brand’s retail pack.
- Unbranded or oddly branded cards bundled as a “free upgrade” with a handheld.
- Capacity claims that outrun the market — if a size-and-price combination does not exist from the major brands’ own stores, it does not exist.
The defence is boring and total: buy from the brand’s own store or a large, accountable retailer, sold and dispatched by the retailer itself rather than a third-party marketplace seller. That is the entire purchasing strategy.
Verify on arrival, before you trust it with saves
Whatever the source, test a new card before your library moves onto it. The reliable method is a full write-and-verify test on a computer: tools in this category (H2testw on Windows is the long-standing example) write test data across the card’s entire reported capacity and then read it back, which exposes a faked card immediately — it will fail at the point where the real storage ends. Only after a card passes should games and saves go on it. Then build the habit that protects you even from honest hardware failure: keep a backup of the saves folder somewhere else. Our cloud save sync guide shows how to keep Snes9x .srm files and save states backed up between devices, and the same folder copy works for a handheld’s card. Test first, back up always — those two habits together make card problems an inconvenience instead of a loss. More hardware guidance is on the gear hub, and Snes9x itself is on the download page.
Looking after the card you bought
A genuine card still deserves basic care. Eject it properly — use the device’s unmount option or shut the handheld down before pulling the card — because a save file being written at the moment of removal is the most mundane way to corrupt one. Avoid filling any card completely; file systems behave best with a little free space, and a retro library is small enough that leaving headroom costs nothing. If your handheld’s firmware lives on the same card as your games, consider keeping a second, imaged card as a spare once everything is set up the way you like it: restoring a working setup then takes minutes instead of an afternoon. And label the real card with its purchase source and date, however unglamorous that sounds — six months from now, “the good SanDisk” and “the one that came in the box” look identical, and only one of them should ever hold your saves.
The same genuine-card advice applies wherever a microSD card holds your library — including the living-room build in our Raspberry Pi SNES console guide, where the card also carries the system itself.
Affiliate note: some links in this guide are affiliate links (they go through this site’s /go/ redirects). If you buy through one, Snes9x.net may earn a commission at no extra cost to you. See our affiliate disclosure.