HDD vs SSD Destruction
HDD vs SSD Destruction: Why Solid-State Drives Need a Different Approach
For years, “wiping a hard drive” meant one thing: overwriting it repeatedly until the original data was gone beyond recovery. That approach worked reliably on traditional hard disk drives — but it doesn’t work the same way on solid-state drives, and a growing number of UK businesses are unknowingly leaving data recoverable on retired SSDs because they’ve applied HDD-era thinking to newer flash technology.
As SSDs increasingly replace HDDs across laptops, desktops, and even enterprise storage, understanding this difference isn’t optional anymore. Here’s what actually changes, and what your business needs to do about it.
How HDDs Store and Erase Data
Traditional hard disk drives store data magnetically on spinning platters. Because of how this magnetic storage works, overwriting a sector with new data physically replaces what was there before. Repeat that process across the entire drive, and recovery becomes practically impossible. This is why standard secure-wiping utilities that perform a full-disk overwrite have remained a reliable, well-understood method for HDDs for decades, and why physical destruction methods like degaussing — which scrambles the magnetic platters using a powerful magnetic field — are also effective against them.
Why SSDs Behave Completely Differently
Solid-state drives don’t use magnetic platters at all. They store data in NAND flash memory, organised into pages grouped within blocks. Critically, individual pages can’t simply be overwritten in place the way a magnetic sector can. When new data is written to an SSD, the drive typically writes it to a new, blank page and marks the old page as invalid rather than erasing it immediately.
This behaviour is compounded by two other SSD-specific technologies:
Wear levelling spreads write operations evenly across the drive’s memory cells to extend the SSD’s lifespan. This means data can be scattered across multiple physical locations in ways that don’t map cleanly to what a standard overwrite command can reach.
Over-provisioning reserves a portion of the drive’s total capacity that isn’t directly addressable by the operating system, used to support the drive’s internal write management. Data can end up sitting in this reserved space, completely invisible to standard wiping software.
The practical result: running a traditional HDD-style overwrite on an SSD can leave data fragments recoverable in areas the software never actually touched, while also causing unnecessary wear to the flash memory for no security benefit.
Common SSD Wiping Mistakes
Assuming a quick format is enough. A quick format only clears the file allocation table — the drive’s internal index of where files are stored. The underlying data itself remains fully intact and recoverable with widely available recovery tools.
Deleting a partition. This makes a drive appear empty, but again, does nothing to the actual data stored in the flash memory cells.
Applying a standard HDD overwrite tool. As explained above, this is neither fully secure nor efficient on an SSD, due to wear levelling and over-provisioning.
Assuming degaussing works on SSDs. Degaussing relies on magnetic fields disrupting magnetic storage. SSDs have no magnetic components, so degaussing has no effect on flash memory whatsoever — a mistake that can leave a business believing a drive is sanitised when it isn’t.
What Actually Works for SSDs
Manufacturer Secure Erase Commands
Most SSDs support built-in secure erase commands — such as ATA Secure Erase for SATA drives or NVMe Format for NVMe drives — that instruct the drive’s own controller to reset all memory cells at the hardware level. Because this happens at the firmware level rather than through the operating system, it reaches areas a standard software overwrite cannot, including over-provisioned space.
Cryptographic Erasure
For self-encrypting drives, cryptographic erasure works by permanently destroying the encryption key rather than the data itself. Since the data was encrypted from the moment it was written, discarding the key renders it permanently unreadable almost instantly — a fast, wear-friendly method that avoids the need for repeated write cycles.
Physical Destruction
Where policy requires absolute certainty, or where a drive is faulty and can’t reliably complete a secure erase command, physical destruction remains the fallback. Shredding is effective for SSDs, but it needs to be thorough — flash memory chips are small, and a shredder set up for HDD platters may not reduce SSD components to a small enough particle size to guarantee the chips themselves are destroyed. This is worth confirming directly with your provider rather than assuming all shredding equipment handles both drive types equally.
Does This Affect Your Certificate of Destruction?
Yes, and it’s worth checking. A certificate of data destruction for an SSD should specify the method used — secure erase command, cryptographic erasure, or physical destruction — rather than a generic reference to “wiping,” since a generic HDD-style overwrite claim on an SSD certificate is a red flag that the provider may not understand the distinction covered in this guide.
What This Means for Mixed Fleets
Most UK businesses today are managing a mix of HDDs and SSDs across their IT estate — older desktops still running traditional hard drives alongside newer laptops and servers built around flash storage. This means a single blanket disposal process applied to an entire batch of retired equipment is rarely appropriate. Drives should be sorted by type before disposal, with the correct method applied to each, something covered in more detail in our guide on hard drive types you can sell in the UK and in choosing between data wiping and physical destruction more broadly.
Does the SSD vs HDD Distinction Affect Resale Value?
It can. SSDs that have been properly sanitised using the correct method retain their resale value in the same way HDDs do — condition, capacity, and interface all still matter. However, a drive that’s been through an ineffective wipe attempt and needs to be sent for physical destruction instead loses any resale value it might otherwise have carried, which is another practical reason to get the method right the first time.
Why This Is a Bigger Compliance Risk Than It Looks
The gap between HDD and SSD sanitisation isn’t just a technical curiosity — it’s a genuine UK GDPR exposure that many businesses don’t realise they have. A business that has consistently and correctly wiped its retired HDDs for years can develop a false sense of confidence that the same process is equally effective once its IT estate shifts towards SSD-based laptops and servers. Because an ineffective SSD wipe doesn’t produce any obvious sign of failure — the drive still appears empty to a casual check — the risk can sit undetected for a long time, only surfacing if a discarded drive is ever recovered and examined by someone with the right tools.
This is precisely the scenario UK GDPR’s accountability principle is designed to guard against: it’s not enough to believe your process worked, you need to be able to demonstrate it did. For SSDs specifically, that means insisting your provider can confirm which sanitisation method was used and why it’s appropriate for flash storage, not simply that “the drive was wiped.”
A Quick Reference
| HDD | SSD | |
|---|---|---|
| Storage method | Magnetic platters | NAND flash memory |
| Standard secure wipe | Full-disk overwrite | Not reliable alone |
| Recommended method | Overwrite or degaussing | Manufacturer secure erase or cryptographic erasure |
| Degaussing effective? | Yes | No |
| Physical destruction | Shredding or crushing | Thorough shredding required — chip size matters |
Final Thoughts
HDDs and SSDs may sit in the same drawer of retired equipment, but they need to be treated as fundamentally different problems when it comes to secure data destruction. Applying HDD-era wiping methods to SSDs can leave data recoverable while giving your business false confidence that it’s been handled. The right approach depends on the drive type, its condition, and your organisation’s risk tolerance — but getting that assessment right at the start avoids compliance gaps down the line.
If you have a mixed fleet of HDDs and SSDs to dispose of and want each handled with the correct method and full certification, find out how our collection process works or get a free quote.
Frequently Asked Questions
Can I use the same wiping software for HDDs and SSDs?
Not reliably. Standard overwrite software designed for HDDs doesn’t account for wear levelling and over-provisioning on SSDs, and can leave data recoverable even after the process completes.
Does degaussing work on SSDs?
No. Degaussing uses magnetic fields to disrupt magnetic storage, and SSDs have no magnetic components. Degaussing an SSD has no effect on the data stored on it.
Is physical destruction always necessary for SSDs?
No. Manufacturer secure erase commands or cryptographic erasure are effective and allow the drive to be reused or resold. Physical destruction is typically reserved for faulty drives or where policy mandates it regardless of method.
How can I tell if my old SSDs were wiped properly?
Check the certification you received when they were disposed of. It should specify the exact method used — secure erase command, cryptographic erasure, or physical destruction — rather than a generic reference to wiping.
Do SSDs lose value if they’ve been securely erased?
No. A properly sanitised SSD retains its resale value based on capacity, condition, and interface, in the same way a correctly wiped HDD does.