Secure File Shredder

Can a website securely shred or permanently delete a file from my computer?

No — and any web tool that claims otherwise is not being honest. A web page runs in a sandbox with no access to your operating system or raw disk, so it cannot reach a file already saved on your drive. What this Secure File Shredder genuinely does, 100% in your browser, is <strong>overwrite the bytes of a file copy you drop here</strong> with cryptographically random data (<code>crypto.getRandomValues</code>) for a chosen number of passes and let you download the destroyed copy, and <strong>wipe the data this site stores in your browser</strong> (localStorage, sessionStorage, IndexedDB, Cache Storage). To erase real disk files, use OS tools and full-disk encryption.

Browsers are sandboxed — no web tool can erase a file already on your disk
Overwrites a copy in memory with CSPRNG random / 0x00 / 0xFF passes, then downloads it
One-click wipe of this origin’s localStorage, sessionStorage, IndexedDB and Cache Storage
NIST SP 800-88: a single overwrite is sufficient on modern drives; multi-pass is legacy
The real fix for disk files: full-disk encryption (BitLocker / FileVault / LUKS) + OS tools

What is

Secure file deletion (data sanitization)

Secure file deletion means destroying data so it cannot be recovered, typically by overwriting the storage or by cryptographically erasing the key that unlocks an encrypted drive. Because a browser cannot access the filesystem or raw storage, this tool implements the browser-possible subset: overwriting a file’s bytes in memory with CSPRNG data and clearing the site’s own browser storage. True disk sanitization is defined by NIST SP 800-88 (Clear / Purge / Destroy) and is done with OS-level tools, drive Secure Erase, or full-disk encryption — not a web page.

Security & Privacy

Related terms

secure deletedata sanitizationoverwriteNIST SP 800-88DoD 5220.22-Mcrypto-erasewear levellingfull-disk encryptioncrypto.getRandomValueslocalStorageIndexedDB

Frequently Asked Questions

A web page cannot reach your filesystem or raw disk sectors, so it can never delete or overwrite a file that is already saved on your drive. This tool reads a file you drop into memory, overwrites those in-memory bytes with cryptographically random data, and gives you the destroyed copy to download — useful for destroying the CONTENT of a copy you control before re-saving. The original, plus any backups, thumbnails, temp files, cloud syncs or previous-version snapshots, remain exactly where they were. To erase real disk files use OS tools such as <code>cipher /w</code> or SDelete on Windows, <code>shred</code> or <code>srm</code> on Linux/macOS, or your drive’s Secure Erase.

No. It overwrites a copy in memory and downloads it; the original file on your disk is untouched.

The multi-pass idea (the famous DoD 5220.22-M 3-pass and 7-pass sequences) was designed for 1990s magnetic hard drives. Modern guidance, NIST SP 800-88 Rev. 2, states that a single overwrite pass leaves no recoverable data on current media — extra passes just take longer without improving erasure, and on SSD/flash they mostly waste write cycles. This tool offers 1 pass (random), a 3-pass and 7-pass DoD-style sequence, and a custom count with zeros / ones / random patterns, mainly so you can match a convention you have been asked for; each method still ends on a random pass so the file finishes as high-entropy data.

On modern drives one pass is enough. NIST SP 800-88 supersedes the old 3- and 7-pass DoD rules.

SSDs, USB sticks and phone storage use wear levelling and over-provisioning to spread writes evenly and prolong the drive’s life. When you overwrite a file, the controller often writes the new data to a fresh block and simply marks the old one for later erasure, so the original bytes can survive in spare cells that software cannot address. That is why overwriting is unreliable on flash. The robust answer is cryptographic erase: keep the whole drive encrypted (full-disk encryption) from day one, and destroying or replacing the encryption key instantly renders all of it unreadable.

Wear levelling makes the SSD write your “overwrite” to a different physical block, leaving the original data behind.

The wipe scans and then clears the data this specific website stores in your browser: localStorage and sessionStorage keys, IndexedDB databases, and Cache Storage (the PWA/service-worker caches). It runs entirely on your device with a confirm step. It cannot remove HTTP-only cookies, the browser’s HTTP disk cache, data belonging to other sites, or anything outside the browser, and IndexedDB deletion can be blocked if you have another tab of this site open. Note that it also clears this tool’s own saved preferences (theme, cookie consent). To clear cookies and all site data, use your browser’s Site Settings / Clear Data control.

