Releasing a card batch for school tablets: the swap-and-survive test

By Cathy, Sales Engineer · Published 2026-11-04 · 5 min read

How a school tablet card batch is released: insert-cycle wear, wipe-and-restore, batch consistency, and cost per device-year — the four gates that predict field failure in education.

Tablets in a classroom, the workload a school card batch is specified against

Tablets in a classroom setting, the workload a school card batch is specified against

A card in a shared school tablet is removed, swapped and reinserted far more often than anyone plans for. That decides more of the failure rate than capacity, speed class or brand. No datasheet mentions it.

The short answer

Four gates decide whether an education batch is released:

  • Insert and remove cycles on the actual tablet, not on a card reader.
  • Wipe-and-restore after a pupil deletes everything, including the folder structure the reader expects.
  • Batch consistency across the delivery, because a school orders once and replaces in dribs and drabs.
  • Cost per device-year, which is the only number a budget committee can compare.

Standardise on 32 GB. It stays in SDHC and formats as FAT32 by default. Most tablets, e-readers and older Chromebooks mount it without argument.

The four gates

GateWhat is checkedPass criterionWhat it catches
1. Insert-cycle wear500+ insert and remove cycles in the device’s own slot, then a full read-backNo enumeration failure, no contact dropoutWeak plating and loose tolerances, which show up in term two
2. Wipe and restoreCard formatted by a pupil, then restored from the school’s imageCard mounts, folder structure and content identicalCards whose partition layout cannot be rebuilt by the deployment tool
3. Batch consistencyTen units from the delivery compared against the approved sampleSame controller, die marking, capacity and file systemA second delivery that behaves differently from the first
4. Cost per device-yearUnit price divided by expected service life, against the replacement rateReplacement rate stated, not assumedThe cheapest card that costs most per year

Gate 1 predicts field failure in education. A card reader tests the card. Only the tablet tests the slot.

What to write into the specification

DecisionThe trap if you leave it vagueWhat goes on the purchase order
Capacity and file system64 GB specified, the e-reader only mounts FAT32, half the delivery is “blank”32 GB SDHC, FAT32, cluster size
Speed classPaying for A2 on a fleet that only stores PDFs and videoA1 (or Class 10) — A2 only if the OS runs apps from the card
Preload and folder structureCards arrive blank, IT rebuilds 800 of them by handImage, folder layout, volume label, and whether cards ship preloaded
MarkingEvery card identical, so a card from year one cannot be told from year threeSchool or device-batch code on the label
PackingBulk bag, then the school repacks into 30 classesIndividually labelled sleeves or class-sized packs
ReplacementOne order, no plan for the next intakeAgreed reorder quantity and a fixed specification to reorder against

The preload row saves more money than any price negotiation. An IT technician imaging 800 cards by hand is a cost that never appears on the quotation.

Five things that actually go wrong

The slot, not the card. Shared tablets are handled by children. Contacts wear, cards go in at an angle, and a card that passed a reader test fails in the device.

A pupil formats the card. The card is fine; the partition layout is gone, and the deployment tool cannot rebuild it because nobody wrote down what it was.

The second delivery is not the first. The school orders 300 in September and 60 in January. The January batch carries a different controller and behaves differently under the same image.

FAT32 versus SDXC. Cards above 32 GB ship as exFAT. Devices with a FAT32-only kernel report them as blank or unreadable. This one is a specification error, not a defect.

No reorder specification. When the cards run out, someone buys “the same ones” from a marketplace listing that shares only the capacity.

When 32 GB is the wrong answer

If the deployment stores video lessons offline, and the tablet mounts exFAT, a 64 GB SDXC card halves how often content is rotated. Test it on the exact model first. Test it on the firmware. The failure mode is silent. It shows up as “card not supported” in front of a class.

microSD cards across the capacity range we produce, shown front and back

What we supply

Cards for education usually mean printed labels, a fixed file system and packing that survives a school store room. The custom memory card range covers capacity, print and packing, the monitoring-grade specification covers the ruggedised option, and the TF card specification template is the document to hand to IT before asking for a price.

MOQ is 50 pieces per design, so a pilot for one year group is a normal order. Artwork and approval 1–7 days, production 3–15 working days, testing 1–5 working days, transit 3–20 days.

Where to go next

Sources

Frequently asked questions

What capacity should I standardize on for a school tablet fleet?

Most K–12 and lower-secondary fleets standardize on 32 GB SDHC, because it is the largest capacity that still formats as FAT32 by default and is accepted by the widest range of Android tablets, e-readers and older Chromebooks. Move to 64 GB SDXC only after you have confirmed, on the exact device model and firmware, that exFAT is mounted natively.

Why do some e-readers reject a 64 GB or 128 GB card?

Cards above 32 GB are SDXC and ship formatted as exFAT. Devices whose kernel or firmware only includes a FAT32 driver will mount the card as unreadable or blank. The fix is either to reformat the card as FAT32 (which then breaks files over 4 GB) or to specify an SDHC card at the BOM stage.

Do I need A1 or A2 for an education tablet?

A1/A2 are application-performance classes defined by the SD Association for running apps from the card. If your deployment only stores PDFs, EPUBs, video and audio, A1 is sufficient and cheaper. Specify A2 only if the OS actually installs and runs apps from removable storage.

Can I pre-load content onto the cards before shipment?

Pre-loading is a common request for education deployments. It requires an exact content manifest, a defined file system, a checksum per card, and a re-test step after writing. Confirm the manifest format, checksum method and rejection criteria with your supplier before the order is placed, not after.

Is a cheaper card acceptable for e-readers?

E-readers write very little — mostly sideloaded books and firmware updates. Read speed and capacity matter more than endurance. The risk is not wear-out, it is counterfeit capacity and poor random-read performance on large EPUB or PDF libraries. Buy from a supplier that can show a capacity verification method.

← All guides

WhatsApp / WeChat Request a quote