Flash Memory for Dashcams and Vehicle DVRs
A dashcam writes continuously and overwrites the oldest footage in a loop, which is the hardest workload you can give a flash card. What matters is not peak speed but sustained write behaviour, stable capacity and batch-to-batch consistency — the same card in unit 1 and unit 5,000. WINTEL supplies MicroSD-class TF cards from 4GB to 256GB with read and write speed specified per project, so the speed class is matched to your recording bitrate and retention window rather than assumed. If you build dashcams, vehicle DVRs or fleet camera systems, send us your recording bitrate, retention requirement and target capacity, and we will quote the matching configuration.
What this buyer actually cares about
Sustained write, not headline speed
Continuous recording leaves no idle time for the card to recover. A card that benchmarks well on a burst test can still drop frames under a 24/7 write loop. The relevant question is what happens in hour 200, not in the first ten minutes.
Capacity against the retention window
Buyers often over-specify capacity because the relationship between bitrate, recording hours and usable capacity is unclear. Getting this right is a cost decision, not just a technical one.
Consistency across the production batch
When a card is a component inside your product, your warranty exposure is your customer’s experience. Mixed silicon sources inside one batch create failures you cannot explain.
Knowing which silicon you are paying for
Fake and misrepresented capacity is a well-documented problem across the whole flash market. Component buyers need to know the actual grade and source, not a marketing label.
What we do about it
- Specify read and write speed per project so it matches your recording bitrate
- Quote capacities from 4GB to 256GB against your retention window
- Source silicon from named suppliers — SanDisk, Toshiba, Micron, SK Hynix, Intel, Samsung
- Match the controller solution to your host rather than reusing whatever is on the line
- Confirm capacity and read/write performance before packing
Products for this application
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.
Send your requirementFrequently asked questions
What capacity do I need for a given recording window?
It depends on your bitrate and how many hours you want to retain. As a working reference, 1080p video runs roughly 1.5GB per hour, so a 64GB card holds in the region of 40 hours of footage before loop-overwrite begins. Confirm your own bitrate first, then size the card.
Can you supply cards with a specified speed class?
Yes. Read and write speed is a per-project specification. Tell us your required speed class and the workload, and we will match the silicon and controller solution to it.
How do I verify the capacity of cards I receive?
Test them yourself rather than trusting the label. H2testw is the standard tool: it writes and reads back a full set of test files and reports the real usable capacity. Our guide walks through the method.
Do you supply cards for fleet or multi-unit deployments?
Yes. The main requirement for multi-unit deployments is batch consistency, so let us know the deployment size and we will explain how the batch is sourced and checked.