01
Review regenerable user files before reclaiming space
See user caches, logs, and saved application state grouped by what creates them, with exact size totals and only the chosen items marked for reversible cleanup.
Folder ReviewFile Review
Review user support files, developer storage, and app leftovers from one careful workspace.
App File Review separates three different cleanup decisions instead of presenting one vague junk total. Inspect regenerable user caches, logs, and saved state; expose node_modules, DerivedData, build output, language caches, and Docker storage; then match an installed app with its support files using exact, name, or weak confidence before choosing what goes to the Trash.
Start the 14-day trial in the app. No payment method is required to try Foldout.
Local tool processingFiles and tool work stay on your Mac.
100+ focused toolsFiles, PDFs, media, capture, and developer workflows.
Settings ready to goFormats, dimensions, and other values carry into the tool.
Try everything first14 days in the app. No payment method required.
This tool is a local inspection and workflow utility for files, settings, and development tasks you control. It reviews selected local information only; Foldout does not connect to other machines, manage accounts, monitor networks, or provide a live service.
What it does
Give user files, developer folders, and app leftovers their own evidence and reversible review path.
Group user caches, logs, and saved application state by category and size.
Find node_modules, DerivedData, .build, build caches, Python caches, and other regenerable developer folders.
Review Docker reclaimable storage separately from project folders.
Match app leftovers using visible confidence labels instead of name guesses alone.
Remove leftovers only or explicitly include the app itself.
Move confirmed items to the Trash and record recoverable actions in Safety Center.
Review the evidence
Give user files, developer folders, and app leftovers their own evidence and reversible review path.
Group user caches, logs, and saved application state by category and size.
02
Expose the developer folders that quietly consume gigabytes
Review node_modules, DerivedData, build caches, SwiftPM output, and Python caches by project, path, category, and size before removing anything.
03
Match an app with its support files before uninstalling
Inspect Application Support, caches, preferences, and logs with confidence labels and sizes. Remove leftovers alone, or explicitly include the app, with every item sent to the Trash.
Why it belongs
Why Folder Review earns a place in the toolbox.
The practical details that make this job faster, clearer, or safer than doing it by hand.
Three cleanup questions stay separate
User support files, developer output, and app leftovers have different risks, so each receives a dedicated tab and evidence model.
Developer storage is tied to context
Project name, category, full path, and size reveal whether a large folder is a rebuildable dependency, cache, or build product.
Leftover matching exposes confidence
Exact bundle-ID, app-name, and optional weak matches remain labeled so a user can distinguish strong evidence from a guess.
The final action stays reversible
Selected files and optional apps are moved to the Trash, with a corresponding Safety Center operation instead of permanent deletion.
How to use it
From opening the tool to saving the result.
- 01
Choose User Files, Developer Files, or App Leftovers.
- 02
Review categories, paths, sizes, and confidence labels.
- 03
Select only the items whose role you understand.
- 04
Move the reviewed selection to the Trash and recover it through Safety Center if needed.
Questions
Before you try Folder Review
Does Foldout permanently delete the selected files?
No. Confirmed items are moved to the Trash and the operation is recorded in Safety Center.
Can it remove an app as well as leftovers?
Yes for eligible non-system apps, but including the app requires a separate explicit toggle.
What do the leftover confidence labels mean?
Exact identifies a bundle-ID match, Name identifies an app-name match, and weak matches stay hidden unless you choose to review them.
Which developer folders can it surface?
The review includes common dependency, build, and cache locations such as node_modules, DerivedData, .build, JavaScript build caches, Python caches, and Docker data.
Related tools