How to use Directory Snapshot Integrity Comparer
- Supply the first collection (the earlier state) and second collection (the later state) using the supported input described beside the controls.
- Review the selected options and the declared scope, then run the directory snapshot comparer.
- Read the result and unresolved findings before downloading or sharing a report. The original input is not changed.
Example: Directory Snapshot Integrity Comparer
Hash two selected local file collections and compare paths, changes and removals. This example uses synthetic public data and the named local fixture files.
Options
- File collections
- Select the intended before and after collections. Browser-provided relative paths are used when available; basename fallback can require smaller, unambiguous selections.
- Snapshots
- Keep the declared path convention with a saved snapshot. Duplicate or unsafe paths must be corrected rather than silently overwritten.
Supported inputs and limits
Where your input is processed
This tool processes your input in this browser. Your text and files are not uploaded to UseFreeTools. Check this tool's limits for anything it may save on your device.
A path change and a content change are different
Comparisons use the recorded relative path. Moving a file can appear as a removal and an addition even if its bytes are unchanged; the tool does not infer renames. A matching hash shows byte agreement under the snapshot convention, not that a file is harmless or came from a trusted publisher.
Questions about Directory Snapshot Integrity Comparer
Will a moved file be called a rename?
No. Paths are compared exactly, so a move can appear as removed and added.
Do identical names prove identical files?
No. The report compares SHA-256 hashes of the exact selected bytes.
Does the tool watch my folder?
No. It reads only the files or snapshots supplied for that run.