How to use Directory Snapshot Integrity Comparer
- Select the earlier and later file collections. If supported by the file chooser, select a folder to retain its relative paths.
- To use a saved state, leave that collection empty and choose its directory-snapshot.json instead. Selected files take priority over the snapshot on the same side.
- Choose All, Changes or a specific path state and run Compare snapshots. Paths match exactly; moved files can appear as removed and added.
- Download directory-comparison.csv for the selected filter and directory-snapshot.json for the complete later collection. Keep file contents separately if you need a backup.
Example: Directory Snapshot Integrity Comparer
Compare four path outcomes: one added, one removed, one changed and one unchanged file.
Options
- First collection (the earlier state)
- Select the files or a folder for the earlier state. Up to 200 files, 10 MB each and 50 MB in total. If the browser supplies a folder-relative path it is used; otherwise the plain file name is used.
- Second collection (the later state)
- Select the files or a folder for the later state, with the same limits. Leave the first collection empty and load a saved snapshot below to compare against an earlier point in time.
- Saved snapshot of the first collection (optional)
- Choose a directory-snapshot.json saved by this tool to use as the earlier state. This is used only when the first collection is empty.
- Saved snapshot of the second collection (optional)
- Use a saved record-only snapshot as the later state when the second collection is empty. Selected source collections take priority over snapshots.
- Paths to display
- The CSV follows this filter. The saved snapshot retains the complete later collection.
Supported inputs and limits
- Each local collection supports up to 200 files, 10 MiB per file and 50 MiB total.
- A saved snapshot must use this tool’s supported JSON format and is limited to 4 MiB and 200 entries.
- Duplicate or unsafe paths are refused.
- The selected filter applies to the on-page rows and comparison CSV; the later snapshot retains all accepted later paths, byte counts and hashes.
- Snapshots contain no file contents and cannot restore files.
More details
No monitoring, malware scan, rename inference or publisher authentication is performed.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved 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.