SD/TF Card Selection Guide — Read the Specs, Match the Scenario

Same Card, Different Device, Different Fate

The same model of TF card might die in two weeks inside a surveillance camera but run fine for six months in an action cam. The difference isn’t the brand — it’s the write workload. Surveillance is 24/7 continuous sequential writes. Action cameras do intermittent burst writes. Raspberry Pi system disks do random small-file writes. Three completely different demands on the flash memory.

flowchart TD
    A["Start with<br/>write workload"] --> B{"How does it write?"}
    B -->|"24/7 sequential"| C["Surveillance / Dashcam<br/>Endurance + wide temp"]
    B -->|"Frequent random"| D["Pi system disk<br/>A2 IOPS"]
    B -->|"Burst / occasional"| E["Camera / Phone / Drone<br/>V or A class"]
    style A fill:#e3f2fd,stroke:#2196F3
    style C fill:#e8f5e9,stroke:#4CAF50
    style D fill:#e8f5e9,stroke:#4CAF50
    style E fill:#e8f5e9,stroke:#4CAF50

Understand the parameters first, then match them to your use case.

What the Labels on the Card Actually Mean

NAND Type: The Hard Limit on Lifespan

Every flash memory cell has a hard limit on how many times it can be erased and rewritten. This is the P/E cycle (Programming/Erasing). Beyond that limit, the cell becomes a bad block:

Sources: Axis surveillance storage white paper, WD endurance in surveillance white paper.

Most consumer cards use TLC, which theoretically offers 1,000–3,000 P/E cycles. But WD’s testing found that budget cards may deliver as few as 10–200 cycles — partly due to lower-grade dies, but mostly due to cut-rate controller firmware.

Then there’s pSLC (pseudo-SLC): running TLC/MLC as if it were SLC, storing only 1 bit per cell. P/E endurance jumps from ~3,000 to 30,000–40,000 cycles, at the cost of 2/3 usable capacity. Industrial cards commonly use this approach.

Why Some Cards Cost 3× More

Tear down a SanDisk High Endurance and you’ll find the same 3D TLC dies as consumer cards. The premium pays for firmware:

• Wear leveling: distributes writes evenly across all blocks, preventing hotspots from wearing out early
• ECC: stronger error correction algorithms extend effective die lifespan
• Power-loss protection: recovers data consistency on unexpected shutdown, reducing filesystem corruption
• Auto Read Refresh: detects blocks with rising error rates and proactively migrates data to healthy blocks

SanDisk MAX Endurance goes further — it runs TLC in pMLC mode (2 bits per cell instead of 3), trading 1/3 capacity for roughly 6× the P/E endurance.

Endurance Ratings: Hours vs TBW — Don’t Mix Them

High-endurance cards use two endurance rating systems with different test conditions. They cannot be directly converted or compared.

Hours (used by Samsung, SanDisk): how long the card can continuously record at a specified bitrate.

TBW (used by WD, Kingston, Dahua): total lifetime write volume.

Samsung and SanDisk official datasheets publish only hours, not TBW. Third-party “equivalent TBW” calculations are not official figures. When comparing cards, stick to one rating system.

Speed Class: V, U, A — Each Measures Something Different

Manufacturers market “read speed 200 MB/s” — but video recording doesn’t care about read speed. It cares about sustained write speed. The SD Association defines three separate rating systems:

A 1080p H.265 surveillance camera typically uses only ~2Mbps — Class 10 is enough. For 4K, V30 is sufficient. A1/A2 measure random IOPS, which is irrelevant for continuous video — that’s for phones running apps and Raspberry Pi system disks.

Temperature Range

A car dashboard in summer sun can exceed 80°C. A consumer card (0–70°C) behind a windshield exceeds its operating range and simply stops working.

Surveillance and Dashcams

Surveillance is the harshest workload for microSD: 24/7 continuous sequential writes with loop-overwrite. Consumer cards typically fail in 2–8 weeks.

Four parameters: endurance (hours or TBW), temperature (-25~85°C for outdoor/automotive), speed (V30 is enough), capacity.

Prices approximate as of mid-2026.

Capacity estimation:

1

Daily storage (GB) = bitrate (Mbps) ÷ 8 × 3600 × 24 ÷ 1024

Surveillance cards should be proactively replaced every 1–2 years — don’t wait for failure. Silent corruption means critical footage may already be lost. Hikvision/Dahua OEM cards read S.M.A.R.T. status through their cameras, and SanDisk Video/Industrial series expose health registers. Check remaining endurance regularly.

