microSD Cards and Embedded Flash for Security Cameras, NVRs and Edge Recording

In short

Surveillance recording is a 24/7 overwrite workload with one extra constraint: the device is often installed somewhere that is expensive to revisit. That makes total bytes written, thermal behaviour and long-term reliability more important than burst speed. WINTEL supplies TF cards from 4GB to 256GB and UDP modules from 128MB to 128GB for cameras, NVR units and edge recording devices, with read and write speed specified per project. For cameras that record internally rather than to a central NVR, UDP modules give you fixed, non-removable storage soldered directly onto the board. Cards ship direct from our Shenzhen line, 50 pieces minimum on standard builds, with a capacity test on a batch sample before packing if you ask for one.

What this buyer actually cares about

Endurance under constant overwrite

Every recording hour consumes write cycles. The question buyers ask is how many, and most suppliers answer with a marketing endurance label rather than the underlying figure.

Thermal behaviour

Cameras in housings, on poles and in direct sun run hot, and flash behaviour changes with temperature. Standard commercial parts are not specified for the full industrial range.

Physical security of the recording medium

A removable card can be removed. In tamper-sensitive installations, fixed internal storage removes that entire class of risk.

Field failure cost

The card is a small part of the bill of materials and a large part of the truck-roll cost when it fails. Buyers care more about batch consistency than about unit price.

What we do about it

  • Supply TF cards and UDP modules sized to your retention requirement
  • Specify read and write speed per project for continuous-write workloads
  • Offer UDP modules for fixed, non-removable internal storage
  • Source silicon from named suppliers so the grade is known before you commit
  • Confirm capacity and performance before packing

Recommended configuration

A starting point drawn from the workloads buyers in this scenario describe. We confirm the exact specification against your bitrate, host and target date rather than quoting a generic figure.

DimensionRecommended starting point
Capacity32–256 GB sized to your retention window
SpeedSustained write for continuous 24/7 overwrite
Flash gradeA+ grade, named silicon source

Common procurement risks

What buyers in this scenario most often get wrong — and how we address it.

  • Endurance overstated by a marketing label, not a real write-cycle figure
  • Commercial parts not specified for in-housing or outdoor temperature
  • Removable card removed or swapped in tamper-sensitive installs
  • Batch inconsistency across a multi-unit deployment

How many days of recording one card actually holds

Capacity is not the first number to specify — bitrate is. Every IP camera publishes the bitrate of the stream it produces, and the retention window falls out of that one figure. The table below uses usable capacity rather than the printed one, because a 128GB card presents roughly 119GiB to the recorder, about 7% less than the label.

Camera / codecBitrateGB written per day64GB128GB256GB512GB
1080p, H.2652 Mbps21.62.8 days5.5 days11.0 days22.0 days
1080p, H.2644 Mbps43.21.4 days2.8 days5.5 days11.0 days
4 MP, H.2656 Mbps64.80.9 days1.8 days3.7 days7.3 days
4K / 8 MP12 Mbps129.60.5 days0.9 days1.8 days3.7 days

GB per day = bitrate in Mbps × 10.8, from 86,400 seconds per day. Usable capacity is taken at 93% of the printed figure. Your recorder’s own stream setting overrides every row in this table.

A 4 Mbps 1080p stream writes 43.2GB every day, so a 128GB card is overwritten for the first time on day three. Thirty days of retention at that bitrate needs about 1.3TB — which is a reason to keep long retention on an NVR and treat the card as the last few days of cover, not as an archive.

This is also where most capacity specifications go wrong in the other direction. A 512GB card that costs more per unit and is overwritten once a fortnight buys nothing over a 128GB card unless the retention policy actually asks for a fortnight.

What an endurance rating is actually made of

Cards are sold with an endurance figure in recording hours, and almost never with the number that produces it. Both describe the same physical limit — how many times a cell can be erased and rewritten — but only the second one can be compared between suppliers.

Cell typeErase cycles, typicalBytes written before wear-out, 128GBThat figure ÷ 43.2 GB per dayWhat shortens it in the field
Consumer TLC1,000–3,000128–384 TB8–24 yearsWrite amplification, heat, and the quality of the controller’s wear levelling
Endurance-tuned TLCsame silicon, different mappingsame ordersame orderLess of the above, but not none of it
pSLC (one bit per cell)20,000–30,0002,560–3,840 TB160 years and upCost per gigabyte, several times that of TLC

Erase-cycle ranges are the ones commonly published for these cell types; the byte figure is simple multiplication (capacity × cycles) and is an upper bound, not a service life.

The arithmetic is generous, and the field is not. A card in a 24/7 recorder never idles: garbage collection runs while new footage is still arriving, free space sits permanently in the last few percent, and the mapping table is rewritten continuously. Write amplification of three to ten times is normal for small-block loop recording, and it divides that years column by the same factor.

