i launched spacefree, a windows app that finds the disk space wsl2 and docker hide

Bhavik Rohit — Mon, 21 Sep 2026 06:17:27 +0000

spacefree is live now. i built it because my C drive kept filling up and i could not see why.

if you use wsl2 or docker desktop, everything lives inside a virtual disk file (ext4.vhdx or docker_data.vhdx). it grows on its own but never shrinks, so deleting stuff inside does not give you space back on windows. the gigabytes are still there, just hidden.

what spacefree does

finds and compacts the wsl and docker virtual disks
scans old node_modules, build folders, package caches and ide caches
labels everything before you touch it, safe to delete or rebuildable
deletions go to the recycle bin by default and every action is logged

everything runs locally, nothing is uploaded. windows only for now, 7 day free trial, no card needed.

what it looks like

would love feedback, especially on what else you would want it to scan. it is early, so tell me what breaks.

https://www.spacefree.net

why your C drive keeps filling up if you use wsl2 or docker on windows

Bhavik Rohit — Thu, 17 Sep 2026 16:58:02 +0000

check this out : https://space-free.vercel.app/

for months i kept getting the low disk space warning on my C drive and had no idea why. i would delete stuff, clear downloads, uninstall apps, and still barely get anything back. turns out the actual problem was not my files at all.

if you use wsl2 or docker desktop on windows, both of them store everything inside a virtual disk file called ext4.vhdx or docker_data.vhdx. these files grow automatically as you use docker or wsl, but here is the part nobody tells you, they never shrink back down on their own. so you can delete 50gb worth of containers, old projects inside wsl, run docker system prune, whatever you want, and your windows C drive still shows almost no extra space back. the gigabytes are not gone, they are just stuck inside that virtual disk file.

there is actually a github issue on microsoft's wsl repo about this exact problem with over a thousand reactions and it has been open since 2019. people are still commenting on it every week. that alone tells you this is not some rare edge case, its a pretty widespread and annoying problem for anyone doing dev work on windows.

the manual fix

if you want to fix it yourself right now, here is the actual process:

shut down wsl completely, run wsl --shutdown in powershell
quit docker desktop fully, not just close the window
if you are on windows pro or enterprise, enable hyper-v so you get the Optimize-VHD command, then run Optimize-VHD -Path "path to your vhdx file" -Mode Full
if you are on windows home, you do not have that command, so you use diskpart instead, select the vdisk file, attach it readonly, then run compact vdisk

this actually works and can free up tens or even hundreds of gb depending on how long its been building up. but its clunky, you have to remember the paths, remember to shut everything down first, and do it manually every few weeks or your disk just fills right back up.

on top of the wsl and docker thing, most dev machines also quietly build up:

old node_modules folders in projects you have not opened in months
build folders and package caches from old projects
ide caches you forgot existed

none of this shows up clearly in windows explorer or storage sense, it just looks like one folder using space, not "this is safe to delete" vs "this is not."

what i built

i got tired of doing the manual vhdx dance every few weeks so i built spacefree, a windows app that automates that whole shutdown, trim, compact sequence into one click, and also scans for the node_modules and build folder clutter i mentioned above. everything gets a plain label before you touch it, safe to delete, rebuildable, or not cleanable, and deletions go to the recycle bin by default instead of being permanently gone.

still windows only, still early, 7 day trial with no card needed if anyone wants to try it on their own machine. genuinely curious if other people are hitting the same node_modules and build folder buildup or if that is just me.