WinReclaim

Understand your storage. Reclaim space without guessing

10 followers

Understand your storage. Reclaim space without guessing

10 followers

Visit website

File storage and sharing apps

•

Content Management Systems

•

AI Metrics and Evaluation

WinReclaim is local-first Windows storage intelligence that shows what is consuming your disk before anything is removed. It combines multi-drive scanning, storage history, consequence labels and cleanup simulation with narrowly scoped cleanup actions. Eligible files enter a seven-day Safe Undo Vault, while protected and unknown items remain untouched. No desktop telemetry, arbitrary path deletion or blind “one-click optimization.”

Free

Launch tags:Windows•Productivity•Open Source

Launch Team / Built With

Describe your app. Get clickable screens, flowcharts and mind maps.From “what if” to “here’s how it works” in one prompt.

Promoted

OpenAI

OpenAI Day

What did GPT-5.6 Sol, Terra and Luna unlock that made your launch possible?

Maker

GPT-5.6 Sol helped me turn a frustrating one-off Windows storage cleanup into a complete product. The project started after I used Codex to investigate what was consuming my drive and burned through a large part of my limits doing manual cleanup work. Sol helped me step back and convert that experience into WinReclaim: a Rust and Tauri application that explains storage usage, classifies cleanup consequences, simulates changes before execution and provides a Safe Undo Vault for eligible files. I used Sol both in Codex and in ChatGPT throughout the build. It helped with the Rust safety architecture, React interface, debugging, testing, documentation, Windows packaging, GitHub releases, the Vercel landing page and launch preparation. The most important thing it unlocked was the ability for one developer to work across systems programming, product design, security review and release engineering without turning the app into an AI-controlled cleaner. Sol accelerated the development proces

Report

4mo ago

Maker

📌

Hi Product Hunt — I’m Amaan, the maker of WinReclaim. WinReclaim started after I tried to understand why so much space had disappeared from my Windows drive. The obvious suspect turned out to be only a small part of the problem. Most of the storage was spread across development caches, generated project files, Android tooling, containers, temporary data and local model stores. I initially approached the problem as a one-off cleanup. That quickly exposed the real issue: Windows cleanup tools often tell you how much space can be removed, but not who created it, what removing it will affect or how difficult it will be to recover. So I built WinReclaim around three steps: 1. Understand - what is using the disk and which workload likely owns it. 2. Simulate - cleanup before making any changes. 3. Reclaim - only reviewed items, with an undo path where recovery is practical. The app is local-first and open source. Scanning, classification, planning, cleanup history and restore all happen on the device. There is no desktop telemetry, and unknown or protected folders cannot be silently added to a cleanup plan. Some of the features I’m most interested in feedback on are: - Storage Time Machine for comparing scans - Reclaim Passports explaining ownership and consequences - Cleanup simulation with projected impact - The seven-day Safe Undo Vault - Detection of development caches and generated project output I’d particularly like to know: when reviewing disk usage, what information would make you confident enough to remove something? Thanks for checking out WinReclaim.

Report

4mo ago

Forum Threads

p/winreclaim

•

4mo ago

What’s the strangest thing quietly consuming space on your Windows PC?

WinReclaim started after I discovered that the obvious culprit was not actually responsible for most of my missing disk space. The real usage was scattered across development caches, generated build output, Android tooling, containers, temporary data and local model stores.

I m curious what other Windows users have found hiding on their drives.

What was consuming far more space than expected, and what information would have made you confident enough to remove it?

View all