Find the dependencies and build files eating your disk, and the dev servers your agents forgot. Review everything. Keep your code.
Free and open source on GitHub. macOS, Windows and Linux.
Permanently remove generated files. Reinstall or rebuild before using these projects again.
Point Gigaflush at a workspace or your whole home folder. A parallel Rust walker streams results as it finds them, largest first.
~/Developer/atlas-mobile build3.2 GB~/Developer/search-index target2.4 GB~/Developer/studio-web node_modules1.2 GB~/Developer/menu-bar .build655 MB4 found · 7.5 GB reclaimable · 2sNothing is preselected. Filter by project, path, or type, and see which toolchain owns each folder and how to get it back.
Confirm the exact paths, then watch each folder go with live progress. The space is back before your coffee is.
Space reclaimed
0.0 GB
| Folder | Size | Share |
|---|---|---|
| node_modules | 2.9 GB | 43% |
| target | 2.4 GB | 35% |
| build | 1.1 GB | 16% |
| .gradle | 0.4 GB | 6% |
✓ Cleanup complete · 4 of 4 folders
Each folder must match its toolchain's convention and sit beside a real project file. A stray build/ or dist/ is never a candidate.
~/Developer/studio-webnpm installRemoving gigabytes should feel decisive, not risky. The filesystem stays in front of you, and the guardrails live in the backend, where the interface can't talk its way past them.
Only known generated folders count, and only beside a real project marker.
Every folder starts unchecked. You choose what goes.
The review sheet lists each full path and how to rebuild it before the destructive button is in reach.
The Rust backend revalidates names and markers right before removal and refuses symlinks and parent traversal.
:4322 · astro previeworphaned 7d182 MB:3000 · next devorphaned 1d312 MB:8000 · manage.py runserverup 9h64 MB:5173 · viteConnected:4321 · astro devConnected:8787 · wrangler devStarted 25m agoClosed terminals and coding agents leave dev servers running for days. They hold :3000, eat memory, and greet you with EADDRINUSE. The Servers tab finds the ones nothing is talking to.
A browser tab or client on the port means it's in use. It stays.
Running at least 30 minutes, under 2% CPU on average, and either orphaned or 6+ hours old.
Your own Node, Bun, Deno, Python, Ruby and PHP servers. Never databases, Docker, editors, agents or language servers.
Re-checked by PID and start time, then sent SIGTERM, exactly like Ctrl+C.
Small enough to forget about, sharp enough to trust with your disk.
Click the icon, scan, close. Menu bar on macOS, system tray on Windows and Linux. Click away or press Esc and it's gone.
Filter, rescan, dismiss. Ctrl on Windows and Linux. Focus lands where you expect.
Follows your OS by default, with a one-click override in the titlebar.
Gigaflush is open source under GPL-3.0. The rules that decide what can be removed are a few dozen readable lines of Rust.
Browse the source →// scanner.rs — every rule needs a sibling marker
match name {
"node_modules" if marker("package.json") => …,
"target" if marker("Cargo.toml") => …,
".build" if marker("Package.swift") => …,
"target" if marker("pom.xml") => …,
_ => return None,
}Built with Rust and Tauri on the system webview. No bundled browser runtime.
Nothing about your files leaves your machine. The only request is a periodic check for a newer version on GitHub.
Results stream in as the walker finds them, batched so the list stays smooth past thousands of folders.
Every build, on every platform, straight from GitHub Releases. No account, no license key, no trial.
Latest releaseRelease notesSHA-256 checksums
macOS 11 or later · Apple Silicon and Intel
Or clear the download flag from Terminal:
xattr -dr com.apple.quarantine /Applications/Gigaflush.appWindows 10 and 11 · x64
Also as .msi
x86_64 · Debian, Ubuntu, Fedora and more
chmod +x Gigaflush-linux-x86_64.AppImage && ./Gigaflush-linux-x86_64.AppImageThe builds aren't code-signed, so macOS and Windows ask once before the first launch. They're built in public by GitHub Actions from the tagged source, and every release has checksums.
Everything is on GitHub under GPL-3.0. You need Node, Rust, and the Tauri prerequisites.
git clone https://github.com/abhinavcdev/gigaflush.git && cd gigaflush && npm install && npm run tauri:buildGigaflush is free and stays free. If it earned a spot in your menu bar, a tip helps pay for the next ecosystem, the Windows server view, and the time spent on bug reports.
Anything else? Ask on GitHub or visit support.
Yes. Every build for macOS, Windows and Linux is free to download, and the source is GPL-3.0 on GitHub. There's no account, license key or trial. If it helps you, there's a tip jar.
The builds aren't code-signed by Apple or Microsoft, which costs money every year. On a Mac, open it once, then click Open Anyway in System Settings → Privacy & Security. On Windows, click More info, then Run anyway. Every build comes from GitHub Actions with published SHA-256 checksums, and you can always build it from source yourself.
Only your own Node, Bun, Deno, Python, Ruby and PHP dev servers that have nothing connected to their port, have used almost no CPU, and were orphaned by a closed terminal or agent or have run for 6+ hours. Databases, Docker, editors, agents and language servers are never listed. Each one is re-checked, then asked to exit like Ctrl+C. Available on macOS and Linux; Windows is next.
No. Cleanup is permanent, which is what actually frees the space. That's why every removal goes through a review sheet listing exact paths and rebuild steps first.
Source code, lockfiles, virtual environments, global caches, SDKs, and generic dist/ or build/ folders without a matching project file. Inaccessible directories are skipped.
Gigaflush checks GitHub for a newer version at most twice a day and shows a small banner. Click it to download the new version from the site. Your settings carry over.
No telemetry, no analytics, no account. The update check is a plain request to GitHub's public API. Scanning and cleanup happen entirely on your machine.
They're logical file-size estimates. Actual disk savings can differ with filesystem compression, clones, or hard links.
Open an issue on GitHub with your OS and Gigaflush version, or email support.
One scan, one review, one click. Your next side project will thank you.
