Deleting a File Does Not Delete the File

By NorwegianSpark Editorial · Published August 8, 2026 — written with AI assistance and reviewed by the NorwegianSpark SA editorial team.

Delete a file, empty the recycle bin, and it is gone. From your point of view, yes. From the drive's point of view, usually not.

Deleting normally removes the entry pointing to the data and marks the space as reusable. The contents sit there until something else is written over them, which may be minutes or may be months. Recovery software exists precisely because this gap is so reliable.

Why the old advice no longer fits

Traditional guidance says overwrite the file several times. That comes from spinning magnetic hard drives, where data lived in a known physical location and overwriting it genuinely replaced it.

Solid-state drives do not work that way. They spread writes across cells to manage wear, so an instruction to overwrite a particular file may write somewhere else entirely, leaving the original data in a cell the operating system can no longer address but which still holds it. Overwriting an SSD file-by-file is therefore both unreliable and needlessly wearing.

This is why file-shredding utilities, once standard advice, are now largely the wrong tool on modern hardware.

The answer that works everywhere

Encrypt the whole drive. Full-disk encryption changes the problem completely: everything written is encrypted, so a deleted file's remnants are encrypted remnants. Without the key, recovery software finds noise.

It also means the leftovers you cannot reach — temporary files, old versions, swap space, the copy in a cache you never knew about — are equally protected. That is the real advantage, because those hidden copies are what file-level shredding always missed.

Both major desktop systems include this. Phones do it by default. Turning it on is a one-time action that solves deletion, loss and theft together, and it is the single highest-value thing in this article.

When you need more

Wiping a whole drive before disposal. Use the drive's own secure-erase command rather than overwriting. For an SSD this instructs the drive to discard its internal encryption key, making everything unreadable in seconds. Manufacturer tools and most system utilities expose it. If the drive was encrypted, a normal reinstall is already sufficient.

A single genuinely sensitive file on an unencrypted drive. Here a shredding tool is reasonable on a mechanical hard drive. On an SSD, accept that it is best-effort and treat encrypting the drive as the actual fix.

Physical destruction. For a failed drive that cannot be erased, or data where the consequence of exposure is severe, destroying the storage is the only certain method. Many recycling centres offer it.

The copies you forget

Deletion attention usually focuses on the file itself, while the copies survive elsewhere:

• Cloud sync. Deleting locally may leave it in the provider's trash for weeks, and in version history longer.
• Backups. A backup that captured the file still has it, which is the correct behaviour and worth remembering.
• Email attachments. Sent and received copies persist independently.
• Thumbnails and previews. Generated automatically, stored separately, frequently overlooked for images and documents.
• Messaging apps. A file shared with someone is now on their device too, and no deletion of yours touches it.

For a document that genuinely must not persist, the file on disk is the easiest copy to deal with. The others require going to each service in turn.

A proportionate approach

For nearly everyone: turn on full-disk encryption, delete normally, and use secure-erase or destruction when disposing of hardware. That covers realistic scenarios — a sold laptop, a lost drive, a discarded phone — without per-file rituals that modern storage makes unreliable anyway.

The genuinely useful mental shift is that "how do I delete this properly" is usually the wrong question. "Is this drive encrypted" answers it better, permanently, and for every file at once.