The problem
Most file tools can show matches. Far fewer explain that an identical configuration, backup or dependency may still be required in every location.
ABOUT DUPESPACE
File cleanup should begin with understanding.
DUPESPACE is a free, open-source project for comparing folders, finding exact duplicate content and reviewing safer Windows cleanup. It is built to explain uncertainty instead of turning every match into a delete button.
WHY THIS PROJECT EXISTS
Duplicate content is easy to detect. Redundancy is a human decision.
The approach
Separate read-only analysis from file actions, preserve at least one item, protect explicit folders and revalidate candidates immediately before cleanup.
The boundary
DUPESPACE does not clean the registry, guess which system files are disposable, certify backups or claim that matching content is automatically safe to remove.
PRODUCT PRINCIPLES
Safety claims should be visible in the workflow.
Explain before acting
A result should tell you what matched, what remains uncertain and what the next action would change.
Protect purpose, not just content
Identical bytes can still belong to separate projects, backups or workflows. Location and intent remain part of the decision.
Keep risky paths separate
Recycle Bin cleanup and permanent deletion have separate consent and code paths. One never silently falls back to the other.
Leave an audit trail
Actions produce reviewable outcomes instead of only reporting a reclaimed-space total.
HOW CONTENT IS REVIEWED
Test evidence comes before confident wording.
Guides and solution pages are checked against the current product behavior. Tested articles record the release, environment and limitations that matter to the result. Screenshots and reports are redacted before publication.
- No invented users, ratings, savings or benchmark results
- Visible publish and review dates
- Corrections update the page instead of hiding a limitation
CONTACT AND ACCOUNTABILITY
Found a bug, unsafe edge case or unclear claim?
Open a GitHub issue with the app version, reproduction steps and redacted errors. Never publish private filenames, full paths, reports, tokens or account information.