This origin’s localStorage, sessionStorage, IndexedDB and Cache Storage — not cookies, other sites, or your disk.

A refreshingly honest, 100% client-side privacy utility that overwrites a file copy’s bytes in memory with cryptographically random data (crypto.getRandomValues) across 1 / 3 / 7 / custom passes and downloads the destroyed copy, and one-click wipes this site’s localStorage, sessionStorage, IndexedDB and Cache Storage — while being clear that a sandboxed browser cannot erase files already on your disk.

Features

Overwrite a dropped file’s bytes in memory with CSPRNG random / 0x00 / 0xFF passes, then download the destroyed copy
Methods: 1 pass (NIST-sufficient), 3- and 7-pass DoD-style, or custom (1–35 passes) — always ending on a random pass
Live progress bar, pass-sequence preview and honest per-method standards note
Scan and one-click wipe this origin’s localStorage, sessionStorage, IndexedDB and Cache Storage with a confirm
Built-in education: OS tools (cipher /w, SDelete, shred, srm), SSD wear-levelling caveat, and full-disk encryption as the real fix

PriceFree

CategorySecurity & Privacy

PlatformAll (any modern browser)

PrivacyThe dropped file is read into memory and overwritten on your device with the browser’s cryptographically secure generator (crypto.getRandomValues, OS-seeded — never Math.random); it is never uploaded, and there is no server, no CDN and no telemetry in the path. The browser-data wipe touches only this origin’s own storage. Nothing is logged or persisted beyond what you choose to download; closing the tab clears the file bytes from memory, and the tool works offline once cached. The only optional network use anywhere on the site is consent-gated ads, which never see your file.

Input: A file dropped or selected from your device (destroyed in memory only), A chosen overwrite method (1 / 3 / 7 / custom passes with random / 0x00 / 0xFF patterns)

Output: A downloaded copy whose bytes are overwritten (final pass CSPRNG random), A cleared browser-storage state for this origin plus a wipe report

Detailed Explanation

How It Works

What This Tool Really Does

The Secure File Shredder is an honest, 100% client-side privacy utility. It does NOT — and technically cannot — erase a file that is already saved on your disk, because a web page runs in a browser sandbox with no access to the operating system or raw storage. Instead it does the two things a browser genuinely can: (1) it reads a file you drop into memory and overwrites every byte with cryptographically random data from crypto.getRandomValues (and optional 0x00 / 0xFF fill passes), then lets you download the destroyed copy; and (2) it scans and one-click wipes the data this website stores in your browser — localStorage, sessionStorage, IndexedDB and Cache Storage.

A sandboxed browser cannot reach or delete files on your disk
Overwrites a file COPY in memory with CSPRNG random / 0x00 / 0xFF passes
Downloads the destroyed copy; the original on disk is untouched
Wipes this origin’s localStorage, sessionStorage, IndexedDB and Cache Storage
Randomness is crypto.getRandomValues (OS CSPRNG) — never Math.random

Methodology

How the Overwrite and Wipe Work

A pure engine (fileShredderEngine.ts) reads the File into a Uint8Array and overwrites it pass by pass in 64 KiB chunks — the maximum crypto.getRandomValues accepts per call — yielding to the event loop between chunks so a live progress bar can render each pass. Random passes call crypto.getRandomValues; zero and one passes fill 0x00 / 0xFF. Every method ends on a random pass so the final bytes are high-entropy, then the buffer is wrapped as a Blob and downloaded. The browser-data wipe uses navigator.storage.estimate() plus a non-destructive scan to show live key counts and byte sizes, then clears Cache Storage (caches.delete), IndexedDB (indexedDB.deleteDatabase), sessionStorage.clear() and localStorage.clear() behind a two-step confirm.

Overwrites in 64 KiB chunks (the getRandomValues 65 536-byte cap)
Random / 0x00 / 0xFF passes; every method ends on a random pass
Non-blocking: yields between chunks so progress renders live
Wipe order: Cache Storage → IndexedDB → sessionStorage → localStorage
Storage is scanned read-only first (navigator.storage.estimate + enumeration)

