PR
[PR]アフィリエイト広告を利用しています
[PR]アフィリエイト広告を利用しています

Best microSD Cards for Android Emulation in 2026: Why A2 Matters More Than Capacity

AndroidスマホとmicroSDカードを手に持つ女性(アイキャッチ) Emulator

If you run RetroArch, AetherSX2-style PS2 frontends or a Saturn core on an Android phone, a Retroid Pocket or an AYN Odin, the microSD card you buy has more effect on load times than almost anything else you can change in software. The catch is that the number printed largest on the package — “190MB/s” — is not the number that decides whether a Saturn game stutters when it streams a cutscene.

This guide covers what the ratings actually guarantee, how much capacity you need per system, five cards worth buying, how to spot a counterfeit before and after purchase, and how to format the card so it stays readable when you move it to your next handheld. Prices are approximate US street prices checked on 30 August 2026.

The short answer: U3 plus A2, from a brand you recognise

Three criteria, in order of importance:

  1. An A2 badge on the card. This is the App Performance Class, and it guarantees random-access performance. It is the single rating that correlates with emulator load times.
  2. U3 (or V30). Guarantees a sustained minimum write of 30 MB/s, which matters when you copy a 60 GB library onto the card and when a core writes large savestates.
  3. A brand with a real warranty channel — SanDisk, Samsung, Lexar, Kingston. Unbranded “high speed 1TB” cards from marketplace sellers are the single largest source of failure reports in handheld communities.
What you mostly play Capacity to buy Rating to look for
NES, SNES, Game Boy, Genesis (Mega Drive) 128 GB UHS-I, U3, A2
PS1, Sega Saturn, TurboGrafx-CD mixed in 256 GB UHS-I, U3, V30, A2
PS2 as the main system, or one card for everything 512 GB to 1 TB UHS-I, U3, V30, A2 (Extreme PRO tier preferred)

The instinct is to buy the largest card you can afford. That is the wrong priority. A 256 GB A2 card will feel faster in an emulator than a 1 TB card without an A2 badge, because emulator I/O is dominated by small random reads, not by bulk transfer.

Why cheap cards stutter: sequential speed versus random IOPS

The “up to 190MB/s” figure on the front of the package is a sequential number. It describes reading or writing one large contiguous file, which is what a camera does when it records 4K video. It is a real number and a useful one — for cameras.

An emulator does something different. Loading a disc image means seeking around a large file in small pieces. A savestate write touches several files. A frontend scanning your library reads thousands of small headers. Shader caches, memory card files, per-game config overrides, BIOS reads — all small, all scattered. That workload is measured in IOPS, not MB/s, and it is exactly what the App Performance Class was created to describe.

Class Minimum random read Minimum random write Minimum sustained sequential write
A1 1,500 IOPS 500 IOPS 10 MB/s
A2 4,000 IOPS 2,000 IOPS 10 MB/s

A2 guarantees roughly 2.7x the random read and 4x the random write of A1. A card with no App class at all guarantees nothing on this axis, which is why a bargain 512 GB card can post a respectable sequential benchmark and still make a Saturn game hitch at every stage transition.

UHS-I, UHS-II, and the 104 MB/s ceiling nobody mentions

This trips up a lot of buyers. The UHS-I bus tops out at 104 MB/s in its fastest standard mode (SDR104). UHS-II uses an extra row of pins and goes considerably higher. So how does a UHS-I card advertise 190 MB/s?

Those cards use a manufacturer-specific overclocked mode — commonly called DDR200 — that is not part of the SD standard. You only get those speeds in a card reader that explicitly supports it. Plug the same card into a phone, a Retroid Pocket or an AYN Odin and you get standard UHS-I speeds.

Two practical consequences:

  • Do not pay extra for UHS-II. Essentially every Android phone and Android handheld reads at UHS-I only. The extra pins do nothing, and you have paid a premium for them.
  • Do not treat the headline MB/s as a device-side promise. Between two A2 cards, the one with the higher advertised sequential figure is usually the better bin of flash, so it is a reasonable tiebreaker — but it is not a number you will see on the handheld itself.

How much capacity do you actually need?

Work it out from your own library rather than guessing. Approximate per-title sizes, which vary with how the dump was made and whether it is compressed (CHD, RVZ and similar formats can cut disc images substantially):

System Typical size per title Roughly how many fit in 256 GB
NES, SNES, Game Boy, Genesis A few hundred KB to a few MB Effectively the entire library, many times over
TurboGrafx-CD (the North American PC Engine; PC Engine CD-ROM² in Japan), Sega CD 200–700 MB per disc Several hundred
PS1, Sega Saturn 350–700 MB per disc; multi-disc titles multiply Around 400–700
PS2 1–9 GB per DVD image Around 30–100
  • 128 GB — fine if you are cartridge-era focused with a modest handful of PS1 or Saturn discs. Cheap enough that it is a reasonable second card.
  • 256 GB — the sensible default. Comfortable for a full cartridge library plus a serious PS1 and Saturn collection.
  • 512 GB to 1 TB — buy this if PS2 is the point, or if you want one card that holds everything and never has to be curated.

