How to choose microSD cards for field recorders, DJ decks and audio loggers — capacity band, file system, sustained-write reality, and what to lock in the BOM.
TL;DR
For audio recorders, DJ decks and field recorders, the card is rarely the bottleneck — the recorder’s host controller and file system are. Buy a reputable Class 10 / U1 card in the 32 GB or 64–128 GB band, formatted by the device itself, and stop paying for V30/V60 ratings that a stereo WAV stream will never touch.
The real decisions are:
- Capacity band — 32 GB if the firmware is old or FAT32-only; 64–128 GB if it mounts exFAT and you record long multi-hour sessions.
- File system — FAT32 up to 32 GB, exFAT above. This is a compatibility decision, not a performance one.
- Sustained write and burst behaviour — the card must absorb write bursts and internal housekeeping without a dropout the recorder notices.
- What you lock in the BOM — controller family, NAND grade, format, capacity band, print marking, and a written acceptance test.
If you are sourcing cards to bundle with hardware, the checklist near the end is the part to hand to your supplier.
Why audio is an unusual storage workload
Audio looks easy on paper. A 24-bit/96 kHz stereo WAV stream is about 4.4 Mbit/s, roughly 0.55 MB/s. Even a Class 4 card has enormous headroom. That is why the marketing answer (“buy the fastest card”) is wrong for this segment and why buyers overpay.
What actually stresses the card is not the average rate but three other things:
- Burst writes. Recorders buffer in RAM and flush in chunks. A multi-track or 32-bit float capture can push short bursts many times the average rate. The card has to absorb those without stalling the host.
- Background housekeeping. The controller performs garbage collection and wear levelling. If the card is nearly full and has been written many times, those operations compete with the live stream. This is where cheap cards fail and good ones do not.
- Power behaviour. Field recorders run on batteries and are often powered down abruptly. A card that is mid-erase when power drops can lose the directory entry for the last file even if the audio blocks were written.
If you want the deeper mechanics, the existing articles on power-loss corruption and what protects data and power-fail-safe write strategy cover them; this guide does not repeat them.
The capacity band decision
This is the first thing to settle, because it determines the file system, and the file system determines whether the device will mount the card at all.
| Band | Default file system | Typical use | Watch out for |
|---|---|---|---|
| 8–32 GB | FAT32 | Interview recorders, body-worn audio loggers, older DJ media players | 4 GB single-file limit — long uninterrupted WAVs must be split |
| 64–128 GB | exFAT | Multi-hour field sessions, multi-track recorders, card-as-archive workflows | Older firmware may refuse to mount exFAT entirely |
| 256 GB+ | exFAT | Rarely justified for audio; useful only if the card doubles as an archive | Cost per GB rises; small-file performance is not better |
Two rules of thumb:
- If the device manual does not explicitly say “supports SDXC” or “supports exFAT”, buy 32 GB. A 64 GB card that will not mount is worse than a 32 GB card that will.
- If you record unattended for more than about four hours per session, go to 64 GB or above, because the 4 GB single-file limit forces file splitting and you want headroom for the split files plus the recorder’s own metadata.
The general logic of where capacity bands stop making economic sense is covered in capacity bands where they stop making sense. For audio specifically, the answer is usually lower than buyers expect.
A worked capacity example
Take a stereo 24-bit/96 kHz WAV at about 0.55 MB/s. A one-hour file is roughly 2 GB. On a 32 GB FAT32 card you fit about 14 hours of continuous audio before the 4 GB per-file limit forces a split; on a 64 GB exFAT card you fit roughly 29 hours. (Illustrative only — not WINTEL data. Your recorder’s bit depth, sample rate and channel count will change these numbers; use the TF card capacity estimator with your own figures.)
The file system question, stated plainly
The SD Association defines SDHC (2–32 GB) as FAT32 by default and SDXC (32 GB–2 TB) as exFAT by default. That is a standard, not a vendor choice, and it is why a 64 GB card arrives formatted exFAT.
Microsoft’s documentation is the authority on the limits that matter here: FAT32 caps a single file at 4 GB and a volume at 32 GB; exFAT removes both. Every recorder that “supports up to 32 GB” is really saying “our firmware only understands FAT32”.
Practical consequences for a buyer:
- Never reformat a 64 GB card to FAT32 to make an old recorder accept it, unless the device vendor explicitly supports that. Many tools will do it, and many recorders will then corrupt the card because their FAT32 driver was written for smaller volumes.
- Format in the device. The recorder’s own format routine writes the allocation unit size and directory layout its firmware expects. A card formatted on a laptop may mount but behave differently under write.
- Ask the supplier what file system the card ships with, and whether they can ship it pre-formatted to your spec. This is a legitimate production instruction, not a special favour.
What the recorder will and will not accept
The gap between “works on my laptop” and “works in the product” is the single most common source of returns in this segment. It comes down to the host controller.
Embedded recorders typically use simpler SD host controllers than a PC card reader. They may run at default speed rather than high-speed mode, have narrower timing margins, and implement less tolerant error recovery. The Linux MMC subsystem documentation is a useful reminder of how much of this is host-specific: tuning, quirks and error handling differ per controller. A card that is marginal on those controllers can mount fine on a PC and drop out under sustained write in the field.
What to test before you commit a batch:
- Continuous record for the longest session your users do, then verify the file opens and the audio is intact to the last sample.
- Record to a nearly full card, because garbage collection behaviour changes as free space shrinks.
- Power-cycle mid-recording, because field recorders get switched off. Check whether the last file is recoverable.
- Test on the actual hardware revision you ship, not a development board. Recorders get silent component changes.
The sample acceptance checklist is a starting structure for this; adapt the record durations to your product.
DJ gear and media players: a different problem
DJ decks and standalone media players are not recorders — they read. But they read in a way that exposes different card weaknesses:
- Library scans read thousands of small files and directory entries. This is a random-read workload, not a streaming one, and it is where cheap cards feel slow in the browser.
- Track loading is a burst read; a card that stalls for a second mid-load produces an audible gap.
- Hot removal is normal in a DJ booth. The card must survive being pulled while mounted.
For this use, capacity matters more than class: a 128 GB card holds a large library and costs little more than 64 GB. The A1/A2 application-performance ratings are the relevant marker here rather than V-class, and the article on A1/A2 application performance explains what those ratings do and do not promise.
What to lock in the BOM
If your product ships with a card, or you are buying cards as an accessory line, the BOM line item should specify more than “microSD 32 GB”. Lock these:
- Controller family. Not a brand claim — the actual controller series. Controller behaviour under power loss and garbage collection is what determines field reliability, and it is the thing that silently changes between batches.
- NAND grade and source. Specify the grade (e.g. good-die vs downgrade) and require lot traceability. The article on lot traceability and die marking explains why marking matters when a batch is questioned.
- Capacity band and usable capacity. State the nominal capacity and the acceptance threshold for usable capacity after formatting.
- File system and allocation unit size as shipped.
- Printed marking. Logo, capacity marking, and any regulatory text. Artwork format requirements are covered in artwork formats we accept and the ones that cost time.
- Acceptance test. A written, repeatable test — continuous record duration, verification method, pass/fail threshold. This is the clause that makes the rest enforceable.
- Packaging and its own minimum. Card print and box print are separate steps with separate minimums; see custom box minimum order higher than drive order for why they diverge.
If you are comparing quotations, the line-by-line method in how to compare two microSD quotations line by line is the right tool — two quotes at the same price per piece are rarely the same product.
Purchase-order checklist for audio and DJ buyers
Work through these in order. Each one exists because skipping it has a known failure mode.
- Confirm the device’s maximum supported capacity and file system from the vendor’s own documentation, not the retail listing. Retail listings routinely overstate support. If the manual says 32 GB, the BOM says 32 GB.
- Decide the capacity band from your users’ real session length, using the 4 GB FAT32 file limit as the boundary. Do not buy 128 GB because it sounds safer; buy it because the sessions need it.
- Specify the file system and allocation unit size as shipped, and state whether the card must arrive pre-formatted or blank.
- Name the controller family and NAND grade in the BOM, and require that substitutions be notified in writing before shipment.
- Require lot traceability — lot code on the card or the reel, tied to the shipment documents.
- Write the acceptance test into the PO: record duration, verification method, sample size per lot, and the remedy if a lot fails. The article on credit, replacement or refund covers how to word the remedy.
- Test on production hardware, not a dev board, and test a nearly-full card as well as a fresh one.
- Specify printed marking and packaging separately, with their own minimums and their own approval step.
- Agree the sample fee and what you will test on the sample before the bulk order — see flash sample fee and what to test on one.
- Agree the payment schedule and the currency clause so that a controller or NAND price move mid-order does not reopen the price. The relevant mechanics are in currency clauses: two places price moves and how much deposit and payment schedules work.
- Confirm the delivery date against your production date, working backwards — the method in I need these by the 15th: working back from a date applies directly to bundled-card launches.
- Keep a retained sample from each accepted lot so that a later field complaint can be compared against what was actually approved.
Where WINTEL fits
WINTEL (Shenzhen Wintel Digital Technology Limited) manufactures custom TF/microSD cards, USB flash drives, UDP modules and semi-finished boards for OEM/ODM buyers. The company operates a 5,000 m² facility in Shenzhen with a stated monthly capacity of 500,000+ units, holds SGS, RoHS, CE and FCC listings, and exports to 50+ countries.
For audio and DJ buyers specifically, the relevant capabilities are custom card printing and packaging on microSD orders, and production to a buyer-specified BOM. Exact minimum order quantities, lead times, artwork requirements and acceptance-test terms are confirmed per quotation — they are not fixed numbers, and any supplier who quotes them without seeing your specification is guessing.
If you are sourcing cards for a hardware product, the most useful first step is to send your device’s supported capacity and file system, your session length, and your acceptance criteria. From there a specification and a quotation can be built. You can request a quote or review the TF card product range.
FAQ
Is a faster card class actually necessary for audio recording? Usually no for the audio stream itself. A 24-bit/96 kHz stereo WAV is roughly 4.4 Mbit/s, far below any Class 10 or U1 card. The class matters for multi-track recorders, 32-bit float multi-channel captures, and for the card’s ability to absorb write bursts and reallocation without a visible dropout. Buy a reputable Class 10 / U1 card rather than paying for V30 or V60 you will not use.
Should I use 32 GB or 64 GB cards for a field recorder? It depends on the file system your device supports. Cards up to 32 GB ship formatted FAT32, which every recorder reads. Cards above 32 GB ship exFAT, which older recorders may not mount at all. If the device firmware is old, stay at 32 GB. If it supports exFAT and you record long sessions, 64–128 GB is the practical band.
Why do cards that work on my laptop fail in the recorder? Recorders often use simpler SD host controllers with narrower timing margins, no high-speed tuning, and less tolerant error recovery. A card that is marginal on those controllers may mount on a PC but drop out under sustained write. Format the card in the recorder itself, not on the PC, and test with a long continuous recording before committing a batch.
Can I put my brand logo on the card and the packaging? Card printing and packaging are separate production steps with separate minimums. WINTEL can discuss custom printing and packaging for microSD orders; exact artwork requirements, minimums and lead times depend on the job and are confirmed per quotation. Do not assume a card-level print minimum equals a box minimum.
What should I lock in the BOM for an audio product that ships with a card? Lock the controller family, the NAND grade, the formatted file system, the capacity band, the card’s printed marking, and a written acceptance test (continuous record for a defined duration, then verify the file). Locking only capacity and price is how batches drift.
Sources
- SD Association — SD Specifications & Speed Class / UHS Speed Class / Video Speed Class: https://www.sdcard.org/developers/sd-standard-overview/ (accessed 2026-11-12)
- SD Association — Capacity and file system (SDHC / SDXC / exFAT): https://www.sdcard.org/developers/sd-standard-overview/capacity-sd-sdhc-sdxc-sduccard/ (accessed 2026-11-12)
- Microsoft Learn — exFAT file system specification: https://learn.microsoft.com/en-us/windows/win32/fileio/exfat-specification (accessed 2026-11-12)
- Microsoft Learn — Maximum volume size (FAT32 limits): https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-volume-size (accessed 2026-11-12)
- Apple Developer — AVAudioRecorder: https://developer.apple.com/documentation/avfaudio/avaudiorecorder (accessed 2026-11-12)
- Linux kernel documentation — MMC/SD host controller subsystem: https://docs.kernel.org/driver-api/mmc/index.html (accessed 2026-11-12)
- USB Implementers Forum (organization root; general reference for USB card readers): https://www.usb.org/ (accessed 2026-11-12)
Sources
- SD Association — SD Specifications & Speed Class / UHS Speed Class / Video Speed Class
- SD Association — Capacity and file system (SDHC / SDXC / exFAT)
- Microsoft Learn — exFAT file system specification
- Microsoft Learn — FAT32 maximum volume / file size limits
- Apple Developer — AVAudioRecorder / Audio Queue Services documentation
- Linux kernel documentation — MMC/SD host controller and card quirks
- USB Implementers Forum — USB mass storage / card reader behaviour
Frequently asked questions
Is a faster card class actually necessary for audio recording?
Usually no for the audio stream itself. A 24-bit/96 kHz stereo WAV is roughly 4.4 Mbit/s, far below any Class 10 or U1 card. The class matters for multi-track recorders, 32-bit float multi-channel captures, and for the card's ability to absorb write bursts and reallocation without a visible dropout. Buy a reputable Class 10 / U1 card rather than paying for V30 or V60 you will not use.
Should I use 32 GB or 64 GB cards for a field recorder?
It depends on the file system your device supports. Cards up to 32 GB ship formatted FAT32, which every recorder reads. Cards above 32 GB ship exFAT, which older recorders may not mount at all. If the device firmware is old, stay at 32 GB. If it supports exFAT and you record long sessions, 64–128 GB is the practical band.
Why do cards that work on my laptop fail in the recorder?
Recorders often use simpler SD host controllers with narrower timing margins, no high-speed tuning, and less tolerant error recovery. A card that is marginal on those controllers may mount on a PC but drop out under sustained write. Format the card in the recorder itself, not on the PC, and test with a long continuous recording before committing a batch.
Can I put my brand logo on the card and the packaging?
Card printing and packaging are separate production steps with separate minimums. WINTEL can discuss custom printing and packaging for microSD orders; exact artwork requirements, minimums and lead times depend on the job and are confirmed per quotation. Do not assume a card-level print minimum equals a box minimum.
What should I lock in the BOM for an audio product that ships with a card?
Lock the controller family, the NAND grade, the formatted file system, the capacity band, the card's printed marking, and a written acceptance test (continuous record for a defined duration, then verify the file). Locking only capacity and price is how batches drift.