Technical Details

Standards: NIST SP 800-88 vs DoD 5220.22-M

The tool follows current data-sanitization guidance honestly. NIST SP 800-88 (Media Sanitization) is the modern standard and states that a single overwrite pass leaves no recoverable data on current drives; its “Purge” tier favours the drive’s built-in Secure Erase or cryptographic erase over repeated overwrites. The famous DoD 5220.22-M 3-pass and 7-pass (ECE) sequences were built for 1990s magnetic media and are now superseded — the DoD itself defers to NIST 800-88. The tool therefore offers 1 pass as the sensible default and exposes 3-/7-/custom-pass options mainly for compatibility with conventions people are still asked to follow, with a plain note that more passes do not improve erasure on modern drives.

NIST SP 800-88: one overwrite pass is sufficient on modern media
NIST “Purge” prefers drive Secure Erase / cryptographic erase
DoD 5220.22-M (3-pass, 7-pass ECE) is legacy and superseded
Multi-pass overwriting is largely theatre on today’s drives
On SSDs, extra passes just consume finite write cycles

Limitations

Honest Limitations

This tool cannot securely erase files already on your disk — it overwrites a copy in memory and downloads it, leaving the original file plus any backups, thumbnails, temp copies, cloud syncs, previous-version snapshots and search indexes untouched. On SSD/flash storage, wear levelling and over-provisioning mean even OS-level overwrites are unreliable, because the controller may write elsewhere and leave the original data in spare cells. The browser-data wipe clears only this origin’s localStorage, sessionStorage, IndexedDB and Cache Storage; it cannot remove HTTP-only cookies, the browser’s HTTP disk cache, other sites’ data, or anything outside the browser, and IndexedDB deletion can be blocked if another tab of this site is open. Firefox does not expose the IndexedDB database list, so those must be cleared from browser settings. Treat this as a privacy aid and teaching tool — for high-stakes erasure use OS tools plus full-disk encryption.

Cannot touch the original disk file, backups, temp copies or cloud syncs
SSD/flash wear levelling defeats overwrite-based erasure
Wipe cannot remove HTTP-only cookies or the browser’s HTTP cache
IndexedDB deletion can be blocked by another open tab of this site
The real fix for disk files: full-disk encryption + OS tools

Privacy & Security

Private by Design

Everything runs on your device. The file you drop is read into memory and overwritten locally — it is never uploaded, and there is no server, no CDN and no telemetry in the path. The overwrite randomness comes from crypto.getRandomValues, the browser’s cryptographically secure generator seeded by the operating system, never Math.random. The browser-data scan and wipe touch only this origin’s own storage. Nothing is logged or persisted beyond the copy you choose to download; closing the tab discards the file bytes from memory. The tool works offline once cached, supports dark mode and a mobile-first responsive layout, and has no analytics; the only optional network use anywhere on the site is consent-gated ads, which never see your file.

File overwriting runs locally — nothing is uploaded
CSPRNG randomness via crypto.getRandomValues (OS-seeded)
No server, no CDN, no logging, no telemetry, no account
File bytes live only in tab memory and are discarded on close
Works offline once cached; dark-mode and mobile-first

What a browser can and cannot do for secure deletion
Task	This tool (in-browser)	The real solution
Erase a file already on disk	Not possible (sandboxed)	OS tools: cipher /w, SDelete, shred, srm
Destroy the content of a file copy	Yes — overwrite bytes in memory + download	Same, or delete on an encrypted volume
Reliably wipe an SSD / USB	Not possible	Drive Secure Erase / crypto-erase (NIST 800-88)
Clear this site’s browser storage	Yes — localStorage / IDB / Cache Storage	Browser Settings → Clear site data (adds cookies)
Number of overwrite passes	1 / 3 / 7 / custom offered	1 pass suffices on modern drives (NIST 800-88)

A web page cannot access your filesystem or raw disk. This tool overwrites file copies and clears in-browser data locally — nothing is uploaded. For real disk erasure use full-disk encryption plus OS tools. As of July 2026.

Cite This Page

