Folder Manifest & Integrity

About this tool

Record exact file-byte evidence with portable root-independent paths, then inspect every difference from a saved baseline without uploading the folder.

• Removes the selected root name, validates portable relative paths, blocks normalized cross-platform collisions, and hashes up to 1,000 files, 100 MB each, and 500 MB total.
• Validates version 1 SHA-256 JSON or identifies a compatible legacy files-only baseline before comparing any path.
• Separates added, modified bytes, metadata-only, removed, and unchanged paths, exposes both hashes for byte changes, and exports complete manifest and comparison evidence.

How to use Folder Integrity

Choose a folder to hash canonical paths relative to its selected root, download the version 1 manifest, then load that JSON beside a later folder and review all five path states before exporting comparison evidence.

When this tool is useful

• Checking a delivery folder against a saved baseline.
• Recording a reproducible local file inventory.

Practical tips

• Store the baseline through a separate trusted channel from the folder it describes.
• Review modified and removed paths first, then confirm metadata-only timestamps independently.
• Remember that empty directories, symlinks, permissions, and ownership are outside browser folder selection.

Examples you can test

Load an example, compare the result with the expected output, then replace it with your own input.

Version 1 baseline plus a later folder with one edited, one new, and one removed file

Added, modified, metadata-only, removed, and unchanged path evidence with current and baseline hashes

Validation checklist

• Confirm the selected root and root-independent relative paths.
• Resolve every modified, added, and removed path before accepting a delivery.
• Keep the manifest and comparison report with their timestamps through a trusted channel.
• Use signing and malware or structural validation separately when required.