The advice that works for a traditional hard drive can leave a solid-state drive full of recoverable data. SSDs store information in a fundamentally different way, so overwriting and degaussing, the old reliable methods, do not do the job. This guide explains why hard-drive techniques fail on flash, what actually destroys SSD data, and how to be sure it is gone.
You destroy SSD data reliably in one of two ways: a verified cryptographic erase or firmware sanitise command designed for the drive, or physical destruction that shreds the flash memory chips to a small particle size. What you do not rely on is overwriting the drive or degaussing it, because neither works properly on solid-state media. An SSD stores data on NAND flash chips and uses wear-levelling and spare capacity to spread writes around, so a simple overwrite cannot guarantee that every location holding data is actually reached. Degaussing, which erases magnetic drives with a strong magnetic field, does nothing at all to flash memory, which is not magnetic. So the correct approach is a method built for flash, applied to a recognised standard such as NIST 800-88, with a certificate to confirm it. That is what SSD destruction is built to deliver.
This matters because most business machines bought in the last several years use SSDs, not spinning hard drives. Laptops, modern servers and workstations increasingly rely on flash storage, so disposal advice written for the hard-drive era is not just outdated, it is a live risk. A business that wipes its SSDs the way it used to wipe its hard drives may believe the data is gone when it is not. This guide explains the why and the how so that does not happen.
The reason the old methods fail comes down to how flash memory physically stores and manages data.
A hard drive writes to fixed magnetic locations. An SSD spreads data across flash cells and hides spare capacity, which is exactly why overwriting and degaussing cannot be trusted on it.
Illustrative. On an SSD, the controller moves data across cells and reserves spare capacity you cannot directly address, so an overwrite may never touch cells that still hold data.
A traditional hard drive records data magnetically at fixed physical locations, so overwriting those locations, or erasing the whole platter with a degausser, reliably destroys the data. An SSD works nothing like this. It stores data in NAND flash cells, and its controller constantly moves data around to spread wear evenly across the cells, a process called wear-levelling. It also keeps a pool of spare capacity, known as over-provisioning, that the operating system cannot see or address directly. The practical consequence is twofold: a software overwrite issued to the visible drive may never reach cells that still hold old data in that hidden pool, and degaussing, which relies on magnetism, has no effect on flash because flash is not magnetic. The methods that gave hard drives a clean, verifiable erasure simply do not map onto how an SSD works.
There is a further wrinkle that trips people up. SSDs use a feature called TRIM, which tells the drive which blocks are no longer in use so it can manage them efficiently, and this can create the impression that deleted data is gone when the reality is more complicated and drive-dependent. Combined with over-provisioning and the controller's internal management, it means you cannot reason about an SSD the way you can about a hard drive, where a given sector either was or was not overwritten. The dependable position is to use a sanitise method the drive itself supports, verified, or to destroy the flash physically. Anything that assumes the operating system has full, direct control over where data sits on the drive is making an assumption that flash storage does not honour.
Line the methods up against solid-state media and the picture is clear.
| Method | Works on an SSD? | Why |
|---|---|---|
| Overwriting (multi-pass software wipe) | Not reliably | Wear-levelling and spare capacity mean the wipe may never reach all cells holding data |
| Degaussing | No | Flash memory is not magnetic; a magnetic field does nothing to it |
| Factory reset | No | Leaves data recoverable, on an SSD as on any drive |
| Cryptographic erase / firmware sanitise | Yes, when verified | Destroys the encryption key or issues the drive's own sanitise command, rendering data unreadable; must be verified |
| Physical destruction (shredding to small particles) | Yes | Destroys the flash chips themselves; particle size must be small because SSD chips are tiny |
Two things stand out. First, every method that was safe for a hard drive, overwriting and degaussing, is unreliable or useless on an SSD, which is the trap. Second, physical destruction has a twist for SSDs: because the flash chips are small, the drive has to be shredded to a smaller particle size than a hard drive to be sure every chip is destroyed. A shredder set up for hard-drive platters can leave SSD chips intact and potentially readable, so the equipment and the particle size matter. The safe methods are a verified cryptographic or firmware sanitise for drives that will be reused, and shredding to an appropriate particle size for drives that will not.
Whether you plan to reuse the drive or retire it decides which of the two correct methods applies.
Modern SSDs support built-in commands that either destroy the internal encryption key or sanitise the flash directly, rendering the data unreadable while leaving the drive usable. Done to the NIST 800-88 Purge level and verified, this allows a working SSD to be securely wiped and its value recovered, rather than destroyed.
Where a drive will not be reused, cannot be verifiably sanitised, or held the most sensitive data, the flash chips are physically destroyed by shredding to a particle size small enough to destroy the chips themselves, not just the casing. This is the NIST 800-88 Destroy level.
Both routes are only complete with confirmation: a verification that the sanitise succeeded, or a record of destruction, and a certificate for each drive. Without that, you have a method but no proof, which for a business is not enough.
Shredding every SSD is secure but wasteful, because a working, verifiably sanitised SSD retains resale value that shredding destroys. A good process matches the method to the drive: verified sanitise for reusable drives so their value can be recovered through buyback, and physical destruction for the rest. The point is not to destroy everything, but to destroy the data on everything, and recover what you can.
Each of these looks like a completed disposal and leaves data behind. They are easy to make precisely because the drive shows no sign anything went wrong.
The single worst mistake. A degausser erases magnetic hard drives, but flash is not magnetic, so the SSD comes out looking processed with its data completely intact. Anyone treating SSDs and hard drives the same way on a degausser is producing a false result.
Running an old multi-pass wipe utility against an SSD. It reports success, but wear-levelling and spare capacity mean it may never have reached every cell. The tool was built for a different technology.
Feeding SSDs through a shredder set for hard-drive platters. The larger particle size can leave intact flash chips in the output, and an intact chip is potentially readable. SSDs need a smaller particle size.
Flash storage is not only in obvious drives. It is soldered into laptops, sits as NVMe modules in modern servers, and is embedded in some appliances and devices. A disposal that only pulls the recognisable drives can miss data-bearing flash entirely.
Assuming a method worked without confirming it. On an SSD a failed method is invisible, so verification and a per-drive certificate are what turn a hopeful process into a proven one.
SSDs are now the default in business machines, so old hard-drive disposal habits quietly became a data-security gap.
The risk here is subtle precisely because it is invisible. A business that has always wiped or degaussed its drives, and always been fine, can carry that habit straight into the SSD era and never notice that the method stopped working. The drive looks wiped, the process feels the same, but the data may still be there in cells the overwrite never reached or chips the degausser never touched. Against a maximum privacy penalty of $50M or more, and the reputational cost of a breach, the fix is simple and worth insisting on: confirm the destruction method is designed for flash, and get a certificate that says so. If your disposal provider cannot explain how they handle SSDs differently from hard drives, that is the question to press.
The questions people ask most about securely destroying data on solid-state drives.
Not reliably. A multi-pass overwrite was designed for hard drives, where data sits at fixed locations. An SSD uses wear-levelling and reserves spare capacity the operating system cannot address, so an overwrite issued to the visible drive may never reach cells that still hold data. The reliable software route for an SSD is a verified cryptographic erase or the drive's own firmware sanitise command, not a traditional overwrite.
No. Degaussing erases magnetic hard drives by applying a strong magnetic field. Solid-state drives store data in flash memory, which is not magnetic, so a degausser has no effect on the data at all. Using a degausser on an SSD is one of the most common and dangerous mistakes, because the drive comes out looking processed but with its data fully intact.
The principle is the same but the particle size is not. SSD flash chips are small, so an SSD must be shredded to a smaller particle size than a hard drive to be sure every chip is destroyed. A shredder configured for hard-drive platters can leave SSD chips intact and potentially readable, so both the equipment and the particle size matter for solid-state media.
Many SSDs encrypt data internally as it is written. A cryptographic erase destroys the encryption key, which renders all the data on the drive unreadable, because without the key the stored content is meaningless. Done to a recognised standard and verified, it is a fast and reliable way to sanitise a working SSD for reuse, and it is one of the methods NIST 800-88 recognises for flash media.
It depends on whether the drive will be reused. A working SSD that can be verifiably sanitised can be securely wiped and its value recovered, which avoids waste. A drive that will not be reused, cannot be reliably sanitised, or held the most sensitive data is physically destroyed. Matching the method to the drive protects the data on all of them while recovering value where it exists.
Through verification and a certificate. A sanitise is verified to confirm it succeeded, or the physical destruction is recorded, and a certificate is issued for each drive stating what was done. That documentation is what lets a business demonstrate the data was destroyed, which matters far more on SSDs precisely because a failed method leaves no visible sign that anything went wrong.
See how ITC destroys data on solid-state drives with a method matched to flash, verified sanitise for reuse or shredding to the right particle size, and a certificate for every drive so you can prove it is gone.
Destroy it properly
Knowing the right method is only half of it. The other half is being able to prove what happened to each serial number. ITC works to the NIST 800-88 standard under ISO/IEC 27001:2022, records chain of custody from your desk to the shredder, and issues a Certificate of Data Destruction listing the devices processed.
