TBW or DWPD — which one should I look at?

They are the same fact. DWPD frames endurance as a daily workload (common for enterprise drives); TBW frames it as a lifetime total. Convert between them with TBW = DWPD × capacity(TB) × 365 × warranty(years). Use whichever matches how you think about the load, but always convert before comparing two drives.

How do I size an SSD''s endurance for my workload?

Estimate the data you write per day (GB/day), then the TBW you need is GB/day × 365 × warranty years ÷ 1000 (in TB). Pick a drive whose rated TBW comfortably exceeds that, and add margin because real deployments amplify writes — RAID/mirroring, deduplication, filesystem metadata and garbage collection all write more to the NAND than your application asked for.

Is a higher DWPD always better?

No — only up to what your workload needs; endurance you never use is money spent for nothing. And two drives with the same DWPD can reach it very differently (higher-endurance NAND vs more over-provisioning vs better wear-levelling), so weigh TBW, warranty, power-loss protection and NAND type together, not DWPD alone.

TBW and DWPD — how to read SSD endurance (and size it for your workload)

Two SSDs sit on your desk. One datasheet says 600 TBW, the other says 1 DWPD. They look like different specs measured in different units — and that's the first trap. They're the same fact about the same thing, written two ways. Once you can move between them, picking the right drive stops being guesswork.

What each number means

TBW — terabytes written. The total data the drive is guaranteed to absorb over its life. A 1TB drive rated 600 TBW is designed to take 600 terabytes of writes before its endurance guarantee runs out [1].

DWPD — drive writes per day. How many times the drive's full capacity you can write every day across the warranty period. Common on enterprise drives because it frames endurance as a daily workload [1].

The only real difference: DWPD depends on the drive's capacity and warranty; TBW doesn't. That's why comparing DWPD across drives of different size or warranty, without converting, is meaningless.

The conversion (and why it's exact)

One formula ties them together [1]:

TBW = DWPD × capacity (TB) × 365 × warranty (years)

Rearranged: DWPD = TBW(TB) × 1000 ÷ (capacity(GB) × 365 × years). A few worked rows:

Drive	Warranty	Stated rating	The other metric
1 TB	5 yr	1 DWPD	= 1,825 TBW
1 TB	5 yr	500 TBW	≈ 0.27 DWPD
7.68 TB	5 yr	14,016 TBW	= 1 DWPD
480 GB	5 yr	3 DWPD	≈ 2,628 TBW

The 500 TBW consumer drive and the 1 DWPD enterprise drive aren't in different worlds — they're ~0.27 vs 1.0 daily writes, a roughly 4× endurance gap, stated in different units.

Where the number actually comes from

A TBW figure isn't picked by marketing. It falls out of the NAND, by the same relation behind microSD endurance:

TBW ≈ capacity × P/E cycles ÷ write amplification (WAF)

Capacity and the NAND's program/erase budget set the raw ceiling; write amplification pulls it back down. WAF is the data the drive actually writes to flash divided by the data the host asked it to write — and it's always ≥ 1, because garbage collection, wear-levelling and metadata make the drive write more than you sent [3]. Better controllers and more over-provisioning push WAF toward 1; that's part of why two drives with the same NAND can carry different TBW.

What JEDEC standardizes

So the ratings are comparable, endurance is measured to a standard, not a house rule. JEDEC JESD218 defines what TBW means and the reliability test method; JESD219 defines the endurance workloads used to get there [2]. JESD218 also fixes related reliability limits such as UBER (uncorrectable bit error rate). When a datasheet says "TBW," it's anchored to that standard — which is exactly why you can trust the conversion above.

Consumer vs enterprise, in DWPD

Endurance need is set by the workload, and the gap is large:

Client / consumer: typically well under ~0.3 DWPD. A 1TB consumer SSD at 500 TBW over 5 years works out to ~0.27 DWPD — fine for a workstation, light for a write-heavy server [1].
Enterprise / write-intensive: 1 DWPD for mixed/read-leaning use, 3 DWPD and up for write-heavy data-centre and logging workloads.

The caveat that catches people

Your application's writes are not the drive's writes. In a real deployment, write amplification stacks: three-way mirroring writes everything three times to three drives; deduplication, RAID repair and filesystem journals all add IO the application never issued [3]. So size endurance against the amplified write volume, with margin — not against the clean number your app reports.

How to pick, in order

Estimate GB/day for the workload (measure it if you can).
Required TBW = GB/day × 365 × warranty years ÷ 1000 (TB). That's your floor.
Pick a drive whose rated TBW clears it with margin — then sanity-check the DWPD makes sense for the size.
Then weigh the rest: power-loss protection for unattended/industrial use, NAND type, and a locked BOM so the drive you qualified keeps shipping.

Bottom line

TBW and DWPD are one number wearing two outfits; convert, then compare. Size against your real, amplified write volume with headroom, confirm the figure is JEDEC-anchored, and don't pay for endurance the workload will never touch. For industrial and embedded buyers we publish the rated TBW/DWPD, power-loss protection and NAND type per part — tell us your GB/day and warranty horizon and we'll point you at the drive that clears it.