Support

Getting help

The fastest way to reach us is by email at [email protected]. To help us help you, please include your Windows version and a short description of what happened — and if a scan failed, the path you were scanning and roughly how large it is.

Frequently asked questions

Does the scanner collect any of my data?

No. It makes zero network calls, has no accounts, no analytics, and no tracking. Scan results are cached on your own machine so you can revisit them. See our Privacy Policy for details.

How do I run it?

The published build is a single self-contained executable — double-click it and the app opens in your browser. It runs a small web server on your own machine, which is why the interface appears as a local page rather than a separate window. Nothing is served to the internet.

Will it delete anything?

Never. The scanner is strictly read-only: it reads file and directory metadata to report sizes and does not modify, move, or delete any file. Cleanup suggestions are informational — deciding what to remove, and removing it, is entirely up to you.

What do the cleanup suggestions actually flag?

Well-known cache and temporary locations — npm and NuGet caches, browser caches, Windows temp, the Recycle Bin — along with file types that are often safe to remove, such as .tmp, .log, .bak, .dmp, and .old. Treat them as a starting point, not an instruction: check anything you don't recognise, and back up first.

The reported size doesn't match what Windows says.

A few things cause that. Locations Windows won't let the scanner read are counted as access-denied and summarised rather than measured. Reparse points — symlinks and junctions — are skipped deliberately, so a linked folder isn't counted twice or walked forever. And scanning a drive root shows an estimated percentage while it runs, based on used disk space, before settling on the measured total.

Can I look at an old scan without rescanning?

Yes. Every scan is cached to your local application data folder and listed in the History panel, so you can reopen it and browse the tree — useful for comparing how disk usage changes over time. The cache keeps the 20 most recent scans and prunes older ones automatically.

Where is the cache, and how do I clear it?

In %LocalAppData%\FolderFileSizeScanner\cache. You can delete individual scans from the History panel, or remove the whole folder. Cached scans contain file paths from your machine, which may include your Windows username — they are never transmitted anywhere.

Can I run two scans at once?

No. The app runs a single scan at a time and enforces a single running instance, so a second launch hands you back to the one already open. Scanning a large drive is disk-bound; running several at once would only make each slower.

Does it work on macOS or Linux?

Not currently. The scanner is a Windows tool.

I found a bug or have a feature request.

We'd love to hear it. Email us at [email protected] with as much detail as you can.

Legal

Privacy Policy  ·  Terms of Service