Temperature takes the rest. Erase-cycle ratings are quoted at 25°C. A camera housing in direct sun runs far above that, and both retention and write reliability fall as the die heats. It is why the same card can last years in a dashcam that runs an hour a day and a much shorter time in a camera that never stops — the card did not change, the duty cycle did.

We would rather tell you which of these two numbers we can document for a specific part than quote an endurance hours figure we cannot defend. If a project needs a documented endurance rating, say so at specification stage and we will tell you plainly whether it is available.

What to put in the purchase order

Most card disputes trace back to a specification that said “high endurance, 128GB” and nothing else. These are the fields that decide what actually arrives.

FieldWhat to writeWhy it moves the price or the risk
Capacity and usable figure“128GB printed, at least 119GiB reported by the host”Separates a card that is honest about decimal capacity from one that is not
Sustained writeThe MB/s held for the file size you actually write, not the burst numberA card can pass a short benchmark and still drop frames in hour 200
Endurance basisRecording hours at a stated bitrate, or TBW — whichever the supplier can documentThe only form that lets two suppliers be compared
Operating temperatureThe range the housing reaches in service, not the range of the roomParts specified beyond commercial range cost more, and pretending they do not is worse
Silicon grade and sourceNamed in writing, per batchGraded die and unscreened die differ materially in cost and in field failure rate
Batch verificationThe test method and the sample size accepted before packingThis is the line that prevents a cheap batch from becoming a truck roll
Packaging and MOQBulk tray or retail pack; 50 pieces minimum on standard cardsRetail packaging carries its own minimum and its own cost

None of these fields are technical decoration. Each one is a place where a supplier can save money quietly, and each one is cheap to specify in writing before the order rather than after the first failure.

The failure that costs the most is a card that lies about its capacity

A card that reports 128GB and really holds 64GB does not fail politely. The recorder fills what it believes is free space, wraps into the area that already holds footage, and destroys the oldest recordings far sooner than the retention plan assumed — while continuing to display free space that does not exist.

The wear side is worse than the data side. Writes that should have been spread across 128GB are concentrated on 64GB, so the card reaches its write limit at roughly twice the rate. An installer who ordered that card for a three-year deployment gets something considerably shorter, and the failure presents as a random card death rather than as a capacity problem.

For a batch order the practical control is a sample test before packing, not a promise after delivery. The mechanism behind inflated capacity, and the three ways a card is made to lie, are set out in why fake-capacity cards keep getting made. The ten-minute test that catches it is in how to verify a card really holds its capacity.

Buyer checklist

  • Confirm your workload (bitrate, retention window, duty cycle) before specifying capacity
  • Match the speed class to the actual workload, not a marketing number
  • Ask for the silicon source and grade in writing before you commit
  • Request a physical sample and approve it before bulk production
  • Confirm MOQ, lead time and Incoterms in the written quotation

Products for this application

Related reading

Sources

Tell us your workload, target capacity and the date you need material — and, if you have it, your bitrate or retention requirement. We will come back with a specification and a schedule rather than a generic price list.

Or email cathy@go-wintel.com — answered by Cathy, sales engineer.

Frequently asked questions

Should I use a removable card or soldered storage?

If the recording medium needs to be swapped by an operator, use a TF card. If it must not be removed — or the unit is sealed and remote — use a UDP module soldered onto the board. See our UDP vs PCB vs COB comparison.

Can you supply parts specified for high temperatures?

Tell us the operating temperature range your product must meet. We will tell you honestly whether the part we can supply is specified for that range, rather than implying an industrial rating we cannot document.

How many write cycles can I expect?

That depends on the die, the controller and the workload. We will share what we can support for your specific configuration; where we cannot give a documented endurance figure, we will say so.

How many days of recording will a 128GB card hold in a security camera?

About 2.8 days on a 4 Mbps 1080p stream, and about 5.5 days at 2 Mbps with H.265. The arithmetic is bitrate × 10.8 to get gigabytes per day, divided into usable capacity — roughly 119GiB on a 128GB card. At 8 MP and 12 Mbps the same card holds under a day, which is why capacity has to be chosen from the camera setting rather than from the label.

Do you sell wholesale to security installers?

Yes, direct from our Shenzhen production line rather than through a distributor. The minimum is 50 pieces on standard card builds, and custom printing or retail packaging carries its own minimum. For multi-site installers we will test a sample from the batch for real capacity before packing, so a mixed or mislabelled lot is caught before it reaches a site that is expensive to revisit.

Do you support long-term supply for a product already in the field?

Long-term availability is a real risk in flash because suppliers discontinue NAND packages on their own schedule. Tell us your expected production life and we will discuss how to plan for it.

WhatsApp / WeChat Request a quote