microSD Cards for Body Cameras and Security Wearables — Buyer's Guide

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

A segment buying guide for body cameras and security wearables — capacity bands, file systems, what devices accept, what to lock in the BOM, and a PO checklist.

Body-worn camera and security wearable recording continuously to microSD

TL;DR

For body cameras and security wearables, buy the card the device firmware was validated against — not the fastest or cheapest card on the shelf. In practice that means: pick a capacity band sized to your shift length and bitrate, agree the file system (exFAT above 32 GB, FAT32 at or below 32 GB), require a card rated for sustained write and elevated operating temperature, and lock NAND lot, controller, firmware and formatting into the BOM. Then verify every shipment with a capacity/write test before it reaches a wearer.

The rest of this guide walks through the checks a procurement or engineering buyer should run before signing a purchase order for a body-camera or security-wearable fleet.

1. Start from the device, not the card

Body cameras and security wearables are closed systems. The firmware, the recording bitrate, the file rotation policy and the file system are all fixed by the device maker. Your job as a buyer is not to find the “best” card in the abstract — it is to find the card the device will accept reliably for the life of the fleet.

Before you shortlist any supplier, get three things in writing from the device vendor:

  • The validated card list or the specific controller/NAND families the firmware has been tested with.
  • The recording profile: resolution, codec, bitrate, and how long a single file runs before rotation.
  • The file system and cluster size the device expects, and whether it reformats the card on first insert.

If the vendor will not provide these, treat that as a risk on the device side, not the card side. A card that is perfect on paper will still fail if the firmware writes in a pattern the card’s controller handles badly. For background on why controller and NAND pairing matters, see flash brand and controller pairing.

2. Choose the capacity band from shift length, not from the shelf

Capacity is the first number buyers reach for and the last one that should be decided. Work it out from the device’s own numbers:

  1. Take the recording bitrate in megabits per second from the device spec.
  2. Multiply by recording seconds per shift to get megabits, then divide by 8 for megabytes.
  3. Add the file-system overhead (typically a few percent) and a working margin for firmware logs, snapshots and firmware update staging.
  4. Round up to the nearest band your supplier stocks.

As an illustration: a device recording at 8 Mbps for a 12-hour shift produces roughly 43 GB of video before overhead (Illustrative only — not WINTEL data). That already puts you above the 32 GB SDHC boundary and into exFAT territory. A device at 4 Mbps for an 8-hour shift lands nearer 14 GB and could live comfortably in a 32 GB card.

Two practical rules follow from this:

  • Do not straddle the 32 GB boundary casually. Crossing from 32 GB to 64 GB changes the default file system from FAT32 to exFAT, and some older firmware handles one but not the other. See capacity bands and where they stop making sense.
  • Standardise on one band for the fleet. Mixed capacities complicate spares, firmware testing and warranty handling. A single band with a clear replacement cycle beats a spread of sizes.

For a rough sizing tool, the TF card capacity estimator will do the arithmetic once you have the bitrate.

3. Match the file system to the device, not to your laptop

The file system is where most body-camera card problems actually originate. The SD Association’s capacity overview sets the convention: cards up to 32 GB ship as SDHC with FAT32, cards above 32 GB ship as SDXC with exFAT. Microsoft’s exFAT specification explains why exFAT exists — it was designed for flash media with large volumes and large files, without FAT32’s 4 GB per-file ceiling and 32 GB volume ceiling.

What that means for a buyer:

  • FAT32 caps individual files at 4 GB. If a body camera writes one long file per shift at high bitrate, it will hit that ceiling and either split the file or fail. Confirm the device’s rotation policy.
  • exFAT removes the 4 GB file limit and is the default above 32 GB, but not every embedded firmware implements it well. Some devices require FAT32 regardless of capacity and will refuse to mount an exFAT card.
  • Cluster size affects write amplification and card lifetime. Smaller clusters mean more metadata writes; larger clusters waste space on small files. The device vendor’s recommended cluster size is the one to use.