Do not use Adoptable Storage

Android offers to “format as internal storage” (Adoptable Storage). It encrypts the card and binds it to that specific device. If the handheld dies, or you upgrade from a Retroid Pocket to an AYN Odin, the card is unreadable in the new device and the data is effectively gone. There is no recovery path for an average user.

Always choose portable storage (external SD). You give up nothing that matters for emulation, and the card stays a card.

Five microSD cards worth buying in 2026

Manufacturer-published sequential figures below were checked against vendor product pages on 30 August 2026. Sequential ratings differ between SKUs of the same product family, so check the part number, not just the product name — Lexar in particular ships multiple PLAY revisions with different ratings.

Card Capacity shown Ratings Published sequential (read / write) Best for
SanDisk Extreme microSDXC 128 GB UHS-I, U3, V30, A2 Varies by SKU; older parts rated 160 MB/s read Cartridge-era libraries, or a cheap second card
SanDisk Extreme microSDXC 256 GB UHS-I, U3, V30, A2 Up to 190 / 130 MB/s The default recommendation for most people
SanDisk Extreme PRO microSDXC 256 GB UHS-I, U3, V30, A2 Up to 200 / 140 MB/s Fastest host-side transfers when loading the card
Samsung PRO Plus microSDXC 512 GB UHS-I, U3, V30, A2 Up to 180 / 130 MB/s on the current revision PS2 libraries; a community staple on Android handhelds
Lexar PLAY microSDXC 1 TB UHS-I, U3, V30, A2 Depends on SKU; the original 1 TB part is rated 160 / 100 MB/s One card for everything, at the lowest cost per GB

Community threads on r/SBCGaming and r/EmulationOnAndroid converge on the same two families — SanDisk Extreme and Samsung PRO Plus — not because they benchmark dramatically higher than rivals, but because their failure and counterfeit rates through legitimate channels are low and their A2 behaviour is consistent across production runs. That consistency is what you are actually paying for.

One accessory worth having regardless of which card you choose: a USB-C card reader that supports UHS-I. Copying 200 GB of disc images through a phone’s MTP connection is painfully slow; pulling the card and writing to it directly from a PC is faster by a wide margin, and it is also how you run a capacity verification test (see below).

What these cost, approximately

NAND pricing moved sharply through 2025 and 2026, so treat these as orientation rather than quotes. Approximate US street prices for genuine, branded A2 cards as of 30 August 2026:

Capacity Rough price band (USD) Price that should worry you
128 GB $15–25 Under $8
256 GB $25–45 Under $12
512 GB $45–90 Under $20
1 TB $110–220 Under $35

Where to buy, and how to avoid a counterfeit

Fake microSD cards are not a rare edge case. The scam is straightforward: take a small, often defective flash die, reprogram the controller to report 256 GB or 1 TB, and sell it. The card mounts, shows the advertised capacity, and accepts files — then silently discards or corrupts everything written past the real capacity. You typically discover this months later when a save file will not load.

Buy from a channel with a real returns path

  • Amazon.com — check the buy box says Ships from and sold by Amazon. A third-party seller with Amazon fulfilment is not the same thing, because commingled inventory means a counterfeit from one seller can end up in your box.
  • B&H Photo and Best Buy — first-party stock, straightforward returns, and no marketplace ambiguity.
  • Manufacturer stores — SanDisk, Samsung and Lexar all sell direct.
  • UK and Australia: the same logic applies to Amazon.co.uk and Amazon.com.au. Look for the equivalent first-party dispatch line, or use a national retailer with a physical returns counter.

The high-risk channels are eBay, Amazon Marketplace third-party sellers, and social-marketplace listings. Not everything sold there is fake, but every documented capacity-fraud wave in recent years has run through those routes.

Warning signs in a listing

  • The price is far below the band above. This is the single most reliable signal. Genuine 1 TB flash has a floor.
  • Keyword-stuffed product titles — listings like “1TB Micro SD Card High Speed Memory TF Card for Switch Phone Camera Drone Tablet” are a marketplace pattern, not a manufacturer one.
  • Review patterns that do not match the product — a flood of five-star reviews in a short window, generic praise with no specifics, or reviews that clearly describe a different item entirely (a sign of a hijacked listing).
  • No printed part number. Genuine cards carry a specific SKU. If the listing photos are generic renders with no readable model code, skip it.

Test the card the day it arrives

Do not wait. Run a full write-and-verify pass before you commit a library to the card, while you are still inside the return window.

  • Windows: H2testw writes 1 GB test files until the card is full, then reads them all back and reports how much data was lost or corrupted. Version 1.4 is the last release and is still the standard tool — verifying that written bytes read back correctly does not go out of date.
  • macOS and Linux: F3 (Fight Flash Fraud) does the same job via f3write followed by f3read.