Title: Secure File Shredder
Author: AnyTool
Published: January 1, 2026
Modified: February 8, 2026
Section: Security & Privacy
URL: https://www.anytool.tech/secure-file-shredder

Formatted Citation

AnyTool. "Secure File Shredder." AnyTool, January 1, 2026. https://www.anytool.tech/secure-file-shredder

A refreshingly honest, 100% client-side Secure File Shredder — the /secure-file-shredder route in the AnyTool Security & Privacy category — that leads with a truth most competing web tools hide: a browser runs in a sandbox with no access to the operating system or raw disk, so no web page can truly shred or delete a file that is already saved on a drive. Instead it implements the two capabilities a browser genuinely has, both with no upload, no server, no CDN and no telemetry. First, OVERWRITE-AND-DOWNLOAD: a pure engine (fileShredderEngine.ts) reads a file the user drops into a Uint8Array and overwrites every byte in place, pass by pass in 64 KiB chunks (the maximum crypto.getRandomValues accepts per call), with random passes drawing from crypto.getRandomValues — the operating-system-seeded CSPRNG, never Math.random — and optional constant 0x00 / 0xFF fill passes; it offers a 1-pass method (the NIST SP 800-88 sufficient default), 3-pass and 7-pass DoD 5220.22-M-style sequences, and a custom count of 1–35 passes with a chosen random / zeros / ones pattern, every method ending on a random pass so the file finishes as high-entropy data, with a live progress bar, a pass-sequence preview and a per-method standards note, before wrapping the destroyed buffer as a Blob for local download. Second, WIPE BROWSER DATA: it non-destructively scans this origin’s storage via navigator.storage.estimate() and enumeration to show live key counts and byte sizes for localStorage, sessionStorage, IndexedDB and Cache Storage, then behind a two-step confirm clears Cache Storage (caches.delete), IndexedDB (indexedDB.deleteDatabase), sessionStorage.clear() and localStorage.clear(), reporting exactly what was removed and honestly flagging that Firefox cannot list IndexedDB databases and that deletion can be blocked by another open tab. A prominent education panel teaches the real answer for disk files: OS-level tools (Windows cipher /w or Sysinternals SDelete; macOS/Linux shred, srm, or emptying the Trash on an encrypted volume; drive Secure Erase / blkdiscard), the fact that SSD and flash wear levelling and over-provisioning make overwriting unreliable because the controller may write to a different physical block and leave the original data in spare cells, and that the robust solution is full-disk encryption (BitLocker, FileVault, LUKS) from day one so a lost or discarded drive is already unreadable and secure erasure becomes cryptographic erase of a single key per NIST SP 800-88. The page follows the golden design system: a custom SecureFileShredderIcon (a teal shredder machine feeding a white document into a white slot with coral and gold shredded strips falling out) in the header and a feature card, exactly four trust badges (100% client-side / Nothing uploaded / CSPRNG overwrite / Free & offline), a critical-truth banner leading the UI, a two-panel tool (overwrite-and-download on the left, browser-data scan-and-wipe on the right), an education panel, three feature cards, a prominent privacy note and an HONEST limitations note, exactly three horizontal ad slots (secure-file-shredder-top / -mid / -bottom) and a sticky mobile action bar (Overwrite / Download / Reset), with full dark-mode and mobile-first responsive support. It is scrupulously HONEST about scope: it cannot erase files already on disk (the original, backups, thumbnails, temp copies, cloud syncs, previous-version snapshots and search indexes are all untouched), overwrite-based erasure is unreliable on SSD/flash, the number of passes is largely theatre on modern drives because NIST SP 800-88 says one pass suffices and DoD 5220.22-M is superseded, and the browser-data wipe cannot remove HTTP-only cookies, the browser’s HTTP disk cache, other sites’ data or anything outside the browser. Privacy is structural: the dropped file is read and overwritten locally in memory with the browser’s cryptographically secure generator, nothing is uploaded or logged, file bytes live only in tab memory and are discarded when the tab closes, the browser-data wipe touches only this origin, the tool works offline once cached, supports dark mode and a mobile-first layout, has no analytics or telemetry, and the only optional network use is consent-gated ads that never see the file.