If you're about to sell, return, or recycle a laptop, the instinct is to delete your files, maybe run an overwrite tool, and call it done. On a spinning hard drive that instinct is basically correct. On a solid-state drive (SSD) — which is what's inside almost every laptop sold today — it isn't. You can securely erase an SSD, but not by overwriting files in place. Here's why, and what actually works.
Why file overwrites don't reliably erase an SSD
Overwriting a file writes new bytes over the old ones so the original content is physically replaced — that's real erasure, and it's exactly what an in-browser eraser tool does. The catch is what "in place" means on flash storage.
An SSD can't rewrite a single cell the way a magnetic platter can. To spread physical wear evenly and stay fast, SSD controllers use wear-leveling: when your OS "overwrites" a file, the controller frequently parks the new data in a different physical location and retires the old block instead of erasing it there. The filesystem reports success. The original bytes may still exist in a block the OS can no longer even address. We cover this mechanism — and the related myth that more overwrite passes helps — in more depth in does deleting a file actually erase it?
The upshot: a software overwrite on an SSD is a best-effort logical wipe. It defeats undelete and file-recovery tools, which is the level NIST calls "Clear." It cannot promise a lab with the right equipment won't recover a fragment from a retired block. For most everyday deletions, Clear is genuinely enough. For a drive that's about to leave your hands entirely, it usually isn't.
The reference standard: NIST SP 800-88
NIST Special Publication 800-88, "Guidelines for Media Sanitization," defines the escalating levels that matter here:
| Level | What it does | Defeats |
|---|---|---|
| Clear | Overwrite user-addressable storage with new data | Standard undelete / recovery software |
| Purge | Techniques that resist laboratory recovery — cryptographic erase, or the drive's own firmware sanitize command | Forensic recovery |
| Destroy | Physical destruction of the media | Everything |
A whole SSD you're decommissioning calls for Purge, not Clear. NIST 800-88 lists two practical ways to get there on flash media:
- Cryptographic erase — if the drive (or a volume on it) was encrypted, destroying the encryption key instantly makes every block unreadable, no matter which physical location the controller actually wrote to. This is the fastest and most broadly applicable Purge method for SSDs, provided encryption was on from the start.
- The drive's own sanitize / secure-erase command — issued directly to the controller (ATA Secure Erase for SATA drives, NVMe Sanitize for NVMe drives). The firmware erases the flash itself, which is the one layer that isn't fooled by wear-leveling, because it operates below it.
Both require access a web browser simply doesn't have — this is OS- and firmware-level work, not something JavaScript running in a tab can issue.
What that actually looks like
Concretely, reaching Purge on a real machine means one of:
- Linux, LUKS-encrypted drive: destroy the volume key (
cryptsetup luksErase) for an instant crypto-erase. - Linux, NVMe: issue an NVMe Sanitize block-erase (
nvme sanitize) — the drive's firmware wipes itself. - Linux/any OS, SATA SSD: the drive's ATA Security Erase Unit command (often run via
hdparm --security-erase). - macOS: disable FileVault and destroy the APFS volume key for a crypto-erase, or use the drive's native secure-erase utility.
- Windows: turn off BitLocker and reformat to destroy the key, or run the drive vendor's secure-erase tool.
These are irreversible, whole-device operations — exactly the kind of thing that shouldn't run silently or by accident, and exactly why FileX draws a hard line around them.
Where FileX's two erasure tools fit
FileX ships two erasure tools, and each is honest about which level it reaches:
The in-browser Eraser overwrites and deletes the contents of a folder you choose, entirely in your browser via the File System Access API — nothing leaves your device. That's Clear: it reliably defeats recovery software, and it's the right tool for cleaning out sensitive files you're done with day to day. It is not, and doesn't claim to be, a whole-drive Purge tool — a browser tab can't touch drive firmware.
The downloadable FileX Eraser Tool (native, Windows/macOS/Linux, Pro-licensed) also supports crypto-erase and purge methods for whole devices. Deliberately, it does not fire the firmware sanitize command itself — that's a destructive, irreversible action on an entire disk, and an unsigned CLI shouldn't auto-execute it. Instead it detects your OS and prints the correct, vetted native command for your platform (nvme sanitize, hdparm --security-erase, cryptsetup luksErase, diskutil secureErase, or the BitLocker equivalent) so you run it deliberately, as an admin, against the right device. For file- and folder-level clear jobs it runs the erase itself and produces the same tamper-evident certificate as the web tool.
The practical takeaway
- Deleting or even overwriting individual files on an SSD is Clear-level protection — good for day-to-day cleanup, not a guarantee for hardware leaving your control.
- The reliable way to reach Purge on an SSD is cryptographic erase (destroy the key) or the drive's own ATA Secure Erase / NVMe Sanitize command — both need OS- or firmware-level access.
- Turn on full-disk encryption from day one on any drive you might ever resell or return. It makes a future crypto-erase instant instead of impossible.
- For files you want gone right now, not a whole drive, the in-browser Eraser overwrites and deletes them locally and hands you a certificate — nothing uploaded.