How long will flash memory actually last in my product, and how do I estimate it?
Estimate by write volume, not by calendar time. Flash wears out from erasing and rewriting cells, so a drive that is written once and read many times can last many years, while one rewritten continuously can wear out in months. Calculate your bytes written per day, multiply by the product's service life, and compare against the endurance the controller and memory grade can deliver. Two things matter more than the raw number: whether the controller does wear levelling, and whether power can be lost mid-write.
The estimate, in three steps
The arithmetic is simple; the inputs are where buyers go wrong.
- Bytes written per day: records per hour × size per record × 24. Use peak, not average.
- Total bytes over life: daily write volume × expected service years.
- Compare against endurance: total bytes written versus what the memory grade and wear levelling can sustain, with a safety factor.
Worked example (illustrative)
A logger writes 1MB per minute continuously. That is 60MB an hour, 1.44GB a day, about 525GB a year. Over a five-year service life the total is roughly 2.6TB written.
Whether that is comfortable or marginal depends entirely on the memory grade and how the controller distributes the writes — which is why the question "how long will it last" cannot be answered without knowing the workload. The same device writing 1MB a day instead of a minute would be a completely different problem.
The point of the number is not to predict a date. It is to make the workload explicit so the grade can be chosen against it.
The two factors that decide more than the arithmetic
**Wear levelling.** Flash cells have a finite number of erase cycles. A controller that spreads writes across the whole memory uses each cell far less often than one that keeps rewriting the same area. Without wear levelling, a small region dies early and takes the product with it, regardless of how much total endurance the memory theoretically had.
**Power loss during a write.** Losing power mid-write can corrupt not just the file being written but the file system structures that map the drive. A device that is unplugged, browns out, or has a failing battery will eventually lose power at the worst moment. Handling this is a controller and file system design question, not a memory quality question — and it is often invisible in a datasheet.
When data retention matters more than endurance
A drive written once and stored is a different problem. Flash retains data without power for years, but retention is affected by temperature and by how much the cells have been worn — a heavily written cell holds data for less time than a fresh one.
For archival use the question is not "how many writes" but "how long without power, at what temperature", which is a different specification to ask for. Products that sit on a shelf for years before first use fall into this category.
Sources
- JEDEC — flash memory endurance and reliability standards
- SD Association — card reliability and power-fail behaviour
Figures quoted on this page are from the published reporting listed above. Where a number is an estimate rather than a published figure, it is described as approximate.
Frequently asked questions
Can I trust the endurance figure in a datasheet?
Treat it as a design target measured under stated conditions, not a guarantee for your workload. Endurance figures usually assume a particular write pattern, temperature and error-correction scheme. Your application may be harsher or gentler. It is more useful to state your workload to the supplier and ask what grade suits it than to compare datasheet numbers between products.
Does a bigger capacity last longer for the same workload?
Usually yes, for the same total bytes written, because the writes are spread across more cells, so each cell is erased less often. This is one of the few legitimate reasons to specify more capacity than the data requires — but it should be a deliberate endurance decision, not an accidental one made by buying the next size up.
What happens when flash wears out?
It does not fail all at once. Cells degrade, error correction works harder, and the controller eventually marks blocks bad and remaps them. A well-designed product shows the effect as reduced usable capacity and slower writes long before outright failure. A product with no bad-block handling and no wear levelling tends to fail suddenly instead, which is the dangerous pattern for field deployment.
Working on a specification?
Send us the product type, capacity, quantity and target date. We reply to business enquiries within 1 business day.
Request a quote