Old builds add up.
See what can go.
That repo you haven’t opened in months can still have a lot of dependencies. Find old build files and caches, inspect the evidence, and review exactly what you want to clear.
macOS + Windows. Pay once. Future updates included.
The project moved on. Its build folders stayed.
A repository can sit untouched while its dependencies and build output keep taking up space. Pip looks for cleanup candidates such as node_modules and .next, shows the evidence beside each finding, and leaves repositories with running servers out of its suggestions.
Review the paths and reclaimable space before approving file cleanup. Files stay in quarantine for seven days, with space freed after purge. Supported cache commands have a separate review step and take effect when they finish, without that file restore window.
- to restore files held in quarantine
- 7 days
- every cleanup path and command
- Review first
- file scans in your selected folders
- On demand
See the evidence beside the files.
Explore your drives and scan selected folders. Cleanup findings explain why files are candidates; repositories with a running server are excluded from suggestions.
Have time to change your mind.
Approved file cleanup moves items into quarantine with seven days to restore them. Those files still occupy disk space until they are purged.
Clean caches with their own tools.
Review supported package-manager and Docker cleanup commands before running them. Cache commands take effect when they finish and have no quarantine restore window.
Review what’s left from your last project.
Read the Storage guideChoose where to look.
Explore disk usage, then scan your chosen folders and the repository roots of your running dev servers when you’re ready.
Review the cleanup plan.
Check each full path, its evidence and reclaimable space. For supported cache cleanup, review the exact command and its scope.
Approve what you want to clear.
Quarantined files remain restorable for seven days before purge. Approved cache commands apply their own cleanup immediately, without that restore window.
Know what a cleanup will actually change.
The size of a folder, the space you can reclaim and the moment that space becomes free can be different. Pip keeps those details in the cleanup plan.
- Why hasn’t my free disk space increased after file cleanup?
- File cleanup first moves approved items into quarantine on the same drive, where they remain restorable for seven days. They still occupy space until purge. Pip then measures the space actually freed. Shared files matter too: a large, hard-linked node_modules folder can have much less reclaimable space than its apparent size suggests.
- Which files are kept out of cleanup suggestions?
- Documents are never cleanup candidates, and repositories with a running server are excluded from suggestions. Regenerable findings are preselected only when the evidence includes a Git repository, an ignored path and a neighbouring manifest. Findings that need your judgement stay unselected until you review them, with the evidence and full paths available before approval.
- Can I restore a package cache after pruning it?
- Cache cleanup commands use the package manager’s or Docker’s own behaviour and bypass file quarantine. There’s no seven-day restore window. Pip shows the exact supported command and its scope before approval; for example, pnpm store prune removes unreferenced packages and cached registry metadata. Review what may need downloading or rebuilding before you run it.
Give your next project room to grow.
Every Pip tool. $29 USD, once. One machine at a time.