How to Securely Erase an SSD Before Selling: NVMe Sanitize, Secure Erase and TRIM Explained

The point is sound. The documentation from Microsoft, NIST and NVM Express explains why, and it also shows where people tend to overstate the risk.

Why the old overwrite trick doesn't carry over​

On a hard drive, the operating system could more or less write over the same physical sector and be done. SSDs don't work that way. As White explains, they use a flash translation layer, wear leveling, garbage collection and spare capacity, so the controller keeps moving data around the NAND. When Windows "overwrites" a file, the controller may put the new data in a different physical location and leave the old cells alone for the moment.

Microsoft's own developer documentation describes the same behavior. Its page on the TRIM and Unmap API says SSDs are block-erased flash devices. Data written to them can't be overwritten in place and has to go somewhere else until the old block is garbage-collected. The same page adds a detail that matters for privacy. When you delete a file, NTFS records the change in the master file table. It doesn't touch every sector the file occupied, so the SSD keeps those sectors until it learns they're no longer needed.

That's why the old "overwrite it a few times" advice is unreliable on flash. Microsoft's documentation for the format command includes a /P:<count> switch. It writes zeros to every sector of the volume and then overwrites the volume the specified number of times with random data. The same page notes that /Q (quick format) overrides /P. A quick format only deletes the file table and root directory of a previously formatted volume.

Even a full /P pass works on the logical sectors Windows can address. It can't reach spare or remapped NAND that the controller keeps outside that view, so the number of passes doesn't prove the physical cells were cleaned.

Section summary:

• A quick format removes file-system structures, not the data itself.
• Overwrites from Windows are applied to logical sectors, and the controller decides where they physically land.
• Remapped and overprovisioned areas can sit outside the operating system's reach.

Kingston, which makes SSDs, says the same in plain terms. Its guide on erasing drives before sale notes that a quick format only clears the file allocation table, meaning the underlying data is still present on the disk. It adds that recovery tools, even free ones, can often restore files after a format, making this unsafe for resale or disposal.

TRIM helps, but it's only a request​

This is where White pulls back a little from the alarming headline. Leftover NAND cells won't necessarily hold your files forever. TRIM lets Windows tell the drive which logical blocks it no longer needs. The controller can then clear them during garbage collection, which makes recovery much harder. This is a big reason why recovering deleted data is generally more difficult on an SSD than on a hard drive.

Microsoft's documentation explains why you still shouldn't rely on it for privacy:

• Windows 7 introduced a standard way to tell SSDs which sectors are no longer needed. NTFS sends TRIM during ordinary operations such as file deletion.
• Microsoft calls TRIM and Unmap hints to the storage media. The File TRIM API doesn't wait for a response from the device, because no return code is expected.
• The format command has a /NoTrim switch that skips the delete notification during a format. Formatting and TRIM are therefore separate actions, and TRIM can be turned off.

Put simply, Windows sends the request and moves on. It doesn't check whether or when the controller physically erased the cells. White concludes that TRIM helps performance but doesn't guarantee privacy, and Microsoft's description of TRIM as a hint backs her up.

Section summary: TRIM makes recovery less likely over time. It is not a confirmed erase.

The better answer is the drive's own erase command​

White recommends having the SSD wipe itself. Secure Erase, Sanitize and cryptographic erase all run below the file system. Instead of Windows writing to logical blocks and hoping the controller follows through, these commands tell the controller to clear the user data it manages internally.

The details depend on the interface, and people often mix them up. Kingston's guide explains that NVMe drives need a different approach to secure erase than SATA SSDs because they use a different command set. While SATA relies on ATA Secure Erase, NVMe drives use built-in commands like NVMe Format and NVMe Sanitize.

