Does Degaussing Work on SSD and NVMe Drives?
By Ali Hassan, Editor, MAH Recycling
No. Degaussing does not work on SSDs or NVMe drives, because they hold data as electrical charge in flash chips, not as magnetic patterns on a platter. A degausser aims a strong magnetic field at memory that does not store anything magnetically, so the data can survive.
For a data centre team retiring mixed hardware, the useful question is what to do instead. Use the drive’s own purge commands, and choose a destruction method that suits flash when the drive has to be destroyed.
Why a magnetic field misses flash memory
A hard drive records bits as magnetic orientation on spinning platters. A strong degausser scrambles that pattern, and it often disrupts the servo tracks too, which is why the drive stops working. NAND flash is different: Phiston’s guide to destroying SSDs points out that these drives store data in flash chips rather than magnetic media.
NIST’s own Revision 2 FAQ is blunt about it. Degaussing can fail to sanitize flash or hybrid components, and even for legacy magnetic drives it counts as a physical purge technique, not a true destroy method.
SSD vs HDD data destruction at a glance
| HDD | SSD / NVMe | |
|---|---|---|
| How data is stored | Magnetic platters | NAND flash chips |
| Degaussing | Valid purge technique, with a field matched to the media | Can fail to sanitize the data |
| Clear (overwrite) | Single pass is enough | Reaches addressable space only; extra passes wear flash |
| Purge | Degaussing, device sanitize commands | Sanitize commands, block erase, cryptographic erase |
| Destroy | Shredding only for the lowest data categories | Same caution; melting or incineration for higher categories |
How flash media should be treated
Start with the fact that a wipe may not reach everything. NIST prefers sanitizing the entire device because of overprovisioning and bad-block remapping, which can leave data in places a normal overwrite never touches. Multi-pass overwriting adds nothing on modern drives and can shorten the life of flash.
So for SSDs that leave your control, aim for Purge. That means device-level sanitize or format commands, block erase, or cryptographic erase. Cryptographic erase is fast, but NIST sets conditions: no sensitive data stored in plaintext before the keys existed, an algorithm of at least 128-bit strength (AES, for example), and keys that you zeroize properly. If a drive held plaintext before encryption was switched on, cryptographic erase alone does not qualify.
Verification matters as much as the command. NIST separates verification, which checks the technique finished without errors, from validation, where your organization decides whether the result fits the data’s sensitivity. Keep a per-device record of both.
When the drive has to be destroyed
This is where the usual advice needs care. Revision 2 tells readers to avoid pulverizing and shredding for anything but the lowest security categories, because modern media packs data densely. For SSDs and other non-magnetic media holding higher-category data, NIST points to incineration, such as melting or smelting.
The FAQ adds that IEEE 2883 lists melting as a destruct method and deprecates shredding and pulverizing for modern HDDs and SSDs. Our reading: fine shredding can still be a legitimate answer for low-sensitivity flash under your policy. For high-classification drives, purge first, then ask your provider about melting.
MAH Recycling’s on-site HDD shredding page covers hard disks. For SSDs, we settle the method with you in the project scope before any work begins.
Sort your fleet by media type and data class before the next refresh, then send the list through our data destruction services page for a written scope.