Write the agreed file system and cluster size into the purchase order, and require the factory to format and verify to that spec. Do not leave formatting to whoever unboxes the cards at the depot.

Speed class markings — U1, U3, V30 and so on — describe minimum sequential write performance under defined test conditions, as defined by the SD Association. They are useful shorthand, but they do not describe what a body camera actually stresses:

  • Sustained write over hours, not a burst benchmark.
  • Random write behaviour, because the device writes metadata, index files and snapshots alongside video.
  • Behaviour when the card is nearly full, which is the state a body camera spends most of its shift in.
  • Thermal behaviour inside a sealed, body-worn enclosure with no airflow.

Ask the supplier for the card’s datasheet or product page and check whether it states support for continuous write workloads and an operating temperature range that covers a device worn against the body or mounted in a warm cabinet. For the thermal side of this problem in a related segment, see dashcam microSD cards dropping frames when hot — the physics is the same.

Do not accept “V30” as the whole answer. V30 tells you the card can sustain 30 MB/s sequential write under test conditions; it does not tell you the card will still be doing that in hour ten at 60 °C with 90 % of its capacity used.

5. Lock the BOM: NAND lot, controller, firmware, formatting

This is the step that separates a fleet purchase from a retail purchase. A body camera that works with today’s card may not work with next quarter’s card if the supplier silently changes the NAND or controller. Lock the following into the BOM and into the purchase order:

  1. NAND family and lot traceability. Require the supplier to declare the NAND type and to be able to trace a finished card back to a lot. See flash memory lot traceability and die marking.
  2. Controller family. The controller determines how the card handles garbage collection, wear levelling and power loss. A controller change is a firmware-level change from the device’s point of view.
  3. Card firmware version. Some cards carry field-updatable firmware; some do not. Record what shipped and require notification before any change.
  4. Formatting and test spec. File system, cluster size, capacity verification method, and the write test the factory runs before packing.
  5. Marking and packaging. Laser marking, label content and packaging must match what your depot and asset-tracking systems expect. If the cards are serialised or asset-tagged, say so up front.

If your supplier cannot or will not lock these, that is the answer to whether they are the right supplier for a fleet.

6. Verify the shipment, not just the sample

A sample that passes tells you the sample passed. It does not tell you the shipment will. Build a receiving test into the purchase order:

  • Capacity test on a sample from each carton using H2testw or f3, to catch cards that report more capacity than they hold.
  • Write-speed spot check on the same sample, at the card’s stated class.
  • Format check: confirm the card mounts with the agreed file system and cluster size on a device from your fleet, not on a laptop.
  • Visual and marking check against the approved artwork.
  • Retain a reference card from each shipment so future disputes have a physical baseline.

The sample acceptance checklist covers the general version of this for flash products; add the device-mount test on top for body cameras.

7. Plan the replacement cycle before you need it

Body-camera cards are consumables. They are written to every shift, they live in a hot sealed enclosure, and they will reach end of life before the device does. Decide up front:

  • Rotation interval — how many months of service before a card is retired, based on the device’s bitrate and the card’s stated endurance.
  • Spare ratio — how many spare cards per fleet you hold, so a failed card is a swap and not a lost shift.
  • Retirement handling — whether retired cards are destroyed, returned, or wiped and reused, and who is accountable for the data on them.

This is a policy decision, not a card-spec decision, but it belongs in the same procurement conversation because it determines order quantity and reorder cadence. If you are planning a multi-year contract, see how long a custom microSD order takes for lead-time planning.

8. Purchase-order checklist for body cameras and security wearables

