If your organisation still treats every retired drive the same way, solid-state storage is the gap in the process. The tools and habits built around spinning disks don’t transfer cleanly, and that mismatch is the reason ssd destruction services exist as a distinct line item rather than a footnote under general data sanitisation. The difference is architectural, not procedural.
A spinning disk obeys you. Flash memory negotiates
On a mechanical hard drive, a logical block address maps to a physical spot on a platter. Tell the drive to overwrite block 40,000 and the head goes to that spot and overwrites it. Do it a few times with random patterns and the old magnetic state is gone.
Flash doesn’t work like that. NAND cells wear out after a finite number of write cycles, so every SSD ships with a controller running a wear-levelling algorithm. That controller decides where data physically lands, and it moves things around constantly to spread the wear.
When you overwrite a file, the controller typically writes the new data to a fresh block and marks the old one invalid. Your original data is still sitting there, physically intact, waiting for garbage collection to get around to it.
The capacity you can’t address
Every SSD also ships with over-provisioned capacity — spare blocks held in reserve for wear levelling and to replace cells that fail. A drive sold as 512 GB might carry 550 GB of actual NAND.
Your operating system cannot see or address that reserve. Neither can most overwrite utilities. Blocks retired from active service can still hold readable fragments, and a lab with the right equipment can read the NAND packages directly, bypassing the controller entirely.
What this means for multi-pass overwriting
Multi-pass overwrite standards written for magnetic media don’t just fail to help on flash — they actively burn write endurance while providing a false sense of completion. Running seven passes on an SSD wears the drive and still leaves the reserve untouched.
Where each method actually fits
Cryptographic erase works well when the drive supports it properly. If the SSD encrypted everything at rest from day one, destroying the key renders all cells unreadable at once. The catch is verification — you’re trusting the firmware’s implementation, and firmware implementations have been found wanting before.
Firmware sanitise commands are the manufacturer’s own block-erase routine, and they do reach the reserve. They’re the right answer for drives being redeployed internally.
Physical destruction removes the trust question entirely. For anything holding regulated data, that certainty is usually the deciding factor.
Why SSD destruction services shred flash differently
An industrial shredder built for hard drives will happily chew an SSD, but the shred size matters far more than it does with platters. A magnetic platter fragment is useless once it’s cut. A NAND package fragment can still hold recoverable data if the die survives intact.
That’s the technical reason to ask a provider a specific question: what particle size do you shred to, and does it guarantee the memory packages themselves are destroyed rather than just separated from the board? A vendor that can answer precisely is doing this properly. One that says “we shred everything” is not.
The documentation is the deliverable
The shredding takes seconds. The paperwork is what you’ll actually be asked for in an audit two years from now.
A serious provider issues a certificate of destruction listing individual serial numbers, captured at intake and matched against what was destroyed. Alongside that, expect a collection inventory with make, model, and serial for every unit, plus a date, location, and named technician for the destruction event itself.
That chain is what turns “we destroyed the drives” into something defensible. Without serial-level records, you have a claim. With them, you have evidence.
Choosing between on-site and off-site
Both models end in the same certificate. The difference is where the risk sits.
On-site means a mobile shredder comes to your loading dock and drives are destroyed before they leave your property. Off-site means transport under documented custody to a fixed facility, usually with an option to observe in person or by video.
Off-site handles volume more economically. On-site removes transit risk completely. Organisations under strict internal protocols sometimes go a step further and rent the unit so their own cleared staff run it.
Whichever route you take, the important thing is that ssd destruction services are chosen because someone understood what flash memory does with deleted data — not because a spinning-disk process got applied to a technology it was never designed for.