Run the test on an empty card, because it fills all free space. Budget several hours for a 512 GB or 1 TB card — it writes and re-reads the entire capacity. Two outcomes should trigger an immediate return: any reported data loss or corruption, and a sustained write speed of only a few MB/s, which indicates either a counterfeit or flash so poor that it will fail soon anyway.

Formatting and setup on Android, Retroid Pocket and AYN Odin

  1. Open Settings → Storage and select the SD card.
  2. Choose Format as portable storage (external SD). Do not choose the internal-storage option — see the Adoptable Storage warning above.
  3. Once formatting completes, use a file manager to create each emulator’s expected folder at the root of the card (for example RetroArch/roms/, plus a BIOS folder if your cores need one).
  4. Copy across only content you produced yourself from hardware and discs you own.
  5. Point each frontend at the card’s paths rather than internal storage, and rescan your library.

Retroid Pocket and AYN Odin devices run Android underneath, so the flow is identical — the manufacturer launcher may place the Settings entry somewhere different, but Storage → SD card → format is the same sequence. If you expect to move the card between devices, the portable-storage choice is non-negotiable.

Two habits worth adopting: keep a copy of your ROM folder on a PC or NAS, because flash cards do wear out and they usually fail without warning; and back up your savestates and memory card files separately, since those are the only files on the card you cannot regenerate.

A note on where the games come from

This guide assumes you are playing content you dumped yourself from hardware and media you legally own. That is the only approach covered here. This site does not name, link to or describe ROM distribution sites, and downloading commercial games you do not own is copyright infringement in the United States, the United Kingdom and Australia alike.

US law on personal backups of media you own is genuinely unsettled. There is no clean statutory safe harbour for dumping a cartridge the way there is for computer software under 17 U.S.C. §117, and the DMCA’s anti-circumvention rules (§1201) complicate anything involving copy protection — which covers most disc-based systems. Courts have not produced a tidy answer. This is general information, not legal advice. If your situation matters to you, talk to a qualified attorney in your jurisdiction.

What is not ambiguous: downloading games from distribution sites is not covered by any backup argument anywhere, regardless of whether you own a physical copy.

FAQ

Is a UHS-II card worth it?

No, for this use case. Android phones, Retroid Pocket and AYN Odin devices read at UHS-I speeds. A UHS-II card works, but the second pin row is unused and you have paid a premium for nothing. Put that money toward capacity instead.

I hear SanDisk cards are heavily counterfeited. Should I avoid them?

Popularity is exactly why they are counterfeited — the fakes chase whatever sells. The brand is not the risk; the channel is. Buy first-party from Amazon, B&H, Best Buy or the manufacturer, and run H2testw or F3 on arrival, and the risk drops to near zero.

Can I just use internal storage?

For cartridge-era systems, often yes. For PS2 the maths ends it quickly: a few dozen DVD images is a few hundred GB, which no phone will spare alongside photos and apps. A dedicated card also makes backups and device migration far simpler, because your entire game library is one object you can copy.

Does a nearly full card get slower?

Yes. Flash controllers need free blocks to work with, and a card at 98% capacity has less room to manoeuvre during writes. Leaving roughly 10% free is a reasonable habit, and it is one more argument for buying a size up rather than a size down.

Will formatting to exFAT versus FAT32 matter?

Use the format Android gives you when you choose portable storage — that will be exFAT on any card 64 GB or larger. FAT32’s 4 GB per-file limit will break larger PS2 images, so do not go out of your way to force it.

Bottom line

Look for the A2 badge and a U3 rating before you look at anything else, including capacity and headline MB/s. Take 128 GB if you are playing NES, SNES and Genesis; 256 GB if PS1 and Saturn are in the mix; 512 GB or more if PS2 is the reason you bought the handheld. Buy from a first-party channel with a real returns path, run H2testw or F3 the day the card arrives, and format as portable storage so the card outlives the device. Do those five things and the card stops being a variable you have to think about.

YouTubeチャンネルも運営中!

昭和~平成のレトロゲームを中心に、ゆっくりボイスで「語って笑って」解説しています。
遊び方のコツや裏話など、ブログでは書ききれないネタも動画でお届け中です。

「メリ爺のゲーム万歳」を見に行く

当ブログは、レトロゲーム好きのみなさんとの「遊び場」として運営しています。
「記事が役に立った」「続きも読んでみたい」と感じていただけたら、下記リンクからのご利用・ご支援で応援してもらえると嬉しいです。

※Amazonのアソシエイトとして、「メリ爺のゲーム万歳」は適格販売により収入を得ています。

Emulator
シェアする
Meritをフォローする

コメント

Copied title and URL