Raspberry Pi and SBC System Disks

When a Raspberry Pi uses microSD as a system disk, the workload is the opposite of surveillance: system logs, package caches, temp files, swap — all random small-file writes. The bottleneck is 4K random IOPS, not sequential bandwidth.

Jeff Geerling tested this: most microSD cards deliver only 0.5–1.5 MB/s in 4K random writes, far below rated sequential speeds. The SD Association defined the A class for exactly this:

The catch: A2 ratings depend on the host supporting SD 6.0 Command Queuing. Raspberry Pi 4 and earlier don’t support CQ — A2 cards may actually perform worse than A1 on those models. Only the Pi 5’s SD interface supports command queuing, where A2 finally pays off. For Pi 4 and below, A1 is the pragmatic choice.

The key to extending system disk lifespan isn’t buying the most expensive card — it’s reducing writes:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11

# Mount /tmp and /var/run as tmpfs to avoid temp file writes
tmpfs /tmp tmpfs defaults,noatime,size=100M 0 0
tmpfs /var/run tmpfs defaults,noatime,size=10M 0 0

# log2ram keeps /var/log in RAM with periodic writeback
sudo apt install log2ram

# Disable swap when RAM is sufficient
sudo systemctl disable dphys-swapfile

# Add noatime to root partition to reduce access-time metadata writes

Start at 32–64GB: enough free blocks for wear leveling, not so small that block scarcity accelerates aging. Brand priority: Samsung EVO+, SanDisk Extreme — avoid white-label.

For heavy workloads, use a USB 3.0 SSD instead of SD — random I/O, endurance, and cost-per-GB all crush SD.

Action Cameras, Drones, DSLRs

The bottleneck here is peak sequential write speed, not endurance. GoPro requires at least V30 + A2, DJI recommends U3/V30 or above, DSLRs shooting 4K/8K need V60/V90.

A2 is meaningless for cameras — cameras don’t run apps on the card, so random IOPS isn’t the bottleneck. Don’t get distracted by “read speed 200 MB/s.” Look at V class (sustained write speed).

Capacity priority — start at 128GB. High-bitrate video eats space fast. V90 + large capacity beats chasing endurance.

Phones and Tablets

Phone internal storage is eMMC/UFS; microSD is typically for expansion. For photos and videos, V10/V30 is enough — just get the most capacity you can.

If you move apps to the card (Android adopted storage), A2 noticeably improves launch and runtime performance — the A class was designed specifically for “running apps on the card.” Note that some phones have dropped the card slot entirely; check before buying.

Industrial and Automotive

Industrial data logging, automotive, and medical equipment demand the most extreme specs: wide temp (-4085°C or automotive -40105°C), vibration resistance, power-loss protection, long lifespan. These use industrial-grade pSLC cards.

Representative products: Swissbit S-56u (3D pSLC, -4085°C), Kingston Industrial (pSLC, -4085°C, rated 3840 TBW), SanDisk Industrial, FORESEE pSLC. For automotive certification, look for AEC-Q100 (e.g., Swissbit S-52u automotive series).

Prices run 5–10× consumer cards, but unattended industrial environments have no alternative — one consumer card failure costs more than the card itself.

Fake Card Detection: Do This First

Tom’s Hardware tested 200+ cards by writing 18 PB across 8 machines and 70 card readers. Results: genuine brand cards from Amazon averaged 3,000–5,000 P/E cycles, while AliExpress “same-name” cards and fake flash averaged only a few hundred — some failed before reaching 100 cycles.

The most common fake is the capacity-expanded card: a 32GB die with modified firmware reporting as 128GB. Data written beyond the real capacity is destroyed. Detection methods:

Windows — H2testw:

Download H2testw, insert the card, select the drive, click “Write + Verify.” It writes and reads back the full capacity — fake cards error at the real capacity boundary.

macOS / Linux — F3:

1
2
3
4
5
6
7
8
9

# macOS
brew install f3
f3write /Volumes/your_sd_card
f3read /Volumes/your_sd_card

# Linux
sudo apt install f3
f3write /media/your_sd_card
f3read /media/your_sd_card

Buy from official stores or major retailers (Amazon direct, JD.com direct). A 128GB card selling for $5 is almost certainly fake.

Quick Selection Reference

Universal rule: verify with H2testw/F3 before use, buy from official channels, avoid expanded-capacity fakes.