Use this as the structure for the PO itself, not as a form to print. Each item is a clause to negotiate and write down.

  1. Device compatibility statement. The supplier confirms in writing that the specified card has been tested against the named device model and firmware version, and states what was tested.
  2. Capacity band and tolerance. The nominal capacity, the acceptable measured capacity range, and the test method used to verify it.
  3. File system and cluster size. The exact format the cards must ship with, and confirmation that the factory formats and verifies to that spec.
  4. Sustained write and temperature specification. The datasheet figures for sustained write and operating temperature, with the test conditions stated.
  5. NAND, controller and firmware lock. The declared NAND family, controller family and card firmware version, with a change-notification clause.
  6. Marking and packaging spec. Approved artwork, marking method, serialisation if required, and packaging that suits your depot.
  7. Test and inspection regime. Which tests run on which sample size per lot, and what the pass criteria are.
  8. Certificate of conformance. What the supplier will certify and against which specification. See what a certificate of conformance actually says.
  9. Replacement and credit terms. What happens if a lot fails the receiving test — replacement, credit, or refund — and on what timeline.
  10. Reorder clause. Confirmation that a follow-on order will use the same locked BOM, and what notice is required if that changes.

9. What WINTEL can and cannot confirm for this segment

WINTEL manufactures custom TF/microSD cards, USB flash drives, UDP modules and semi-finished boards for OEM/ODM buyers. For body-camera and security-wearable programmes, the relevant capability is custom TF/microSD supply to a buyer’s specification, with the BOM items above agreed at order stage.

What this guide does not claim on WINTEL’s behalf: specific speed classes, endurance or TBW figures, temperature ratings, MOQ, lead times, test results, customer references or certifications. Those are programme-specific and must be confirmed directly with WINTEL for your order. Start with request a quote and specify the device model, firmware version and file system you need the cards validated against.

For the wider picture on how custom microSD orders are structured, see how to compare two microSD quotations line by line and the TF card product page.

FAQ

Can I use a normal consumer microSD card in a body camera? Physically yes, but consumer cards are often not specified for continuous write workloads. For a device that records all shift, look for a card whose datasheet or product page states support for sustained write and a high-temperature rating, and confirm the device’s own compatibility list.

Does a higher speed class always mean a better card for a body camera? No. Speed class (U1/U3/V30 etc.) describes minimum sequential write performance under defined test conditions. Body cameras usually need steady sustained writes plus good random-write behaviour and heat tolerance, which speed class does not fully describe.

What capacity should I standardise on? Match capacity to the device’s recording bitrate, shift length and file rotation, then add margin. Standardise on one band across the fleet so replacement stock, firmware testing and spares management stay simple.

Should cards ship pre-formatted? Yes. Agree the file system (usually exFAT above 32 GB, FAT32 at or below 32 GB) and the cluster size with the device maker, and confirm the factory formats and tests to that spec before shipment.

How do I protect against counterfeit or downgraded cards? Buy from a factory that can show NAND lot traceability, test capacity and write speed on the finished card, and provide a certificate of conformance. Inspect a sample batch with H2testw or f3 before accepting a shipment.

Sources

Sources

Frequently asked questions

Can I use a normal consumer microSD card in a body camera?

Physically yes, but consumer cards are often not specified for continuous write workloads. For a device that records all shift, look for a card whose datasheet or product page states support for sustained write and a high-temperature rating, and confirm the device's own compatibility list.

Does a higher speed class always mean a better card for a body camera?

No. Speed class (U1/U3/V30 etc.) describes minimum sequential write performance. Body cameras usually need steady sustained writes plus good random-write behaviour and heat tolerance, which speed class does not fully describe.

What capacity should I standardise on?

Match capacity to the device's recording bitrate, shift length and file rotation, then add margin. Standardise on one band across the fleet so replacement stock, firmware testing and spares management stay simple.

Should cards ship pre-formatted?

Yes, agree the file system (usually exFAT above 32 GB, FAT32 at or below 32 GB) and the cluster size with the device maker, and confirm the factory formats and tests to that spec before shipment.

How do I protect against counterfeit or downgraded cards?

Buy from a factory that can show NAND lot traceability, test capacity and write speed on the finished card, and provide a certificate of conformance. Inspect a sample batch with H2testw or f3 before accepting a shipment.

← All guides

WhatsApp / WeChat Request a quote