How to Safely Clean Up Developer Disk Space on Windows (Without Breaking Your Projects)

By LilBuba.ai · 28 July 2026 · 6 min read

If you write code on Windows, your SSD is quietly filling up with things you don't need — and most of it will come straight back the moment you actually need it. The trick to reclaiming that space isn't deleting aggressively. It's deleting the right things, and being able to undo it if you get one wrong.

Where the space actually goes

It's rarely your code. It's the regenerable junk that piles up around it:

The common thread: all of it is regenerable. Delete a node_modules and npm install brings it back. Delete a build/ and your next compile rebuilds it. It's cache, not work.

Why people don't clean it up (and the one real danger)

Two reasons. First, it's tedious — the junk is scattered across dozens of project folders. Second, and more importantly: it's genuinely scary. Delete the wrong folder and you've binned a config, an .env, an uncommitted change, or a local database you forgot was there. So most of us just… buy a bigger drive.

The safe way to do it has three rules:

  1. Only touch the regenerable stuff — never source, never config, never uncommitted work.
  2. Know what you're still working on — the folder you're working in today should be left alone.
  3. Make it reversible — nothing should be truly gone until you're certain.

Doing it by hand (and the free tools that help)

You can absolutely script this yourself. Credit where it's due — there are excellent free command-line tools for it. npkill is brilliant for hunting down node_modules, and kondo cleans a wider set of project artifacts. If you live in the terminal and trust your own rm -rf, they're superb and free, and we'll happily say so.

The catch is they're command-line, they mostly delete outright (no safety net), and they tend to solve one slice of the problem rather than the whole messy picture on a Windows machine.

The safe-GUI approach: what we built K8 Cruft to do

We made K8 Cruft for the developer who'd rather not script it — and, honestly, who's been burned once by a too-clever cleanup.

It scores each pile by how safe it is to remove. So you can see at a glance what's genuinely disposable versus what deserves a second look, and it flags the regenerable items plainly: this comes back with one command — delete with confidence.

It shows you where and when. Every find comes with its full path and when anything inside it last changed, so you can see which project it belongs to before you clear it. It doesn't guess what you're working on this week — you know that, so it leaves the call to you.

Nothing is deleted until you press Purge. This is the bit that matters most. Anything you clear goes to a quarantine you can restore from in one click. Change your mind, or realise you needed that .venv after all? It's not gone — it's just parked.

It's Windows-native, a one-time £24.95 (no subscription, no account), and it runs 100% locally — nothing about your machine or your projects ever leaves it.

The honest bottom line

If you're happy in the terminal, npkill and kondo are free and great — use them. If you'd rather a safe Windows app that shows you what's safe and where it lives, and lets you undo anything, that's what K8 Cruft is for.

Either way, the message is the same: stop buying bigger drives to store cache. Most of what's filling your SSD will regenerate itself the moment you need it.


Clear your dev junk safely — nothing deleted without your say-so.

K8 Cruft finds the node_modules, build caches, Python venvs and forgotten build output eating your disk. It scores what's safe, shows every find's path and date, and quarantines everything so you can restore in one click. 100% local.

See how K8 Cruft works →

K8 Cruft is available at lilbuba.ai. One-time purchase, £24.95. No subscription. No cloud. Your code stays on your machine, where it belongs. Safe. Smart. Stupidly Fast.