Find build junk across a drive. Uncheck what you keep. Delete the rest.

A disk cleaner for Windows developers. Below is the real app on a made-up drive. Press Scan.

riptide
Demo — nothing touches your disk

Zap

Find folders by name and send them to the Recycle Bin.

ScanIllustration
Records4.87M
Reclaim41.8GB
Not a benchmark.

Open on a wider screen to try the demo.

What it finds

93 known caches

Reads the file table, not the folders

riptide opens the raw volume and reads the NTFS Master File Table in one sequential pass. It never walks the folder tree.

First read4.87M records in 26 sOn the author's machine.
RescanUnder 1 sAfter the first read. Updates come from the NTFS change journal.
Without admin rightsDirectory walkSlower, same results. riptide says which one ran.

Every row shows its risk

How a delete is kept safe

  1. Deletes go to the Recycle Bin. Permanent delete is a checkbox you tick each time.
  2. The server deletes only paths one of its own scans found.
  3. Drive roots, Windows, Program Files, user profile roots and key folders are refused.
  4. Before a delete, riptide checks each build folder still sits next to its marker, such as a target folder next to Cargo.toml.
  5. You type the count to confirm.

Cleans with the tool's own command

For these, riptide runs the tool's cleanup instead of deleting folders.

Get riptide

Needs

  • Windows, with NTFS drives.
  • Node.js.
  • ripgrep (rg) on your PATH, for Search.
  • Admin rights for the fast scan. Without them, riptide walks the folders.

Run

  1. git clone https://github.com/dustinlacewell/riptide
  2. npm install
  3. npm run devWindows asks for admin rights, then riptide opens in a new console.
  4. Open the local address it prints.