For NVMe, NVM Express, the group behind the specification, says there are multiple commands in the NVMe specification to securely erase user data. The NVMe format command includes support for crypto erase to quickly erase user data by switching the crypto key, as well as full media erase which today physically erases the NAND. Sanitize goes further. It has the same capabilities as format, while also removing Metadata, information from the queues, and guarantees completion by automatically starting after a device reset.

NVM Express's guide to its NVMe-CLI tool adds more context:

Note the first row. An NVMe Format with no secure-erase setting is basically a large TRIM. The word "format" doesn't guarantee much on its own, even at the NVMe command level.

Cryptographic erase is fast, but it depends on how the drive handles encryption and keys. It isn't a feature every SSD implements the same way. NVM Express also stresses checking which sanitize actions a controller reports before you choose one. Block erase, crypto erase and overwrite are each optional.

Section summary: Use a device-level command that your specific drive supports, and use Sanitize where it's available.

A practical checklist for Windows users​

The drive's firmware does the actual erasing. Your job is to send the right command, confirm it finished, and avoid erasing the wrong disk.

1. Back up first. Each of these operations is designed to make data unrecoverable. White, who regularly recommends the 3-2-1 backup rule, would point out that losing files by accident is easy.
2. Identify the drive and its interface. Check whether it's SATA or NVMe, and note the make and model. Device Manager or the manufacturer's utility will show this. The interface determines which commands apply.
3. Start with the manufacturer's tool. White cites tools such as Samsung Magician. Kingston says its secure erase tool works by issuing the ATA Secure Erase command directly to the SSD's controller, which instructs the drive to internally wipe all user-accessible data areas. Supported options vary by model, so follow your vendor's documentation rather than a generic guide.
4. Check your motherboard firmware. White notes that some motherboards include an NVMe Secure Erase option in the BIOS/UEFI. Whether yours has one depends on the board.
5. Don't try to wipe the system drive from inside Windows. Usually you can't. That's why the BIOS option or the vendor's bootable tools exist.
6. Confirm it finished. NVM Express's material shows Sanitize reporting progress and completion through a log page. Don't assume the job is done just because you started it.
7. For advanced users only: NVM Express documents Linux nvme-cli commands for checking sanitize capabilities and running Sanitize. Those are Linux procedures, not Windows ones. Selecting the wrong device will wipe it immediately.

How far you need to go depends on the data​

White doesn't overstate the risk. She acknowledges that a random Facebook Marketplace buyer is very unlikely to have the skills or the interest to dig up your old files, and she leaves the decision to the reader. Her own approach is cautious: she keeps most old drives, and when she does sell one, she goes to considerable lengths to make sure it's clean.

NIST's standards take the same risk-based approach. Its current guidance is SP 800-88 Rev. 2, Guidelines for Media Sanitization, published in September 2025. It supersedes Rev. 1 from December 2014. NIST defines sanitization as making access to target data infeasible for a given level of effort, and it ties the choice of method to how sensitive the information is. Some vendor guides still cite Rev. 1. One wiping-software maker invokes NIST SP 800-88 Rev. 1 guidelines, for example. IT teams that write disposal policies should make sure they're referencing the current revision.

The "level of effort" wording means "100% clean" isn't something you can claim in the abstract. What you can say is that the drive was sanitized with a particular method against a particular threat, and that completion was confirmed. For a gaming SSD full of dog photos, a successful vendor Secure Erase is more than enough. For a laptop drive that held client records, follow your organization's sanitization policy and keep a record of what was done.

Bottom line​

The headline might suggest your SSD is secretly keeping your old files. The accurate version is less dramatic but still worth acting on:

• Delete changes file-system records.
• TRIM asks the drive to discard logical blocks, and Windows doesn't wait for confirmation.
• Format builds a new file system, and a quick format doesn't touch the old data.
• Sanitize, Secure Erase or crypto erase is when the drive itself clears the data.

Only the last of these is meant to destroy data. Older advice may still tell you to run several overwrite passes. On an SSD, a single erase command from the drive's own firmware is the more reliable method.