Secure File Shredder

Deleting removes the pointer, not the data

A normal delete unlinks the filename and marks the space reusable. The bytes stay on disk until something overwrites them, which is why undelete tools recover files routinely. Overwriting the contents first is what makes recovery from the raw sectors impractical.

One pass is enough on modern drives

The 35-pass Gutmann method was designed for MFM and RLL encoding used by drives of the early 1990s and has no benefit on any current hardware. A single pass of zeros or random data makes magnetic recovery infeasible on a modern platter drive. Multi-pass wiping mostly wastes time and drive life.

SSDs cannot be shredded reliably

Wear levelling means the controller writes new data to different physical cells, so overwriting a file's logical blocks leaves the original cells intact and unreachable through the filesystem. Copy-on-write filesystems, snapshots, and journals cause the same problem on any medium. For an SSD the working answers are full-disk encryption with key destruction, or the drive's own secure erase command.

Copies survive elsewhere

Shredding one file leaves backups, cloud sync history, version control, temporary files, swap space, thumbnail caches and email attachments untouched. Anything genuinely sensitive has usually existed in several places, and shredding the original addresses only one of them.

Encryption from the start is the real answer

Data encrypted before it is written is unrecoverable once the key is gone, regardless of what physical remnants remain. That is a design decision rather than a cleanup step, and it is why full-disk encryption has largely replaced shredding as the standard practice.